Eelco Hillenius wrote:
> On 8/4/06, J Aaron Farr <[EMAIL PROTECTED]> wrote:
> > aren't "proven an actual community" and "work the standard
> > 'apache way'" graduation requirements, not entry requirements?
> > If we expect something coming into the incubator to already
> > have a fully functioning, health Apache-style community, then
> > the only point of the Incubator is for handling licensing issues.
> Over at Wicket we have been operating 'the Apache way' from a very
> early stage in the project (about two years). We have mail archives,
> commit logs, releases, and history of letting new committers in to
> prove all that if people are willing to spend an hour looking for it.
> But we feel we have to prove ourselves all over again as the
> incubation process expects it's podlings to prove themselves within
> the confines of the incubation process.
And that is correct. There is really little point to "external incubation",
since we do require communities to demonstrate their practices within the
Incubator, and to the Incubator PMC.
As for how long it takes, the judgment is subjective, so it takes however
long it takes to convince the PMC that the community is ready to leave the
Incubator. In the past, the issues have tended to be understanding of ASF
practices, community diversity, and community growth. As we see more
well-developed open development projects come into the Incubator, I would
hope to see them graduate quicker, but that'll be down to how well they do.
The real concern seems to be related to how best to support the existing
user community during incubation, and that ought to be resolvable.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
