summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
Diffstat (limited to 'glep-0041.rst')
-rw-r--r--glep-0041.rst83
1 files changed, 83 insertions, 0 deletions
diff --git a/glep-0041.rst b/glep-0041.rst
new file mode 100644
index 0000000..71b6a7b
--- /dev/null
+++ b/glep-0041.rst
@@ -0,0 +1,83 @@
+GLEP: 41
+Title: Making Arch Testers official Gentoo Staff
+Version: $Revision$
+Last-Modified: $Date$
+Author: Simon Stelling <blubb@gentoo.org>, Homer Parker <hparker@gentoo.org>
+Status: Rejected
+Type: Standards Track
+Content-Type: text/x-rst
+Created: 7-Sep-2005
+Post-History: 15-Sep-2005, 13-Nov-2005, 17-Aug-2007
+
+Abstract
+========
+
+Arch Testers should be treated as official Gentoo staff.
+
+Status
+======
+
+Rejected by the Gentoo Council on 13 Oct. 2005. This GLEP may be resubmitted
+if the issues brought up in the council meeting,
+http://www.gentoo.org/proj/en/council/meeting-logs/20051013.txt,
+are addressed in a new version of this GLEP.
+
+
+Motivation
+==========
+
+Since Mike Doty (kingtaco) created an Arch Tester (AT) project in January 2005
+to reduce the developer's load and the amount of open keywording bugs for the
+amd64 porting team, many users have volunteered to become ATs. They are doing
+a fair share of everyday's work to keep the amd64 and ppc trees up to date.
+While they spent many hours and even had to pass the staff quiz, they are
+currently not recognized as official members of Gentoo.
+
+
+Specification
+=============
+
+ATs should basically be treated as staff. This includes the following changes
+to the current situation:
+
+- Get a @(subdomain_to_be_determined).gentoo.org email address. The email
+ address will just be an alias, and will be forwarded to their @gentoo.org
+ address if they go on to become a Gentoo developer.
+- Get read-only access to the gentoo-x86 repository. This doesn't have to be
+ individual accounts, a single account, without a shell, with all of their
+ keys will be sufficient.
+
+There will be a 30 day probationary/mentoring period for new ATs.The lead AT/HT
+for arch/herd will be responsible for the mentoring period. If arch/herd
+doesn't have a Lead AT/HT, then either the arch/herd lead or the Strategic AT
+Lead will be responsible. The Lead AT is a seasoned developer that watches for talent,
+recruits and mentors ATs. Additionally, the mentoring period should be shortened
+to a minimum of two weeks if an AT wants to take the end quiz to become a developer,
+assuming he has been AT for at least two weeks. The amd64 porting team has handled
+situations like this for a while and only made positive experiences.
+
+Also, the idea of an arch tester as a trustworthy user who is able to test
+critical changes (such as hard masked software branches), could be expanded
+to other herds. These 'ATs' wouldn't be called arch testers as the 'arch' is
+irritating, instead, herd tester (HT) could be used.
+
+As arch testers (and herd testers) become official staff, they should be
+handled by DevRel.
+
+Since ATs don't want to have to handle the big 'communication overhead'
+normally, they won't be subscribed to the gentoo-core mailing list and won't
+be able to vote.
+
+
+Backwards Compatibility
+=======================
+
+All current active arch testers should be migrated.
+
+
+Copyright
+=========
+
+This work is licensed under the Creative Commons Attribution-ShareAlike 3.0
+Unported License. To view a copy of this license, visit
+http://creativecommons.org/licenses/by-sa/3.0/.