/[gentoo]/xml/htdocs/proj/en/glep/glep-0041.txt
Gentoo

Contents of /xml/htdocs/proj/en/glep/glep-0041.txt

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.3 - (hide annotations) (download)
Fri Nov 11 18:42:27 2005 UTC (9 years, 1 month ago) by hparker
Branch: MAIN
Changes since 1.2: +16 -8 lines
File MIME type: text/plain
Updated glep 41

1 g2boojum 1.1 GLEP: 41
2     Title: Making Arch Testers official Gentoo Staff
3 blubb 1.2 Version: $Revision: 1.2 $
4 hparker 1.3 Last-Modified: $Date: 2005/10/13 14:53:37 $
5 g2boojum 1.1 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 hparker 1.3 - Get a @(subdomain_to_be_determined).gentoo.org email address. The email
36     address will just be an alias, and will be forwarded to their @gentoo.org
37     address if they go on to become a Gentoo developer.
38     - Get read-only access to the gentoo-x86 repository. This doesn't have to be
39     individual accounts, a single account, without a shell, with all of their
40     keys will be sufficiant.
41    
42     There will be a 30 day probationary/mentoring period for new ATs.The lead AT/HT
43     for arch/herd will be responsible for the mentoring period. If arch/herd
44     doesn't have a Lead AT/HT, then either the arch/herd lead or the Strategic AT
45     Lead will be responsible. The Lead AT is a seasoned developer that watches for talent,
46     recruits and mentors ATs. Additionally, the mentoring period should be shortened
47     to a minimum of two weeks if an AT wants to take the end quiz to become a developer,
48     assuming he has been AT for at least two weeks. The amd64 porting team has handled
49     situations like this for a while and only made positive experiences.
50 g2boojum 1.1
51 blubb 1.2 Also, the idea of an arch tester as a trustworthy user who is able to test
52 g2boojum 1.1 critical changes (such as hard masked software branches), could be expanded
53 blubb 1.2 to other herds. These 'ATs' wouldn't be called arch testers as the 'arch' is
54 g2boojum 1.1 irritating, instead, herd tester (HT) could be used.
55    
56     As arch testers (and herd testers) become official staff, they should be
57     handled by DevRel.
58    
59 blubb 1.2 Since ATs don't want to have to handle the big 'communication overhead'
60     normally, they won't be subscribed to the gentoo-core mailing list and won't
61     be able to vote.
62    
63 g2boojum 1.1
64     Backwards Compatibility
65     =======================
66    
67 blubb 1.2 All current active arch testers should be migrated.
68 g2boojum 1.1
69    
70     Copyright
71     =========
72    
73     This document has been placed in the public domain.

  ViewVC Help
Powered by ViewVC 1.1.20