On Fri, 3 Nov 2000, Pier P. Fumagalli wrote:
> Sorry for starting what it might end up as a long flamewar, but reading
> almost 500 emails on the list I ended up a little confused... Also, in a
> bunch of side discussions, but related always to the same topic, I feel
> there's something wrong going around here...
>
> Question: WHAT THE HACK IS TOMCAT 3.3 ???
I'm not disagreeing with you Pier, but I will say I believe that there are
2 possible ways to interpret the current situation, and I do not think
I'm the only one who thinks this.
1) The fact that there are smart software developers out there
contributing to Tomcat 3.x codebase and not necessarily contributing to
the 4.0 codebase is a failure of the Jakarta Apache community to obtain
sufficient buy-in from those people. The division of resources in this
situation is what should be avoided at all cost, because this is the one
major limitation OSS has: division of finite resources within a community
because of forking. I would assume one of ASF goals is to prevent this.
2) Or alternatively, anything beyond Tomcat 3.1 refects that Tomcat 3.1 is
a "rolling beta", which means the "code-train" is in such bad shape that
the developers are throwing track in front of it as it moves forward. Not
a good thing.
Or maybe we have a combination between the two. At any rate, ASF should
rule clearly whether to let the code-train of 3.x roll off the track,
whether to let it continue to roll on track but away from it's auspices,
or to support the two code bases as is.
By doing nothing ASF implicitly supports the latter, which is
counterintuive to ASF's entire raison d'etre.
my $0.02
-Nick
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
