> Anthony: I'll present a few scenarios in which a fork is a good thing. I think
in
> doing so, I'll show why it is necessary.
<SNIP>
> Anthony: Someday, of course, someone will add to this. Maybe Steve quits.
Maybe
> someone comes up with another new idea which Steve does not like. But the
> point is forking prevents dictatorial control (notice how Larry could not
> stop the GUI), it allows innovation (Steve and John), and permits software
> to go on even if the guy in charge does not want it to (change from Bob to
> Larry).
>
> Anthony: Some of these stories and people are based (loosely) upon real people
and
> stories. Some are so general as to apply to many stories. Bonus points to
> whomever can guess what the story and people are based on.
Adrian: Yes, forking has great potential and can solve many problems, but it
creates a few problems as well. Each time you fork, you divide the
workforce so the development of the project slows. Eventually, the majority
of users decide which is better and the group can reform, but a great deal
of time and effort is wasted. This is not to say that forking shouldn't be
allowed, it should, but we should not use it as our only means of dealing
with problems. It should be almost a last resort.
