Gentoo Archives: gentoo-dev

From: Jonathan Coome <maedhros@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Making the developer community more open
Date: Wed, 22 Mar 2006 10:53:55
Message-Id: 1143024569.27445.23.camel@getafix.chiltonfoliat.org
In Reply to: Re: [gentoo-dev] Making the developer community more open by Bret Towe
1 On Mon, 2006-03-20 at 15:45 -0800, Bret Towe wrote:
2 > perhaps having some proxys of a sort that accept patchs and such
3 > from trusted users that would commit fixes to portage would help.
4 > similiar to the kernel format that way users can 'commit'/help out quickly
5 > without having to go thru the long process of becoming a dev
6
7 Taking this idea a bit further, what about proxy maintainers? There seem
8 to be quite a few packages that are being effectively maintained by
9 users on bugzilla, but are not in portage because they don't have a
10 maintainer. A developer could then take these ebuilds, make sure they
11 don't do anything malicious, or break QA, or whatever, and act as the
12 bridge between the portage tree and the users actually working on the
13 ebuild and keeping things up to date and working.
14
15 There could then be a bug for each such package where all the patches,
16 ebuilds and version bumps could be posted. The developer who accepts the
17 package could just take those ebuilds, maybe corrected if necessary, and
18 commit them. If the ebuild breaks, it's up to the developer to fix it.
19 If the package breaks, however, it would be up to the users on the bug
20 to fix it, although of course the developer would be able to fix it if
21 he or she could.
22
23 If there doesn't seem to be anyone interested in keeping the package
24 working anymore then it could be masked and subsequently removed as
25 packages are now. If there are security problems and the fix is not
26 trivial, it might be sensible to mask the package until someone can fix
27 it rather than waiting for a fix to become available.
28
29 If the developer working as the proxy disappeared, or retired, then the
30 packages could be assigned back to maintainer-wanted (not
31 maintainer-needed) but left in the tree until they broke, at which point
32 they could be removed again unless anyone wants to pick them up.
33 Similarly, if the users maintaining the package disappeared and the
34 package broke, it could be masked and removed.
35
36 This would seem to me to add more flexibility, and allow more ebuilds to
37 get into the tree without breaking the tree or causing security
38 problems. The only difference would be that the developer who took the
39 package would not be responsible for making sure the program worked -
40 that would be the responsibility of the users maintaining it in
41 bugzilla. There should probably be some large, friendly warnings to
42 inform anyone installing it that is the case, as well.
43
44 What do you think?
45
46 --
47 Jonathan Coome <maedhros@g.o>
48 Gentoo Forums Moderator
49
50 --
51 gentoo-dev@g.o mailing list

Replies

Subject Author
[gentoo-dev] Re: Making the developer community more open Duncan <1i5t5.duncan@×××.net>