Gentoo Archives: gentoo-dev

From: Mark Loeser <halcy0n@g.o>
To: gentoo-dev@l.g.o
Subject: [gentoo-dev] QA Proposal v3
Date: Sat, 22 Apr 2006 23:53:58
1 Here is the newest revision of my proposal. Not much has changed, but I
2 added and changed some small things. Constructive feedback is
3 appreciated. I'd like to get this voted on by the council at the next
4 meeting.
6 * The QA team's purpose is to provide cross-team assistance in keeping
7 the tree in a good state. This is done primarily by finding and pointing
8 out issues to maintainers and, where necessary, taking direct action.
9 * In case of emergency, or if package maintainers refuse to cooperate,
10 the QA team may take action themselves to fix the problem. The QA
11 team does not want to override the maintainer's wishes by default, but only
12 wish to do so when the team finds it is in the best interest of users
13 and fellow developers to have the issue addressed as soon as possible.
14 * The QA team may also offer to fix obvious typos and similar minor
15 issues, and silence from the package maintainers can be taken as agreement
16 in such situations. Coding style issues fall under this category, and
17 while they are not severe, they can make automated checks of the tree more
18 difficult.
19 * There will be cases when our tools are incapable of handling a certain
20 situation and policy must be broken in order to get something working
21 completely. This will hopefully not occur very often but each time it
22 does occur, the QA team and the maintainer will come to some agreement
23 on an interim solution and it is expected that a bug will be opened with
24 the appropriate team to work towards a correct solution.
25 * In the case of disagreement on policy among QA members, the majority
26 of established QA members must agree with the action.
27 * In the event that a developer still insists that a package does not
28 break QA standards, an appeal can be made at the next council meeting. The
29 package should be dealt with per QA's request until such a time that a
30 decision is made by the council.
31 * Just because a particular QA violation has yet to cause an issue does
32 not change the fact that it is still a QA violation.
33 * If a particular developer persistently causes breakage, the QA team
34 may request that devrel re-evaluates that developer's commit rights.
35 Evidence of past breakages will be presented with this request to
36 devrel.
37 * The QA team will maintain a list of current "QA Standards" with
38 explanations as to why they are problems, and how to fix the problem.
39 The list is not meant by any means to be a comprehensive document, but
40 rather a dynamic document that will be updated as new problems are
41 discovered. The QA team will also do their best to ensure all developer
42 tools are in line with the current QA standards.
43 * In order to join the QA team, you must be a developer for at least 4
44 months and must ask the current lead for approval.
45 * The QA team will work with Recruiters to keep related documentation
46 and quizzes up to date, so that up and coming developers will have access
47 to all of the necessary information to avoid past problems.
48 * QA will take an active role in cleaning up unmaintained and broken
49 packages from the tree. It is also encouraged of members of the QA team to
50 assist in mentoring new developers that wish to take over unmaintained
51 packages/herds.
54 --
55 Mark Loeser - Gentoo Developer (cpp gcc-porting qa toolchain x86)
56 email - halcy0n AT gentoo DOT org
57 mark AT halcy0n DOT com
58 web -


Subject Author
Re: [gentoo-dev] QA Proposal v3 Thomas Cort <tcort@g.o>
Re: [gentoo-dev] QA Proposal v3 Daniel Goller <morfic@g.o>
Re: [gentoo-dev] QA Proposal v3 Daniel Goller <morfic@g.o>
Re: [gentoo-dev] QA Proposal v3 Paul de Vrieze <pauldv@g.o>
Re: [gentoo-dev] QA Proposal v3 Mark Loeser <halcy0n@g.o>