On 5/23/07, Stephen Colebourne <[EMAIL PROTECTED]> wrote:
In fact, I object to the fact the it seems to be so difficult to escape Jakarta.
:) So far, it's been *much* less difficult than creating the Jakarta Commons in the first place! Back in the day, we actually had a separate mailing list just for for the discussions about whether to create the subproject, and how it would work if we did! :) So far, the TLP resolution quickly passed by a landslide. Two of us had reservations about an "Apache Commons" project that's devoted to Java, as opposed to an "Apache [Java|Jakarta|Mocha|J] Commons" that's devoted to Java. There were two other negative votes for different reasons, and almost thirty votes in the affirmative. Meanwhile, some of us have pointed out that the other remaining subprojects are within the scope of the Jakarta Commons, and have wondered if these subprojects would now like to join the commons. Of course, that could happen before or after the proposed resolution is offered to the board. But, if it did happen first, that change would remove any complaint as to using Apache Jakarta Commons as a project name.
From the beginning, the intent was to submit the proposed resolution
to the June board meeting. There's time yet to see if the other subprojects want to join, so nothing is being delayed.
I'd encourage people to step back for a moment and look at what Jakarta actually is today. Its a very disparate group of voices pulling in different directions. This is a natural result of the true meaning of Jakarta - the community around the code - leaving. There is no longer any focus within Jakarta. Nor has there been for a *very* long time.
Ummm, you may be confusing cause and effect. Jakarta has been " very disparate group of voices pulling in different directions" for as long as I've been here, which would be going on seven years. :) -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
