1 |
On Tue, Apr 22, 2003 at 06:00:09PM +0200, Klavs Klavsen wrote: |
2 |
> On Tue, 2003-04-22 at 16:57, Peter Ruskin wrote: |
3 |
> > On Tuesday 22 Apr 2003 15:26, Dan Armak wrote: |
4 |
> > > The second will facilitate quick acceptance of user-submitted ebuilds |
5 |
> > > in some way - probably drawing upon the submitters in one way or |
6 |
> > > another. |
7 |
> > |
8 |
> > I'm more than willing to maintain ebuilds I submit. |
9 |
> > |
10 |
> |
11 |
> Same here. What are the requirements for being a maintainer? |
12 |
> I don't think one has to make the newest version available ASAP. |
13 |
> This f.ex. didn't happen with drip - which was why I created a new |
14 |
> version myself. |
15 |
> |
16 |
> I think people who submit ebuilds should automacally be added as |
17 |
> maintainer of the ebuild. If they contribute with a newer version of a |
18 |
> given ebuild - then they should be added as maintainer - keeping the old |
19 |
> maintainer too. |
20 |
> |
21 |
> It's a Community distro and I don't think anyone will mind - as long as |
22 |
> it's all build on volutarity - ie. make a newer version if you like - |
23 |
> don't if you don't. |
24 |
|
25 |
The problem is that we can't just give everyone who submits an ebuild or |
26 |
two commit access. |
27 |
|
28 |
We are, however, stepping up recruiting somewhat with a recruiting email |
29 |
address. There are also ideas floating around for ways to make it easier |
30 |
for users to get ebuilds into the tree quicker. |
31 |
|
32 |
-- |
33 |
Jon Portnoy |
34 |
avenj/irc.freenode.net |
35 |
|
36 |
-- |
37 |
gentoo-dev@g.o mailing list |