* Re: [gentoo-project] Upcoming council meeting - Wednesday, 8th of June, 1900 UTC
@ 2011-06-01 0:07 99% ` Jorge Manuel B. S. Vicetto
0 siblings, 0 replies; 1+ results
From: Jorge Manuel B. S. Vicetto @ 2011-06-01 0:07 UTC (permalink / raw
To: gentoo-project
[-- Attachment #1.1: Type: text/plain, Size: 1082 bytes --]
On 01-06-2011 00:01, Jorge Manuel B. S. Vicetto wrote:
> Hello fellow developers and community,
>
> The Gentoo Council will conduct its next meeting on Wednesday, 8th of
> June, at 1900 UTC [1] in the #gentoo-council channel of the Freenode
> IRC network.
>
> Meeting agenda:
>
> * roll call
>
> * ChangeLog policy
> * GLEP48 review
I'm attaching a patch to the current GLEP48 text[2]. This is my proposal
for the update of this GLEP. I've included the text already approved in
the March meeting of the council and that wasn't committed yet.
> * open bugs with council involvement
> * next meeting date / chair
> * open floor - listen to the community
>
> If you have anything you'd like to push to the council for
> discussion, feel free to reply to this thread.
>
> [1] http://www.gentoo.org/proj/en/council/utctolocal.html?time=2000
>
[2] - http://www.gentoo.org/proj/en/glep/glep-0048.txt
--
Regards,
Jorge Vicetto (jmbsvicetto) - jmbsvicetto at gentoo dot org
Gentoo- forums / Userrel / Devrel / KDE / Elections / RelEng
[-- Attachment #1.2: glep-0048.patch --]
[-- Type: text/plain, Size: 4901 bytes --]
? glep-0048.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 -B -r1.3 glep-0048.txt
--- glep-0048.txt 5 Sep 2006 20:36:38 -0000 1.3
+++ glep-0048.txt 31 May 2011 23:45:16 -0000
@@ -1,13 +1,13 @@
GLEP: 48
Title: QA Team's Role and Purpose
-Version: $Revision: 1.3 $
-Last-Modified: $Date: 2006/09/05 20:36:38 $
+Version: $Revision: 1.4 $
+Last-Modified: $Date: 2011/06/08 20:36:38 $
Author: Mark Loeser <halcy0n@gentoo.org>,
Status: Final
Type: Standards Track
Content-Type: text/x-rst
Created: 24 April 2006
-Post-History: 24-Apr-2006, 5-Sep-2006
+Post-History: 24-Apr-2006, 5-Sep-2006, 8-Jun-2011
Abstract
@@ -29,11 +29,23 @@
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
@@ -59,17 +71,32 @@
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.
+* QA team members are expected to follow and enforce approved policies, so
+ the team members need to give the example. Refusal to comply with the
+ existing policies may lead to removal from the team.
+* In case a particular developer is an immediate danger or persistently causes
+ breakage to the tree, either the QA lead or two members of the QA team may
+ request commit rights of given developer to be suspended by anyone with such
+ privileges (currently Infra and Devrel team).
+* If a developer refuses to follow and or publicly defies approved policies,
+ the QA team may ask for commit privileges suspension for as long as the
+ team finds appropriate or until the developer is ready to comply with said
+ policy, following the rules in the previous point.
+* Any disagrement about a particular approved tree policy may be appealed to
+ the council, but all developers are expected to comply with policies until
+ they are revised or withdrawn.
+* As long as the developer misbehaviour is limited to technical issues in the
+ tree, the issue shall be dealt by the QA team. If the developer exhibits
+ further problems, the issue shall be escalated to DevRel.
+* Whenever the QA team escalates an issue to DevRel, it shall have 15 days to
+ present the case and provide support evidence. DevRel shall then follow its
+ established policies to evaluate it.
* 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.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 900 bytes --]
^ permalink raw reply [relevance 99%]
Results 1-1 of 1 | reverse | options above
-- pct% links below jump to the message on this page, permalinks otherwise --
2011-06-01 0:01 [gentoo-project] Upcoming council meeting - Wednesday, 8th of June, 1900 UTC Jorge Manuel B. S. Vicetto
2011-06-01 0:07 99% ` Jorge Manuel B. S. Vicetto
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox