| 1 |
On Sun, 2006-01-08 at 14:40 +0100, Carsten Lohrke wrote: |
| 2 |
> > If you feel so strongly about this, why not setup a "cleaning crew" |
| 3 |
> > project that goes around doing exactly this? |
| 4 |
> |
| 5 |
> Don't you think that it is pretty much barefaced to let a small group do the |
| 6 |
> dirty, boring and annoying work, while those who don't care a bit can |
| 7 |
> continue to do so?! |
| 8 |
|
| 9 |
Not really... We already have a QA project. Join it. If certain |
| 10 |
developers are constantly breaking QA, inform them. If they continue to |
| 11 |
do it after being warned, go to devrel. While the QA team can go and |
| 12 |
clean up some things, it should only really do so *once* and inform the |
| 13 |
developer. Otherwise, the developer might not honestly know that he is |
| 14 |
doing something incorrectly, or that anyone is even paying attention. |
| 15 |
Doing this allows for a cleanup of the tree, without putting |
| 16 |
restrictions arbitrarily on the entire developer pool. |
| 17 |
|
| 18 |
-- |
| 19 |
Chris Gianelloni |
| 20 |
Release Engineering - Strategic Lead |
| 21 |
x86 Architecture Team |
| 22 |
Games - Developer |
| 23 |
Gentoo Linux |
| 24 |
|
| 25 |
-- |
| 26 |
gentoo-dev@g.o mailing list |
Archives