Sounds entirely feasible. I'm not sure Tomcat would be too stunned at moving out, as Jakarta has a lot of brand recognition for them [the years of people thinking Jakarta was a web server].
One of the reasons for sorting out Apache-Commons vs Jakarta Commons is that it's holding up the movement of the regexps, ecs and bcel inside a more active community. Hen On Wed, 19 Nov 2003, Stephen Colebourne wrote: > While reading through all this talk of change, one thought did occur to me: > > Lets assume the larger projects leave Jakarta and become TLPs (ant, tomcat, > struts, jetspeed, tapestry, velocity, log4j...) either voluntarily or are > kicked out. > > So, whats left? > ORO, Regexp, BCEL, jakarta-commons, ...? > > So, maybe 'Jakarta' becomes jakarta-commons plus a few other libraries which > on a different day might have been commons libraries anyway! > > This seems like a really good solution - in essence, j-c takes over the > remnants of Jakarta, once the bigger projects become TLPs, and essentially > moves up to being a TLP itself. > > Benefits include > - having a core place of community still for Java developers under the > Jakarta name > - being of a manageable size (one person could feasibly read all the mails) > - thus one PMC could understand it > - having a group responsible for the Jakarta website > > Stephen > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
