Gentoo Archives: gentoo-dev

From: Martin Schlemmer <azarah@××××××××××××.org>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] GLEP 41: Making Arch Testers official Gentoo Staff
Date: Mon, 12 Sep 2005 20:14:19
Message-Id: 1126555690.14207.93.camel@lycan.lan
In Reply to: [gentoo-dev] GLEP 41: Making Arch Testers official Gentoo Staff by Simon Stelling
1 On Mon, 2005-09-12 at 21:39 +0200, Simon Stelling wrote:
2
3 > ATs should basically be treated as staff. This includes the following changes
4 > to the current situation:
5 >
6 > - Get a @gentoo.org email address
7
8 Personally think this might only be fair.
9
10 > - Get read-only access to the gentoo-x86 repository
11 >
12
13 Can understand the reasoning for this ... we have acl's, etc to make
14 this possible?
15
16 > Additionally, the mentoring period should be shortened to two weeks if an AT
17 > wants to take the end quiz to become a developer, assuming he has been AT for
18 > at least two weeks. Users which want to become developers should also run
19 > through the process of an AT. The amd64 porting team has handled situations
20 > like this for a while and only made positive experiences.
21 >
22
23 Not too familiar on this, so i guess its going to depend on how thorough
24 the planned (new?) AT tests are.
25
26 > Also, the idea of an arch tester as a trustful user who is able to test
27 > critical changes (such as hard masked software branches), should be expanded
28 > to every herd. These 'ATs' wouldn't be called arch testers as the 'arch' is
29 > irritating, instead, herd tester (HT) could be used.
30 >
31 > As arch testers (and herd testers) become official staff, they should be
32 > handled by DevRel.
33 >
34 >
35 > Backwards Compatibility
36 > =======================
37 >
38 > All current arch testers should be migrated to staff.
39 >
40 >
41 > Copyright
42 > =========
43 >
44 > This document has been placed in the public domain.
45 >
46 --
47 Martin Schlemmer

Attachments

File name MIME type
signature.asc application/pgp-signature