? glep-48-changes.patch
Index: glep-0048.txt
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/glep/glep-0048.txt,v
retrieving revision 1.3
diff -u -B -r1.3 glep-0048.txt
--- glep-0048.txt	5 Sep 2006 20:36:38 -0000	1.3
+++ glep-0048.txt	20 Jan 2011 02:36:49 -0000
@@ -34,6 +34,14 @@
 * The QA team's purpose is to provide cross-team assistance in keeping the
   tree in a good state. This is done primarily by finding and pointing out
   issues to maintainers and, where necessary, taking direct action.
+* The QA team is directed by a lead, chosen yearly by private or
+  public election among the members of the team. The QA team lead can
+  choose one member as deputy, whose decisions should be considered as
+  they were made by the lead in case he (or she) is not available.
+* The QA team lead approves applicant developers as team members.  By
+  doing this he (or she) will accept to direct them as part of the team
+  and will be held responsible for their actions, as taken on behalf
+  of the QA team.
 * In case of emergency, or if package maintainers refuse to cooperate,
   the QA team may take action themselves to fix the problem.  The QA team
   does not want to override the maintainer's wishes by default, but only
@@ -59,17 +67,21 @@
   made by the council.
 * Just because a particular QA violation has yet to cause an issue does not
   change the fact that it is still a QA violation.
-* If a particular developer persistently causes breakage, the QA team
-  may request that devrel re-evaluates that developer's commit rights.
-  Evidence of past breakages will be presented with this request to devrel.
+* In case a particular developer persistently causes breakage, the QA
+  lead may request his (or her) commit rights to be suspended.  Devrel
+  should then proceed to evalute the situation, by finding a
+  compromise or definitely revoking those rights.
+* Should a situation arise where a developer causes breakage to the
+  point it cannot be ascribed to bona-fide mistake, either the lead or
+  two members of the QA team can require the Infra team to temporarily
+  suspend access to said developer, pending analysis of the causes and
+  resolution to be provided within a week of said suspension.
 * The QA team will maintain a list of current "QA Standards" with explanations
   as to why they are problems, and how to fix the problem.  The list is not
   meant by any means to be a comprehensive document, but rather a dynamic
   document that will be updated as new problems are discovered.  The QA team
   will also do their best to ensure all developer tools are in line with the
   current QA standards.
-* In order to join the QA team, you must be a developer for at least 4 months
-  and must ask the current lead for approval.
 * The QA team will work with Recruiters to keep related documentation and
   quizzes up to date, so that up and coming developers will have access to all
   of the necessary information to avoid past problems.