openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842022-01-27T15:24:56ZopenSUSE Project Management Tool
Redmine openQA Project - coordination #105624 (New): [saga][epic] Reconsider how openQA handles secretshttps://progress.opensuse.org/issues/1056242022-01-27T15:24:56Znicksingernsinger@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>In the ongoing effort to improve our security we introduced things like e.g. <a href="https://github.com/os-autoinst/os-autoinst/pull/1909" class="external">https://github.com/os-autoinst/os-autoinst/pull/1909</a> which is a necessary step to improve how we handle passwords/secrets.<br>
I'd like to see that openQA also supports accessing passwords over different channels which are specifically designed to store secrets.<br>
I know that our public cloud testers already had similar challenges. IIUC they currently use their own setup of "vault" (see 3. in Suggestions). Maybe we could unify this approach and apply it to our whole infrastructure.</p>
<a name="Ideas"></a>
<h2 >Ideas<a href="#Ideas" class="wiki-anchor">¶</a></h2>
<ul>
<li>Support variables with arbitrary commands to access password managers like e.g. keepass (for small, local installations), pass or whatever the user decides to use.</li>
<li>Support GPG encrypted variables (and an according configuration for a private key for openQA)</li>
<li>Support common interfaces for software which is specifically designed for such use-cases. E.g. <a href="https://www.vaultproject.io/" class="external">https://www.vaultproject.io/</a></li>
</ul>
openQA Project - coordination #103950 (New): [saga][epic] Scale up: Efficient handling of large s...https://progress.opensuse.org/issues/1039502021-12-14T10:16:12Zokurzokurz@suse.comopenQA Project - coordination #103944 (New): [saga][epic] Scale up: More robust handling of diver...https://progress.opensuse.org/issues/1039442021-12-14T10:04:26Zokurzokurz@suse.comopenQA Project - coordination #103941 (New): [saga][epic] Scale up: Efficient, event-based handli...https://progress.opensuse.org/issues/1039412021-12-14T09:59:15Zokurzokurz@suse.comopenQA Project - coordination #103938 (New): [saga][epic] Scale up: Efficient handling of large s...https://progress.opensuse.org/issues/1039382021-12-14T09:56:41Zokurzokurz@suse.comopenQA Project - coordination #102915 (New): [saga][epic] Automated classification of failureshttps://progress.opensuse.org/issues/1029152021-11-23T22:12:41Zokurzokurz@suse.com
<a name="User-Story"></a>
<h2 >User Story<a href="#User-Story" class="wiki-anchor">¶</a></h2>
<p>As a reviewer of failed openQA tests I want failures of jobs to be automatically classified for example "test regression", "product regression", "infrastructure issue" to not waste time on bisecting failures</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> If a job fails or incompletes a classification is provided so that at best no further "test review" effort is needed by human reviewers to triage the issue</li>
</ul>
openQA Project - coordination #102906 (New): [saga][epic] Increased stability of tests with less ...https://progress.opensuse.org/issues/1029062021-11-23T21:53:45Zokurzokurz@suse.com
<a name="User-Story"></a>
<h2 >User Story<a href="#User-Story" class="wiki-anchor">¶</a></h2>
<p>As a reviewer of failed openQA tests I want known failures of jobs be handled fully automatically to not waste time on investigating known failures</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> If a job fails for any reason that is "known" already in the context of the current openQA instance no further "test review" effort is needed by human reviewers</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
<p>Definitions:</p>
<ul>
<li>"known" means that a certain symptom of a test failure has been described with e.g. a matching pattern in either a test distribution, os-autoinst or also openQA itself</li>
<li>"test review" means what we currently do in openSUSE or SLE by providing job labels with issue references in openQA comments which are carried over or automatically labeled</li>
</ul>
openQA Project - coordination #102861 (New): [saga][epic] Improved openQA for multi-user environm...https://progress.opensuse.org/issues/1028612021-11-23T08:38:54Zokurzokurz@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>When multiple and many users use an openQA instance it's often helpful to learn about what others are doing, what can be expected, e.g. when jobs can be expected to start, where to contribute to with test result reviewing, find administration errors, configuration overlap and conflicts.</p>
<a name="Ideas"></a>
<h2 >Ideas<a href="#Ideas" class="wiki-anchor">¶</a></h2>
<ul>
<li>Inform openQA webUI users about potential worker class mismatch or long delays</li>
<li>Guide users from index page onto hot spots, where to start reviewing</li>
</ul>
QA - coordination #99303 (New): [saga][epic] Future improvements for SUSE Maintenance QA workflow...https://progress.opensuse.org/issues/993032021-09-26T08:24:33Zokurzokurz@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>Scale up the business while ensuring highest quality with automated testing, approval and release of package updates for SLE and openSUSE</p>
openQA Project - coordination #92323 (New): [saga][epic] Scale up: Fine-grained control over use ...https://progress.opensuse.org/issues/923232021-05-07T15:35:37Zokurzokurz@suse.com
<a name="Ideas"></a>
<h2 >Ideas<a href="#Ideas" class="wiki-anchor">¶</a></h2>
<ul>
<li>Have a configurable list of file type/name/pattern with retention period or size quota for each file type/name/pattern</li>
<li>Allow to configure retention period for the video individually <a class="issue tracker-4 status-1 priority-3 priority-lowest child" title="action: Allow to configure retention period for the video individually (New)" href="https://progress.opensuse.org/issues/67087">#67087</a></li>
<li>Something better than single fixed, unflexible volumes. E.g. dm-cache, lvmcache, bcache, SUSE enterprise storage. Maybe also splitting stored results in openQA by "recent, active" and "old, archived" and then put both categories in different folders which can be mounted from different storage locations, e.g. fast, expensive for "recent, active" and slow, cheap, big for "old, archived"</li>
<li>try out tuned ext4 for worker pool fs to use a more modern default base fs than ext2 even though internally it's the same new code but we might benefit still, e.g. from faster fs formatting times. <a class="issue tracker-6 status-3 priority-4 priority-default closed parent" title="coordination: [saga][epic] Scale up: Efficient handling of large storage to be able to run current tests effici... (Resolved)" href="https://progress.opensuse.org/issues/64746#note-2">#64746#note-2</a></li>
</ul>
openQA Tests - coordination #50507 (New): [qe-core][functional][saga] document lib/ functionshttps://progress.opensuse.org/issues/505072019-04-17T09:17:05Zjorauchjrauch@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>As we currently have no documentation for the functions in lib/ we need a mechanism to automatically generate it from POD inside the files.</p>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
<p>The team decided to apply the best practices described in <a href="https://www.perl.com/pub/2005/07/14/bestpractices.html/" class="external">https://www.perl.com/pub/2005/07/14/bestpractices.html/</a></p>
openQA Tests - coordination #42464 (New): [qe-core][functional][saga] remote system management: s...https://progress.opensuse.org/issues/424642018-10-14T15:10:09Zokurzokurz@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>Ensure the whole SLE ecosystem works together smoothly, e.g. a SLES server can be properly administered using salt, SLE+suma can be integrated, SLE+storage can be integrated, etc.</p>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
<p>This is a long term goal and involves multiple teams.</p>
openQA Tests - coordination #37339 (New): [qe-core][functional][saga][ipmi] Stable testing on IPM...https://progress.opensuse.org/issues/373392018-06-14T05:05:57Zokurzokurz@suse.com
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> Our tests on IPMI backend are seen as stable</li>
<li><strong>AC2:</strong> Tests include x11 tests, e.g. over VNC</li>
</ul>
openQA Tests - coordination #33859 (New): [qe-core][sles][functional][saga][s390x] Review s390x B...https://progress.opensuse.org/issues/338592018-03-27T13:35:25Zmgriessmeiermgriessmeier@suse.com
<a name="User-Story"></a>
<h2 >User Story<a href="#User-Story" class="wiki-anchor">¶</a></h2>
<p>In late february coolo and me were visiting the IBM Regression Testing team in Böblingen to talk about test coverage and unification of our testcase into openQA.<br>
There were two main topics in this meeting. One was about how we can integrate the automated testcases conducted by IBM into openQA (this discussion is still ongoing).</p>
<p>The second, more relevant topic atm, was to talk about Bugs in SLE* which were found by IBM and to see which of the executed scenarios are covered on our side and which are not. It turned out that we lack a lot of test-scenarios and therefore missed some bugs in the product</p>
<p>This ticket is about to collect all those bugs and act on them by creating subtasks for implementing those scenarios step-by-step</p>
<a name="Further-information"></a>
<h2 >Further information<a href="#Further-information" class="wiki-anchor">¶</a></h2>
<p>using tags to define those further:</p>
<ul>
<li>[INFRA] - needs to be clarified with Ihno or Gerhard, e.g. Hardware component/setup on system level is missing, blocks other tags</li>
<li>[YAST] - Affecting a YaST module, extending YaST module tests for s390x</li>
<li>[MANUAL] - Can be verified manually in first place</li>
<li>[AUTOMATE] - eligible for being automated in the future</li>
<li>[FIXED] - bug is verified fixed </li>
</ul>
<a name="Network"></a>
<h3 >Network<a href="#Network" class="wiki-anchor">¶</a></h3>
<ul>
<li>[INFRA] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1084096" class="external">Network is not configured during installation when performing a zPXE installation</a> - (sles15 beta7)</li>
<li>[INFRA] <a href="https://bugzilla.suse.com/show_bug.cgi?id=706967" class="external">IPV6 default gateway not set by installer</a> - (sles11.2)</li>
<li>[INFRA][MANUAL][AUTOMATE][YAST] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1071287" class="external">Vlan package missing</a> - (sles15 beta1)</li>
<li>[INFRA] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1002974" class="external">Not possible to install w/o network on s390x, making use of SLES installation process with DVD from HMC drive.</a> - (sles12.2)</li>
<li>[INFRA] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1083158" class="external">Network not starting correctly when installing using a PCI network device</a> - (sles15 beta7)</li>
<li>[INFRA] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1069295" class="external">Problems installing SLES 15 using VLAN and a custom MAC address</a> - (sles15 beta2)</li>
<li>[FIXED] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1067915" class="external">Yast showing error during finalizing when firewall is disabled during installation</a> - (sles15 beta2)</li>
<li>[YAST][MANUAL][AUTOMATE] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1042055" class="external">Error "Augeas parsing/serializing error: Failed to match" displayed during installation step "Saving network configuration" when VLAN is configured</a> - (sles12.3)</li>
<li>[INFRA] <a href="https://bugzilla.suse.com/show_bug.cgi?id=982727" class="external">Installation via HTTPS not possible when using Self-Signed Certifcate</a> - (sles12.2)</li>
<li>[YAST][MANUAL][AUTOMATE] <a href="https://bugzilla.suse.com/show_bug.cgi?id=944349" class="external">autoyast2: yast2-network: Installation using AutoYast fails in second stage</a> - (sles12.1)</li>
<li>[YAST][MANUAL][AUTOMATE] <a href="https://bugzilla.suse.com/show_bug.cgi?id=941948" class="external">Network configuration missing in autoinst.xml</a> - (sles12.1)</li>
<li>[INFRA] <a href="https://bugzilla.suse.com/show_bug.cgi?id=929524" class="external">Possible parameters for network installation using TFTP</a> - (sles11.4)</li>
<li>[FIXED] <a href="https://bugzilla.suse.com/show_bug.cgi?id=927100" class="external">Netmask parameter is not fetched correctly from parmfile (yast)</a> - (sles11.4)</li>
</ul>
<a name="Access-amp-Package"></a>
<h3 >Access & Package*<a href="#Access-amp-Package" class="wiki-anchor">¶</a></h3>
<ul>
<li>[FIXED] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1067007" class="external">Installer does not make use of given password while adding installer repository</a> - (sles15)</li>
<li>[FIXED] <a href="https://bugzilla.suse.com/show_bug.cgi?id=927993" class="external">Installation of SLES11-SP4 on z10 breaks after downloading 3 of 6 installation files</a> - (sles11.4)</li>
<li>[FIXED] <a href="https://bugzilla.suse.com/show_bug.cgi?id=706605" class="external">LPAR installation expects even the default value of device address to be entred manually</a> - (sles11.2)</li>
<li>[YAST][MANUAL][AUTOMATE] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1068326" class="external">Package yast2-cio is missing</a> - (sles15 beta2)</li>
<li>[YAST][MANUAL][AUTOMATE] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1073074" class="external">Package yast2-cio not installed by default on s390x</a> - (sles15 beta4)</li>
</ul>
<a name="System-hangs"></a>
<h3 >System hangs<a href="#System-hangs" class="wiki-anchor">¶</a></h3>
<ul>
<li>[INFRA] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1038255" class="external">Using zpxe.rexx script to perform zPXE installation on zVM results in kernel panic during boot</a> - (sles12.3)</li>
</ul>
<a name="Devices"></a>
<h3 >Devices<a href="#Devices" class="wiki-anchor">¶</a></h3>
<ul>
<li>[MANUAL][AUTOMATE] <a href="https://bugzilla.suse.com/show_bug.cgi?id=943623" class="external">Installation on iSCSI failed</a> - (sles12.1)</li>
<li>[YAST][MANUAL][AUTOMATE] <a href="https://bugzilla.suse.com/show_bug.cgi?id=808695" class="external">DASD selection not updated in Expert partitioning</a> - (sles11.3)</li>
<li>[YAST][MANUAL][AUTOMATE] <a href="https://bugzilla.suse.com/show_bug.cgi?id=815259" class="external">DASD or zfcp/scsi disks are listed for partitioning, even after deselecting DASD or zfcp/scsi disks</a> - (sles11.3)</li>
<li>[INFRA] <a href="https://bugzilla.suse.com/show_bug.cgi?id=584703" class="external">Installation is not happening on FBA emulated SCSI disk</a> - (sles11.2)</li>
<li>[YAST][MANUAL][AUTOMATE] <a href="https://bugzilla.suse.com/show_bug.cgi?id=709138" class="external">Installation fails when two DASDs are used.</a> - (sles11.2)</li>
<li>[YAST][MANUAL][AUTOMATE] <a href="https://bugzilla.suse.com/show_bug.cgi?id=707059" class="external">DASD devices onlined via Yast2 are not persistant across reboot</a> - (sles11.2)</li>
<li>[YAST][MANUAL][AUTOMATE] <a href="https://bugzilla.suse.com/show_bug.cgi?id=706911" class="external">AutoYast installation fails to detect/sense the DASD</a> - (sles11.2)</li>
<li>[MANUAL][AUTOMATE] <a href="https://bugzilla.suse.com/show_bug.cgi?id=708617" class="external">Unable to install SLES on LVM in a z/VM guest</a> - (sles11.2)</li>
<li>[YAST][MANUAL][AUTOMATE] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1070265" class="external">Not possible to format EDEV device (yast)</a> - (sles15 beta3)</li>
<li>[YAST][MANUAL][AUTOMATE] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1009112" class="external">System is falling into maintenance mode when adding a dasd with chccwdef and adding partitions with yast</a> - (sles12.2)</li>
<li>[FIXED] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1081200" class="external">YaST Partitioner no longer offering /boot/zipl as mount point</a> - (sles15 beta6)</li>
<li>[FIXED] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1081194" class="external">YaST does not properly detect that a DASD is not formatted</a> - (sles15 beta6)</li>
<li>[YAST][MANUAL][AUTOMATE] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1081198" class="external">Changing proposed file system defaults fstab mount option to "Device Name" (yast2-storage-ng)</a> - (sles15 beta6)</li>
<li>[INFRA] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1070175" class="external">Cannot add a partition to a MDISK</a> - (sles15 beta3)</li>
<li>[INFRA] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1070206" class="external">"No proposal possible" error message when installing on MDISK</a> - (sles15 beta3)</li>
<li>[YAST][MANUAL][AUTOMATE] <a href="https://bugzilla.suse.com/show_bug.cgi?id=982726" class="external">Filesystem and Mount point not reliably selectable in the Yast Expert Partitioner when using yast.ssh</a> - (sles12.2)</li>
<li>[YAST][MANUAL][AUTOMATE] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1076305" class="external">yast: Cannot remove mount point with the partitioner</a> - (sles15 beta4)</li>
<li>[YAST][MANUAL][AUTOMATE] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1020336" class="external">"yast onpanic" dialog does not offer prepared zFCP dump devices</a> - (sles12.3)</li>
<li>[YAST][MANUAL][AUTOMATE] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1081018" class="external">yast2-s390x: internal error when trying to install on multipathed zfcp LUN without swap device</a> - (sles15 beta7)</li>
<li>[MANUAL][AUTOMATE] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1070569" class="external">system installed with default partitioning (btrfs) on zfcp comes up in emergency shell</a> - (sles15 beta3)</li>
<li>[INFRA] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1068389" class="external">Yast does not enable non-NPIV zfcp device when "Get WWPNs" is pressed for the first time (yast2-s390)</a> - (sles15 beta2)</li>
<li>[INFRA] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1068260" class="external">yast2-s390: Yast shows "Unkown Error 10" when activating SCSI LUNs on NPIV-enabled zfcp device</a> - (sles15 beta2)</li>
<li>[FIXED] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1067265" class="external">YaST detects a formatted DASD as unformatted</a> - (sles15 beta1)</li>
<li>[FIXED] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1063393" class="external">YaST reports "Error Disks formatting failed. Exit code: 255" after formatting DASD</a> - (sles15 beta1)</li>
<li>[INFRA] <a href="https://bugzilla.suse.com/show_bug.cgi?id=935127" class="external">SLES 12 as a guest can not be installed on a CDL formated ECKD disk</a> - (sles12.2)</li>
<li>[YAST][MANUAL][AUTOMATE] <a href="https://bugzilla.suse.com/show_bug.cgi?id=993382" class="external">iSCSI volume not activated after installation</a> - (sles12.2)</li>
<li>[YAST][MANUAL][AUTOMATE] <a href="https://bugzilla.suse.com/show_bug.cgi?id=926706" class="external">yast2 refuses to use a non-standard iqn as iSCSI initiator</a> - (sles11.4)</li>
<li>[FIXED] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1084503" class="external">YaST does not offer to format an unformatted DASD</a> - (sles15 beta7)</li>
</ul>
<a name="Others"></a>
<h3 >Others<a href="#Others" class="wiki-anchor">¶</a></h3>
<ul>
<li>[YAST][MANUAL][AUTOMATE] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1081783" class="external">Time zone settings from installation dialog are ignored (yast?)</a> - (sles15 beta7)</li>
<li>[YAST][MANUAL][AUTOMATE] <a href="https://bugzilla.suse.com/show_bug.cgi?id=1040944" class="external">Exiting the "yast dump" dialog always displays an error (yast2-s390)</a> - (sles12.3)</li>
</ul>
openQA Project - coordination #12134 (New): [saga] better marketing for openQAhttps://progress.opensuse.org/issues/121342016-05-26T06:42:12Zokurzokurz@suse.com
<p>Potential improvement points:</p>
<ul>
<li>add wikipedia page describing openQA</li>
<li>someone could write a recent blog article</li>
<li>keep track of reference sources describing / tracking openQA, e.g. wikipedia list</li>
<li>better use of the twitter account (@openQAhq)</li>
<li>Gerald from SUSE suggested: Market SUSE QE Tools Workshop more, connect to general SUSE YouTube channel, talk to TAMs to invite partners</li>
</ul>
<a name="wikipedia"></a>
<h2 >wikipedia<a href="#wikipedia" class="wiki-anchor">¶</a></h2>
<p><a href="https://en.wikipedia.org/wiki/List_of_GUI_testing_tools">https://en.wikipedia.org/wiki/List_of_GUI_testing_tools</a> listed openQA but <br>
unfortunately no separate wikipedia article for openQA which it IMHO deserves. <br>
openQA was actually listed as "discontinued" since an anonymous edit from <br>
2016-02 which I corrected to being active citing the page <a href="http://os-autoinst.github.io/openQA/">http://os-autoinst.github.io/openQA/</a>. Maybe the broken OBS link as reported in <a class="issue tracker-4 status-3 priority-3 priority-lowest closed" title="action: broken link: http://os-autoinst.github.io/openQA/downloads/ (Resolved)" href="https://progress.opensuse.org/issues/9436">#9436</a> was <br>
making the wikipedia change author to think it is not active which would be <br>
sad and probably something we want to avoid in the future.<br>
I corrected this but the entry was deleted as visible in <a href="https://en.wikipedia.org/w/index.php?title=List_of_GUI_testing_tools&diff=prev&oldid=709701233">https://en.wikipedia.org/w/index.php?title=List_of_GUI_testing_tools&diff=prev&oldid=709701233</a> as it was stated that there is no article describing openQA.</p>
<p>But there was a page "OpenQA" which unfortunately got deleted as well:<br>
<a href="https://en.wikipedia.org/w/index.php?title=Special%3ALog&type=delete&user=&page=OpenQA&year=&month=-1&tagfilter=&subtype=">https://en.wikipedia.org/w/index.php?title=Special%3ALog&type=delete&user=&page=OpenQA&year=&month=-1&tagfilter=&subtype=</a><br>
Reasons stated are:</p>
<pre><code>20:40, 3 May 2016 BethNaught (talk | contribs) deleted page OpenQA (G12: Unambiguous copyright infringement of https://github.com/os-autoinst/openQA/blob/master/docs/GettingStarted.asciidoc; not GPL is CC BY-SA compatible)
03:09, 26 March 2016 Diannaa (talk | contribs) deleted page OpenQA (G12: Unambiguous copyright infringement of http://os-autoinst.github.io/openQA/, https://progress.opensuse.org/projects/openqa-improvement/wiki, http://os-autoinst.github.io/openQA/downloads/)
</code></pre>
<p>Does anyone know who might have created that wikipedia article and what we can do to come up with a safe version of it?</p>
<p>Would it help to dual-license some content, e.g. our README under CC-BY-SA or something?</p>