| … | |
… | |
| 2 | <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> |
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"> |
3 | <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> |
| 4 | |
4 | |
| 5 | <head> |
5 | <head> |
| 6 | <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> |
6 | <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> |
| 7 | <meta name="generator" content="Docutils 0.4: http://docutils.sourceforge.net/" /> |
7 | <meta name="generator" content="Docutils 0.8.1: http://docutils.sourceforge.net/" /> |
| 8 | <title>GLEP 48 -- QA Team's Role and Purpose</title> |
8 | <title>GLEP 48 -- QA Team's Role and Purpose</title> |
| 9 | <link rel="stylesheet" href="tools/glep.css" type="text/css" /> |
9 | <link rel="stylesheet" href="tools/glep.css" type="text/css" /></head> |
| 10 | </head> |
|
|
| 11 | <body bgcolor="white"> |
10 | <body bgcolor="white"> |
| 12 | <table class="navigation" cellpadding="0" cellspacing="0" |
11 | <table class="navigation" cellpadding="0" cellspacing="0" |
| 13 | width="100%" border="0"> |
12 | width="100%" border="0"> |
| 14 | <tr><td class="navicon" width="150" height="35"> |
13 | <tr><td class="navicon" width="150" height="35"> |
| 15 | <a href="http://www.gentoo.org/" title="Gentoo Linux Home Page"> |
14 | <a href="http://www.gentoo.org/" title="Gentoo Linux Home Page"> |
| … | |
… | |
| 26 | <tbody valign="top"> |
25 | <tbody valign="top"> |
| 27 | <tr class="field"><th class="field-name">GLEP:</th><td class="field-body">48</td> |
26 | <tr class="field"><th class="field-name">GLEP:</th><td class="field-body">48</td> |
| 28 | </tr> |
27 | </tr> |
| 29 | <tr class="field"><th class="field-name">Title:</th><td class="field-body">QA Team's Role and Purpose</td> |
28 | <tr class="field"><th class="field-name">Title:</th><td class="field-body">QA Team's Role and Purpose</td> |
| 30 | </tr> |
29 | </tr> |
| 31 | <tr class="field"><th class="field-name">Version:</th><td class="field-body">1.3</td> |
30 | <tr class="field"><th class="field-name">Version:</th><td class="field-body">1.4</td> |
| 32 | </tr> |
31 | </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> |
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> |
| 34 | </tr> |
33 | </tr> |
| 35 | <tr class="field"><th class="field-name">Author:</th><td class="field-body">Mark Loeser <halcy0n at gentoo.org>,</td> |
34 | <tr class="field"><th class="field-name">Author:</th><td class="field-body">Mark Loeser <halcy0n at gentoo.org>,</td> |
| 36 | </tr> |
35 | </tr> |
| 37 | <tr class="field"><th class="field-name">Status:</th><td class="field-body">Final</td> |
36 | <tr class="field"><th class="field-name">Status:</th><td class="field-body">Final</td> |
| 38 | </tr> |
37 | </tr> |
| 39 | <tr class="field"><th class="field-name">Type:</th><td class="field-body">Standards Track</td> |
38 | <tr class="field"><th class="field-name">Type:</th><td class="field-body">Standards Track</td> |
| 40 | </tr> |
39 | </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> |
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> |
| 42 | </tr> |
41 | </tr> |
| 43 | <tr class="field"><th class="field-name">Created:</th><td class="field-body">24 April 2006</td> |
42 | <tr class="field"><th class="field-name">Created:</th><td class="field-body">24 April 2006</td> |
| 44 | </tr> |
43 | </tr> |
| 45 | <tr class="field"><th class="field-name">Post-History:</th><td class="field-body">24-Apr-2006, 5-Sep-2006</td> |
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> |
| 46 | </tr> |
45 | </tr> |
| 47 | </tbody> |
46 | </tbody> |
| 48 | </table> |
47 | </table> |
| 49 | <hr /> |
48 | <hr /> |
| 50 | <div class="contents topic"> |
49 | <div class="contents topic" id="contents"> |
| 51 | <p class="topic-title first"><a id="contents" name="contents">Contents</a></p> |
50 | <p class="topic-title first">Contents</p> |
| 52 | <ul class="simple"> |
51 | <ul class="simple"> |
| 53 | <li><a class="reference" href="#abstract" id="id2" name="id2">Abstract</a></li> |
52 | <li><a class="reference internal" href="#abstract" id="id2">Abstract</a></li> |
| 54 | <li><a class="reference" href="#motivation" id="id3" name="id3">Motivation</a></li> |
53 | <li><a class="reference internal" href="#motivation" id="id3">Motivation</a></li> |
| 55 | <li><a class="reference" href="#specification" id="id4" name="id4">Specification</a></li> |
54 | <li><a class="reference internal" href="#specification" id="id4">Specification</a></li> |
| 56 | <li><a class="reference" href="#backwards-compatibility" id="id5" name="id5">Backwards Compatibility</a></li> |
55 | <li><a class="reference internal" href="#backwards-compatibility" id="id5">Backwards Compatibility</a></li> |
| 57 | <li><a class="reference" href="#copyright" id="id6" name="id6">Copyright</a></li> |
56 | <li><a class="reference internal" href="#copyright" id="id6">Copyright</a></li> |
| 58 | </ul> |
57 | </ul> |
| 59 | </div> |
58 | </div> |
| 60 | <div class="section"> |
59 | <div class="section" id="abstract"> |
| 61 | <h1><a class="toc-backref" href="#id2" id="abstract" name="abstract">Abstract</a></h1> |
60 | <h1><a class="toc-backref" href="#id2">Abstract</a></h1> |
| 62 | <p>This GLEP outlines the abilities and purpose of the Quality Assurance team |
61 | <p>This GLEP outlines the abilities and purpose of the Quality Assurance team |
| 63 | for Gentoo.</p> |
62 | for Gentoo.</p> |
| 64 | </div> |
63 | </div> |
| 65 | <div class="section"> |
64 | <div class="section" id="motivation"> |
| 66 | <h1><a class="toc-backref" href="#id3" id="motivation" name="motivation">Motivation</a></h1> |
65 | <h1><a class="toc-backref" href="#id3">Motivation</a></h1> |
| 67 | <p>For years now developers have been saying how we need an empowered QA team to |
66 | <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 |
67 | handle problems concerning the tree. This GLEP provides the structure for |
| 69 | such a team and specifies the roles the team would fulfill.</p> |
68 | such a team and specifies the roles the team would fulfill.</p> |
| 70 | </div> |
69 | </div> |
| 71 | <div class="section"> |
70 | <div class="section" id="specification"> |
| 72 | <h1><a class="toc-backref" href="#id4" id="specification" name="specification">Specification</a></h1> |
71 | <h1><a class="toc-backref" href="#id4">Specification</a></h1> |
| 73 | <p>The QA team should be given certain abilities to look out for the best |
72 | <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 |
73 | 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 |
74 | work to ensure developers have the information they need, and that packages |
| 76 | are maintained.</p> |
75 | are maintained. The QA team is also tasked with the authority to ensure |
|
|
76 | tree policies are respected.</p> |
| 77 | <ul class="simple"> |
77 | <ul class="simple"> |
| 78 | <li>The QA team's purpose is to provide cross-team assistance in keeping the |
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 |
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> |
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> |
| 81 | <li>In case of emergency, or if package maintainers refuse to cooperate, |
92 | <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 |
93 | 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 |
94 | 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 |
95 | 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> |
96 | fellow developers to have the issue addressed as soon as possible.</li> |
| … | |
… | |
| 110 | as to why they are problems, and how to fix the problem. The list is not |
121 | 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 |
122 | 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 |
123 | 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 |
124 | will also do their best to ensure all developer tools are in line with the |
| 114 | current QA standards.</li> |
125 | 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 |
126 | <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 |
127 | 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> |
128 | 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 |
129 | <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 |
130 | 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 |
131 | encouraged of members of the QA team to assist in mentoring new developers |
| 123 | that wish to take over unmaintained packages/herds.</li> |
132 | that wish to take over unmaintained packages/herds.</li> |
| 124 | </ul> |
133 | </ul> |
| 125 | </div> |
134 | </div> |
| 126 | <div class="section"> |
135 | <div class="section" id="backwards-compatibility"> |
| 127 | <h1><a class="toc-backref" href="#id5" id="backwards-compatibility" name="backwards-compatibility">Backwards Compatibility</a></h1> |
136 | <h1><a class="toc-backref" href="#id5">Backwards Compatibility</a></h1> |
| 128 | <p>Not a problem for this GLEP.</p> |
137 | <p>Not a problem for this GLEP.</p> |
| 129 | </div> |
138 | </div> |
| 130 | <div class="section"> |
139 | <div class="section" id="copyright"> |
| 131 | <h1><a class="toc-backref" href="#id6" id="copyright" name="copyright">Copyright</a></h1> |
140 | <h1><a class="toc-backref" href="#id6">Copyright</a></h1> |
| 132 | <p>This document has been placed in the public domain.</p> |
141 | <p>This document has been placed in the public domain.</p> |
| 133 | </div> |
142 | </div> |
| 134 | |
143 | |
| 135 | </div> |
144 | </div> |
| 136 | <div class="footer"> |
145 | <div class="footer"> |
| 137 | <hr class="footer" /> |
146 | <hr class="footer" /> |
| 138 | <a class="reference" href="glep-0048.txt">View document source</a>. |
147 | <a class="reference external" href="glep-0048.txt">View document source</a>. |
| 139 | Generated on: 2007-10-13 13:39 UTC. |
148 | Generated on: 2011-09-14 10:49 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. |
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. |
| 141 | |
150 | |
| 142 | </div> |
151 | </div> |
| 143 | </body> |
152 | </body> |
| 144 | </html> |
153 | </html> |
| 145 | |
|
|