Gentoo Archives: gentoo-dev

From: Chris White <chriswhite@g.o>
To: gentoo-dev@l.g.o
Subject: [gentoo-dev] [Summary] GLEP 41: Making Arch Testers official Gentoo Staff
Date: Mon, 12 Sep 2005 22:30:33
1 Leave to gleps to make long threads ;).
3 So anyways, here's what the deal is so far:
5 Simon Stelling(blubb) starts out by producing the glep. For those of you that
6 have no idea, arch testers were something mainly promoted by the amd64 team.
7 Basically, arch testers are non gentoo devs that do architecture testing and
8 nothing more. Testing ebuilds, helping with bugs, that kind of thing.
10 So basically, Simon wants arch testers to become official devs (with limited
11 restrictions). They've taken the staff quiz already, and he wants them to be
12 officially and _read only_ access to the portage tree. If
13 they want read/write access they do the usual stuff to become a dev and all
14 is happy.
16 Ciaran McCreesh(ciaranm) then comes in asking for numbers. You know, how many
17 are arch testers, how many went inactive, that sort of thing...
19 Martin Schlemmer(azarah) agrees with Ciaran and states that these numbers
20 should be provided before addressing the glep. Should the numbers be
21 reasonable, a probation period should be created to see how it all works out.
23 Olivier Crete(tester) comes up with some numbers [1] and asks about council
24 voting privileges.
26 Stephen P. Becker(geoman) that this is short of giving them commit access to
27 the tree. He would like arch testers to be somewhat of a probation period
28 from being a full dev.
30 Simon Stelling(blubb) says that that's fine and dandy, but also notes that not
31 all Arch Testers(I'm lazy and will call them AT's now..) want to become devs,
32 and some AT's will still be left.
34 Martin Schlemmer(azarah) comments that all the above appear ok, and asks if
35 cvs has the access control to handle read only for the main gentoo-x86 cvs
36 branch. He's ok with the whole email assignment though. One
37 ponit he makes is about the arch tests, in order for users to become an amd64
38 dev, they have to go through the arch test too. He just wants to make sure
39 the arch tests are solid enough.
41 Donnie Berkholz(spyderous) wants clarification on users having to become arch
42 testers in order to become arch devs.
44 Stephen P. Becker(geoman) still thinks that arch testers should become devs,
45 and that if a mips arch tester came along and was good, they'd skip steps and
46 make said person a dev.
48 Homer Parker(hparker) states that this glep was made for the arch testers that
49 don't wish to become devs, because of time restraints or commitment. Homer
50 also notes that AT's have been effectively utilized for amd64 and ppc.
52 Stephen P. Becker(geoman) questions why these arch testers should become devs
53 if they get more access than some other devs get.
55 Homer Parker(hparker) asks what privileges that at's get that most devs don't.
57 Simon Stelling (blubb) posts some facts, which I'll put here because they're
58 short and important:
60 "As of now, amd64 has 20 ATs, 6 of them became devs, 1 is inactive. The rest
61 stayed AT. The "oldest" of the remaining has been AT since February, the
62 youngest since Aug 23, so I think it definitively is."
64 Homer Parker(hparker) states ppc has 3-4 AT's
66 Joseph Jezak(josejx) clarifies ppc has 3 devs, and 1 has become an official
67 dev.
69 Simon Stelling(blubb) clarifies that users should become AT members before
70 becoming a dev, but emphasizes should, as this can be different in some
71 situations.
73 Homer Parker(hparker) mentions that the AT before dev requirement has worked
74 well with amd64, and that if they see an AT member with skills, they will
75 approach them about becomming a dev.
77 So there's your summary of glep 41 so far.
79 If this gets any larger I'll make a part II :p.
81 [1]
83 Chris White