/[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.6 - (show annotations) (download) (as text)
Sun Oct 14 17:00:15 2007 UTC (6 years, 6 months ago) by antarus
Branch: MAIN
Changes since 1.5: +4 -251 lines
File MIME type: text/html
the canary on 53 went well, changing the rest

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 <head>
6 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
7 <meta name="generator" content="Docutils 0.4: http://docutils.sourceforge.net/" />
8 <title>GLEP 48 -- QA Team's Role and Purpose</title>
9 <link rel="stylesheet" href="tools/glep.css" type="text/css" />
10 </head>
11 <body bgcolor="white">
12 <table class="navigation" cellpadding="0" cellspacing="0"
13 width="100%" border="0">
14 <tr><td class="navicon" width="150" height="35">
15 <a href="http://www.gentoo.org/" title="Gentoo Linux Home Page">
16 <img src="http://www.gentoo.org/images/gentoo-new.gif" alt="[Gentoo]"
17 border="0" width="150" height="35" /></a></td>
18 <td class="textlinks" align="left">
19 [<b><a href="http://www.gentoo.org/">Gentoo Linux Home</a></b>]
20 [<b><a href="http://www.gentoo.org/proj/en/glep">GLEP Index</a></b>]
21 [<b><a href="http://www.gentoo.org/proj/en/glep/glep-0048.txt">GLEP Source</a></b>]
22 </td></tr></table>
23 <table class="rfc2822 docutils field-list" frame="void" rules="none">
24 <col class="field-name" />
25 <col class="field-body" />
26 <tbody valign="top">
27 <tr class="field"><th class="field-name">GLEP:</th><td class="field-body">48</td>
28 </tr>
29 <tr class="field"><th class="field-name">Title:</th><td class="field-body">QA Team's Role and Purpose</td>
30 </tr>
31 <tr class="field"><th class="field-name">Version:</th><td class="field-body">1.3</td>
32 </tr>
33 <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:36:38</a></td>
34 </tr>
35 <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>
36 </tr>
37 <tr class="field"><th class="field-name">Status:</th><td class="field-body">Final</td>
38 </tr>
39 <tr class="field"><th class="field-name">Type:</th><td class="field-body">Standards Track</td>
40 </tr>
41 <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>
42 </tr>
43 <tr class="field"><th class="field-name">Created:</th><td class="field-body">24 April 2006</td>
44 </tr>
45 <tr class="field"><th class="field-name">Post-History:</th><td class="field-body">24-Apr-2006, 5-Sep-2006</td>
46 </tr>
47 </tbody>
48 </table>
49 <hr />
50 <div class="contents topic">
51 <p class="topic-title first"><a id="contents" name="contents">Contents</a></p>
52 <ul class="simple">
53 <li><a class="reference" href="#abstract" id="id2" name="id2">Abstract</a></li>
54 <li><a class="reference" href="#motivation" id="id3" name="id3">Motivation</a></li>
55 <li><a class="reference" href="#specification" id="id4" name="id4">Specification</a></li>
56 <li><a class="reference" href="#backwards-compatibility" id="id5" name="id5">Backwards Compatibility</a></li>
57 <li><a class="reference" href="#copyright" id="id6" name="id6">Copyright</a></li>
58 </ul>
59 </div>
60 <div class="section">
61 <h1><a class="toc-backref" href="#id2" id="abstract" name="abstract">Abstract</a></h1>
62 <p>This GLEP outlines the abilities and purpose of the Quality Assurance team
63 for Gentoo.</p>
64 </div>
65 <div class="section">
66 <h1><a class="toc-backref" href="#id3" id="motivation" name="motivation">Motivation</a></h1>
67 <p>For years now developers have been saying how we need an empowered QA team to
68 handle problems concerning the tree. This GLEP provides the structure for
69 such a team and specifies the roles the team would fulfill.</p>
70 </div>
71 <div class="section">
72 <h1><a class="toc-backref" href="#id4" id="specification" name="specification">Specification</a></h1>
73 <p>The QA team should be given certain abilities to look out for the best
74 interests of all developers, as well as our users. The QA team should also
75 work to ensure developers have the information they need, and that packages
76 are maintained.</p>
77 <ul class="simple">
78 <li>The QA team's purpose is to provide cross-team assistance in keeping the
79 tree in a good state. This is done primarily by finding and pointing out
80 issues to maintainers and, where necessary, taking direct action.</li>
81 <li>In case of emergency, or if package maintainers refuse to cooperate,
82 the QA team may take action themselves to fix the problem. The QA team
83 does not want to override the maintainer's wishes by default, but only
84 wish to do so when the team finds it is in the best interest of users and
85 fellow developers to have the issue addressed as soon as possible.</li>
86 <li>The QA team may also offer to fix obvious typos and similar minor issues,
87 and silence from the package maintainers can be taken as agreement in such
88 situations. Coding style issues fall under this category, and while they
89 are not severe, they can make automated checks of the tree more difficult.</li>
90 <li>There will be cases when our tools are incapable of handling a certain
91 situation and policy must be broken in order to get something working
92 completely. This will hopefully not occur very often but each time it
93 does occur, the QA team and the maintainer will come to some agreement on
94 an interim solution and it is expected that a bug will be opened with the
95 appropriate team to work towards a correct solution.</li>
96 <li>In the case of disagreement among QA members the majority of established
97 QA members must agree with the action. Some examples of disagreements are:
98 whether the percieved problem violates the policy or whether the solution
99 makes the situation worse.</li>
100 <li>In the event that a developer still insists that a package does not break
101 QA standards, an appeal can be made at the next council meeting. The package
102 should be dealt with per QA's request until such a time that a decision is
103 made by the council.</li>
104 <li>Just because a particular QA violation has yet to cause an issue does not
105 change the fact that it is still a QA violation.</li>
106 <li>If a particular developer persistently causes breakage, the QA team
107 may request that devrel re-evaluates that developer's commit rights.
108 Evidence of past breakages will be presented with this request to devrel.</li>
109 <li>The QA team will maintain a list of current &quot;QA Standards&quot; with explanations
110 as to why they are problems, and how to fix the problem. The list is not
111 meant by any means to be a comprehensive document, but rather a dynamic
112 document that will be updated as new problems are discovered. The QA team
113 will also do their best to ensure all developer tools are in line with the
114 current QA standards.</li>
115 <li>In order to join the QA team, you must be a developer for at least 4 months
116 and must ask the current lead for approval.</li>
117 <li>The QA team will work with Recruiters to keep related documentation and
118 quizzes up to date, so that up and coming developers will have access to all
119 of the necessary information to avoid past problems.</li>
120 <li>QA will take an active role in cleaning up and removing from the tree
121 unmaintained packages as they are found to be broken. It is also
122 encouraged of members of the QA team to assist in mentoring new developers
123 that wish to take over unmaintained packages/herds.</li>
124 </ul>
125 </div>
126 <div class="section">
127 <h1><a class="toc-backref" href="#id5" id="backwards-compatibility" name="backwards-compatibility">Backwards Compatibility</a></h1>
128 <p>Not a problem for this GLEP.</p>
129 </div>
130 <div class="section">
131 <h1><a class="toc-backref" href="#id6" id="copyright" name="copyright">Copyright</a></h1>
132 <p>This document has been placed in the public domain.</p>
133 </div>
134
135 </div>
136 <div class="footer">
137 <hr class="footer" />
138 <a class="reference" href="glep-0048.txt">View document source</a>.
139 Generated on: 2007-10-13 13:39 UTC.
140 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.
141
142 </div>
143 </body>
144 </html>

  ViewVC Help
Powered by ViewVC 1.1.20