On Wed, Sep 17, 2003 at 04:58:04PM -0400, Noel J. Bergman wrote: >... > What needs be done to adopt this project for inbubation, other than a vote > to accept it, getting CLAs from the project members, and setting up the > infrastructure?
Since there is no (current) PMC stating they need this project to be incubated, then it is up to the Incubator PMC to vote on bringing it into the Incubator. [ in the normal scenario, a PMC says "we want this project; please incubate it; here are some people to assist in that" ] For the Geronimo case, the Board said "we will create a PMC for it upon successful incubation". That, in effect, said there is an exit PMC for that project. A similar case doesn't apply here unless you want to bring it up to the Board first. (altho I'd probably guess that the Board would not have an opinion on this) Thus, the PMC will need to vote on accepting this. (I'll start that vote on [EMAIL PROTECTED] in a moment) Regarding the resources listed, since this is an Incubator-sponsored project, the resource names will need to fall under its namespace: [EMAIL PROTECTED] cvs:incubator-directory (bugzilla is prolly fine as "directory") Also note that I'll repeat my comment about a separate -user and -dev list. For "new" projects, I would highly recommend avoiding that partitioning. The developers should see and participate directly with the users of the project. IMO, only when the user (non-dev) community begins to be a burden upon dev@, should a -user mailing list be created. Cheers, -g -- Greg Stein, http://www.lyra.org/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
