HTTPD and got it accepted by Jakarta as a Jakarta project. Some folks might take issue with that. Its impractical right?
What about mod_perl for Tomcat? (silly but what about that as a name)
So the reverse is true. The issue isn't what so and so can or can't do, its about good sense. Lets just take a step back and say
is Commons a confusing name for a top level project?
my answer: yes.
Then maybe lets just call a vote on whether to rename it. This is somewhat challanged by the lack of actual committers to the
project... I trust that if a step back is taken and only the above issue considered, that the PMC members of this project will do the right thing.
-Andy
Rodent of Unusual Size wrote:
* On 2002-10-24 at 06:53,
[EMAIL PROTECTED] <[EMAIL PROTECTED]> excited the electrons to say:
What I haven't seen is any good arguments as to why a-c is a step
forward for j-c and not a big step back.
wrong question, i think. 'it's not all about you.' the question is whether/why a-c is a step forward for *apache*. if the answer to that is positive, *then* your question above can be considered. but this dog-in-the-manger 'anything "commons" needs j-c's approval' attitude has got to go.
yes, i'm being blunt -- but i'm getting a little tired of the
impression i'm getting from multiple people that j-c's opinion
is either the only one that matters, or the most important.
