I don't think this would be a good idea to not allow one podling to release anything. Let me state my thoughts: the goal of a podling is to build a lively and heterogeneous community to be able to graduate. Usually, there is one or more company behind a project. If there are more than one company, the community will not be completely homogeneous, so things will be eased. So the problem is when a single company provides resources for a given project. In such a case, other committers usually come from the user community and this takes time. I think that one of the goal of the podling should be to build a user community, so that users can become developers. So not allowing podlings to release anything will certainly not help building / growing the user community, hence the dev community.
Cheers, Guillaume Nodet Davanum Srinivas wrote: > Niclas, > > Here the scenario is a project with all committers from one employer > and regular releases. > > -- dims > > On 3/17/07, Niclas Hedhman <[EMAIL PROTECTED]> wrote: >> On Friday 16 March 2007 19:46, Davanum Srinivas wrote: >> > What are we going to do >> > about projects that will show signs of life but will remain in >> > incubator for a very long time. when do we kick them out? 3 years? 5 >> > years? >> >> No community -> no releases ?? >> >> >> Cheers >> Niclas >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
