Linked by Thom Holwerda on Mon 18th Oct 2010 21:56 UTC, submitted by poundsmack
Features, Office "A group of key contributors and community members recently decided to fork the project and establish The Document Foundation in order to drive forward community-driven development of the open source office suite. Oracle has responded to the move by asking several members of TDF to step down from their positions as representatives on the OOo community council."
Permalink for comment 445644
To read all comments associated with this story, please click here.
Unfortunate impasse with this fork
by BlueofRainbow on Tue 19th Oct 2010 00:32 UTC
Member since:

As an user of software, I have encountered what appears to bad forks as well as good ones.

I see a good fork as one when a group of interested developers takes ownership of the code from a developer-owner who has essentially retired from the project he/she has created. The case of Syllable (from Atheos) comes to my mind. I'm sure there are many others, even some in which the original developer-owner continues later on in a slightly different direction/fashion while remaining "compatible" on the core of the project.

I see a bad fork as one when a group of interested developers seeking to bring improvements to a project, yet is seemingly forever being denied/hold back by the original developer-owner splits from the committee/organization overseeing the project. Divergences in direction of a project do not have to lead to this - however this appears to be a frequent situation in most technology driven projects.

Not being intimate with the whole background, I see the story as one about a bad fork although in this case, the original developer-owner also maintains an independent (commercial) branch of the code.

From this, I feel that it would be better if The Document Foundation has the same status as that of Oracle within the OpenOffice Org and that both - with their respective own branches of the code - remain in collaboration to have an aligned common core which would allow sharing of improvements for the ultimate benefit of the end-users.

Reply Score: 2