/dev/urandom
RSS Feed

uRandom

(beta!!!)
Email Address Password
Remember Me

Or Create a (Free) Account.

Sun 27th Apr 00:51 2008: Organic Open Source... Wholemeal, with Extra Wheatgerms?

Ted Ts'o has been talking about Sun and Open Source, and discussing Open Source lately; he has now revisted it.

Hopefully we can omit references to 12-year-old childish reposts to childish posts, and start looking deeper into the issues that Ted raises.

Ted started by asking "what Sun was trying to do with OpenSolaris": "It was never was [sic] Sun’s intention to try to promote a kernel engineering community", but rather that "there is significantly *more* value in having a whole undivided ecosystem based on a compatible set of distributions, where application developers, university students, custom distro builders and users are all able to take advantage of each other’s work." (John Polcher)

So far, this is a fair discussion of a few of the many merits of F/OSS software development.

Ted Ts'o then added the Organic issue - the idea that sponsored F/OSS development is somehow different from purely needs-driven (ESR's "scratch my own itch" model) development. Although Ted doesn't cite ESR directly, the "organic" concept is very reminiscent of the ESR popularisation of FSF, and the subsequent "hijacking" of FSF into "Open Source" as something close to a religion. Ted's involvment in Linux predates pretty much everyone but Linus Torvalds; Ted was one of the initial contributors to Linux, and has been dedicated ever since, so I am not going to attempt to teach my grandmother to suck eggs, nor to tell Ted the history of F/OSS or how Linux - or even Apache or other F/OSS projects came to grow so dramatically in the 1990s.

Nor am I in any technical ability able to correct Ted, given his huge contribution to GNU/Linux and the F/OSS community - so why am I bothering to write this post? How very dare I, indeed?

Ted's idea of Organic F/OSS is that which is developed purely by user demand - as Apache and Linux were developed, as prime examples. Non-Organic F/OSS, by Ted's definition, are things like OpenOffice.org, MySQL (both currently Sun-Sponsored), and presumably Firefox (still largely ex-Netscape employees?), GNOME and its offshoots (still largely Novell / Ximian / etc history for its developers?)

Does corporate sponsorship somehow tarnish a F/OSS project, Ted?

I really do appreciate the differences between the development of something like Linux, or Apache, and how things such as OpenOffice.org or OpenSolaris have ended up under the same OSI umbrella. But does it really matter?

Q1: If some crappy piece of software which you don't want to use, happens to be released under a F/OSS license, does it affect you in any way?
A1: No.

Q2: If some crappy piece of software which you are (in some way) obliged to use, is released under a closed-source license, does that affect you?
A2: Potentially, Yes. Possibly not (but don't say that to RMS!)

Q3: If some fantastic piece of software which you don't want to use, happens to be released under a F/OSS license, does it affect you?
A3: No.

Q4: If some fantastic piece of software which you are (in some way) obliged to use, happens to be released under a F/OSS license, does it affect you?
A4: No.

So what is the issue, Ted? The only way in which the F/OSS community is negatively impacted, is if we are obliged to use closed source software. Sun, whatever their motivations, are not obliging you to do that.

Sun bought StarOffice a few years ago - took it, improved it (largely in-house, but with many external contributions) and, I suspect and hope, learned a lot along the way about cooperating with the F/OSS community. I'm on OOo2.4 right now, and whilst it's not perfect, it's pretty darn good as a productivity suite - the best I have used yet (though my latest alternative comparison was the pitiful MS Office, so maybe that's an unequal test). Having one major sponsor doesn't harm the project in any important way; yes, it means that if the sponsor disppeared, or abandoned the project, that the funding would disappear, but assuming that the grass-roots desire for the product existed, then (by the ESR theory) others will appear to fund the development (and, given history - many of the same developers: See the Ximian / SuSE / Novell / migration as an example).

Ted mentions support as an issue; ESR praised it as a benefit of the Open Source licensing model itself: "Sun Salescritters who were sending around TCO analysis comparing 24×7 phone support form Red Hat with Support-by-email from Sun totally missed the point.) What’s important to commercial end users is that they be able to avoid the effects of vendor lock-in, which implies that if all of the developers are employed by one vendor, it doesn’t provide the value the end users were looking for."

If there is a team of developers whose career is based upon their expertise in Apache, MySQL, Linux, Solaris, or any other Open Source technology, then those developers are sure of their ability to work in their chosen field whilst that software is in active use.

It doesn't need to matter to them, who pays the salary, just as it doesn't matter to Linux or Apache developers. Okay, they have a loyalty to their employer, but whilst their employer values their contribution to that project, then the project will thrive.

I doubt that Ted is really calling all F/OSS project development to fall under the Debian model, with a complicated hierarchy of priests, as he ended his second post with this statement:

"So while Linux may not be completely optimized in terms of “less priests” and more inclusion, at least over 1200 developers contributed to 2.6.25 during its development cycle. Compared to that, Open Solaris is positively dominated by “high priests” and with a “you may not touch the holy-of-holies” attitude; heck, they won’t even allow you to compare them to other religions without branding you a heretic and suing you for licensing violations!"

I'm not sure quite what the point is, though. I don't have the figures to hand of how many individuals committed changes to Linux 2.6.25, or Solaris 11.whatever, or who they are employed by (and why), but Ted has provided no evidence for such strong mentions of "branding you a heretic and suing you for licensing violations!"

I strongly prefer to use Free Software. I also think that Sun create particularly good Hardware and Software. The fact that nearly all of their Software stack is now Open Source, brings me back to how proud I am that Sun employed Bill Joy to write vi (I admit - I use vim now) - if they had done nothing else, that would earn them a place in F/OSS history. That Bill was a co-founder gives Sun an even bigger place in F/OSS history.

The F/OSS community is also, largely, based around the concepts of UNIX - *BSD, Linux, UNIX... the technical foundations are all in the same places - (mainly AT&T, MIT and Berkeley, let's admit it).

The whole Organic -vs- Non-Organic issue is not an issue. I have huge respect for Ted Ts'o and his work, but Ted: we're all in same camp, fighting on the same side.

Steve


Comments for 'Organic Open Source... Wholemeal, with Extra Wheatgerms?'

Sun 27 Apr 2008 @ 02:30 GMT : Ted Ts\\\'o (Anonymous Poster)
I don't think you understood what I was trying to get at....
Ted's idea of Organic F/OSS is that which is developed purely by user demand - as Apache and Linux were developed, as prime examples.

No, that's not what I was trying to get at. Look, let's use a pure Linux example. JFS was a filesystem that is in OS/2 and AIX, which was reimplemented and contributed to Linux by IBM. It was released under an open source license, but the only developers who understood it worked at IBM. As a result, only SuSE supported in their distribution, and then only reluctantly, and ultimately JFS has gone into maintenance mode, even though initially it was better technologically than ext3.

In contrast, the ext3 filesystem had, and still has, developers from many different companies: IBM, Red Hat, Google, Bull, NEC, and now, even Sun (due to the Clusterfs acquisition). As a result, the funding for ext3 development came from multiple companies, and so the total amount of funding was more. Also, the work done by the Clusterfs folks was to enable their product, and it enhanced ext3/ext4 in ways which IBM or Red Hat wouldn't consider doing because the business justification just wasn't there. In addition, because there was a large base of developers from many companies, it also helped assure Linux distributions that they had expertise in house to support customers who might have issues with that particular filesystem?

The result, ext3, and now ext4 has prospered, and while JFS was initially superior technologically, ext4 has surpassed JFS. So within Linux, I would call ext3/ext4 more "organic" than JFS, which because all of the developer expertise comes from a single company, I would call "non-organic", or "synthetic". And, if I were choosing a filesystem, I would to choose one which was widely supported across a large number of companies.

This is one of the reasons why I have been encouraging many companies in the Linux ecosystem to support btrfs --- a filesystem which I believe in the long run will supplant ext4. But in order to successful, the support for btrfs has to be organic. If the only developers for btrfs come from a single company (such as Oracle --- the original author of btrfs works for Oracle), its chances for success will be much lessened.

So no, I absolutely do not believe that having corporate support "tarnishes" a project. In fact, as I pointed out, most of apache's contributions had implicit corporate support from many companies. My argument is to be successful, it's ideal if a project has developers from many corporations. That way, the costs get shared, and each company can improve the project in ways that meet its own business objectives. It's the true "stone soup" model.

In contrast, Sun is having to spend a fair amount of resources integrated patches to support laptops in order to assure Open Solaris's success. That doesn't directly support Sun's business bottom line, but it's overhead necessary to keep the platform alive, at least according to Jonathan Schwartz (and I'd agree with him). In contrast, IBM spends little to no money on Linux desktop support, because IBM is a server-centric company. Instead, companies like Ubuntu and Dell and now Lenovo support aspects of Linux's laptop support.

Hence, the organic model is much more sustainable, from a corporate budgeting point of view.

You could post a comment if you were logged in.

create an account



© Steve Parker 2000 - 2010 unless otherwise noted.