| 1 |
Hi, everyone. |
| 2 |
|
| 3 |
I'm not gentoo dev (yet), but I take the chance to vent an idea I have a |
| 4 |
while, based on my personal experience in bugzilla. |
| 5 |
|
| 6 |
On Wed, 2006-10-04 at 07:15 -0500, Brandon Low wrote: |
| 7 |
|
| 8 |
> What if the problem is too many devs instead of too few? Slackware |
| 9 |
> Linux is a comparatively simple to maintain distribution, but ONE person |
| 10 |
> does it. How many devs are on Gentoo now? 200? more? A close knit |
| 11 |
> group of college students and bored professionals should be able to |
| 12 |
> maintain this distribution. |
| 13 |
|
| 14 |
I think the challenge is the amount of packages. One person could not |
| 15 |
maintain all packages in gentoo. |
| 16 |
|
| 17 |
What you didn't need to be a gentoo dev to be a package maintainer? Lets |
| 18 |
say anyone could be marked as maintainer in an ebuild. When there is a |
| 19 |
bug, the package maintainer fixes the bug and submits an updated |
| 20 |
ebuild/patch whatever. This person has no commit access. |
| 21 |
|
| 22 |
Then a "committer", a gentoo-dev (someone with little more experience), |
| 23 |
just take a quick look at it and commit it. |
| 24 |
|
| 25 |
This way fewer dev with commit access is needed, and more people from |
| 26 |
community are able to offload the dev's. |
| 27 |
|
| 28 |
This would also make the threshold lower for people to become a |
| 29 |
maintainer. |
| 30 |
|
| 31 |
Personally there are a few packages I could maintain, but I don't think |
| 32 |
its worth becomming a developer to just maintain 1 single package. |
| 33 |
|
| 34 |
I think this how the do with the freebsd ports tree. I am maintainer for |
| 35 |
1 single freebsd port without being a committer. |
| 36 |
|
| 37 |
-- |
| 38 |
Natanael Copa |
| 39 |
|
| 40 |
-- |
| 41 |
gentoo-dev@g.o mailing list |
Archives