en/glep/glep-0041.txt

GLEP: 41
Title: Making Arch Testers official Gentoo Staff
Version: $Revision: $
Last-Modified: $Date: $
Author: Simon Stelling <blubb@gentoo.org>,
Status: Draft
Type: Standards Track
Content-Type: text/x-rst
Created: 7-Sep-2005
Post-History: 15-Sep-2005

Abstract
========

Arch Testers should be treated as official Gentoo staff.


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 @gentoo.org email address
- Get read-only access to the gentoo-x86 repository

Additionally, the mentoring period should be shortened to 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 trustful user who is able to test
critical changes (such as hard masked software branches), could be expanded
to other herd. 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.


Backwards Compatibility
=======================

All current active arch testers should be migrated to staff.


Copyright
=========

This document has been placed in the public domain.
1	g2boojum	1.1	GLEP: 41
2			Title: Making Arch Testers official Gentoo Staff
3			Version: $Revision: $
4			Last-Modified: $Date: $
5			Author: Simon Stelling <blubb@gentoo.org>,
6			Status: Draft
7			Type: Standards Track
8			Content-Type: text/x-rst
9			Created: 7-Sep-2005
10			Post-History: 15-Sep-2005
11
12			Abstract
13			========
14
15			Arch Testers should be treated as official Gentoo staff.
16
17
18			Motivation
19			==========
20
21			Since Mike Doty (kingtaco) created an Arch Tester (AT) project in January 2005
22			to reduce the developer's load and the amount of open keywording bugs for the
23			amd64 porting team, many users have volunteered to become ATs. They are doing
24			a fair share of everyday's work to keep the amd64 and ppc trees up to date.
25			While they spent many hours and even had to pass the staff quiz, they are
26			currently not recognized as official members of Gentoo.
27
28
29			Specification
30			=============
31
32			ATs should basically be treated as staff. This includes the following changes
33			to the current situation:
34
35			- Get a @gentoo.org email address
36			- Get read-only access to the gentoo-x86 repository
37
38			Additionally, the mentoring period should be shortened to two weeks if an AT
39			wants to take the end quiz to become a developer, assuming he has been AT for
40			at least two weeks. The amd64 porting team has handled situations
41			like this for a while and only made positive experiences.
42
43			Also, the idea of an arch tester as a trustful user who is able to test
44			critical changes (such as hard masked software branches), could be expanded
45			to other herd. These 'ATs' wouldn't be called arch testers as the 'arch' is
46			irritating, instead, herd tester (HT) could be used.
47
48			As arch testers (and herd testers) become official staff, they should be
49			handled by DevRel.
50
51
52			Backwards Compatibility
53			=======================
54
55			All current active arch testers should be migrated to staff.
56
57
58			Copyright
59			=========
60
61			This document has been placed in the public domain.