incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rodney Waldhoff <>
Subject projects "in" versus "entering" versus "affiliated with" the incubator
Date Tue, 21 Oct 2003 16:15:49 GMT
On the "Projects Being Incubated" page
(<>), there are four
categories listed:

* "Projects in the Incubator" (AltRMI, FtpServer, WSRP4J, JaxMe, Pluto)

* "Projects entering the Incubator" (Apache Geronimo, XMLBeans)

* "Projects affiliated to the Incubator" (Lenya)

* "Projects previously Incubated" (Tapestry)

The latter category is pretty obvious, but can someone clarify the
difference between projects "in", "entering" or "affiliated to" the
Incubator?  Have those "entering" the incubator not yet been voted upon?
What does it mean that "Lenya is being incubated inside the Cocoon
project"?  Does this mean that that it is the Cocoon PMC that determines
when this project is ready to "gradudate"?

Also, some projects (AltRMI, FtpServer, Geronimo) are using incubator-*
modules in CVS, while others (WSRP4J, JaxMe, Pluto, XMLBeans) are using
their "destination" repositories (xml-*, ws-*, etc.).  Similarly, some
projects (AltRMI, FtpServer, Pluto, Geronimo) are using* as their web point of entry,
others (WSRP4J, JaxMe, XMLBeans, Lenya) are using their "destination"
hosts (*,*, etc.).  Similarly,
some projects are using * mailing lists, others are
using their destination hosts.  (Curiously, there doesn't seem to be a
complete overlap between those projects using one piece of incubator
infrastructure and those using another.)

How is it determined whether a project uses the incubator-based or
destination-based infrastructural component?  Is this by project option?
By destination PMC option?  By Incubator PMC option?  Some combination of

- Rod <>

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

View raw message