On Thu, 2006-10-05 at 00:00 +0100, Duncan Coutts wrote:
> On Wed, 2006-10-04 at 17:13 -0400, Chris Gianelloni wrote:
> 
> > With the increase in developer and project overlays, I see the
> > possibility for reducing work needed to maintain many packages.  As
> > Natanael Copa, it would be nice for him to be able to maintain packages
> > without having CVS access.  The idea of formalizing and promoting "proxy
> > developers" has come up a few times before, and I think it is a great
> > idea.  Work is done in the overlays, tested, improved, then committed
> > into the main tree once the kinks have been worked out.  We get a
> > stronger core tree with fewer "developers" and a better interaction with
> > the community.
> 
> Some projects/herds already work this way with good results. We
> regularly get contributions from users that go into our overlay, get
> tested by us and other users and then get into the main portage tree
> some time later.
> 
> We have a very low barrier to entry, it's just darcs record; darcs send.
> Then one of the devs reviews and applies/rejects the patch. Easy.

If the "proxy maintainer" is specified as contact person in the ebuild,
and will be added to the CC list on bugs posted, the official developer
will not need to care about it until he gets a response from the proxy
developer.

> For some of our ebuilds we already have de-facto "proxy developers".

If it would be possible to become a proxy developer, I'd be maintainer
for several packages. Its not the first time I'm offering that:
https://bugs.gentoo.org/show_bug.cgi?id=76213#c2

Nobody has ever showed interest and I'm not pushing my services on
anyone.

But I'd like to do official portage and not any overlay. I have
submitted ebuilds to bugzilla that ended up in an overlay somehwere (bug
got closed) and has dissapeared for ever. I can't post bugs about
overlays in bugzilla, (I suppose) so no updated ebuild have been
submitted and I ended up just running my own local overlay.

--
Natanael Copa

-- 
gentoo-dev@gentoo.org mailing list

Reply via email to