/[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.7 - (show annotations) (download) (as text)
Wed Sep 14 10:58:27 2011 UTC (2 years, 11 months ago) by tove
Branch: MAIN
CVS Tags: HEAD
Changes since 1.6: +39 -31 lines
File MIME type: text/html
Update the html version of GLEP 48 (QA Team's Role and Purpose) (#362803)

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

  ViewVC Help
Powered by ViewVC 1.1.20