1 |
> Please elaborate on how a "full.fledged developer" would differ from a |
2 |
> "package maintainer" technically. What requirements and/or |
3 |
> priviledges do you think could be reduced? |
4 |
|
5 |
I haven't thought that through fully (in hopes of a few good |
6 |
suggestions!), but off the top of my head, maintainers don't need to |
7 |
complete the staff quiz. On the technical side, about the only thing |
8 |
they really require is a sound knowledge of bash, the do's and don'ts |
9 |
of ebuilds, and knowledge of how to use eclasses. Perhaps we can |
10 |
create a separate quiz for maintainers, which stresses on versioning, |
11 |
handling bump requests, keeping ebuilds clean etc, and nothing more. |
12 |
I'm willing to help form the quiz, but I certainly can't do it alone. |
13 |
|
14 |
As for the privileges, maintainers wouldn't need an email account, |
15 |
commit access to portions not concerning their package(s), voice on |
16 |
#gentoo-dev... Essentially, we need to keep limit the privileges to |
17 |
whatever infra can provide within reasonable limits - I expect the |
18 |
number of maintainers to be far greater than the developer count. |
19 |
|
20 |
On another note, we may introduce a rule that no package may be marked |
21 |
stable unless a "full-fledged developer" or QA member has approved it |
22 |
(along with the usual arch-tester stamp). This might help in ensuring |
23 |
the quality of our stable tree. |
24 |
|
25 |
-- |
26 |
Anant |
27 |
-- |
28 |
gentoo-dev@l.g.o mailing list |