| 1 |
On Wed, 2006-03-22 at 09:15 -0500, Dan Meltzer wrote: |
| 2 |
> Asking developers to "proxy" takes almost as much time as it does to |
| 3 |
> ask them to maintain a package by themselves. The developer is |
| 4 |
> directly responsible for anything he commits, so he will have to still |
| 5 |
> test the ebuild, still test any revisions, and still follow the |
| 6 |
> package to make sure there are no problems. The writing the ebuild |
| 7 |
> part of the process is not that much of the commitment, I don't see |
| 8 |
> the point. |
| 9 |
|
| 10 |
Well no, that's not really what I was suggesting. Developers who took on |
| 11 |
these ebuilds would only be responsible for checking that they don't |
| 12 |
break the tree and that they do actually work. They aren't responsible |
| 13 |
for fixing the package when it breaks, or for following its development |
| 14 |
at all - that's the responsibility of the _users_ maintaining the |
| 15 |
package. |
| 16 |
|
| 17 |
Yes, writing the ebuild is the least part of the process, but there's |
| 18 |
often a lot more involved, and it's that that's being done in bugzilla |
| 19 |
at the moment. The way I see it, the developer would only be responsible |
| 20 |
for the ebuilds, and not for doing everything else. |
| 21 |
|
| 22 |
-- |
| 23 |
Jonathan Coome <maedhros@g.o> |
| 24 |
Gentoo Forums Moderator |
| 25 |
|
| 26 |
-- |
| 27 |
gentoo-dev@g.o mailing list |
Archives