| 1 |
В Чтв, 03/04/2008 в 18:56 +0300, Petteri Räty пишет: |
| 2 |
> >> Petteri Räty wrote: |
| 3 |
> >> Defining required amount of activity for ebuild devs. I would like us to |
| 4 |
> >> raise the required amount of activity for ebuild devs. |
| 5 |
|
| 6 |
> I checked the current slacker script and it checks for having at least |
| 7 |
> one commit in last 60 days. We could of course just change the slacker |
| 8 |
> script to list the activity for everyone during the last 60 days and |
| 9 |
> leave the interpretation to undertakers. |
| 10 |
|
| 11 |
Number of commits is bad measure for work and time spent on gentoo: some |
| 12 |
work require long investigation and exactly one commit, while another |
| 13 |
work require lots of commits and small amount of time spent on that. So, |
| 14 |
please, stop this formalism! |
| 15 |
|
| 16 |
Also this change does not magically fix bugs so bugs are different |
| 17 |
issue. If you know how/want to fix the bug just mail maintainer, wait |
| 18 |
some time (one day normally is enough if bug was opened for a long |
| 19 |
time...) and fix bug. That's it! No need to retire maintainer to fix |
| 20 |
bugs in his packages. |
| 21 |
|
| 22 |
Security is also unrelated as this change does not improve security. |
| 23 |
|
| 24 |
The only reason we have that script is to check that developer really |
| 25 |
left gentoo, but forgot to notify infra... |
| 26 |
|
| 27 |
-- |
| 28 |
Peter. |
Archives