Open Source, Free Markets, and Forking
Slashdot pointed me to a great story on forking in open source projects: how and why developers branch off from the "trunk" of a development project. I've been thinking a fair amount of the value of a fork (the kind that splits open source communities - not the kind you eat with :-), especially in light of OpenOffice.org.
OO.o is somewhat analagous to Mozilla (under Netscape's and AOL's direction): bloatware, with every possible feature one could want. So, Blake Ross forked it and created FireFox, as Wired recently reported. Today, we're the beneficiaries of Ross' lack of conformity - FireFox is much, much better than Mozilla ever was.
Back to OO.o. Why not fork it? Today, Sun does 95% of the development, but lacks the resources to take on Microsoft Office with single-minded determination. The open source community, in parallel, lacks any real incentive to take up the code (both because most don't care much for office suites and because Sun's licensing scheme ensures that they own all modifications through the JCA). Besides, the learning curve for familiarizing oneself with the code makes casual, 'drive-by' code contributions somewhat difficult.
So why doesn't some company (or a community, if one can be found) take up the OO.o banner, fork it, and offer a stripped-down version that evades OO.o's bloatware problem? I don't much like Apple's new iWorks suite - it's a bit too stripped down - but I think the idea is generally good. Someone could develop a lightning fast version of OO.o, sell it retail for $49.95, and make a good business out of it.
Wouldn't be good community practice, you say? Maybe. But in my view, forking, as the first link above identifies, encourages competition. When a project is bogging down or is otherwise not up to a class of users' preferences, it should be forked. Forking drives innovation through competition. OO.o would be the better for the fork.
