/[gentoo]/xml/htdocs/proj/en/glep/glep-0048.html
Gentoo

Contents of /xml/htdocs/proj/en/glep/glep-0048.html

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.2 - (show annotations) (download) (as text)
Tue Sep 5 20:34:55 2006 UTC (8 years, 2 months ago) by g2boojum
Branch: MAIN
Changes since 1.1: +248 -5 lines
File MIME type: text/html
updates

1 <?xml version="1.0" encoding="utf-8" ?>
2 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
3 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
4 <!--
5 This HTML is auto-generated. DO NOT EDIT THIS FILE! If you are writing a new
6 PEP, see http://www.python.org/peps/pep-0001.html for instructions and links
7 to templates. DO NOT USE THIS HTML FILE AS YOUR TEMPLATE!
8 -->
9 <head>
10 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
11 <meta name="generator" content="Docutils 0.4: http://docutils.sourceforge.net/" />
12 <title>GLEP 48 -- QA Team's Role and Purpose</title>
13 <style type="text/css">
14
15 /*
16 :Author: David Goodger
17 :Contact: goodger@users.sourceforge.net
18 :date: $Date: 2003/06/02 17:03:08 $
19 :version: $Revision: 1.1 $
20 :copyright: This stylesheet has been placed in the public domain.
21
22 Default cascading style sheet for the PEP HTML output of Docutils.
23 */
24
25 .first {
26 margin-top: 0 }
27
28 .last {
29 margin-bottom: 0 }
30
31 .navigation {
32 width: 100% ;
33 background: #cc99ff ;
34 margin-top: 0px ;
35 margin-bottom: 0px }
36
37 .navigation .navicon {
38 width: 150px ;
39 height: 35px }
40
41 .navigation .textlinks {
42 padding-left: 1em ;
43 text-align: left }
44
45 .navigation td, .navigation th {
46 padding-left: 0em ;
47 padding-right: 0em ;
48 vertical-align: middle }
49
50 .rfc2822 {
51 margin-top: 0.5em ;
52 margin-left: 0.5em ;
53 margin-right: 0.5em ;
54 margin-bottom: 0em }
55
56 .rfc2822 td {
57 text-align: left }
58
59 .rfc2822 th.field-name {
60 text-align: right ;
61 font-family: sans-serif ;
62 padding-right: 0.5em ;
63 font-weight: bold ;
64 margin-bottom: 0em }
65
66 a.toc-backref {
67 text-decoration: none ;
68 color: black }
69
70 body {
71 margin: 0px ;
72 margin-bottom: 1em ;
73 padding: 0px }
74
75 dd {
76 margin-bottom: 0.5em }
77
78 div.section {
79 margin-left: 1em ;
80 margin-right: 1em ;
81 margin-bottom: 1.5em }
82
83 div.section div.section {
84 margin-left: 0em ;
85 margin-right: 0em ;
86 margin-top: 1.5em }
87
88 div.abstract {
89 margin: 2em 5em }
90
91 div.abstract p.topic-title {
92 font-weight: bold ;
93 text-align: center }
94
95 div.attention, div.caution, div.danger, div.error, div.hint,
96 div.important, div.note, div.tip, div.warning {
97 margin: 2em ;
98 border: medium outset ;
99 padding: 1em }
100
101 div.attention p.admonition-title, div.caution p.admonition-title,
102 div.danger p.admonition-title, div.error p.admonition-title,
103 div.warning p.admonition-title {
104 color: red ;
105 font-weight: bold ;
106 font-family: sans-serif }
107
108 div.hint p.admonition-title, div.important p.admonition-title,
109 div.note p.admonition-title, div.tip p.admonition-title {
110 font-weight: bold ;
111 font-family: sans-serif }
112
113 div.figure {
114 margin-left: 2em }
115
116 div.footer, div.header {
117 font-size: smaller }
118
119 div.footer {
120 margin-left: 1em ;
121 margin-right: 1em }
122
123 div.system-messages {
124 margin: 5em }
125
126 div.system-messages h1 {
127 color: red }
128
129 div.system-message {
130 border: medium outset ;
131 padding: 1em }
132
133 div.system-message p.system-message-title {
134 color: red ;
135 font-weight: bold }
136
137 div.topic {
138 margin: 2em }
139
140 h1 {
141 font-family: sans-serif ;
142 font-size: large }
143
144 h2 {
145 font-family: sans-serif ;
146 font-size: medium }
147
148 h3 {
149 font-family: sans-serif ;
150 font-size: small }
151
152 h4 {
153 font-family: sans-serif ;
154 font-style: italic ;
155 font-size: small }
156
157 h5 {
158 font-family: sans-serif;
159 font-size: x-small }
160
161 h6 {
162 font-family: sans-serif;
163 font-style: italic ;
164 font-size: x-small }
165
166 .section hr {
167 width: 75% }
168
169 ol.simple, ul.simple {
170 margin-bottom: 1em }
171
172 ol.arabic {
173 list-style: decimal }
174
175 ol.loweralpha {
176 list-style: lower-alpha }
177
178 ol.upperalpha {
179 list-style: upper-alpha }
180
181 ol.lowerroman {
182 list-style: lower-roman }
183
184 ol.upperroman {
185 list-style: upper-roman }
186
187 p.caption {
188 font-style: italic }
189
190 p.credits {
191 font-style: italic ;
192 font-size: smaller }
193
194 p.label {
195 white-space: nowrap }
196
197 p.topic-title {
198 font-family: sans-serif ;
199 font-weight: bold }
200
201 pre.line-block {
202 font-family: serif ;
203 font-size: 100% }
204
205 pre.literal-block, pre.doctest-block {
206 margin-left: 2em ;
207 margin-right: 2em ;
208 background-color: #eeeeee }
209
210 span.classifier {
211 font-family: sans-serif ;
212 font-style: oblique }
213
214 span.classifier-delimiter {
215 font-family: sans-serif ;
216 font-weight: bold }
217
218 span.interpreted {
219 font-family: sans-serif }
220
221 span.option-argument {
222 font-style: italic }
223
224 span.pre {
225 white-space: pre }
226
227 span.problematic {
228 color: red }
229
230 table {
231 margin-top: 0.5em ;
232 margin-bottom: 0.5em }
233
234 td, th {
235 padding-left: 0.5em ;
236 padding-right: 0.5em ;
237 vertical-align: top }
238
239 td.num {
240 text-align: right }
241
242 th.field-name {
243 font-weight: bold ;
244 text-align: left ;
245 white-space: nowrap }
246
247 h1 tt, h2 tt, h3 tt, h4 tt, h5 tt, h6 tt {
248 font-size: 100% }
249
250 tt {
251 background-color: #eeeeee }
252
253 ul.auto-toc {
254 list-style-type: none }
255
256 </style>
257 </head>
258 <body bgcolor="white">
259 <table class="navigation" cellpadding="0" cellspacing="0"
260 width="100%" border="0">
261 <tr><td class="navicon" width="150" height="35">
262 <a href="http://www.gentoo.org/" title="Gentoo Linux Home Page">
263 <img src="http://www.gentoo.org/images/gentoo-new.gif" alt="[Gentoo]"
264 border="0" width="150" height="35" /></a></td>
265 <td class="textlinks" align="left">
266 [<b><a href="http://www.gentoo.org/">Gentoo Linux Home</a></b>]
267 [<b><a href="http://www.gentoo.org/peps">GLEP Index</a></b>]
268 [<b><a href="http://www.gentoo.org/proj/en/glep/glep-0048.txt">GLEP Source</a></b>]
269 </td></tr></table>
270 <table class="rfc2822 docutils field-list" frame="void" rules="none">
271 <col class="field-name" />
272 <col class="field-body" />
273 <tbody valign="top">
274 <tr class="field"><th class="field-name">GLEP:</th><td class="field-body">48</td>
275 </tr>
276 <tr class="field"><th class="field-name">Title:</th><td class="field-body">QA Team's Role and Purpose</td>
277 </tr>
278 <tr class="field"><th class="field-name">Version:</th><td class="field-body">1.2</td>
279 </tr>
280 <tr class="field"><th class="field-name">Last-Modified:</th><td class="field-body"><a class="reference" href="http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/proj/en/glep/glep-0048.txt?cvsroot=gentoo">2006/09/05 20:34:26</a></td>
281 </tr>
282 <tr class="field"><th class="field-name">Author:</th><td class="field-body">Mark Loeser &lt;halcy0n&#32;&#97;t&#32;gentoo.org&gt;,</td>
283 </tr>
284 <tr class="field"><th class="field-name">Status:</th><td class="field-body">Final</td>
285 </tr>
286 <tr class="field"><th class="field-name">Type:</th><td class="field-body">Standards Track</td>
287 </tr>
288 <tr class="field"><th class="field-name">Content-Type:</th><td class="field-body"><a class="reference" href="glep-0002.html">text/x-rst</a></td>
289 </tr>
290 <tr class="field"><th class="field-name">Created:</th><td class="field-body">24 April 2006</td>
291 </tr>
292 <tr class="field"><th class="field-name">Post-History:</th><td class="field-body">24-Apr-2006</td>
293 </tr>
294 </tbody>
295 </table>
296 <hr />
297 <div class="contents topic">
298 <p class="topic-title first"><a id="contents" name="contents">Contents</a></p>
299 <ul class="simple">
300 <li><a class="reference" href="#abstract" id="id2" name="id2">Abstract</a></li>
301 <li><a class="reference" href="#motivation" id="id3" name="id3">Motivation</a></li>
302 <li><a class="reference" href="#specification" id="id4" name="id4">Specification</a></li>
303 <li><a class="reference" href="#backwards-compatibility" id="id5" name="id5">Backwards Compatibility</a></li>
304 <li><a class="reference" href="#copyright" id="id6" name="id6">Copyright</a></li>
305 </ul>
306 </div>
307 <div class="section">
308 <h1><a class="toc-backref" href="#id2" id="abstract" name="abstract">Abstract</a></h1>
309 <p>This GLEP outlines the abilities and purpose of the Quality Assurance team
310 for Gentoo.</p>
311 </div>
312 <div class="section">
313 <h1><a class="toc-backref" href="#id3" id="motivation" name="motivation">Motivation</a></h1>
314 <p>For years now developers have been saying how we need an empowered QA team to
315 handle problems concerning the tree. This GLEP provides the structure for
316 such a team and specifies the roles the team would fulfill.</p>
317 </div>
318 <div class="section">
319 <h1><a class="toc-backref" href="#id4" id="specification" name="specification">Specification</a></h1>
320 <p>The QA team should be given certain abilities to look out for the best
321 interests of all developers, as well as our users. The QA team should also
322 work to ensure developers have the information they need, and that packages
323 are maintained.</p>
324 <ul class="simple">
325 <li>The QA team's purpose is to provide cross-team assistance in keeping the
326 tree in a good state. This is done primarily by finding and pointing out
327 issues to maintainers and, where necessary, taking direct action.</li>
328 <li>In case of emergency, or if package maintainers refuse to cooperate,
329 the QA team may take action themselves to fix the problem. The QA team
330 does not want to override the maintainer's wishes by default, but only
331 wish to do so when the team finds it is in the best interest of users and
332 fellow developers to have the issue addressed as soon as possible.</li>
333 <li>The QA team may also offer to fix obvious typos and similar minor issues,
334 and silence from the package maintainers can be taken as agreement in such
335 situations. Coding style issues fall under this category, and while they
336 are not severe, they can make automated checks of the tree more difficult.</li>
337 <li>There will be cases when our tools are incapable of handling a certain
338 situation and policy must be broken in order to get something working
339 completely. This will hopefully not occur very often but each time it
340 does occur, the QA team and the maintainer will come to some agreement on
341 an interim solution and it is expected that a bug will be opened with the
342 appropriate team to work towards a correct solution.</li>
343 <li>In the case of disagreement among QA members the majority of established
344 QA members must agree with the action. Some examples of disagreements are:
345 whether the percieved problem violates the policy or whether the solution
346 makes the situation worse.</li>
347 <li>In the event that a developer still insists that a package does not break
348 QA standards, an appeal can be made at the next council meeting. The package
349 should be dealt with per QA's request until such a time that a decision is
350 made by the council.</li>
351 <li>Just because a particular QA violation has yet to cause an issue does not
352 change the fact that it is still a QA violation.</li>
353 <li>If a particular developer persistently causes breakage, the QA team
354 may request that devrel re-evaluates that developer's commit rights.
355 Evidence of past breakages will be presented with this request to devrel.</li>
356 <li>The QA team will maintain a list of current &quot;QA Standards&quot; with explanations
357 as to why they are problems, and how to fix the problem. The list is not
358 meant by any means to be a comprehensive document, but rather a dynamic
359 document that will be updated as new problems are discovered. The QA team
360 will also do their best to ensure all developer tools are in line with the
361 current QA standards.</li>
362 <li>In order to join the QA team, you must be a developer for at least 4 months
363 and must ask the current lead for approval.</li>
364 <li>The QA team will work with Recruiters to keep related documentation and
365 quizzes up to date, so that up and coming developers will have access to all
366 of the necessary information to avoid past problems.</li>
367 <li>QA will take an active role in cleaning up and removing from the tree
368 unmaintained packages as they are found to be broken. It is also
369 encouraged of members of the QA team to assist in mentoring new developers
370 that wish to take over unmaintained packages/herds.</li>
371 </ul>
372 </div>
373 <div class="section">
374 <h1><a class="toc-backref" href="#id5" id="backwards-compatibility" name="backwards-compatibility">Backwards Compatibility</a></h1>
375 <p>Not a problem for this GLEP.</p>
376 </div>
377 <div class="section">
378 <h1><a class="toc-backref" href="#id6" id="copyright" name="copyright">Copyright</a></h1>
379 <p>This document has been placed in the public domain.</p>
380 </div>
381
382 </div>
383 <div class="footer">
384 <hr class="footer" />
385 <a class="reference" href="glep-0048.txt">View document source</a>.
386 Generated on: 2006-09-05 20:34 UTC.
387 Generated by <a class="reference" href="http://docutils.sourceforge.net/">Docutils</a> from <a class="reference" href="http://docutils.sourceforge.net/rst.html">reStructuredText</a> source.
388
389 </div>
390 </body>
391 </html>

  ViewVC Help
Powered by ViewVC 1.1.20