I think what we've seen is that all VOTEs get just enough votes to pass because once enough passing votes are in, people choose to spend the little time they have available for the projects on something else.
3 votes are enough for a release, and I don't think we have to be afraid of not reaching that target for any upcoming release. EdB On Fri, Dec 5, 2014 at 1:00 PM, Bertrand Delacretaz <bdelacre...@apache.org> wrote: > On Friday, December 5, 2014, Jeffry Houser <jef...@dot-com-it.com> wrote: > >> ...Could part of the problem we have too many projects under the Apache > Flex banner? >> Do other Apache projects have 9+ completely separated, but related, > projects?... > > The key is not how many modules you are managing but whether those belong > to the same community. > > To take an example that I'm familiar with, Apache Sling manages more than > 100 modules [1] and releases them very regularly. That works fine. > > Sometimes one needs to call for more PMC members to get enough votes on a > module that interests only few people, and when that became hard we just > went back to our list of committers and elected a bunch of them as PMC > members (which also means you look for new committers often, as people also > go). Because people care about the overall health of the project, they will > take the time to vote on releases even for modules that they're not really > interested in. > > -Bertrand > > [1] http://sling.apache.org/downloads.cgi -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
