* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/qa/bug-wranglers: index.xml
@ 2008-07-05 3:40 Mark Loeser (halcy0n)
0 siblings, 0 replies; 33+ messages in thread
From: Mark Loeser (halcy0n) @ 2008-07-05 3:40 UTC (permalink / raw
To: gentoo-commits
halcy0n 08/07/05 03:40:08
Added: index.xml
Log:
Move the bug-wranglers project under QA
Revision Changes Path
1.1 xml/htdocs/proj/en/qa/bug-wranglers/index.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.1&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.1&content-type=text/plain
Index: index.xml
===================================================================
<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/xsl/project.xsl" type="text/xsl"?>
<?xml-stylesheet href="/xsl/guide.xsl" type="text/xsl"?>
<!DOCTYPE project SYSTEM "/dtd/project.dtd">
<project>
<name>Bug Wranglers</name>
<longname>The Bug Wranglers Project</longname>
<date>2008-05-21</date>
<author title="Author">
<mail link="jer" />
</author>
<description>
The Gentoo Bug Wranglers project controls, describes the tasks and goals
carried out by everyone who wrangles bugs on Gentoo's bug tracker.
</description>
<longdescription>
<p>
The Gentoo Bug Wranglers project controls, describes the tasks and goals
carried out by everyone who wrangles bugs on Gentoo's bug tracker.
</p>
</longdescription>
<goals>
<p>
The goal of the Bug Wranglers project is to clarify how new bugs on
Gentoo's bug tracker should be handled. This document describes the rules to
bug assignment, CC'ing herd teams, maintainers, the role of metadata.xml and
herds.xml, who are bug wranglers and how one should contact them.
</p>
</goals>
<dev role="Bug wrangler">carlo</dev>
<dev role="Bug wrangler">jakub</dev>
<dev role="Bug wrangler">jer</dev>
<dev role="Bug wrangler">jkt</dev>
<extrachapter>
<title>Bug Wrangling</title>
<section>
<title>Checking Bug Reports</title>
<body>
<p>
How and when you assign a bug report depends on the type of bug report and the
correctness and completeness of the bug report.
</p>
<ul>
<li>Bug reports requesting <b>version bumps</b> may be be assigned to
the appropriate maintainers directly. It can be a good idea to check the
Description of the bug for references to security bugs, in which case the bug
report should be assigned to <mail
link="security@gentoo.org">security@gentoo.org</mail> immediately, with the
maintainers CC'd.</li>
<li>Bug reports that say something isn't working or compiling <b>without a
comprehensive analysis of the causes</b>, should contain at least the output of
`emerge --info' as well as a thorough description of the problem, including
error output (or expected versus actual output), the command that led to the
error or faulty output, and concise steps explaining how to reproduce the
issue. It is customary to only assign a bug report once these requirements have
been fulfilled.</li>
<li>Bug reports that <b>include patches</b> or other solutions accompanying the actual bug description can usually be assigned directly to the maintainers.</li>
</ul>
</body>
</section>
<!--
<section>
<title>Assigning Bug Reports</title>
<body>
</body>
</section>
-->
</extrachapter>
<extrachapter>
<title>Participating</title>
<section>
<body>
<p>All Gentoo developers who can change the Assignee fields of new bugs, are
welcome to help assign bugs to the right developers. Most developers will
appreciate it if, while doing so, you follow the rules layed out above.</p>
</body>
</section>
</extrachapter>
<extrachapter position="bottom">
<title>How to contact us</title>
<section>
<title>Via e-mail</title>
<body>
<p>
There is currently no single contact. Please refer to the developer list above.
</p>
</body>
</section>
</extrachapter>
</project>
--
gentoo-commits@lists.gentoo.org mailing list
^ permalink raw reply [flat|nested] 33+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/qa/bug-wranglers: index.xml
@ 2008-07-05 7:40 Christian Faulhammer (opfer)
0 siblings, 0 replies; 33+ messages in thread
From: Christian Faulhammer (opfer) @ 2008-07-05 7:40 UTC (permalink / raw
To: gentoo-commits
opfer 08/07/05 07:40:04
Modified: index.xml
Log:
Add a link to bugs.g.o and add a paragraph about package atom
Revision Changes Path
1.2 xml/htdocs/proj/en/qa/bug-wranglers/index.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.2&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.2&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?r1=1.1&r2=1.2
Index: index.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- index.xml 5 Jul 2008 03:40:07 -0000 1.1
+++ index.xml 5 Jul 2008 07:40:04 -0000 1.2
@@ -18,8 +18,9 @@
<longdescription>
<p>
-The Gentoo Bug Wranglers project controls, describes the tasks and goals
-carried out by everyone who wrangles bugs on Gentoo's bug tracker.
+The Gentoo Bug Wranglers project controls, describes the tasks and
+goals carried out by everyone who wrangles bugs on Gentoo's <uri
+link="http://bugs.gentoo.org/">bug tracker</uri>.
</p>
</longdescription>
@@ -62,6 +63,7 @@
issue. It is customary to only assign a bug report once these requirements have
been fulfilled.</li>
<li>Bug reports that <b>include patches</b> or other solutions accompanying the actual bug description can usually be assigned directly to the maintainers.</li>
+<li>Make sure that a full package atom is found in the summary to make search easier.</li>
</ul>
</body>
</section>
--
gentoo-commits@lists.gentoo.org mailing list
^ permalink raw reply [flat|nested] 33+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/qa/bug-wranglers: index.xml
@ 2008-07-14 19:30 Jeroen Roovers (jer)
0 siblings, 0 replies; 33+ messages in thread
From: Jeroen Roovers (jer) @ 2008-07-14 19:30 UTC (permalink / raw
To: gentoo-commits
jer 08/07/14 19:30:48
Modified: index.xml
Log:
Add further descriptions of how to check and improve bug reports.
Revision Changes Path
1.3 xml/htdocs/proj/en/qa/bug-wranglers/index.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.3&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.3&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?r1=1.2&r2=1.3
Index: index.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- index.xml 5 Jul 2008 07:40:04 -0000 1.2
+++ index.xml 14 Jul 2008 19:30:48 -0000 1.3
@@ -6,7 +6,7 @@
<project>
<name>Bug Wranglers</name>
<longname>The Bug Wranglers Project</longname>
-<date>2008-05-21</date>
+<date>2008-07-14</date>
<author title="Author">
<mail link="jer" />
</author>
@@ -42,7 +42,7 @@
<title>Bug Wrangling</title>
<section>
-<title>Checking Bug Reports</title>
+<title>Checking and Improving Bug Reports</title>
<body>
<p>
How and when you assign a bug report depends on the type of bug report and the
@@ -61,9 +61,18 @@
error output (or expected versus actual output), the command that led to the
error or faulty output, and concise steps explaining how to reproduce the
issue. It is customary to only assign a bug report once these requirements have
-been fulfilled.</li>
+been fulfilled. If the reporter hasn't fulfilled these requirements, the bug
+should be ASSIGNED to bug-wranglers, and a full build log should be requested
+from the reporter.</li>
<li>Bug reports that <b>include patches</b> or other solutions accompanying the actual bug description can usually be assigned directly to the maintainers.</li>
-<li>Make sure that a full package atom is found in the summary to make search easier.</li>
+<li>The Bug Summary uniquely identifies the bug that is being reported. As
+there could be several bugs saying that cat/pkg "failed to emerge", it is
+important to at least replace such generic descriptions of an emerge failing
+with a more exact description, noting the ebuild phase that failed or, better
+yet, the first error message that occured.</li>
+<li>Bug reports that refer to a single or a few (similar) packages should
+detail the package atom as completely as possible in the Summary. Bug reports
+about eclasses should list the full eclass filename.</li>
</ul>
</body>
</section>
--
gentoo-commits@lists.gentoo.org mailing list
^ permalink raw reply [flat|nested] 33+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/qa/bug-wranglers: index.xml
@ 2008-07-23 16:18 Jeroen Roovers (jer)
0 siblings, 0 replies; 33+ messages in thread
From: Jeroen Roovers (jer) @ 2008-07-23 16:18 UTC (permalink / raw
To: gentoo-commits
jer 08/07/23 16:18:51
Modified: index.xml
Log:
Add more policy. Add links, add formatting, finally add assignment policy (thanks to darkside for the poke on IRC).
Revision Changes Path
1.4 xml/htdocs/proj/en/qa/bug-wranglers/index.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.4&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.4&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?r1=1.3&r2=1.4
Index: index.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- index.xml 14 Jul 2008 19:30:48 -0000 1.3
+++ index.xml 23 Jul 2008 16:18:50 -0000 1.4
@@ -29,7 +29,8 @@
The goal of the Bug Wranglers project is to clarify how new bugs on
Gentoo's bug tracker should be handled. This document describes the rules to
bug assignment, CC'ing herd teams, maintainers, the role of metadata.xml and
-herds.xml, who are bug wranglers and how one should contact them.
+<uri link="/proj/en/metastructure/herds/herds.xml">herds.xml</uri>,
+who are bug wranglers and how one should contact them.
</p>
</goals>
@@ -42,7 +43,7 @@
<title>Bug Wrangling</title>
<section>
-<title>Checking and Improving Bug Reports</title>
+<title>Assessing Bug Reports</title>
<body>
<p>
How and when you assign a bug report depends on the type of bug report and the
@@ -65,25 +66,66 @@
should be ASSIGNED to bug-wranglers, and a full build log should be requested
from the reporter.</li>
<li>Bug reports that <b>include patches</b> or other solutions accompanying the actual bug description can usually be assigned directly to the maintainers.</li>
-<li>The Bug Summary uniquely identifies the bug that is being reported. As
+<li>The <c>Summary</c> uniquely identifies the bug that is being reported. As
there could be several bugs saying that cat/pkg "failed to emerge", it is
important to at least replace such generic descriptions of an emerge failing
with a more exact description, noting the ebuild phase that failed or, better
yet, the first error message that occured.</li>
<li>Bug reports that refer to a single or a few (similar) packages should
-detail the package atom as completely as possible in the Summary. Bug reports
+detail the package atom as completely as possible in the <c>Summary</c>. Bug reports
about eclasses should list the full eclass filename.</li>
</ul>
</body>
</section>
-<!--
<section>
<title>Assigning Bug Reports</title>
<body>
+<p>
+To assign a bug report to the right people, you will need to find some more
+information, depending on the type of bug report.
+</p>
+<ul>
+<li>If a bug report pertains to a specific <b>package</b>, then you enter the
+package's directory in your copy of the <uri
+link="http://sources.gentoo.org/viewcvs.py/gentoo-x86/">gentoo-x86 CVS
+repository</uri> (or perhaps the online version which should always be more or
+less up to date) and read the <c>metadata.xml</c> file you find there. When
+<c>metadata.xml</c> lists a single maintainer or herd, then you assign the bug
+to that maintainer or herd. When the file lists multiple entries, then you
+assign the bug to the first maintainer, and CC the other maintainer(s) and
+herd(s).</li>
+<li>In cases where <c>metadata.xml</c> lists a herd which Gentoo Bugzilla
+doesn't know about (which it will ask you to correct before it accepts changes
+to the bug report), you should consult <uri
+link="/proj/en/metastructure/herds/herds.xml">herds.xml</uri> to figure out the
+appropriate e-mail alias for that herd.</li>
+<li>When a bug report calls attention to <b>multiple packages</b>, then things
+become slightly more complicated. When the listed packages do not belong to the
+same maintainer or team, for instance when a library upgrade causes several
+packages to fail to emerge or run, then you should ask the bug reporter to file
+separate bugs assigned to each set of packages' maintainer(s), and make those
+bug reports block the original bug report, which then becomes a <b>tracker
+bug</b> (denoted by the <c>Tracker</c> keyword. Bug reports with many
+maintainers CC'd are known to bog down and never get resolved. Of course, you
+should only create a tracker bug when the bug is confirmed and the solution is
+clear.</li>
+<li>Bug reports that concern <b>eclasses</b> should be assigned to the eclass
+maintainer. To figure out who maintains an eclass, browse to the
+<uri link="http://sources.gentoo.org/viewcvs.py/gentoo-x86/eclass">gentoo-x86/eclass</uri> directory, open the file and read who maintains the eclass at the top
+of the file.</li>
+<li>A <b>keyword request</b> should be assigned to the package's maintainer and CC'd
+to the appropriate arch team(s).</li>
+<li>A <b>stabilisation request</b> should be handled by the package's maintainer, so
+you should not CC arches in your role as bug wrangler.</li>
+<li>Bug reports that relate to issues other than the portage tree, like
+problems with Gentoo's bugzilla, Gentoo infrastructure, mirrors or staffing
+matters (devrel, userrel and so on) are usually easier to assign. The <c>Product</c>
+and <c>Component</c> fields of each bug should help you (re)assign these reports
+appropriately.</li>
+</ul>
</body>
</section>
--->
</extrachapter>
@@ -91,9 +133,11 @@
<title>Participating</title>
<section>
<body>
-<p>All Gentoo developers who can change the Assignee fields of new bugs, are
+<p>
+Any Gentoo developers who can change the <c>Assignee</c> fields of new bugs are
welcome to help assign bugs to the right developers. Most developers will
-appreciate it if, while doing so, you follow the rules layed out above.</p>
+appreciate it if, while doing so, you follow the rules layed out above.
+</p>
</body>
</section>
</extrachapter>
^ permalink raw reply [flat|nested] 33+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/qa/bug-wranglers: index.xml
@ 2008-07-23 16:19 Jeroen Roovers (jer)
0 siblings, 0 replies; 33+ messages in thread
From: Jeroen Roovers (jer) @ 2008-07-23 16:19 UTC (permalink / raw
To: gentoo-commits
jer 08/07/23 16:19:48
Modified: index.xml
Log:
Date change.
Revision Changes Path
1.5 xml/htdocs/proj/en/qa/bug-wranglers/index.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.5&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.5&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?r1=1.4&r2=1.5
Index: index.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- index.xml 23 Jul 2008 16:18:50 -0000 1.4
+++ index.xml 23 Jul 2008 16:19:48 -0000 1.5
@@ -6,7 +6,7 @@
<project>
<name>Bug Wranglers</name>
<longname>The Bug Wranglers Project</longname>
-<date>2008-07-14</date>
+<date>2008-07-23</date>
<author title="Author">
<mail link="jer" />
</author>
^ permalink raw reply [flat|nested] 33+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/qa/bug-wranglers: index.xml
@ 2008-08-21 0:51 Mark Loeser (halcy0n)
0 siblings, 0 replies; 33+ messages in thread
From: Mark Loeser (halcy0n) @ 2008-08-21 0:51 UTC (permalink / raw
To: gentoo-commits
halcy0n 08/08/21 00:51:05
Modified: index.xml
Log:
Some minor language clean up and a few more details added (like where to find us on IRC)
Revision Changes Path
1.6 xml/htdocs/proj/en/qa/bug-wranglers/index.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.6&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.6&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?r1=1.5&r2=1.6
Index: index.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- index.xml 23 Jul 2008 16:19:48 -0000 1.5
+++ index.xml 21 Aug 2008 00:51:05 -0000 1.6
@@ -46,16 +46,15 @@
<title>Assessing Bug Reports</title>
<body>
<p>
-How and when you assign a bug report depends on the type of bug report and the
+How and when you assign a bug report depends on the type of bug report as well as
correctness and completeness of the bug report.
</p>
<ul>
-<li>Bug reports requesting <b>version bumps</b> may be be assigned to
-the appropriate maintainers directly. It can be a good idea to check the
-Description of the bug for references to security bugs, in which case the bug
-report should be assigned to <mail
-link="security@gentoo.org">security@gentoo.org</mail> immediately, with the
-maintainers CC'd.</li>
+<li>Bug reports requesting <b>version bumps</b> should be assigned to
+the appropriate maintainers directly. Also check the description of the
+bug for references to security bugs, in which case the bug report should
+be assigned to <mail link="security@gentoo.org">security@gentoo.org</mail>
+immediately, with the maintainers CC'd.</li>
<li>Bug reports that say something isn't working or compiling <b>without a
comprehensive analysis of the causes</b>, should contain at least the output of
`emerge --info' as well as a thorough description of the problem, including
@@ -65,7 +64,8 @@
been fulfilled. If the reporter hasn't fulfilled these requirements, the bug
should be ASSIGNED to bug-wranglers, and a full build log should be requested
from the reporter.</li>
-<li>Bug reports that <b>include patches</b> or other solutions accompanying the actual bug description can usually be assigned directly to the maintainers.</li>
+<li>Bug reports that <b>include patches</b> or other solutions accompanying
+the actual bug description can usually be assigned directly to the maintainers.</li>
<li>The <c>Summary</c> uniquely identifies the bug that is being reported. As
there could be several bugs saying that cat/pkg "failed to emerge", it is
important to at least replace such generic descriptions of an emerge failing
@@ -74,7 +74,7 @@
<li>Bug reports that refer to a single or a few (similar) packages should
detail the package atom as completely as possible in the <c>Summary</c>. Bug reports
about eclasses should list the full eclass filename.</li>
-</ul>
+</ul>
</body>
</section>
@@ -112,8 +112,8 @@
clear.</li>
<li>Bug reports that concern <b>eclasses</b> should be assigned to the eclass
maintainer. To figure out who maintains an eclass, browse to the
-<uri link="http://sources.gentoo.org/viewcvs.py/gentoo-x86/eclass">gentoo-x86/eclass</uri> directory, open the file and read who maintains the eclass at the top
-of the file.</li>
+<uri link="http://sources.gentoo.org/viewcvs.py/gentoo-x86/eclass">gentoo-x86/eclass</uri>
+directory, open the file and read who maintains the eclass at the top of the file.</li>
<li>A <b>keyword request</b> should be assigned to the package's maintainer and CC'd
to the appropriate arch team(s).</li>
<li>A <b>stabilisation request</b> should be handled by the package's maintainer, so
@@ -138,6 +138,11 @@
welcome to help assign bugs to the right developers. Most developers will
appreciate it if, while doing so, you follow the rules layed out above.
</p>
+<p>
+Users are encouraged to assist in wrangling bugs as well. Even without bugzilla
+privileges you can help by reproducing bugs and posting additional information
+where possible.
+</p>
</body>
</section>
</extrachapter>
@@ -148,7 +153,15 @@
<title>Via e-mail</title>
<body>
<p>
-There is currently no single contact. Please refer to the developer list above.
+There is currently no single contact. Please refer to the developer list above.
+</p>
+</body>
+</section>
+<section>
+<title>Via IRC</title>
+<body>
+<p>
+You can find us on irc.freenode.net at #gentoo-bugs.
</p>
</body>
</section>
^ permalink raw reply [flat|nested] 33+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/qa/bug-wranglers: index.xml
@ 2008-09-02 20:35 Jeroen Roovers (jer)
0 siblings, 0 replies; 33+ messages in thread
From: Jeroen Roovers (jer) @ 2008-09-02 20:35 UTC (permalink / raw
To: gentoo-commits
jer 08/09/02 20:35:45
Modified: index.xml
Log:
Several minor formatting and language improvements. Reduce developer list. Add project goals. Update long description with credit to jakub. Add note about improving metadata.xml.
Revision Changes Path
1.7 xml/htdocs/proj/en/qa/bug-wranglers/index.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.7&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.7&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?r1=1.6&r2=1.7
Index: index.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- index.xml 21 Aug 2008 00:51:05 -0000 1.6
+++ index.xml 2 Sep 2008 20:35:44 -0000 1.7
@@ -6,21 +6,32 @@
<project>
<name>Bug Wranglers</name>
<longname>The Bug Wranglers Project</longname>
-<date>2008-07-23</date>
+<date>2008-09-02</date>
<author title="Author">
<mail link="jer" />
</author>
<description>
-The Gentoo Bug Wranglers project controls, describes the tasks and goals
-carried out by everyone who wrangles bugs on Gentoo's bug tracker.
+The Gentoo Bug Wranglers project controls, describes the tasks to be carried out and
+goals to be achieved for everyone who wrangles bugs on Gentoo's bug tracker.
</description>
<longdescription>
<p>
-The Gentoo Bug Wranglers project controls, describes the tasks and
-goals carried out by everyone who wrangles bugs on Gentoo's <uri
-link="http://bugs.gentoo.org/">bug tracker</uri>.
+The Gentoo Bug Wranglers project controls, describes the tasks to be carried out and
+goals to be achieved for everyone who wrangles bugs on Gentoo's <uri
+link="http://bugs.gentoo.org/">bug tracker</uri>.</p>
+<p>The project was erected after the de facto resignation of long time <e>Main
+Bug Wrangler</e> Jakub Moc, when it turned out we required a division of labour
+to see all bugs reassigned within an acceptable timeframe (from the moment of a
+bug report's creation to its proper assignment). For his years of relentless
+bug wrangling, this project both owes him its gratitude and earns its
+existence.</p>
+<p>In its current phase, the project now strives to get every bug assigned
+within a day, counting from the moment when enough information has been
+gathered. In the future, the project's aims are to credit developers and users
+who help out, to maintain a list of notable bug wranglers, and to gather yet
+more useful guidelines on this page.
</p>
</longdescription>
@@ -34,10 +45,7 @@
</p>
</goals>
-<dev role="Bug wrangler">carlo</dev>
-<dev role="Bug wrangler">jakub</dev>
-<dev role="Bug wrangler">jer</dev>
-<dev role="Bug wrangler">jkt</dev>
+<dev role="Lead">jer</dev>
<extrachapter>
<title>Bug Wrangling</title>
@@ -94,7 +102,9 @@
<c>metadata.xml</c> lists a single maintainer or herd, then you assign the bug
to that maintainer or herd. When the file lists multiple entries, then you
assign the bug to the first maintainer, and CC the other maintainer(s) and
-herd(s).</li>
+herd(s). If you find that <c>metadata.xml</c> lists inappropriate and/or
+confusing contact information, then make a note of that in a comment on the bug
+report and assign/CC the bug report as optimal as possible.</li>
<li>In cases where <c>metadata.xml</c> lists a herd which Gentoo Bugzilla
doesn't know about (which it will ask you to correct before it accepts changes
to the bug report), you should consult <uri
@@ -134,9 +144,9 @@
<section>
<body>
<p>
-Any Gentoo developers who can change the <c>Assignee</c> fields of new bugs are
-welcome to help assign bugs to the right developers. Most developers will
-appreciate it if, while doing so, you follow the rules layed out above.
+All Gentoo developers who can change the <c>Assignee</c> fields of new bugs are
+welcome to help assign bugs to the right developers. Most assignees will
+appreciate it if, in doing so, you follow the rules layed out above.
</p>
<p>
Users are encouraged to assist in wrangling bugs as well. Even without bugzilla
@@ -153,7 +163,7 @@
<title>Via e-mail</title>
<body>
<p>
-There is currently no single contact. Please refer to the developer list above.
+Please refer to the developer list above.
</p>
</body>
</section>
@@ -161,7 +171,7 @@
<title>Via IRC</title>
<body>
<p>
-You can find us on irc.freenode.net at #gentoo-bugs.
+You can find some of us on the Freenode network in <uri link="irc://irc.freenode.net/gentoo-bugs">#gentoo-bugs</uri>.
</p>
</body>
</section>
^ permalink raw reply [flat|nested] 33+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/qa/bug-wranglers: index.xml
@ 2008-09-08 16:24 Jeroen Roovers (jer)
0 siblings, 0 replies; 33+ messages in thread
From: Jeroen Roovers (jer) @ 2008-09-08 16:24 UTC (permalink / raw
To: gentoo-commits
jer 08/09/08 16:24:09
Modified: index.xml
Log:
Clarify KEYWORDREQ. Explain more about eclass bug assignment. Stress atom description in Summary.
Revision Changes Path
1.8 xml/htdocs/proj/en/qa/bug-wranglers/index.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.8&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.8&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?r1=1.7&r2=1.8
Index: index.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- index.xml 2 Sep 2008 20:35:44 -0000 1.7
+++ index.xml 8 Sep 2008 16:24:08 -0000 1.8
@@ -6,7 +6,7 @@
<project>
<name>Bug Wranglers</name>
<longname>The Bug Wranglers Project</longname>
-<date>2008-09-02</date>
+<date>2008-09-08</date>
<author title="Author">
<mail link="jer" />
</author>
@@ -80,8 +80,11 @@
with a more exact description, noting the ebuild phase that failed or, better
yet, the first error message that occured.</li>
<li>Bug reports that refer to a single or a few (similar) packages should
-detail the package atom as completely as possible in the <c>Summary</c>. Bug reports
-about eclasses should list the full eclass filename.</li>
+detail the <b>package atom(s)</b> as completely as possible in the
+<c>Summary</c>, including a version only when other versions do not exhibit the
+bug.</li>
+<li>Bug reports about <b>eclasses</b> should list the full eclass filename in the
+<c>Summary</c>.</li>
</ul>
</body>
</section>
@@ -123,11 +126,16 @@
<li>Bug reports that concern <b>eclasses</b> should be assigned to the eclass
maintainer. To figure out who maintains an eclass, browse to the
<uri link="http://sources.gentoo.org/viewcvs.py/gentoo-x86/eclass">gentoo-x86/eclass</uri>
-directory, open the file and read who maintains the eclass at the top of the file.</li>
-<li>A <b>keyword request</b> should be assigned to the package's maintainer and CC'd
-to the appropriate arch team(s).</li>
+directory, open the file and read who maintains the eclass at the top of the
+file. When an eclass file does not list maintainers, the bug report should
+note this omission and the last committer to that file should be made the
+report's assignee.</li>
+<li>A <b>keyword request</b> should be assigned to the package's maintainer and
+CC'd to the appropriate arch team(s). The report's <c>Keywords</c> field should
+contain the <c>KEYWORDREQ</c> keyword.</li>
<li>A <b>stabilisation request</b> should be handled by the package's maintainer, so
-you should not CC arches in your role as bug wrangler.</li>
+you should not CC arch teams in your role as bug wrangler, nor set the
+<c>STABLEREQ</c> keyword in the <c>Keywords</c> field.</li>
<li>Bug reports that relate to issues other than the portage tree, like
problems with Gentoo's bugzilla, Gentoo infrastructure, mirrors or staffing
matters (devrel, userrel and so on) are usually easier to assign. The <c>Product</c>
^ permalink raw reply [flat|nested] 33+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/qa/bug-wranglers: index.xml
@ 2008-09-10 5:07 Jeroen Roovers (jer)
0 siblings, 0 replies; 33+ messages in thread
From: Jeroen Roovers (jer) @ 2008-09-10 5:07 UTC (permalink / raw
To: gentoo-commits
jer 08/09/10 05:07:46
Modified: index.xml
Log:
Add acquisition section. Improvements here and there.
Revision Changes Path
1.9 xml/htdocs/proj/en/qa/bug-wranglers/index.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.9&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.9&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?r1=1.8&r2=1.9
Index: index.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- index.xml 8 Sep 2008 16:24:08 -0000 1.8
+++ index.xml 10 Sep 2008 05:07:46 -0000 1.9
@@ -6,7 +6,7 @@
<project>
<name>Bug Wranglers</name>
<longname>The Bug Wranglers Project</longname>
-<date>2008-09-08</date>
+<date>2008-09-10</date>
<author title="Author">
<mail link="jer" />
</author>
@@ -70,8 +70,8 @@
error or faulty output, and concise steps explaining how to reproduce the
issue. It is customary to only assign a bug report once these requirements have
been fulfilled. If the reporter hasn't fulfilled these requirements, the bug
-should be ASSIGNED to bug-wranglers, and a full build log should be requested
-from the reporter.</li>
+should be marked <c>ASSIGNED</c> to bug-wranglers, and a full build log should
+be requested from the reporter.</li>
<li>Bug reports that <b>include patches</b> or other solutions accompanying
the actual bug description can usually be assigned directly to the maintainers.</li>
<li>The <c>Summary</c> uniquely identifies the bug that is being reported. As
@@ -90,6 +90,50 @@
</section>
<section>
+<title>Acquiring More Information (and when not to)</title>
+<body>
+<p>Bug reports can quickly get messy from comments and attachments that may or
+may not be appropriate to the bug being reported. Handing over such bug reports
+to the proper assignees is not much fun, and you cannot delete comments or
+attachments that aren't any use (although you can mark the latter as obsolete
+if need be). Since you cannot filter out the information you ultimately hand
+over to the assignee, you will have to make sure you don't just ask for the
+right information, but ask it in the best possible way. Sometimes, it is
+necessary to request that no more information is added. In general, be gentle
+in your verbal assessment of a bug report. Even if you are quite certain that
+it's going to be resolved as <c>INVALID</c>, you should treat the reporter
+<b>courteously</b>.</p>
+<ul>
+<li>If you find that a reported problem arose because <b>the reporter lacks
+certain skills</b> or knowledge, then provide the so-called 'obvious' solution
+to the problem and suggest that he might try that. It is unnecessary to explain
+that you consider the reported problem not to be a bug. Just resolve the bug
+with a <c>TEST-REQUEST</c> (instead of as <c>INVALID</c>) and suggest that the
+reporter tests the solution you provide, and that he reopens the bug only when
+that doesn't solve the problem.</li>
+<li>Assume that the reporter can help but may not know how, without either
+suggesting he may not know how or assuming he does know how. In practice, that
+means you provide the <b>commands that produce the information you require</b>.
+Do so even if the means to that end seem trivial, like asking for `emerge
+--info' or `emerge -vp cat/pkg'.</li>
+<li>Do not assume that the reporter ought to know <b>how to report bugs</b>. An
+omitted `emerge --info' does not call for a public flogging, it simply calls
+for the missing `emerge --info'. Even experienced reporters make mistakes, so
+simply request the information, mark the bug as <c>ASSIGNED</c> and wait for
+the information you requested.</li>
+<li>Bug reports should be concise, as all too quickly they bog down and can
+be best understood after reading, say, nothing but comment #1, #2 and #7,
+ignoring all 40 intermediate and later comments which are the me-toos and
+not-mes (including lots of `emerge --info' and/or hardware collection lists
+that may or may not be relevant). <b>When enough information has been
+presented</b> to 'make a case', it's appropriate to say so.</li>
+<li>Some bugs make your blood boil. Ignore them and let someone else handle
+them.</li>
+</ul>
+</body>
+</section>
+
+<section>
<title>Assigning Bug Reports</title>
<body>
<p>
@@ -103,7 +147,7 @@
repository</uri> (or perhaps the online version which should always be more or
less up to date) and read the <c>metadata.xml</c> file you find there. When
<c>metadata.xml</c> lists a single maintainer or herd, then you assign the bug
-to that maintainer or herd. When the file lists multiple entries, then you
+to that maintainer or herd. When the file lists multiple entries, then you
assign the bug to the first maintainer, and CC the other maintainer(s) and
herd(s). If you find that <c>metadata.xml</c> lists inappropriate and/or
confusing contact information, then make a note of that in a comment on the bug
@@ -127,7 +171,7 @@
maintainer. To figure out who maintains an eclass, browse to the
<uri link="http://sources.gentoo.org/viewcvs.py/gentoo-x86/eclass">gentoo-x86/eclass</uri>
directory, open the file and read who maintains the eclass at the top of the
-file. When an eclass file does not list maintainers, the bug report should
+file. When an eclass file does not list maintainers, the bug report should
note this omission and the last committer to that file should be made the
report's assignee.</li>
<li>A <b>keyword request</b> should be assigned to the package's maintainer and
@@ -157,10 +201,18 @@
appreciate it if, in doing so, you follow the rules layed out above.
</p>
<p>
-Users are encouraged to assist in wrangling bugs as well. Even without bugzilla
+Users are encouraged to assist in wrangling bugs as well. Even without bugzilla
privileges you can help by reproducing bugs and posting additional information
where possible.
</p>
+<p>The best approach to bug wrangling is to really <b>get involved</b> with
+individual bug reports. Do not wrangle bugs if all you want is to shorten the
+list down. Just CC yourself when you are not quite sure you assigned a bug
+report properly or when you requested information. You can always un-CC when
+you find the bug has landed in the right hands.</p>
+<p>The bug wranglers are now many, which means that you don't have to do
+<b>everything</b>. It also means that you can keep check on the bug reports you
+responded to and help guide them to satisfactory solutions.</p>
</body>
</section>
</extrachapter>
^ permalink raw reply [flat|nested] 33+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/qa/bug-wranglers: index.xml
@ 2009-03-27 21:37 Jeroen Roovers (jer)
0 siblings, 0 replies; 33+ messages in thread
From: Jeroen Roovers (jer) @ 2009-03-27 21:37 UTC (permalink / raw
To: gentoo-commits
jer 09/03/27 21:37:58
Modified: index.xml
Log:
Add Polynomial-C as member.
Revision Changes Path
1.10 xml/htdocs/proj/en/qa/bug-wranglers/index.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.10&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.10&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?r1=1.9&r2=1.10
Index: index.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- index.xml 10 Sep 2008 05:07:46 -0000 1.9
+++ index.xml 27 Mar 2009 21:37:58 -0000 1.10
@@ -6,7 +6,7 @@
<project>
<name>Bug Wranglers</name>
<longname>The Bug Wranglers Project</longname>
-<date>2008-09-10</date>
+<date>2009-03-27</date>
<author title="Author">
<mail link="jer" />
</author>
@@ -46,6 +46,7 @@
</goals>
<dev role="Lead">jer</dev>
+<dev role="Member">Polynomial-C</dev>
<extrachapter>
<title>Bug Wrangling</title>
^ permalink raw reply [flat|nested] 33+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/qa/bug-wranglers: index.xml
@ 2009-09-29 20:02 Jeremy Olexa (darkside)
0 siblings, 0 replies; 33+ messages in thread
From: Jeremy Olexa (darkside) @ 2009-09-29 20:02 UTC (permalink / raw
To: gentoo-commits
darkside 09/09/29 20:02:50
Modified: index.xml
Log:
If a stablereq comes in and the package is maintainer-needed, then bug-wranglers should add arches and set the Keyword field. As discussed in #gentoo-bugs
Revision Changes Path
1.11 xml/htdocs/proj/en/qa/bug-wranglers/index.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.11&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.11&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?r1=1.10&r2=1.11
Index: index.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- index.xml 27 Mar 2009 21:37:58 -0000 1.10
+++ index.xml 29 Sep 2009 20:02:49 -0000 1.11
@@ -6,7 +6,7 @@
<project>
<name>Bug Wranglers</name>
<longname>The Bug Wranglers Project</longname>
-<date>2009-03-27</date>
+<date>2009-09-29</date>
<author title="Author">
<mail link="jer" />
</author>
@@ -180,7 +180,9 @@
contain the <c>KEYWORDREQ</c> keyword.</li>
<li>A <b>stabilisation request</b> should be handled by the package's maintainer, so
you should not CC arch teams in your role as bug wrangler, nor set the
-<c>STABLEREQ</c> keyword in the <c>Keywords</c> field.</li>
+<c>STABLEREQ</c> keyword in the <c>Keywords</c> field. Unless the package is
+maintainer-needed, then you should add arches and set the Keyword field if the
+bug makes sense.</li>
<li>Bug reports that relate to issues other than the portage tree, like
problems with Gentoo's bugzilla, Gentoo infrastructure, mirrors or staffing
matters (devrel, userrel and so on) are usually easier to assign. The <c>Product</c>
^ permalink raw reply [flat|nested] 33+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/qa/bug-wranglers: index.xml
@ 2009-10-23 18:31 Jeremy Olexa (darkside)
0 siblings, 0 replies; 33+ messages in thread
From: Jeremy Olexa (darkside) @ 2009-10-23 18:31 UTC (permalink / raw
To: gentoo-commits
darkside 09/10/23 18:31:03
Modified: index.xml
Log:
Update for security related bugs, patch by few in irc
Revision Changes Path
1.12 xml/htdocs/proj/en/qa/bug-wranglers/index.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.12&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.12&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?r1=1.11&r2=1.12
Index: index.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- index.xml 29 Sep 2009 20:02:49 -0000 1.11
+++ index.xml 23 Oct 2009 18:31:03 -0000 1.12
@@ -6,7 +6,7 @@
<project>
<name>Bug Wranglers</name>
<longname>The Bug Wranglers Project</longname>
-<date>2009-09-29</date>
+<date>2009-10-23</date>
<author title="Author">
<mail link="jer" />
</author>
@@ -63,7 +63,8 @@
the appropriate maintainers directly. Also check the description of the
bug for references to security bugs, in which case the bug report should
be assigned to <mail link="security@gentoo.org">security@gentoo.org</mail>
-immediately, with the maintainers CC'd.</li>
+immediately, using product "Gentoo Security" and component "Vulnerabilities",
+with the maintainers CC'd.</li>
<li>Bug reports that say something isn't working or compiling <b>without a
comprehensive analysis of the causes</b>, should contain at least the output of
`emerge --info' as well as a thorough description of the problem, including
^ permalink raw reply [flat|nested] 33+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/qa/bug-wranglers: index.xml
@ 2009-10-28 21:27 Jeremy Olexa (darkside)
0 siblings, 0 replies; 33+ messages in thread
From: Jeremy Olexa (darkside) @ 2009-10-28 21:27 UTC (permalink / raw
To: gentoo-commits
darkside 09/10/28 21:27:30
Modified: index.xml
Log:
Changes to profiles handling and note about overworking. Patch by few in #gentoo-bugs
Revision Changes Path
1.13 xml/htdocs/proj/en/qa/bug-wranglers/index.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.13&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.13&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?r1=1.12&r2=1.13
Index: index.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- index.xml 23 Oct 2009 18:31:03 -0000 1.12
+++ index.xml 28 Oct 2009 21:27:30 -0000 1.13
@@ -6,7 +6,7 @@
<project>
<name>Bug Wranglers</name>
<longname>The Bug Wranglers Project</longname>
-<date>2009-10-23</date>
+<date>2009-10-28</date>
<author title="Author">
<mail link="jer" />
</author>
@@ -184,11 +184,16 @@
<c>STABLEREQ</c> keyword in the <c>Keywords</c> field. Unless the package is
maintainer-needed, then you should add arches and set the Keyword field if the
bug makes sense.</li>
+<li>Bug reports that concern <b>profiles</b> should be assigned to
+<uri link="mailto:qa@gentoo.org">qa@gentoo.org</uri> with
+<uri link="mailto:release@gentoo.org">release@gentoo.org</uri> CC'd. Exceptions
+are profiles that are obviously maintained by some herd, like hardened, selinux,
+prefix, etc. Those get assigned to the maintaining herd.</li>
<li>Bug reports that relate to issues other than the portage tree, like
problems with Gentoo's bugzilla, Gentoo infrastructure, mirrors or staffing
-matters (devrel, userrel and so on) are usually easier to assign. The <c>Product</c>
-and <c>Component</c> fields of each bug should help you (re)assign these reports
-appropriately.</li>
+matters (devrel, userrel and so on) are usually easier to assign. The
+<c>Product</c> and <c>Component</c> fields of each bug should help you
+(re)assign these reports appropriately.</li>
</ul>
</body>
</section>
@@ -214,9 +219,9 @@
list down. Just CC yourself when you are not quite sure you assigned a bug
report properly or when you requested information. You can always un-CC when
you find the bug has landed in the right hands.</p>
-<p>The bug wranglers are now many, which means that you don't have to do
-<b>everything</b>. It also means that you can keep check on the bug reports you
-responded to and help guide them to satisfactory solutions.</p>
+<p>Bug-wrangling is an exhausting job. Don't try to do <b>everything</b>. This
+means that you better keep check on the bug reports you responded to and help
+guide them to satisfactory solutions.</p>
</body>
</section>
</extrachapter>
^ permalink raw reply [flat|nested] 33+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/qa/bug-wranglers: index.xml
@ 2009-11-09 13:41 Markos Chandras (hwoarang)
0 siblings, 0 replies; 33+ messages in thread
From: Markos Chandras (hwoarang) @ 2009-11-09 13:41 UTC (permalink / raw
To: gentoo-commits
hwoarang 09/11/09 13:41:44
Modified: index.xml
Log:
Added my self to project
Revision Changes Path
1.14 xml/htdocs/proj/en/qa/bug-wranglers/index.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.14&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.14&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?r1=1.13&r2=1.14
Index: index.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- index.xml 28 Oct 2009 21:27:30 -0000 1.13
+++ index.xml 9 Nov 2009 13:41:43 -0000 1.14
@@ -47,6 +47,7 @@
<dev role="Lead">jer</dev>
<dev role="Member">Polynomial-C</dev>
+<dev role="Member">hwoarang</dev>
<extrachapter>
<title>Bug Wrangling</title>
^ permalink raw reply [flat|nested] 33+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/qa/bug-wranglers: index.xml
@ 2010-05-26 3:36 Jeroen Roovers (jer)
0 siblings, 0 replies; 33+ messages in thread
From: Jeroen Roovers (jer) @ 2010-05-26 3:36 UTC (permalink / raw
To: gentoo-commits
jer 10/05/26 03:36:17
Modified: index.xml
Log:
Update developer list, date.
Revision Changes Path
1.15 xml/htdocs/proj/en/qa/bug-wranglers/index.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.15&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.15&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?r1=1.14&r2=1.15
Index: index.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- index.xml 9 Nov 2009 13:41:43 -0000 1.14
+++ index.xml 26 May 2010 03:36:17 -0000 1.15
@@ -6,7 +6,7 @@
<project>
<name>Bug Wranglers</name>
<longname>The Bug Wranglers Project</longname>
-<date>2009-10-28</date>
+<date>2010-05-26</date>
<author title="Author">
<mail link="jer" />
</author>
@@ -46,8 +46,11 @@
</goals>
<dev role="Lead">jer</dev>
-<dev role="Member">Polynomial-C</dev>
+<dev role="Member">jlec</dev>
<dev role="Member">hwoarang</dev>
+<dev role="Member">Polynomial-C</dev>
+<dev role="Member">wormo</dev>
+<dev role="Member">ssuominen</dev>
<extrachapter>
<title>Bug Wrangling</title>
^ permalink raw reply [flat|nested] 33+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/qa/bug-wranglers: index.xml
@ 2010-10-03 19:39 Markos Chandras (hwoarang)
0 siblings, 0 replies; 33+ messages in thread
From: Markos Chandras (hwoarang) @ 2010-10-03 19:39 UTC (permalink / raw
To: gentoo-commits
hwoarang 10/10/03 19:39:24
Modified: index.xml
Log:
Remove myself from project
Revision Changes Path
1.16 xml/htdocs/proj/en/qa/bug-wranglers/index.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.16&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.16&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?r1=1.15&r2=1.16
Index: index.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- index.xml 26 May 2010 03:36:17 -0000 1.15
+++ index.xml 3 Oct 2010 19:39:24 -0000 1.16
@@ -47,7 +47,6 @@
<dev role="Lead">jer</dev>
<dev role="Member">jlec</dev>
-<dev role="Member">hwoarang</dev>
<dev role="Member">Polynomial-C</dev>
<dev role="Member">wormo</dev>
<dev role="Member">ssuominen</dev>
^ permalink raw reply [flat|nested] 33+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/qa/bug-wranglers: index.xml
@ 2010-10-26 18:35 Jeroen Roovers (jer)
0 siblings, 0 replies; 33+ messages in thread
From: Jeroen Roovers (jer) @ 2010-10-26 18:35 UTC (permalink / raw
To: gentoo-commits
jer 10/10/26 18:35:46
Modified: index.xml
Log:
Require a full CATEGORY/PKG where applicable.
Revision Changes Path
1.17 xml/htdocs/proj/en/qa/bug-wranglers/index.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.17&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.17&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?r1=1.16&r2=1.17
Index: index.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- index.xml 3 Oct 2010 19:39:24 -0000 1.16
+++ index.xml 26 Oct 2010 18:35:46 -0000 1.17
@@ -85,9 +85,9 @@
with a more exact description, noting the ebuild phase that failed or, better
yet, the first error message that occured.</li>
<li>Bug reports that refer to a single or a few (similar) packages should
-detail the <b>package atom(s)</b> as completely as possible in the
-<c>Summary</c>, including a version only when other versions do not exhibit the
-bug.</li>
+detail the <b>package atom(s)</b> as completely as possible (at least the
+CATEGORY/PKG(s)) in the <c>Summary</c>, including a version only when other
+versions do not exhibit the bug.</li>
<li>Bug reports about <b>eclasses</b> should list the full eclass filename in the
<c>Summary</c>.</li>
</ul>
^ permalink raw reply [flat|nested] 33+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/qa/bug-wranglers: index.xml
@ 2010-10-26 18:46 Jeroen Roovers (jer)
0 siblings, 0 replies; 33+ messages in thread
From: Jeroen Roovers (jer) @ 2010-10-26 18:46 UTC (permalink / raw
To: gentoo-commits
jer 10/10/26 18:46:09
Modified: index.xml
Log:
Clarify note about CATEGORY/PKG some more.
Revision Changes Path
1.18 xml/htdocs/proj/en/qa/bug-wranglers/index.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.18&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.18&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?r1=1.17&r2=1.18
Index: index.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- index.xml 26 Oct 2010 18:35:46 -0000 1.17
+++ index.xml 26 Oct 2010 18:46:09 -0000 1.18
@@ -87,7 +87,9 @@
<li>Bug reports that refer to a single or a few (similar) packages should
detail the <b>package atom(s)</b> as completely as possible (at least the
CATEGORY/PKG(s)) in the <c>Summary</c>, including a version only when other
-versions do not exhibit the bug.</li>
+versions do not exhibit the bug. Also note that CATEGORY/PKG[-VERSION].ebuild
+is never a valid atom - either refer to CATEGORY/PKG/PKG[-VERSION].ebuild or
+simply remove the .ebuild suffix entirely.</li>
<li>Bug reports about <b>eclasses</b> should list the full eclass filename in the
<c>Summary</c>.</li>
</ul>
^ permalink raw reply [flat|nested] 33+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/qa/bug-wranglers: index.xml
@ 2010-11-16 15:10 PaweA Hajdan (phajdan.jr)
0 siblings, 0 replies; 33+ messages in thread
From: PaweA Hajdan (phajdan.jr) @ 2010-11-16 15:10 UTC (permalink / raw
To: gentoo-commits
phajdan.jr 10/11/16 15:10:55
Modified: index.xml
Log:
Add information about bug wranglers to staffing needs page.
Revision Changes Path
1.19 xml/htdocs/proj/en/qa/bug-wranglers/index.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.19&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.19&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?r1=1.18&r2=1.19
Index: index.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- index.xml 26 Oct 2010 18:46:09 -0000 1.18
+++ index.xml 16 Nov 2010 15:10:55 -0000 1.19
@@ -45,6 +45,21 @@
</p>
</goals>
+<recruitment>
+<job>
+<summary>Bug Wrangler</summary>
+<details>
+Gentoo needs more people handling new bugs (i.e. assigning them
+to the right people, making sure the reporter has submitted enough info,
+etc.)
+</details>
+<requirements>
+Good understanding of Gentoo and Bugzilla, always respecting the users.
+</requirements>
+<contact>jer</contact>
+</job>
+</recruitment>
+
<dev role="Lead">jer</dev>
<dev role="Member">jlec</dev>
<dev role="Member">Polynomial-C</dev>
^ permalink raw reply [flat|nested] 33+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/qa/bug-wranglers: index.xml
@ 2011-01-23 18:43 Jeroen Roovers (jer)
0 siblings, 0 replies; 33+ messages in thread
From: Jeroen Roovers (jer) @ 2011-01-23 18:43 UTC (permalink / raw
To: gentoo-commits
jer 11/01/23 18:43:03
Modified: index.xml
Log:
Text formatting. Wording.
Revision Changes Path
1.20 xml/htdocs/proj/en/qa/bug-wranglers/index.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.20&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.20&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?r1=1.19&r2=1.20
Index: index.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- index.xml 16 Nov 2010 15:10:55 -0000 1.19
+++ index.xml 23 Jan 2011 18:43:03 -0000 1.20
@@ -6,7 +6,7 @@
<project>
<name>Bug Wranglers</name>
<longname>The Bug Wranglers Project</longname>
-<date>2010-05-26</date>
+<date>2011-01-23</date>
<author title="Author">
<mail link="jer" />
</author>
@@ -18,20 +18,24 @@
<longdescription>
<p>
-The Gentoo Bug Wranglers project controls, describes the tasks to be carried out and
-goals to be achieved for everyone who wrangles bugs on Gentoo's <uri
-link="http://bugs.gentoo.org/">bug tracker</uri>.</p>
-<p>The project was erected after the de facto resignation of long time <e>Main
+The Gentoo Bug Wranglers project controls and describes the tasks to be carried
+out and goals to be achieved for everyone who wrangles bugs on Gentoo's <uri
+link="http://bugs.gentoo.org/">bug tracker</uri>.
+</p>
+<p>
+The project was set up after the de facto resignation of long time <e>Main
Bug Wrangler</e> Jakub Moc, when it turned out we required a division of labour
-to see all bugs reassigned within an acceptable timeframe (from the moment of a
-bug report's creation to its proper assignment). For his years of relentless
-bug wrangling, this project both owes him its gratitude and earns its
-existence.</p>
-<p>In its current phase, the project now strives to get every bug assigned
-within a day, counting from the moment when enough information has been
-gathered. In the future, the project's aims are to credit developers and users
-who help out, to maintain a list of notable bug wranglers, and to gather yet
-more useful guidelines on this page.
+to get all bugs properly assigned within an acceptable timeframe (from the
+moment of a bug report's creation to its proper assignment). For his years of
+relentless bug wrangling, this project both owes him its gratitude and earns
+its existence.
+</p>
+<p>
+The project strives to get every bug assigned within a day, counting from
+the moment when enough information has been gathered. In the future, the
+project's aims are to credit developers and users who help out, to maintain a
+list of notable bug wranglers, and to gather yet more useful guidelines on this
+page.
</p>
</longdescription>
@@ -163,7 +167,8 @@
information, depending on the type of bug report.
</p>
<ul>
-<li>If a bug report pertains to a specific <b>package</b>, then you enter the
+<li>
+If a bug report pertains to a specific <b>package</b>, then you enter the
package's directory in your copy of the <uri
link="http://sources.gentoo.org/viewcvs.py/gentoo-x86/">gentoo-x86 CVS
repository</uri> (or perhaps the online version which should always be more or
@@ -173,14 +178,18 @@
assign the bug to the first maintainer, and CC the other maintainer(s) and
herd(s). If you find that <c>metadata.xml</c> lists inappropriate and/or
confusing contact information, then make a note of that in a comment on the bug
-report and assign/CC the bug report as optimal as possible.</li>
-<li>In cases where <c>metadata.xml</c> lists a herd which Gentoo Bugzilla
+report and assign/CC the bug report as optimal as possible.
+</li>
+<li>
+In cases where <c>metadata.xml</c> lists a herd which Gentoo Bugzilla
doesn't know about (which it will ask you to correct before it accepts changes
to the bug report), you should consult <uri
link="/proj/en/metastructure/herds/herds.xml">herds.xml</uri> to figure out the
-appropriate e-mail alias for that herd.</li>
-<li>When a bug report calls attention to <b>multiple packages</b>, then things
-become slightly more complicated. When the listed packages do not belong to the
+appropriate e-mail alias for that herd.
+</li>
+<li>
+When a bug report calls attention to <b>multiple packages</b>, then things
+get slightly more complicated. When the listed packages do not belong to the
same maintainer or team, for instance when a library upgrade causes several
packages to fail to emerge or run, then you should ask the bug reporter to file
separate bugs assigned to each set of packages' maintainer(s), and make those
@@ -188,32 +197,43 @@
bug</b> (denoted by the <c>Tracker</c> keyword. Bug reports with many
maintainers CC'd are known to bog down and never get resolved. Of course, you
should only create a tracker bug when the bug is confirmed and the solution is
-clear.</li>
-<li>Bug reports that concern <b>eclasses</b> should be assigned to the eclass
+clear.
+</li>
+<li>
+Bug reports that concern <b>eclasses</b> should be assigned to the eclass
maintainer. To figure out who maintains an eclass, browse to the
<uri link="http://sources.gentoo.org/viewcvs.py/gentoo-x86/eclass">gentoo-x86/eclass</uri>
directory, open the file and read who maintains the eclass at the top of the
file. When an eclass file does not list maintainers, the bug report should
note this omission and the last committer to that file should be made the
-report's assignee.</li>
-<li>A <b>keyword request</b> should be assigned to the package's maintainer and
+report's assignee.
+</li>
+<li>
+A <b>keyword request</b> should be assigned to the package's maintainer and
CC'd to the appropriate arch team(s). The report's <c>Keywords</c> field should
-contain the <c>KEYWORDREQ</c> keyword.</li>
-<li>A <b>stabilisation request</b> should be handled by the package's maintainer, so
+contain the <c>KEYWORDREQ</c> keyword.
+</li>
+<li>
+A <b>stabilisation request</b> should be handled by the package's maintainer, so
you should not CC arch teams in your role as bug wrangler, nor set the
<c>STABLEREQ</c> keyword in the <c>Keywords</c> field. Unless the package is
maintainer-needed, then you should add arches and set the Keyword field if the
-bug makes sense.</li>
-<li>Bug reports that concern <b>profiles</b> should be assigned to
+bug makes sense.
+</li>
+<li>
+Bug reports that concern <b>profiles</b> should be assigned to
<uri link="mailto:qa@gentoo.org">qa@gentoo.org</uri> with
<uri link="mailto:release@gentoo.org">release@gentoo.org</uri> CC'd. Exceptions
are profiles that are obviously maintained by some herd, like hardened, selinux,
-prefix, etc. Those get assigned to the maintaining herd.</li>
-<li>Bug reports that relate to issues other than the portage tree, like
+prefix, etc. Those get assigned to the maintaining herd.
+</li>
+<li>
+Bug reports that relate to issues other than the portage tree, like
problems with Gentoo's bugzilla, Gentoo infrastructure, mirrors or staffing
matters (devrel, userrel and so on) are usually easier to assign. The
<c>Product</c> and <c>Component</c> fields of each bug should help you
-(re)assign these reports appropriately.</li>
+(re)assign these reports appropriately.
+</li>
</ul>
</body>
</section>
^ permalink raw reply [flat|nested] 33+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/qa/bug-wranglers: index.xml
@ 2011-08-03 19:57 Jeroen Roovers (jer)
0 siblings, 0 replies; 33+ messages in thread
From: Jeroen Roovers (jer) @ 2011-08-03 19:57 UTC (permalink / raw
To: gentoo-commits
jer 11/08/03 19:57:00
Modified: index.xml
Log:
Remove ambiguity about metadata.xml listings and how to order them, thanks to _AxS_ and few.
Revision Changes Path
1.21 xml/htdocs/proj/en/qa/bug-wranglers/index.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.21&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.21&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?r1=1.20&r2=1.21
Index: index.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -r1.20 -r1.21
--- index.xml 23 Jan 2011 18:43:03 -0000 1.20
+++ index.xml 3 Aug 2011 19:57:00 -0000 1.21
@@ -175,10 +175,11 @@
less up to date) and read the <c>metadata.xml</c> file you find there. When
<c>metadata.xml</c> lists a single maintainer or herd, then you assign the bug
to that maintainer or herd. When the file lists multiple entries, then you
-assign the bug to the first maintainer, and CC the other maintainer(s) and
-herd(s). If you find that <c>metadata.xml</c> lists inappropriate and/or
-confusing contact information, then make a note of that in a comment on the bug
-report and assign/CC the bug report as optimal as possible.
+assign the bug to the first <maintainer>, and CC the other
+<maintainer>(s) and <herd>(s). If you find that <c>metadata.xml</c>
+lists inappropriate and/or confusing contact information, then make a note of
+that in a comment on the bug report and assign/CC the bug report as best as
+possible.
</li>
<li>
In cases where <c>metadata.xml</c> lists a herd which Gentoo Bugzilla
^ permalink raw reply [flat|nested] 33+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/qa/bug-wranglers: index.xml
@ 2011-08-03 19:57 Jeroen Roovers (jer)
0 siblings, 0 replies; 33+ messages in thread
From: Jeroen Roovers (jer) @ 2011-08-03 19:57 UTC (permalink / raw
To: gentoo-commits
jer 11/08/03 19:57:40
Modified: index.xml
Log:
Update date.
Revision Changes Path
1.22 xml/htdocs/proj/en/qa/bug-wranglers/index.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.22&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.22&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?r1=1.21&r2=1.22
Index: index.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- index.xml 3 Aug 2011 19:57:00 -0000 1.21
+++ index.xml 3 Aug 2011 19:57:39 -0000 1.22
@@ -6,7 +6,7 @@
<project>
<name>Bug Wranglers</name>
<longname>The Bug Wranglers Project</longname>
-<date>2011-01-23</date>
+<date>2011-08-03</date>
<author title="Author">
<mail link="jer" />
</author>
^ permalink raw reply [flat|nested] 33+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/qa/bug-wranglers: index.xml
@ 2011-09-09 6:20 Justin Lecher (jlec)
0 siblings, 0 replies; 33+ messages in thread
From: Justin Lecher (jlec) @ 2011-09-09 6:20 UTC (permalink / raw
To: gentoo-commits
jlec 11/09/09 06:20:41
Modified: index.xml
Log:
Removed myself from the project
Revision Changes Path
1.23 xml/htdocs/proj/en/qa/bug-wranglers/index.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.23&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.23&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?r1=1.22&r2=1.23
Index: index.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -r1.22 -r1.23
--- index.xml 3 Aug 2011 19:57:39 -0000 1.22
+++ index.xml 9 Sep 2011 06:20:41 -0000 1.23
@@ -65,7 +65,6 @@
</recruitment>
<dev role="Lead">jer</dev>
-<dev role="Member">jlec</dev>
<dev role="Member">Polynomial-C</dev>
<dev role="Member">wormo</dev>
<dev role="Member">ssuominen</dev>
^ permalink raw reply [flat|nested] 33+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/qa/bug-wranglers: index.xml
@ 2011-10-10 19:02 Mike Gilbert (floppym)
0 siblings, 0 replies; 33+ messages in thread
From: Mike Gilbert (floppym) @ 2011-10-10 19:02 UTC (permalink / raw
To: gentoo-commits
floppym 11/10/10 19:02:07
Modified: index.xml
Log:
Add myself
Revision Changes Path
1.24 xml/htdocs/proj/en/qa/bug-wranglers/index.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.24&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.24&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?r1=1.23&r2=1.24
Index: index.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -r1.23 -r1.24
--- index.xml 9 Sep 2011 06:20:41 -0000 1.23
+++ index.xml 10 Oct 2011 19:02:07 -0000 1.24
@@ -68,6 +68,7 @@
<dev role="Member">Polynomial-C</dev>
<dev role="Member">wormo</dev>
<dev role="Member">ssuominen</dev>
+<dev role="Member">floppym</dev>
<extrachapter>
<title>Bug Wrangling</title>
^ permalink raw reply [flat|nested] 33+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/qa/bug-wranglers: index.xml
@ 2012-05-18 4:30 Mike Gilbert (floppym)
0 siblings, 0 replies; 33+ messages in thread
From: Mike Gilbert (floppym) @ 2012-05-18 4:30 UTC (permalink / raw
To: gentoo-commits
floppym 12/05/18 04:30:25
Modified: index.xml
Log:
Remove myself. I don't do enough wrangling these days.
Revision Changes Path
1.25 xml/htdocs/proj/en/qa/bug-wranglers/index.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.25&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.25&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?r1=1.24&r2=1.25
Index: index.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -r1.24 -r1.25
--- index.xml 10 Oct 2011 19:02:07 -0000 1.24
+++ index.xml 18 May 2012 04:30:25 -0000 1.25
@@ -68,7 +68,6 @@
<dev role="Member">Polynomial-C</dev>
<dev role="Member">wormo</dev>
<dev role="Member">ssuominen</dev>
-<dev role="Member">floppym</dev>
<extrachapter>
<title>Bug Wrangling</title>
^ permalink raw reply [flat|nested] 33+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/qa/bug-wranglers: index.xml
@ 2012-05-30 14:28 Jeroen Roovers (jer)
0 siblings, 0 replies; 33+ messages in thread
From: Jeroen Roovers (jer) @ 2012-05-30 14:28 UTC (permalink / raw
To: gentoo-commits
jer 12/05/30 14:28:43
Modified: index.xml
Log:
Add more guidelines about the format of the Summary.
Revision Changes Path
1.26 xml/htdocs/proj/en/qa/bug-wranglers/index.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.26&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.26&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?r1=1.25&r2=1.26
Index: index.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -r1.25 -r1.26
--- index.xml 18 May 2012 04:30:25 -0000 1.25
+++ index.xml 30 May 2012 14:28:43 -0000 1.26
@@ -79,14 +79,13 @@
How and when you assign a bug report depends on the type of bug report as well as
correctness and completeness of the bug report.
</p>
-<ul>
-<li>Bug reports requesting <b>version bumps</b> should be assigned to
+<p>Bug reports requesting <b>version bumps</b> should be assigned to
the appropriate maintainers directly. Also check the description of the
bug for references to security bugs, in which case the bug report should
be assigned to <mail link="security@gentoo.org">security@gentoo.org</mail>
immediately, using product "Gentoo Security" and component "Vulnerabilities",
-with the maintainers CC'd.</li>
-<li>Bug reports that say something isn't working or compiling <b>without a
+with the maintainers CC'd.</p>
+<p>Bug reports that say something isn't working or compiling <b>without a
comprehensive analysis of the causes</b>, should contain at least the output of
`emerge --info' as well as a thorough description of the problem, including
error output (or expected versus actual output), the command that led to the
@@ -94,23 +93,25 @@
issue. It is customary to only assign a bug report once these requirements have
been fulfilled. If the reporter hasn't fulfilled these requirements, the bug
should be marked <c>ASSIGNED</c> to bug-wranglers, and a full build log should
-be requested from the reporter.</li>
-<li>Bug reports that <b>include patches</b> or other solutions accompanying
-the actual bug description can usually be assigned directly to the maintainers.</li>
-<li>The <c>Summary</c> uniquely identifies the bug that is being reported. As
+be requested from the reporter.</p>
+<p>Bug reports that <b>include patches</b> or other solutions accompanying
+the actual bug description can usually be assigned directly to the maintainers.</p>
+<p>The <c>Summary</c> uniquely identifies the bug that is being reported. As
there could be several bugs saying that cat/pkg "failed to emerge", it is
important to at least replace such generic descriptions of an emerge failing
with a more exact description, noting the ebuild phase that failed or, better
-yet, the first error message that occured.</li>
-<li>Bug reports that refer to a single or a few (similar) packages should
+yet, the first error message that occured.</p>
+<p>Bug reports that refer to a single or a few (similar) packages should
detail the <b>package atom(s)</b> as completely as possible (at least the
-CATEGORY/PKG(s)) in the <c>Summary</c>, including a version only when other
-versions do not exhibit the bug. Also note that CATEGORY/PKG[-VERSION].ebuild
-is never a valid atom - either refer to CATEGORY/PKG/PKG[-VERSION].ebuild or
-simply remove the .ebuild suffix entirely.</li>
-<li>Bug reports about <b>eclasses</b> should list the full eclass filename in the
-<c>Summary</c>.</li>
-</ul>
+CATEGORY/PKG(s)) at the start of the <c>Summary</c>. If the ebuild is from an
+overlay, the name of the overlay should be prefixed at the start in square
+brackets. The atom should include a version only when other versions do not
+exhibit the bug. Also note that CATEGORY/PKG[-VERSION].ebuild is never a valid
+atom - either refer to CATEGORY/PKG/PKG[-VERSION].ebuild or simply remove the
+.ebuild suffix entirely.</p>
+<pre caption="The standard format of the Summary">[name overlay] CATEGORY/PKG(-version(-revision)) - problem description</pre>
+<p>Bug reports about <b>eclasses</b> should list the full eclass filename in the
+<c>Summary</c> instead of an atom.</p>
</body>
</section>
^ permalink raw reply [flat|nested] 33+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/qa/bug-wranglers: index.xml
@ 2012-12-19 3:06 Jeroen Roovers (jer)
0 siblings, 0 replies; 33+ messages in thread
From: Jeroen Roovers (jer) @ 2012-12-19 3:06 UTC (permalink / raw
To: gentoo-commits
jer 12/12/19 03:06:25
Modified: index.xml
Log:
Update date.
Revision Changes Path
1.27 xml/htdocs/proj/en/qa/bug-wranglers/index.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.27&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.27&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?r1=1.26&r2=1.27
Index: index.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml,v
retrieving revision 1.26
retrieving revision 1.27
diff -u -r1.26 -r1.27
--- index.xml 30 May 2012 14:28:43 -0000 1.26
+++ index.xml 19 Dec 2012 03:06:25 -0000 1.27
@@ -6,7 +6,7 @@
<project>
<name>Bug Wranglers</name>
<longname>The Bug Wranglers Project</longname>
-<date>2011-08-03</date>
+<date>2012-05-30</date>
<author title="Author">
<mail link="jer" />
</author>
^ permalink raw reply [flat|nested] 33+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/qa/bug-wranglers: index.xml
@ 2013-08-07 14:35 Jeroen Roovers (jer)
0 siblings, 0 replies; 33+ messages in thread
From: Jeroen Roovers (jer) @ 2013-08-07 14:35 UTC (permalink / raw
To: gentoo-commits
jer 13/08/07 14:35:30
Modified: index.xml
Log:
Add tomwij.
Revision Changes Path
1.28 xml/htdocs/proj/en/qa/bug-wranglers/index.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.28&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.28&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?r1=1.27&r2=1.28
Index: index.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -r1.27 -r1.28
--- index.xml 19 Dec 2012 03:06:25 -0000 1.27
+++ index.xml 7 Aug 2013 14:35:30 -0000 1.28
@@ -6,7 +6,7 @@
<project>
<name>Bug Wranglers</name>
<longname>The Bug Wranglers Project</longname>
-<date>2012-05-30</date>
+<date>2013-08-07</date>
<author title="Author">
<mail link="jer" />
</author>
@@ -65,9 +65,10 @@
</recruitment>
<dev role="Lead">jer</dev>
-<dev role="Member">Polynomial-C</dev>
-<dev role="Member">wormo</dev>
+<dev role="Member">polynomial-c</dev>
<dev role="Member">ssuominen</dev>
+<dev role="Member">tomwij</dev>
+<dev role="Member">wormo</dev>
<extrachapter>
<title>Bug Wrangling</title>
^ permalink raw reply [flat|nested] 33+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/qa/bug-wranglers: index.xml
@ 2013-08-07 14:44 Jeroen Roovers (jer)
0 siblings, 0 replies; 33+ messages in thread
From: Jeroen Roovers (jer) @ 2013-08-07 14:44 UTC (permalink / raw
To: gentoo-commits
jer 13/08/07 14:44:01
Modified: index.xml
Log:
Add {action} to Summary format.
Revision Changes Path
1.29 xml/htdocs/proj/en/qa/bug-wranglers/index.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.29&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.29&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?r1=1.28&r2=1.29
Index: index.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -r1.28 -r1.29
--- index.xml 7 Aug 2013 14:35:30 -0000 1.28
+++ index.xml 7 Aug 2013 14:44:01 -0000 1.29
@@ -110,7 +110,7 @@
exhibit the bug. Also note that CATEGORY/PKG[-VERSION].ebuild is never a valid
atom - either refer to CATEGORY/PKG/PKG[-VERSION].ebuild or simply remove the
.ebuild suffix entirely.</p>
-<pre caption="The standard format of the Summary">[name overlay] CATEGORY/PKG(-version(-revision)) - problem description</pre>
+<pre caption="The standard format of the Summary">[name overlay] CATEGORY/PKG(-version(-revision)) - {problem description}/{action}</pre>
<p>Bug reports about <b>eclasses</b> should list the full eclass filename in the
<c>Summary</c> instead of an atom.</p>
</body>
^ permalink raw reply [flat|nested] 33+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/qa/bug-wranglers: index.xml
@ 2013-08-11 14:59 Jeroen Roovers (jer)
0 siblings, 0 replies; 33+ messages in thread
From: Jeroen Roovers (jer) @ 2013-08-11 14:59 UTC (permalink / raw
To: gentoo-commits
jer 13/08/11 14:59:17
Modified: index.xml
Log:
Add directions on repositories.xml for bugs about packages in overlays.
Revision Changes Path
1.30 xml/htdocs/proj/en/qa/bug-wranglers/index.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.30&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.30&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?r1=1.29&r2=1.30
Index: index.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml,v
retrieving revision 1.29
retrieving revision 1.30
diff -u -r1.29 -r1.30
--- index.xml 7 Aug 2013 14:44:01 -0000 1.29
+++ index.xml 11 Aug 2013 14:59:17 -0000 1.30
@@ -6,7 +6,7 @@
<project>
<name>Bug Wranglers</name>
<longname>The Bug Wranglers Project</longname>
-<date>2013-08-07</date>
+<date>2013-08-11</date>
<author title="Author">
<mail link="jer" />
</author>
@@ -190,6 +190,11 @@
appropriate e-mail alias for that herd.
</li>
<li>
+Bug reports about packages in <b>overlays</b> should be assigned to the
+<owner> tag in <uri
+link="https://api.gentoo.org/overlays/repositories.xml">repositories.xml</uri>. Some of these overlays want to get their bugs tracked elsewhere, and explicitly state this in their <description> tags.
+</li>
+<li>
When a bug report calls attention to <b>multiple packages</b>, then things
get slightly more complicated. When the listed packages do not belong to the
same maintainer or team, for instance when a library upgrade causes several
^ permalink raw reply [flat|nested] 33+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/qa/bug-wranglers: index.xml
@ 2013-08-11 15:17 Jeroen Roovers (jer)
0 siblings, 0 replies; 33+ messages in thread
From: Jeroen Roovers (jer) @ 2013-08-11 15:17 UTC (permalink / raw
To: gentoo-commits
jer 13/08/11 15:17:38
Modified: index.xml
Log:
Make XML tags look like code.
Revision Changes Path
1.31 xml/htdocs/proj/en/qa/bug-wranglers/index.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.31&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.31&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?r1=1.30&r2=1.31
Index: index.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml,v
retrieving revision 1.30
retrieving revision 1.31
diff -u -r1.30 -r1.31
--- index.xml 11 Aug 2013 14:59:17 -0000 1.30
+++ index.xml 11 Aug 2013 15:17:38 -0000 1.31
@@ -176,11 +176,11 @@
less up to date) and read the <c>metadata.xml</c> file you find there. When
<c>metadata.xml</c> lists a single maintainer or herd, then you assign the bug
to that maintainer or herd. When the file lists multiple entries, then you
-assign the bug to the first <maintainer>, and CC the other
-<maintainer>(s) and <herd>(s). If you find that <c>metadata.xml</c>
-lists inappropriate and/or confusing contact information, then make a note of
-that in a comment on the bug report and assign/CC the bug report as best as
-possible.
+assign the bug to the first <c><maintainer></c>, and CC the other
+<c><maintainer></c>(s) and <c><herd></c>(s). If you find that
+<c>metadata.xml</c> lists inappropriate and/or confusing contact information,
+then make a note of that in a comment on the bug report and assign/CC the bug
+report as best as possible.
</li>
<li>
In cases where <c>metadata.xml</c> lists a herd which Gentoo Bugzilla
@@ -191,8 +191,10 @@
</li>
<li>
Bug reports about packages in <b>overlays</b> should be assigned to the
-<owner> tag in <uri
-link="https://api.gentoo.org/overlays/repositories.xml">repositories.xml</uri>. Some of these overlays want to get their bugs tracked elsewhere, and explicitly state this in their <description> tags.
+<c><owner></c> tag in <uri
+link="https://api.gentoo.org/overlays/repositories.xml">repositories.xml</uri>.
+Some of these overlays want to get their bugs tracked elsewhere, and explicitly
+state this in their <c><description></c> tags.
</li>
<li>
When a bug report calls attention to <b>multiple packages</b>, then things
^ permalink raw reply [flat|nested] 33+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/qa/bug-wranglers: index.xml
@ 2013-08-11 15:29 Jeroen Roovers (jer)
0 siblings, 0 replies; 33+ messages in thread
From: Jeroen Roovers (jer) @ 2013-08-11 15:29 UTC (permalink / raw
To: gentoo-commits
jer 13/08/11 15:29:55
Modified: index.xml
Log:
best => well
Revision Changes Path
1.32 xml/htdocs/proj/en/qa/bug-wranglers/index.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.32&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.32&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?r1=1.31&r2=1.32
Index: index.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml,v
retrieving revision 1.31
retrieving revision 1.32
diff -u -r1.31 -r1.32
--- index.xml 11 Aug 2013 15:17:38 -0000 1.31
+++ index.xml 11 Aug 2013 15:29:55 -0000 1.32
@@ -180,7 +180,7 @@
<c><maintainer></c>(s) and <c><herd></c>(s). If you find that
<c>metadata.xml</c> lists inappropriate and/or confusing contact information,
then make a note of that in a comment on the bug report and assign/CC the bug
-report as best as possible.
+report as well as you can.
</li>
<li>
In cases where <c>metadata.xml</c> lists a herd which Gentoo Bugzilla
^ permalink raw reply [flat|nested] 33+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/proj/en/qa/bug-wranglers: index.xml
@ 2013-12-10 13:45 Lars Wendler (polynomial-c)
0 siblings, 0 replies; 33+ messages in thread
From: Lars Wendler (polynomial-c) @ 2013-12-10 13:45 UTC (permalink / raw
To: gentoo-commits
polynomial-c 13/12/10 13:45:01
Modified: index.xml
Log:
Moved "Bug-wranglers" qa subpage to wiki.
Revision Changes Path
1.33 xml/htdocs/proj/en/qa/bug-wranglers/index.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.33&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.33&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?r1=1.32&r2=1.33
Index: index.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml,v
retrieving revision 1.32
retrieving revision 1.33
diff -u -r1.32 -r1.33
--- index.xml 11 Aug 2013 15:29:55 -0000 1.32
+++ index.xml 10 Dec 2013 13:45:01 -0000 1.33
@@ -3,7 +3,7 @@
<?xml-stylesheet href="/xsl/guide.xsl" type="text/xsl"?>
<!DOCTYPE project SYSTEM "/dtd/project.dtd">
-<project>
+<project disclaimer="obsolete" redirect="http://wiki.gentoo.org/wiki/Project:Bug-wranglers">
<name>Bug Wranglers</name>
<longname>The Bug Wranglers Project</longname>
<date>2013-08-11</date>
^ permalink raw reply [flat|nested] 33+ messages in thread
end of thread, other threads:[~2013-12-10 13:45 UTC | newest]
Thread overview: 33+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-09-02 20:35 [gentoo-commits] gentoo commit in xml/htdocs/proj/en/qa/bug-wranglers: index.xml Jeroen Roovers (jer)
-- strict thread matches above, loose matches on Subject: below --
2013-12-10 13:45 Lars Wendler (polynomial-c)
2013-08-11 15:29 Jeroen Roovers (jer)
2013-08-11 15:17 Jeroen Roovers (jer)
2013-08-11 14:59 Jeroen Roovers (jer)
2013-08-07 14:44 Jeroen Roovers (jer)
2013-08-07 14:35 Jeroen Roovers (jer)
2012-12-19 3:06 Jeroen Roovers (jer)
2012-05-30 14:28 Jeroen Roovers (jer)
2012-05-18 4:30 Mike Gilbert (floppym)
2011-10-10 19:02 Mike Gilbert (floppym)
2011-09-09 6:20 Justin Lecher (jlec)
2011-08-03 19:57 Jeroen Roovers (jer)
2011-08-03 19:57 Jeroen Roovers (jer)
2011-01-23 18:43 Jeroen Roovers (jer)
2010-11-16 15:10 PaweA Hajdan (phajdan.jr)
2010-10-26 18:46 Jeroen Roovers (jer)
2010-10-26 18:35 Jeroen Roovers (jer)
2010-10-03 19:39 Markos Chandras (hwoarang)
2010-05-26 3:36 Jeroen Roovers (jer)
2009-11-09 13:41 Markos Chandras (hwoarang)
2009-10-28 21:27 Jeremy Olexa (darkside)
2009-10-23 18:31 Jeremy Olexa (darkside)
2009-09-29 20:02 Jeremy Olexa (darkside)
2009-03-27 21:37 Jeroen Roovers (jer)
2008-09-10 5:07 Jeroen Roovers (jer)
2008-09-08 16:24 Jeroen Roovers (jer)
2008-08-21 0:51 Mark Loeser (halcy0n)
2008-07-23 16:19 Jeroen Roovers (jer)
2008-07-23 16:18 Jeroen Roovers (jer)
2008-07-14 19:30 Jeroen Roovers (jer)
2008-07-05 7:40 Christian Faulhammer (opfer)
2008-07-05 3:40 Mark Loeser (halcy0n)
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox