I think the ultimate question here is what organization best benefits the committers.Huh! Is this not very self centered? Surely we should be asking what is best for ours customers/users.
No. Because whether it is in Jakarta Commons, or ASF Commons, the users get the same 'deal.' It's under the Apache Software License, freely available. Websites are available, the infrastructure is the same. So, I think the user wouldn't care whether its under ASF Commons or Jakarta Commons.
I believe the only difference, in this case, is what the committers believe.
My problem with Commons remains its cross-language aims, and I have always disagreed with division by functionality. (For example start thinking about what the website home page will be like. It will have an introduction and then a list of Java components, and a list of Perl components and a list of C# components....... No way is that ever serving the users well.)
Then, I think you are taking a very short-sighted view of the world. Everything is not just Java. I think functional groupings are probably more useful. Is an HTTP Client in Java and C *that* fundamentally different? I don't believe so.
The problems that they have to solve are essentially the same. I believe it'd be beneficial to pool our resources aligned on functional groupings rather than language barriers that aren't very strong to begin with. -- justin
