Thomas Cort wrote: > There have been a number of developers leaving Gentoo in the past 6 > months as well as a number of news stories on DistroWatch, Slashdot, > LWN, and others about Gentoo's internal problems. No one seems to have > pin pointed the problem, but it seems glaringly obvious to me. We > simply don't have enough developers to support the many projects that > we have. Here are my ideas for fixing this problem: > > - Cut the number of packages in half (put the removed ebuilds in > community run overlays)
No, thank you. We are already decimating packages in certain areas but isn't a good solution. > > - Formal approval process (or at least strict criteria) for adding > new packages let the herds decide... > > - Make every dev a member of at least 1 arch team Ok > > - Double the number of developers with aggressive recruiting NO! I want to know people I'm working with. Double the people doing recruiting and evaluation! (I have at least one guy in wait phase) > > - No competing projects No projects that don't coordinate between them. > > - New projects must have 5 devs, a formal plan, and be approved by the > council some projects starts by one and then grow... > > - Devs can only belong to 5 projects at most No. > > - Drop all arches and Gentoo/Alt projects except Linux on amd64, > ppc32/64, sparc, and x86 No. > > - Reduce the number of projects by eliminating the dead, weak, > understaffed, and unnecessary projects too much subjective so, No. > > - Project status reports once a month for every project bureocracy.... In short, interesting ideas, I don't like more than half of them. what about: let treecleaners do their job, recruiters get more people, put the devmanual where it belongs, have better coordination between projects to the point stepping on others feet is quite hard and not dead easy as today? those point and less noise on gentoo-dev. lu -- Luca Barbato Gentoo/linux Gentoo/PPC http://dev.gentoo.org/~lu_zero -- gentoo-dev@gentoo.org mailing list
