Re: [gentoo-dev] Gentoo World Domination. a 10 step guide

[Natanael Copa <natanael.copa@gmail.com>]

Hi, everyone.

I'm not gentoo dev (yet), but I take the chance to vent an idea I have a
while, based on my personal experience in bugzilla.

On Wed, 2006-10-04 at 07:15 -0500, Brandon Low wrote:

> What if the problem is too many devs instead of too few?  Slackware
> Linux is a comparatively simple to maintain distribution, but ONE person
> does it.  How many devs are on Gentoo now?  200? more?  A close knit
> group of college students and bored professionals should be able to
> maintain this distribution.

I think the challenge is the amount of packages. One person could not
maintain all packages in gentoo.

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 way fewer dev with commit access is needed, and more people from
community are able to offload the dev's.

This would also make the threshold lower for people to become a
maintainer.

Personally there are a few packages I could maintain, but I don't think
its worth becomming a developer to just maintain 1 single package.

I think this how the do with the freebsd ports tree. I am maintainer for
1 single freebsd port without being a committer.

--
Natanael Copa

-- 
gentoo-dev@gentoo.org mailing list