/[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.1 - (hide annotations) (download) (as text)
Mon Apr 24 17:51:17 2006 UTC (8 years, 3 months ago) by halcy0n
Branch: MAIN
File MIME type: text/html
add the html version of glep 48 as well

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

  ViewVC Help
Powered by ViewVC 1.1.20