Bernd Fondermann wrote: > David Crossley wrote: > > Bernd Fondermann wrote: > >> Ross Gardler wrote: > >> > Mladen Turk wrote: > >> >> Graham Leggett wrote: > >> >>> Mladen Turk wrote: > >> >>> > >> >>>> Make sure lab projects can make releases. > >> >>>> The reason for no releases policy is a mystery to me and > >> >>>> it actually forced me to move one of my projects from > >> >>>> labs to sourceforge. > >> >>> > >> >>> The reason for "no releases" is that if you want to make releases, you > >> >>> should be in the incubator. > >> >> > >> >> And for the incubator you need a community > >> > > >> > No you don't. You need mentors and a champion (shouldn't be hard for > >> > anyone who is already an ASF committer). You need a desire to build > >> > community. You do not need a community, the incubator is there to > >> > incubate community, not code: > >> > > >> > "The Apache Incubator has two primary goals: > >> > > >> > Ensure all donations are in accordance with the ASF legal standards > >> > Develop new communities that adhere to our guiding principles" > >> > >> Although, to be honest, no-community proposals have been turned down in the > >> past. > > > > Apache PhotArk (incubating) started with one person. > > Yes, I wasn't claiming that /all/ such proposals were turned down, but > /some/ definitively were. > PhotArk is a special case because AFAIR it was started by an ASF > member and other ASF committers immediately joined.
It was commenced by Angela Cymbalak (not a committer at the time). She came along with an idea and some beginnings of code, but no community at all. Then a group of interested people started to gather and work out the way to proceed. They started on the general@ list, then moved to the little-used projects@ list to form the initial community and develop their proposal. Then an official Proposal, etcetera In the early stages it was called Caitrin and PicaGalley. -David --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
