On 1 September 2011 09:23, ant elder <[email protected]> wrote: > On Wed, Aug 31, 2011 at 1:41 PM, Mladen Turk <[email protected]> wrote: >> On 08/31/2011 01:20 PM, Ross Gardler wrote: >>> >>> On 30 August 2011 17:44, Mladen Turk<[email protected]> wrote: >>>> >>>> On 08/30/2011 05:52 PM, Graham Leggett wrote: >>>>> >>>>> On 30 Aug 2011, at 5:49 PM, 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. >> >> Since when? Don't tell me that a single person >> can constitute an incubator podling. >> > > I don't think there is any Incubator rule on the minimum initial > committers but I've been part of the Incubator for over 6 years and > don't recall there ever being a poddling accepted with only a single > initial committer and i do recall several occasions where single > committer projects have been suggested to go elsewhere to grow their > community before trying to be an Incubator poddling.
Whilst I agree that no podling has been accepted with a single committer, there have been non refused either. Third parties with no experience of the ASF are one thing, ASF committers with friends who will pile on is another. > The Incubator is mainly about learning about community building which It is just as much about ensuring due diligence is done on the code and that community is developed. > is quite different from Lab work Yes, the IP and community goal is also quite different from labs. > so i don't think the Incubator is > very appropriate for most labs. Agreed. But it *is* appropriate for people who want to create releases and build community. IT is those people who are complaining about labs. > I also think its quite reasonable to > want to do releases of lab code as part of the innovation process. I've said it many many times before. Take a proposal to the board and see what they think. Maybe I'm totally off the mark, but the no releases rule was put there for good reasons. Nobody who wants to remove it agrees with my reasons (although there are people who agree). > There are some signs that some Labs PMC people are starting to think > this might be ok, i think its just going to take some time. I agree. I'd say we are about 50/50 right now. My concern is that nobody has yet addressed the real reasons why releases are not allowed (in a nutshell that it would become a way to circumvent the incubator). Ross > > ...ant > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Ross Gardler (@rgardler) Programme Leader (Open Development) OpenDirective http://opendirective.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
