1 |
On Tue, Apr 22, 2003 at 08:00:12PM +0200, Klavs Klavsen wrote: |
2 |
> On Tue, 2003-04-22 at 19:55, Mark Bainter wrote: |
3 |
> > Jon Portnoy [avenj@g.o] wrote: |
4 |
> > > The problem is that we can't just give everyone who submits an ebuild or |
5 |
> > > two commit access. |
6 |
> > > |
7 |
> > > We are, however, stepping up recruiting somewhat with a recruiting email |
8 |
> > > address. There are also ideas floating around for ways to make it easier |
9 |
> > > for users to get ebuilds into the tree quicker. |
10 |
> > |
11 |
> > I don't disagree with this. You might consider letting them still be a |
12 |
> > maintainer though, and just have people who are new maintainers pass |
13 |
> > their changes through a more seasoned member of the community until they |
14 |
> > have a few releases under their belt, or whatever criteria the devs think |
15 |
> > demonstrates the level of trust necessary to give them commit access to |
16 |
> > their ebuilds. |
17 |
> |
18 |
> See this sounds like a good idea. I ofcourse don't want the current |
19 |
> maintainer to feel dumped because someone else makes an ebuild for the |
20 |
> newest version of a program. |
21 |
> |
22 |
> Perhaps something like a Primary - and secondary ebuild maintainers |
23 |
> could be established? |
24 |
> |
25 |
|
26 |
|
27 |
Something similar is in the works as part of the maintainers for ebuilds |
28 |
thing. Nothing has been absolutely decided on yet, so it's premature to |
29 |
offer details and get people's hopes up, but hopefully the new system |
30 |
will provide for a better way to keep track of ebuild updates and figure |
31 |
out what ebuilds need new maintainers, allowing us to recruit new |
32 |
developers to maintain ebuilds in an intelligent and systematic fashion. |
33 |
|
34 |
In short: good things are coming (hopefully) :-) |
35 |
|
36 |
-- |
37 |
Jon Portnoy |
38 |
avenj/irc.freenode.net |
39 |
|
40 |
-- |
41 |
gentoo-dev@g.o mailing list |