From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1Ph4uB-0008Te-0i for garchives@archives.gentoo.org; Sun, 23 Jan 2011 18:43:15 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 8671CE00E6; Sun, 23 Jan 2011 18:43:05 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 40052E0B0D for ; Sun, 23 Jan 2011 18:43:05 +0000 (UTC) Received: from flycatcher.gentoo.org (flycatcher.gentoo.org [81.93.255.6]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTPS id 7B2B11B4027 for ; Sun, 23 Jan 2011 18:43:04 +0000 (UTC) Received: by flycatcher.gentoo.org (Postfix, from userid 2078) id 2098E20054; Sun, 23 Jan 2011 18:43:03 +0000 (UTC) From: "Jeroen Roovers (jer)" To: gentoo-commits@lists.gentoo.org Reply-To: gentoo-dev@lists.gentoo.org, jer@gentoo.org Subject: [gentoo-commits] gentoo commit in xml/htdocs/proj/en/qa/bug-wranglers: index.xml X-VCS-Repository: gentoo X-VCS-Files: index.xml X-VCS-Directories: xml/htdocs/proj/en/qa/bug-wranglers X-VCS-Committer: jer X-VCS-Committer-Name: Jeroen Roovers Content-Type: text/plain; charset=utf8 Message-Id: <20110123184303.2098E20054@flycatcher.gentoo.org> Date: Sun, 23 Jan 2011 18:43:03 +0000 (UTC) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-commits@lists.gentoo.org Content-Transfer-Encoding: quoted-printable X-Archives-Salt: X-Archives-Hash: 97faf1b7058fad421836dd46ddd14cb5 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=3D1.20&view=3Dmarkup plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/= bug-wranglers/index.xml?rev=3D1.20&content-type=3Dtext/plain diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/qa/= bug-wranglers/index.xml?r1=3D1.19&r2=3D1.20 Index: index.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.x= ml,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 @@ Bug Wranglers The Bug Wranglers Project -2010-05-26 +2011-01-23 @@ -18,20 +18,24 @@ =20

-The Gentoo Bug Wranglers project controls, describes the tasks to be car= ried out and -goals to be achieved for everyone who wrangles bugs on Gentoo's bug tracker.

-

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 = bug tracker. +

+

+The project was set up after the de facto resignation of long time Ma= in Bug Wrangler Jakub Moc, when it turned out we required a division of= labour -to see all bugs reassigned within an acceptable timeframe (from the mome= nt of a -bug report's creation to its proper assignment). For his years of relent= less -bug wrangling, this project both owes him its gratitude and earns its -existence.

-

In its current phase, the project now strives to get every bug assign= ed -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 t= he +moment of a bug report's creation to its proper assignment). For his yea= rs of +relentless bug wrangling, this project both owes him its gratitude and e= arns +its existence. +

+

+The project strives to get every bug assigned within a day, counting fro= m +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 maint= ain a +list of notable bug wranglers, and to gather yet more useful guidelines = on this +page.

=20 @@ -163,7 +167,8 @@ information, depending on the type of bug report.

    -
  • If a bug report pertains to a specific package, then you ente= r the +
  • +If a bug report pertains to a specific package, then you enter th= e package's directory in your copy of the gentoo-x86 CVS repository (or perhaps the online version which should always be m= ore or @@ -173,14 +178,18 @@ assign the bug to the first maintainer, and CC the other maintainer(s) a= nd herd(s). If you find that metadata.xml 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.
    • -
  • In cases where metadata.xml lists a herd which Gentoo Bugzill= a +report and assign/CC the bug report as optimal as possible. +
    • +
  • +In cases where metadata.xml lists a herd which Gentoo Bugzilla doesn't know about (which it will ask you to correct before it accepts c= hanges to the bug report), you should consult herds.xml to figur= e out the -appropriate e-mail alias for that herd.
    • -
  • When a bug report calls attention to multiple packages, then = things -become slightly more complicated. When the listed packages do not belong= to the +appropriate e-mail alias for that herd. +
    • +
  • +When a bug report calls attention to multiple packages, then thin= gs +get slightly more complicated. When the listed packages do not belong to= the same maintainer or team, for instance when a library upgrade causes seve= ral 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 (denoted by the Tracker 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 solut= ion is -clear.
    • -
  • Bug reports that concern eclasses should be assigned to the e= class +clear. +
    • +
  • +Bug reports that concern eclasses should be assigned to the eclas= s maintainer. To figure out who maintains an eclass, browse to the gen= too-x86/eclass 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 shou= ld note this omission and the last committer to that file should be made th= e -report's assignee.
    • -
  • A keyword request should be assigned to the package's maintai= ner and +report's assignee. +
    • +
  • +A keyword request should be assigned to the package's maintainer = and CC'd to the appropriate arch team(s). The report's Keywords field= should -contain the KEYWORDREQ keyword.
    • -
  • A stabilisation request should be handled by the package's ma= intainer, so +contain the KEYWORDREQ keyword. +
    • +
  • +A stabilisation request should be handled by the package's mainta= iner, so you should not CC arch teams in your role as bug wrangler, nor set the STABLEREQ keyword in the Keywords field. Unless the packag= e is maintainer-needed, then you should add arches and set the Keyword field = if the -bug makes sense.
    • -
  • Bug reports that concern profiles should be assigned to +bug makes sense. +
    • +
  • +Bug reports that concern profiles should be assigned to qa@gentoo.org with release@gentoo.org CC'd. E= xceptions are profiles that are obviously maintained by some herd, like hardened, = selinux, -prefix, etc. Those get assigned to the maintaining herd.
    • -
  • Bug reports that relate to issues other than the portage tree, like +prefix, etc. Those get assigned to the maintaining herd. +
    • +
  • +Bug reports that relate to issues other than the portage tree, like problems with Gentoo's bugzilla, Gentoo infrastructure, mirrors or staff= ing matters (devrel, userrel and so on) are usually easier to assign. The Product and Component fields of each bug should help you -(re)assign these reports appropriately.
    • +(re)assign these reports appropriately. +