| 1 |
On Wed, 04 Oct 2006 15:09:06 +0200 |
| 2 |
Natanael Copa <natanael.copa@×××××.com> wrote: |
| 3 |
|
| 4 |
> What you didn't need to be a gentoo dev to be a package maintainer? |
| 5 |
> Lets say anyone could be marked as maintainer in an ebuild. When |
| 6 |
> there is a bug, the package maintainer fixes the bug and submits an |
| 7 |
> updated ebuild/patch whatever. This person has no commit access. |
| 8 |
> |
| 9 |
> Then a "committer", a gentoo-dev (someone with little more |
| 10 |
> experience), just take a quick look at it and commit it. |
| 11 |
|
| 12 |
This already happens on some packages (in particular where the upstream |
| 13 |
author is happy to maintain the Gentoo ebuild). One very important |
| 14 |
thing is for the Gentoo "proxy" dev to be listed in metadata.xml (as |
| 15 |
well as the non-Gentoo maintainer). |
| 16 |
|
| 17 |
The Gentoo dev takes formal responsibility for any commits. The trick |
| 18 |
is to find a Gentoo dev who is prepared to proxy for you; that involves |
| 19 |
a trust relationship between the dev and the maintainer. The amount of |
| 20 |
work the dev has to do depends on how well the maintainer follows the |
| 21 |
Gentoo ebuild rules. |
| 22 |
|
| 23 |
-- |
| 24 |
Kevin F. Quinn |
Archives