diff --git a/glep-0048.txt b/glep-0048.new.txt
index c894556..9711797 100755
@@ -34,6 +34,19 @@ are maintained.
* 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. The deputy has all his powers directly
+ delegated from the QA team lead and thus his actions and decisions should
+ be considered equal to those of the QA team lead. Deputy is directly
+ responsible only to the QA team lead.
+* The QA team lead may approve developers who apply to be team members. By
+ doing this he (or she) will accept responsibility to direct them as part
+ of the team and will be held responsible for any actions the team member
+ takes on behalf of the QA team.
+* Any QA team lead decision can be revoked by major opposing vote from
+ all current QA members. Given the nature of this action new elections
+ should be held within 1 month to elect a new QA team lead.
* 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 +72,23 @@ are maintained.
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 commit rights of given developer to be suspended by
+ the Infra team. Devrel should then proceed to evaluate the situation, by
+ finding a compromise or pernamently revoking those rights.
+* Should a situation arise where a developer causes breakage to the point
+ that it cannot be ascribed to bona-fide mistake, either the QA 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 by QA team within 14 days of said suspension.
+ Resolution for these kind of issues is completely in hands of the QA team
+ and only the Gentoo Council can revisit the case.
* 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.