On Wed, 04 Oct 2006 15:09:06 +0200 Natanael Copa <[EMAIL PROTECTED]> wrote:
> What you didn't need to be a gentoo dev to be a package maintainer? > Lets say anyone could be marked as maintainer in an ebuild. When > there is a bug, the package maintainer fixes the bug and submits an > updated ebuild/patch whatever. This person has no commit access. > > Then a "committer", a gentoo-dev (someone with little more > experience), just take a quick look at it and commit it. This already happens on some packages (in particular where the upstream author is happy to maintain the Gentoo ebuild). One very important thing is for the Gentoo "proxy" dev to be listed in metadata.xml (as well as the non-Gentoo maintainer). The Gentoo dev takes formal responsibility for any commits. The trick is to find a Gentoo dev who is prepared to proxy for you; that involves a trust relationship between the dev and the maintainer. The amount of work the dev has to do depends on how well the maintainer follows the Gentoo ebuild rules. -- Kevin F. Quinn
signature.asc
Description: PGP signature
