On Thu, Jul 03, 2003 at 04:22:10PM -0400, Andrew C. Oliver wrote: >... > 1. Top level project - IMHO this isn't big enough and you don't have the > open source experience or robust community to pull that off (not intended to > be a criticism)
There is no size minimum for a TLP, but I believe the Board would want to see the PMC has more direct experience at the ASF. So yes, I don't see that the Board would approve constructing a new PMC for this. > 2. XML - I'm sure it would be fine. > > 3. Jakarta - IMHO this the best place for it. > > The division of XML vs Jakarta predates me for certain, but I think the main > issues surrounding that are rusty. The problem is Jakarta itself. Centering a PMC around a *language* rather than functionality is the inherent problem. These questions will continue to arise over and over. When Grisha Trubetskoy wanted to contribute mod_python to the ASF, a good number of people called for creating a 'python' TLP. The Board decided to stop perpetrating the per-language concept. Instead, mod_python was added to the Apache HTTP Server Project (it *is* a module for Apache httpd, after all). mod_php, mod_perl, and mod_tcl fall under the same argument, of course, but they get a Grandfather Pass :-) To that extent, I'd say it is an XML project. However, I think it is mostly up to the XMLBeans community to ask for one or the other. If that PMC says "okay", then everything is fine. (and no... PMCs are not allowed to meet at sundown to duel for an arriving project :-) Cheers, -g -- [EMAIL PROTECTED] ... ASF Chairman ... http://www.apache.org/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
