Gentoo Archives: gentoo-commits

From: "Jeroen Roovers (jer)" <jer@g.o>
To: gentoo-commits@l.g.o
Subject: [gentoo-commits] gentoo commit in xml/htdocs/proj/en/qa/bug-wranglers: index.xml
Date: Tue, 02 Sep 2008 20:35:47
Message-Id: E1KacbJ-00031y-2c@stork.gentoo.org
1 jer 08/09/02 20:35:45
2
3 Modified: index.xml
4 Log:
5 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.
6
7 Revision Changes Path
8 1.7 xml/htdocs/proj/en/qa/bug-wranglers/index.xml
9
10 file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.7&view=markup
11 plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?rev=1.7&content-type=text/plain
12 diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml?r1=1.6&r2=1.7
13
14 Index: index.xml
15 ===================================================================
16 RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/qa/bug-wranglers/index.xml,v
17 retrieving revision 1.6
18 retrieving revision 1.7
19 diff -u -r1.6 -r1.7
20 --- index.xml 21 Aug 2008 00:51:05 -0000 1.6
21 +++ index.xml 2 Sep 2008 20:35:44 -0000 1.7
22 @@ -6,21 +6,32 @@
23 <project>
24 <name>Bug Wranglers</name>
25 <longname>The Bug Wranglers Project</longname>
26 -<date>2008-07-23</date>
27 +<date>2008-09-02</date>
28 <author title="Author">
29 <mail link="jer" />
30 </author>
31
32 <description>
33 -The Gentoo Bug Wranglers project controls, describes the tasks and goals
34 -carried out by everyone who wrangles bugs on Gentoo's bug tracker.
35 +The Gentoo Bug Wranglers project controls, describes the tasks to be carried out and
36 +goals to be achieved for everyone who wrangles bugs on Gentoo's bug tracker.
37 </description>
38
39 <longdescription>
40 <p>
41 -The Gentoo Bug Wranglers project controls, describes the tasks and
42 -goals carried out by everyone who wrangles bugs on Gentoo's <uri
43 -link="http://bugs.gentoo.org/">bug tracker</uri>.
44 +The Gentoo Bug Wranglers project controls, describes the tasks to be carried out and
45 +goals to be achieved for everyone who wrangles bugs on Gentoo's <uri
46 +link="http://bugs.gentoo.org/">bug tracker</uri>.</p>
47 +<p>The project was erected after the de facto resignation of long time <e>Main
48 +Bug Wrangler</e> Jakub Moc, when it turned out we required a division of labour
49 +to see all bugs reassigned within an acceptable timeframe (from the moment of a
50 +bug report's creation to its proper assignment). For his years of relentless
51 +bug wrangling, this project both owes him its gratitude and earns its
52 +existence.</p>
53 +<p>In its current phase, the project now strives to get every bug assigned
54 +within a day, counting from the moment when enough information has been
55 +gathered. In the future, the project's aims are to credit developers and users
56 +who help out, to maintain a list of notable bug wranglers, and to gather yet
57 +more useful guidelines on this page.
58 </p>
59 </longdescription>
60
61 @@ -34,10 +45,7 @@
62 </p>
63 </goals>
64
65 -<dev role="Bug wrangler">carlo</dev>
66 -<dev role="Bug wrangler">jakub</dev>
67 -<dev role="Bug wrangler">jer</dev>
68 -<dev role="Bug wrangler">jkt</dev>
69 +<dev role="Lead">jer</dev>
70
71 <extrachapter>
72 <title>Bug Wrangling</title>
73 @@ -94,7 +102,9 @@
74 <c>metadata.xml</c> lists a single maintainer or herd, then you assign the bug
75 to that maintainer or herd. When the file lists multiple entries, then you
76 assign the bug to the first maintainer, and CC the other maintainer(s) and
77 -herd(s).</li>
78 +herd(s). If you find that <c>metadata.xml</c> lists inappropriate and/or
79 +confusing contact information, then make a note of that in a comment on the bug
80 +report and assign/CC the bug report as optimal as possible.</li>
81 <li>In cases where <c>metadata.xml</c> lists a herd which Gentoo Bugzilla
82 doesn't know about (which it will ask you to correct before it accepts changes
83 to the bug report), you should consult <uri
84 @@ -134,9 +144,9 @@
85 <section>
86 <body>
87 <p>
88 -Any Gentoo developers who can change the <c>Assignee</c> fields of new bugs are
89 -welcome to help assign bugs to the right developers. Most developers will
90 -appreciate it if, while doing so, you follow the rules layed out above.
91 +All Gentoo developers who can change the <c>Assignee</c> fields of new bugs are
92 +welcome to help assign bugs to the right developers. Most assignees will
93 +appreciate it if, in doing so, you follow the rules layed out above.
94 </p>
95 <p>
96 Users are encouraged to assist in wrangling bugs as well. Even without bugzilla
97 @@ -153,7 +163,7 @@
98 <title>Via e-mail</title>
99 <body>
100 <p>
101 -There is currently no single contact. Please refer to the developer list above.
102 +Please refer to the developer list above.
103 </p>
104 </body>
105 </section>
106 @@ -161,7 +171,7 @@
107 <title>Via IRC</title>
108 <body>
109 <p>
110 -You can find us on irc.freenode.net at #gentoo-bugs.
111 +You can find some of us on the Freenode network in <uri link="irc://irc.freenode.net/gentoo-bugs">#gentoo-bugs</uri>.
112 </p>
113 </body>
114 </section>