4. Making the incubating project have it's own CVS module is a terrible idea. It gives the incubating project and the new users the idea that the project is already a full-apache project. This is the same problem that had arised on Avalon, where projects that were really sandbox code started appearing in the main excalibur CVS, making users use them as they were properly released, which was not true.
All incubating projects therefore should reside in the incubator module.
I'd also propose that all committers of the sponsoring PMC can have access to it, as well as all the committers from other incubating projects (so they can eventually lend a hand in need).
6. Making a separate mailing list right from the start that is in the final destination address is again IMHO not a good idea. I would propose that all incubating projects start de-facto on the [EMAIL PROTECTED] ML, and eventually migrate to [EMAIL PROTECTED]
-1: Providing isolated resources makes it much easier to zap stuff upon incubation failure. Also, if both -user, -dev, and -cvs mails originating from several incubating projects would be aggregated onto a single set of incubation- lists, I'm pretty sure people would be very quickly annoyed.
Other than that: enthusiastic +0.75.
</Steven> -- Steven Noels http://outerthought.org/ Outerthought - Open Source, Java & XML Competence Support Center Read my weblog at http://blogs.cocoondev.org/stevenn/ stevenn at outerthought.org stevenn at apache.org
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
