1 |
On 3/5/08, Anant Narayanan <anant@g.o> wrote: |
2 |
> On 06-Mar-08, at 2:35 AM, Petteri Räty wrote: |
3 |
> > Thomas Anderson kirjoitti: |
4 |
> >> Arch Testers don't have tree access. This proposal gives the |
5 |
> >> package maintainer the ability to commit their changes. |
6 |
> > |
7 |
> > How would you ensure ebuild quality for these package maintainers? |
8 |
> |
9 |
> |
10 |
> Maintainers will also go through a recruitment process, although a |
11 |
> much shorter one which focusses only on ebuild maintenance - |
12 |
> maintainers will not have the karma to introduce new ebuilds into the |
13 |
> tree. The idea is to make the recruitment process as easy and quick as |
14 |
> possible, while ensuring that the person involved has the requisite |
15 |
> skills. |
16 |
|
17 |
Maybe break this down for me again please: |
18 |
|
19 |
What are the technical differences between a 'Package Maintainer' and |
20 |
a 'Developer'? |
21 |
|
22 |
I guess technical is the wrong word. Lets back up. What problem are |
23 |
you trying to solve? |
24 |
|
25 |
In your original mail; you stated that: |
26 |
|
27 |
a) The requirements to become a package maintainer for Gentoo may be |
28 |
lesser than that of the full-fledged developer. This serves a couple |
29 |
of purposes: |
30 |
- Users might become more motivated to becoming a maintainer for |
31 |
Gentoo, since it would require less time and effort from their end |
32 |
- Might reduce the number of orphaned packages we have in the tree |
33 |
|
34 |
So your goals are: |
35 |
|
36 |
Have more maintained packages in the tree. |
37 |
Get more people (users) involved in making Gentoo better. |
38 |
|
39 |
And you want to accomplish this by: |
40 |
|
41 |
Creating a position that has less stringent requirements to encourage |
42 |
interested folks to contribute. |
43 |
|
44 |
Your point B) also mentions removing pressure from existing developers |
45 |
by having some move to this new position to be less 'reponsible'. |
46 |
|
47 |
Can you explain how this 'Package Maintainer' is 'less responsible' |
48 |
than a full fledged developer? Can you also explain in more detail |
49 |
how the position of 'Package Maintainer' is also easier to obtain than |
50 |
the position of 'Developer'? |
51 |
|
52 |
You also stated: |
53 |
|
54 |
"Meanwhile, developers can do innovative things that they really like |
55 |
without having to maintain packages just because of a formality." |
56 |
|
57 |
I'm a bit new here; but since when was it required for a developer to |
58 |
maintain any packages? |
59 |
|
60 |
I care a lot less about how to implement this idea technically (cvs |
61 |
acls or lack of Gentoo.org e-mail address) and more so on what this |
62 |
will actually gain us; and how we should go about designing this |
63 |
position to accomplish the goals I think you want it to accomplish. |
64 |
|
65 |
> |
66 |
> Also, packages may not be marked stable until a full-fledged-developer/ |
67 |
> QA-member has approved of it. Packages being broken in the testing |
68 |
> tree are not uncommon, and we are usually notified quickly enough to |
69 |
> fix it. |
70 |
> |
71 |
> -- |
72 |
> |
73 |
> Anant-- |
74 |
> |
75 |
> gentoo-dev@l.g.o mailing list |
76 |
> |
77 |
> |
78 |
-- |
79 |
gentoo-dev@l.g.o mailing list |