1 |
On Sat, Sep 02, 2006 at 12:13:13AM +0200, Stefan Schweizer wrote: |
2 |
> As requested by multiple devs in my last mail thread about this I have |
3 |
> written a GLEP. I send this here before sending to gentoo-dev@ so that |
4 |
> I can gather what devrel thinks about it. Please have a look. |
5 |
|
6 |
Perhaps not what devrel thinks but i'll rather drop my personal |
7 |
opinion. |
8 |
First off, imo there should have been a GLEP before, or this one |
9 |
should GLEP up stuff that is used as the starting point of this GLEP, |
10 |
more see below. |
11 |
|
12 |
> Current situation |
13 |
> ================ |
14 |
> |
15 |
> Currently there are specific deals with arch testers and devrel/infra to allow |
16 |
> arch testers to edit bugs. This GLEP is written to standardize the process and |
17 |
> make it available for all aspects of Gentoo where work is being done by people |
18 |
> who are no full developers. |
19 |
|
20 |
This is very vague. What kind of contributors are you talking about? I |
21 |
assume you mean people contributing on sunrise, or does that also |
22 |
imply people who contribute to another project should get those |
23 |
privileges, too? What kind of people do you have in mind? |
24 |
Does that mean the contributors become official project members like |
25 |
devs/ATs? |
26 |
|
27 |
> Requirements |
28 |
> ============ |
29 |
> |
30 |
> Bugzilla permissions |
31 |
> ------------ |
32 |
> |
33 |
> It is needed that contributors who work on bugs can edit them on their own and |
34 |
> do not have to rely on their mentoring or supervising developers to reassign |
35 |
> or modify bugs. |
36 |
|
37 |
Stupid question, but why don't they do the quiz and become developer/staff/AT |
38 |
if they want to work on bugs? What's the reasoning to make another |
39 |
class of users who can edit bugs? Also is bugzi rights _all_ they are |
40 |
supposed to get or other stuff, too? |
41 |
Also, what kind of bugzi permissions are we talking about, just |
42 |
marking bugs as fixed? |
43 |
|
44 |
> An example for this has been obvious since the overlays project was established. |
45 |
> Bugs for overlays should be filed on bugs.gentoo.org and will most likely get |
46 |
> assigned to the developer/herd. This does allow a contributor to fix the bug |
47 |
> but only to mark it as fixed in bugzilla when he is also an arch tester. |
48 |
|
49 |
That's one of the reasons why sunrise should have been GLEPed from the |
50 |
beginning rather than finding out there are some substantial work flow |
51 |
and permission problems. ;-) |
52 |
|
53 |
> Security |
54 |
> ----------------- |
55 |
> |
56 |
> To ensure that not everyone who asks for it can get access to edit bugs it is |
57 |
> required to complete the ebuild quiz prior to requesting access |
58 |
|
59 |
The ebuild quiz is also used in the AT project, so what exactly would |
60 |
be the difference between your contributor and and an AT/HT? |
61 |
|
62 |
> Management |
63 |
> --------------- |
64 |
> |
65 |
> This cannot be managed by devrel, because they lack the resources to do it. |
66 |
|
67 |
s/devrel/recruiters and have you talked it over with them or is this |
68 |
only an assumption? I'm not saying they do have the resources, but |
69 |
that statement sounds rather final for the first version of a GLEP. |
70 |
|
71 |
|
72 |
Executive summary (+ some more opinion): |
73 |
The whole glep is very vague, please be a bit more specific. |
74 |
Also, there really should be a good reason to introduce a new class of |
75 |
"official Gentoo people with extra permissions" as well as a |
76 |
difference to the ATs. Currently contributor and AT seem to have both |
77 |
the same requirements and permissions. |
78 |
|
79 |
cheers, |
80 |
Wernfried |
81 |
|
82 |
-- |
83 |
Wernfried Haas (amne) - amne at gentoo dot org |
84 |
Gentoo Forums: http://forums.gentoo.org |
85 |
IRC: #gentoo-forums on freenode - email: forum-mods at gentoo dot org |