| 1 |
On Thu, 2006-03-23 at 18:34 -0500, Dan Meltzer wrote: |
| 2 |
> On 3/23/06, Daniel Goller <morfic@g.o> wrote: |
| 3 |
> > On Wed, 2006-03-22 at 09:15 -0500, Dan Meltzer wrote: |
| 4 |
> > > Asking developers to "proxy" takes almost as much time as it does to |
| 5 |
> > > ask them to maintain a package by themselves. |
| 6 |
> > |
| 7 |
> > wrong |
| 8 |
> > |
| 9 |
> > > The developer is |
| 10 |
> > > directly responsible for anything he commits, so he will have to still |
| 11 |
> > > test the ebuild, still test any revisions, and still follow the |
| 12 |
> > > package to make sure there are no problems. The writing the ebuild |
| 13 |
> > > part of the process is not that much of the commitment, I don't see |
| 14 |
> > > the point. |
| 15 |
> > > |
| 16 |
> > |
| 17 |
> > we are not just talking about new ebuilds/bumps |
| 18 |
> > having someone do all the work and having to only verify the end results |
| 19 |
> > of the users work is a big help, instead of having to look into the |
| 20 |
> > problem, checking if a fix exists elsewhere, or digging through the |
| 21 |
> > source yourself, you verify the fix solves the problem and does only |
| 22 |
> > that. |
| 23 |
> > |
| 24 |
> > and everyone wins |
| 25 |
> |
| 26 |
> So it sounds like you are asking them to do everything developers do, |
| 27 |
> |
| 28 |
> why not just make them be developers? |
| 29 |
> > |
| 30 |
|
| 31 |
because they do not want more than take care of their one package and do |
| 32 |
not want more than someone taking care of their work, maybe? |
| 33 |
or maybe because they don't like a lot of devs due to bad experiences, |
| 34 |
and would not want to be any part of the group, but still enjoy working |
| 35 |
on packages |
| 36 |
|
| 37 |
there are people who i would love to see as devs, but are not |
| 38 |
particularly interested on having to deal with some of the devs, having |
| 39 |
a proxy allows them to help gentoo w/o being exposed to the people they |
| 40 |
otherwise would have to deal with |
Archives