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
