> Two opposing points af view can be divisive in open source projects, but
> they need not be. I say branch the code, let both sides run with their
> ideas.
That is, to a certain extent, what happened with Avalon. What we saw was a
community fall apart. It got to the point where they would consider forking
as a normative tool to preclude argument/discussion (and the need for
consensus). Bad idea. Not something I want to see replicated anywhere
else. The clear message coming from the ASF is that Community is more
important than code.
If there is a good reason for a branch, the Community should be behind both
of them, such as Serge's current branch for testing a fix or the proposed
branch of v2 and v3 (unless we use a separate module).
The difference is in how forks are used and viewed. It is good as a source
control technique allowing the Community to maintain two parallel tracks; it
is bad when it splits the community.
--- Noel
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
