What about allowing podlings to do release without using the org.apache.* packages or the apache brand anywhere in the release ? These would be just plain Apache Licensed releases without any ties to the Apache brand. Such releases, not endorsed by the ASF could be synced to the central repo without any objections as there would be no more ties to the Apache brand. When the podling graduates, it could use the org.apache packages as the ASF endorses the project. This would be more incentive for the podling to graduate, without adding barriers to be able to build the community.
On Fri, Oct 3, 2008 at 4:09 PM, Aidan Skinner <[EMAIL PROTECTED]> wrote: > On Fri, Oct 3, 2008 at 2:53 PM, Jukka Zitting <[EMAIL PROTECTED]>wrote: > > >> Do people think that we shouldn't make such a distinction, or that we >> should perhaps explicitly consider "community quality" as a release >> criteria? >> > > Getting releases out of the incubator is difficult and subjective enough as > it is. Without regular releases it would be nearly impossible to build a > community around a project. Without being able to do that, why would anybody > engage in this process in the first place? > > - Aidan > -- > Apache Qpid - World Domination through Advanced Message Queueing > http://cwiki.apache.org/qpid > "Nine-tenths of wisdom consists in being wise in time." - Theodore Roosevelt > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://open.iona.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
