| 1 | GLEP: 48 |
1 | GLEP: 48 |
| 2 | Title: QA Team's Role and Purpose |
2 | Title: QA Team's Role and Purpose |
| 3 | Version: $Revision: 1.3 $ |
3 | Version: $Revision: 1.4 $ |
| 4 | Last-Modified: $Date: 2006/09/05 20:36:38 $ |
4 | Last-Modified: $Date: 2011/06/08 20:52:01 $ |
| 5 | Author: Mark Loeser <halcy0n@gentoo.org>, |
5 | Author: Mark Loeser <halcy0n@gentoo.org>, |
| 6 | Status: Final |
6 | Status: Final |
| 7 | Type: Standards Track |
7 | Type: Standards Track |
| 8 | Content-Type: text/x-rst |
8 | Content-Type: text/x-rst |
| 9 | Created: 24 April 2006 |
9 | Created: 24 April 2006 |
| 10 | Post-History: 24-Apr-2006, 5-Sep-2006 |
10 | Post-History: 24-Apr-2006, 5-Sep-2006, 8-Jun-2011 |
| 11 | |
11 | |
| 12 | |
12 | |
| 13 | Abstract |
13 | Abstract |
| 14 | ======== |
14 | ======== |
| 15 | |
15 | |
| … | |
… | |
| 27 | ============= |
27 | ============= |
| 28 | |
28 | |
| 29 | The QA team should be given certain abilities to look out for the best |
29 | The QA team should be given certain abilities to look out for the best |
| 30 | interests of all developers, as well as our users. The QA team should also |
30 | interests of all developers, as well as our users. The QA team should also |
| 31 | work to ensure developers have the information they need, and that packages |
31 | work to ensure developers have the information they need, and that packages |
| 32 | are maintained. |
32 | are maintained. The QA team is also tasked with the authority to ensure |
|
|
33 | tree policies are respected. |
| 33 | |
34 | |
| 34 | * The QA team's purpose is to provide cross-team assistance in keeping the |
35 | * The QA team's purpose is to provide cross-team assistance in keeping the |
| 35 | tree in a good state. This is done primarily by finding and pointing out |
36 | tree in a good state. This is done primarily by finding and pointing out |
| 36 | issues to maintainers and, where necessary, taking direct action. |
37 | issues to maintainers and, where necessary, taking direct action. |
|
|
38 | * The QA team is directed by a lead, chosen yearly by private or |
|
|
39 | public election among the members of the team. The QA team lead can |
|
|
40 | choose one member as a deputy. The deputy has all of his powers directly |
|
|
41 | delegated from the QA team lead and thus his actions and decisions should |
|
|
42 | be considered equal to those of the QA team lead. The deputy is directly |
|
|
43 | responsible only to the QA team lead. |
|
|
44 | * The QA team lead must approve developers who would like to join the project. The |
|
|
45 | applicant must demonstrate a thorough understanding of the duties he would like |
|
|
46 | to perform. By accepting the applicant the QA team lead will accept |
|
|
47 | the responsibility to direct them as part of the team and will be held |
|
|
48 | responsible for any action the team member takes on behalf of the QA team. |
| 37 | * In case of emergency, or if package maintainers refuse to cooperate, |
49 | * In case of emergency, or if package maintainers refuse to cooperate, |
| 38 | the QA team may take action themselves to fix the problem. The QA team |
50 | the QA team may take action themselves to fix the problem. The QA team |
| 39 | does not want to override the maintainer's wishes by default, but only |
51 | does not want to override the maintainer's wishes by default, but only |
| 40 | wish to do so when the team finds it is in the best interest of users and |
52 | wish to do so when the team finds it is in the best interest of users and |
| 41 | fellow developers to have the issue addressed as soon as possible. |
53 | fellow developers to have the issue addressed as soon as possible. |
| … | |
… | |
| 66 | as to why they are problems, and how to fix the problem. The list is not |
78 | as to why they are problems, and how to fix the problem. The list is not |
| 67 | meant by any means to be a comprehensive document, but rather a dynamic |
79 | meant by any means to be a comprehensive document, but rather a dynamic |
| 68 | document that will be updated as new problems are discovered. The QA team |
80 | document that will be updated as new problems are discovered. The QA team |
| 69 | will also do their best to ensure all developer tools are in line with the |
81 | will also do their best to ensure all developer tools are in line with the |
| 70 | current QA standards. |
82 | current QA standards. |
| 71 | * In order to join the QA team, you must be a developer for at least 4 months |
|
|
| 72 | and must ask the current lead for approval. |
|
|
| 73 | * The QA team will work with Recruiters to keep related documentation and |
83 | * The QA team will work with Recruiters to keep related documentation and |
| 74 | quizzes up to date, so that up and coming developers will have access to all |
84 | quizzes up to date, so that up and coming developers will have access to all |
| 75 | of the necessary information to avoid past problems. |
85 | of the necessary information to avoid past problems. |
| 76 | * QA will take an active role in cleaning up and removing from the tree |
86 | * QA will take an active role in cleaning up and removing from the tree |
| 77 | unmaintained packages as they are found to be broken. It is also |
87 | unmaintained packages as they are found to be broken. It is also |
Parent Directory
| 
Revision Log
| 
Patch