1 |
Jorge Manuel B. S. Vicetto kirjoitti: |
2 |
> Petteri Räty wrote: |
3 |
> |
4 |
> I agree with the above point. |
5 |
> Also, as I recall, both Pettery (betelgeuse) and Denis (calchan) have |
6 |
> stated before that we no longer have any queue of people waiting on |
7 |
> recruiters to join Gentoo. I'm not seeing an avalanche of new blood |
8 |
> entering the distro, so I'm wondering where we want to go. |
9 |
> If we keep going the route of the last months, I wonder how long it will |
10 |
> take until we get under 150 devs. I don't think this will benefit |
11 |
> anyone. Furthermore, the trend in the last months was in large part the |
12 |
> result of finally retiring people that had been slacking for a long |
13 |
> time. This proposal could (would?) lead to sending away people that |
14 |
> still do work, albeit at a slower pace or on bursts. |
15 |
> |
16 |
|
17 |
We do have somewhat of a backlog at this point because Calchan was away |
18 |
for a while and you can always query bugzilla for the current situation. |
19 |
|
20 |
> |
21 |
> As others have commented, I don't agree with this point. Also, you're |
22 |
> forgetting we have quite a few people working on this project and that |
23 |
> we have many different roles. |
24 |
> |
25 |
|
26 |
And you are assuming that undertakers wouldn't check their role before |
27 |
acting. |
28 |
|
29 |
> Recalling previous discussions about work on gentoo and some of the |
30 |
> existing roles, what will you do to AT folks, release members or QA |
31 |
> members? Are they also obliged to do a weekly commit to keep their |
32 |
> "privileges"? |
33 |
|
34 |
AT folks aren't devs and see above. |
35 |
|
36 |
> Finally, I thought the whole point of removing access to infra boxes |
37 |
> (which is the end result of retiring a dev), was a concern with security |
38 |
> and not a way to get rid of people - with the exception of |
39 |
> administrative action by devrel. |
40 |
|
41 |
Security and gives us a better picture on what is really maintained and |
42 |
what is not. |
43 |
|
44 |
> |
45 |
> I understand and agree that ebuild devs should keep a minimum level of |
46 |
> work to justify their access to the gentoo-x86 tree. I would also like |
47 |
> to have a few devs that can do major commits (although commit sprees can |
48 |
> have their own problems), but I think there's still a place in this |
49 |
> distro for people that want to maintain a few packages, that want to do |
50 |
> AT work, that care with the QA of the tree or that work on releases. |
51 |
> These people shouldn't be sent away, just because they can't keep with |
52 |
> weekly commits (not enough work or time?) or because they work in bursts. |
53 |
> |
54 |
|
55 |
To quote myself: |
56 |
"How does having the average time between commits be at most a week |
57 |
sound and if it goes under that, undertakers will get a notification?" |
58 |
|
59 |
I didn't suggest they have to commit every week. This means 4 commits a |
60 |
month instead of the currently monthly or bimonthly commit check in the |
61 |
script. |
62 |
|
63 |
> |
64 |
> As a final thought, I think this point is a tangent to the old debate |
65 |
> about tree-wide commit privileges and or the scm of the tree. Afterall, |
66 |
> if gentoo-x86 was a git tree and or we had acls in the tree, I don't |
67 |
> think we would be having or would need to have this argument. |
68 |
> |
69 |
|
70 |
If we used git, proxy maintaining would be easier. |
71 |
|
72 |
Regards, |
73 |
Petteri |