| 1 |
On Tue, 2003-04-22 at 19:55, Mark Bainter wrote: |
| 2 |
> Jon Portnoy [avenj@g.o] wrote: |
| 3 |
> > The problem is that we can't just give everyone who submits an ebuild or |
| 4 |
> > two commit access. |
| 5 |
> > |
| 6 |
> > We are, however, stepping up recruiting somewhat with a recruiting email |
| 7 |
> > address. There are also ideas floating around for ways to make it easier |
| 8 |
> > for users to get ebuilds into the tree quicker. |
| 9 |
> |
| 10 |
> I don't disagree with this. You might consider letting them still be a |
| 11 |
> maintainer though, and just have people who are new maintainers pass |
| 12 |
> their changes through a more seasoned member of the community until they |
| 13 |
> have a few releases under their belt, or whatever criteria the devs think |
| 14 |
> demonstrates the level of trust necessary to give them commit access to |
| 15 |
> their ebuilds. |
| 16 |
|
| 17 |
See this sounds like a good idea. I ofcourse don't want the current |
| 18 |
maintainer to feel dumped because someone else makes an ebuild for the |
| 19 |
newest version of a program. |
| 20 |
|
| 21 |
Perhaps something like a Primary - and secondary ebuild maintainers |
| 22 |
could be established? |
| 23 |
|
| 24 |
-- |
| 25 |
Regards, |
| 26 |
Klavs Klavsen, GSEC - kl@××××.dk - http://www.vsen.dk |
| 27 |
|
| 28 |
Working with Unix is like wrestling a worthy opponent. |
| 29 |
Working with windows is like attacking a small whining child |
| 30 |
who is carrying a .38. |
Archives