On Sep 21, 2007, at 3:10 PM, Costin Manolache wrote:
Let's assume CTR ( lazy consensus - i.e. assume everyone agrees ) -
what if
it
turns that the consensus is lacking, not on the technical validity
of the
change
but on weather a particular change is the right direction. Should
tomcat
bundle the
CGI / SSI support - or have a smaller set of feature in the base,
like jetty
? NIO or apr ?
Keep backward compat or fix major problems - and what's the middle
line ?
Certainly the rest of the community out there in addition to the
PMC determines a lot of that. In which point, I think the
majority would rule.
sides. And if 2 people have different opinion on an API in the
trunck -
first to make the change
that can't be vetoed, or gives up in the flame war - wins.
Again, majority would rule.
All this is certainly not unique in any way to Tomcat.
Does anyone really think that developers in every other
ASF project, or any other project, don't have disagreements
or differing views of direction or implementation??
But this is about *collaborative, communal* development.
If unanimous consensus can't be reached, then majority
rules and we go on from there.
All this requires an active and attentive developer community
that makes up its own mind... I don't think anyone can argue that
we don't have that now :)
API and big, long term changes and the direction of the project
shouldn't
be lazy consensus,
no matter if done in trunk or branch, i.e. result of one individual
submitting (valid) code.
It needs some more comunity involvment.
No one has said that at all, afaik. So I agree with your
strawman argument :)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
