On 4/2/07, Henri Yandell <[EMAIL PROTECTED]> wrote:
I think the end should be nigh for Jakarta (those on private@ will have seen a thread in which I side-topic'd with the feeling that the end should be nigh for Jakarta). Previously I've suggested that Commons should flatten into Jakarta and that Jakarta should become a general 'Java components' project; however there are some negatives to that that I think are critical.
Firstly, it leaves the future Jakarta with a lot of dead projects that are going nowhere. That's not going to change in the short to medium term, so it just becomes a millstone for the project's neck. Secondly, the Jakarta PMC will always remain a big group of people who care about the brand name and the various legacies, rather than a small focused PMC. I think this isn't desirable for any active community that are a part of Jakarta currently - trying to have a PMC that are acting as one community when not being one community doesn't work. Thirdly, I think by being here we are helping to delay the inevitable and keeping the old, broken umbrella going. Moving to TLP will help things move along, and will provide a place for things to move to. So with that said - I'd like to propose that we move to commons.apache.org.
+1 We have talked about this lots of times before and some discussions have had us breaking commons itself apart into pieces. My +1 is for the whole of commons as an Apache TLP. To answer some other questions that have come up before and will resurface: +1 for only Java components (flame away, this is just my HO) +1 for bringing sandbox along +1 for welcoming small components from other Jakarta subprojects +0 for waiting to do this until we have a clear idea of where the rest of the Jakarta subprojects are going. Phil --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
