Jason: > Using the Apache name directly is somewhat misleading because > it has the flavor of Apache-wide solidarity in a market segment which > generally isn't the case.
"Solidarity"? An important choice of words. Apache is a community alright, but solidarity is often hard to find. > If I had been on your mailing list when the first naming discussions > were being held I would have made the same comments. In the above case I > would say "Jakarta Avalon Server Framework" would be more appropriate. If I had been around when Turbine was proposed as a project, or when it started to evolve into a framework I would've made some comments as well. Jakarta is a bit of a mess and no-one is to blame. We need some solidarity, some tolerance. Keep that in mind in discussions like this. (and I'm not talking to you in specific, Jason, but to the world at large, being the socialist Dutch guy I am.) "Jakarta Avalon Server Framework" has exactly the same problems as you mentioned before: it still links "Jakarta" and "Server Framework". And we're not the only framework at jakarta. I'm inclined to just forget about all this . . . shame being a committer comes with responsibility as well . . . means I can't really type "back into lurking mode", doesn't it? cheers, - Leo, The Philosopher(tm) -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
