We might just follow the same general procedure we've used for Jakarta, the Commons, and the Incubator.
* A Struts subproject is created in response to a proposal to the DEV list. * The proposal must be made by a Struts Committer and name two other Struts Committers who are willing to support the subproject. * At least one of the three Committers must also be a Struts PMC member. * The proposal is subject to a consensus vote, like any other product change. (A consensus vote is subject to a binding veto. A majority vote, like we use for releases, is not.) Of course, there are going to be other implicit criteria, like the code being donated to the ASF, the subproject being relevant and wildly popular, and so forth. But I don't think we need to spell all that out. So long as we have three willing vict -err- volunteers and a proposal subject to consensus, it'll sort itself out :) I'd be happy to be one of the Committers named on a proposal to create a scripting subproject. -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
