On Tue, 2003-04-22 at 19:55, Mark Bainter wrote:
> Jon Portnoy [avenj@gentoo.org] wrote:
> > The problem is that we can't just give everyone who submits an ebuild or 
> > two commit access.
> > 
> > We are, however, stepping up recruiting somewhat with a recruiting email 
> > address. There are also ideas floating around for ways to make it easier 
> > for users to get ebuilds into the tree quicker.
> 
> I don't disagree with this.  You might consider letting them still be a
> maintainer though, and just have people who are new maintainers pass 
> their changes through a more seasoned member of the community until they
> have a few releases under their belt, or whatever criteria the devs think
> demonstrates the level of trust necessary to give them commit access to
> their ebuilds.

See this sounds like a good idea. I ofcourse don't want the current
maintainer to feel dumped because someone else makes an ebuild for the
newest version of a program.

Perhaps something like a Primary - and secondary ebuild maintainers
could be established?

-- 
Regards,
Klavs Klavsen, GSEC - kl@vsen.dk - http://www.vsen.dk

Working with Unix is like wrestling a worthy opponent. 
Working with windows is like attacking a small whining child 
who is carrying a .38.