--- xml/htdocs/proj/en/glep/glep-0048.html 2007/10/14 17:00:15 1.6 +++ xml/htdocs/proj/en/glep/glep-0048.html 2011/09/14 10:58:27 1.7 @@ -4,10 +4,9 @@ - + GLEP 48 -- QA Team's Role and Purpose - - + @@ -28,9 +27,9 @@ - + - + @@ -38,46 +37,58 @@ - + - +
-
-

Contents

+
+

Contents

-
-

Abstract

+
+

Abstract

This GLEP outlines the abilities and purpose of the Quality Assurance team for Gentoo.

-
-

Motivation

+
+

Motivation

For years now developers have been saying how we need an empowered QA team to handle problems concerning the tree. This GLEP provides the structure for such a team and specifies the roles the team would fulfill.

-
-

Specification

+
+

Specification

The QA team should be given certain abilities to look out for the best interests of all developers, as well as our users. The QA team should also work to ensure developers have the information they need, and that packages -are maintained.

+are maintained. The QA team is also tasked with the authority to ensure +tree policies are respected.

  • 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 a deputy. The deputy has all of 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. The deputy is directly +responsible only to the QA team lead.
  • +
  • The QA team lead must approve developers who would like to join the project. The +applicant must demonstrate a thorough understanding of the duties he would like +to perform. By accepting the applicant the QA team lead will accept +the responsibility to direct them as part of the team and will be held +responsible for any action the team member takes 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 @@ -112,8 +123,6 @@ 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.
  • @@ -123,23 +132,22 @@ that wish to take over unmaintained packages/herds.
-
-

Backwards Compatibility

+
+

Backwards Compatibility

Not a problem for this GLEP.

-
-

Copyright

+
-