incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Noel J. Bergman" <>
Subject RE: Clearing the air round Incubator and Ruper (was Re: projects incubated by the incubator PMC)
Date Wed, 10 Dec 2003 18:50:09 GMT
Nicola Ken Barozzi wrote:

> First of all, we are in the process of deciding and clearly documenting
> that only TLPs are to be incubated. Why? Because in Apache there are
> only TLPs.

I don't agree.  The Incubator has a dual role.  One is the building of new
Projects, but the other is vetting all incoming codebases.  Some confusion
comes from applying the term "incubation" to both aspects of its role.

Please review the thread in the Board archives that I pointed out to Jason.
As Sander noted as well, it was clearly stated that the Incubator is
responsible for all incoming codebases developed outside of the Foundation.
No, patches don't need to come through the incubator, and yes, there are
grey areas, but the clearly stated intent was that the Board had designated
the Incubator as the sole place through which an externally developed
codebase could enter the ASF.

Where the confusion comes from is related to the Community building usage of
the term "incubation."  The other PMCs have expressed that they want to do
the Community Building when a codebase and a community is merging into their
larger community.  That is fine, but it does not change the Board's mandate
regarding oversight of externally developed code.  If the incoming code has
a designated place to go, we should facilitate the PMC being able to start
their Community Building, both we are responsible for ensuring that the IP
issues are cleared, adn they are responsible for working with us to make
sure it happens.

	--- Noel

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message