My Photo

Disclaimer

  • This is my personal weblog. The opinions expressed are my own and not those of my employer. My work related blog is at Microsoft StartupZone.

Enter your email address:

Delivered by FeedBurner

« Are Google Apps a productivity killer? | Main | Ning versus Live Spaces and Yahoo Groups »

TrackBack

TrackBack URL for this entry:
http://www.typepad.com/services/trackback/6a00d8341bf9da53ef00d8347b051f69e2

Listed below are links to weblogs that reference Who wrote Linux 2.6.20? How large is the community?:

» Are there really thousands of little elves writing open source software? from StillSecure, After All These Years
Don Dodge on The Next Big Thing has a good article up today about who really wrote the Linux source code and based upon that how big is the community and what do they really do. A lot of what [Read More]

Comments

"How many of you have made changes to the source code? 8%
Very few Open Source users ever touch the source code. So is it really about the source code? "
I think that speaks for CIO's (the pool you polled). I think the majority of users that actually modify code modify smaller programs/utilities/etc rather than larger applications and much less the kernel.

Cory, I get yor point about the audience, but the assumption was that the CIOs were responding on behalf of all the developers at their company. No offense, but most CIOs don't code...and shouldn't.

I also agree that probably most modifications to source code are very simple tweaks to utilities, drivers, and controls.

However, it is still surprising how few companies actually touch the source code. I think it is just the comfort in knowing that they can if they need to.

I believe that Open Source for the developers its about the code and for the CIO its about price and for both its about freedom.

It's not about modifying the source code; it's about being able to read it and find out how things work. Making changes to your own copy of a project is best avoided, as you'll have to merge those changes in to future versions of the software (unless you can convince them to accept your changes back in to the trunk).

Being able to see exactly how the software you are running works is invaluable, both for working around bugs and for writing extensions. Most popular open-source tools include an extension or plugin mechanism which offers some level of protection against changes in the software breaking your custom code.

Of course it's also about having an insurance policy. If you have access to the source code (and a license to do what you need with it) you don't have to trust your vendor not to discontinue support, as happened to several million Visual Basic programmers a few years ago.

Google maintains its own Linux kernel which they've forked a LONG time ago.

Ingo Molnar works for Google now btw but apparently they're going to allow/want him to work on the mainline kernel.

It is not about the source code, it is about who can influence the direction of the software. With open source no one can have power to influence like MS with Windows. The beauty of OSS is that they are influenced by democratic process with balance of all stake holders.

Anyway your discovery is very revealing and killing big myth about OSS.

Thanks for all the comments. I agree that part of the appeal of Open Source is the ability to look at the source code to see what it is doing, and perhaps how to tune it. I also agree that having the source is an "insurance policy" of sorts, just knowing that you have the source and can change it if you ever want to.

Just to be clear, this is NOT my research. The fine people at Linux News Weekly did the research and published it on their site. See the link above. I am simply adding my experience, my(biased)opinions, and the results of a live CIO survey I conducted recently.

BTW, Chris DiBona at Google is a personal friend. Chris is in charge of all open source programs at Google, an outstanding author of many software books, and formerly associated with Slashdot. My "Where is Google?" question is not a swipe at Google...I was just surprised.

I think that it is foolish to belive that no one has the influence over OOS like MS has over Windows. Microsoft actually has a lot less control over their OS than they would like. Their customers, especially their major corporate customers, have a huge influence over the development of Windows. Even non-MS products like Samba have resulted in changes to Windows.

Companies like IBM also have a much larger influence over open source than most people seem to realize, and they do leverage it to their advantage. Consider the ODF/OpenXML debate in which IBM is trying to kill OpemXML, something open source proponents have been demanding for years, in order to sell more copies of Lotus.

"A small number of companies contribute most of the code to Open Source development, so is it really about the community?"

Don't forget that there's much more to community contributions than just writing source code. I'm a software developer, but generally don't work on the code for open source products that I use.

However, I do make numerous contributions in terms of filing bug reports, helping out users on mailing lists, etc.

Not everyone donates code. Some people donate QA. Some people donate tech support. Some people donate marketing (e.g., via blogging and evangelizing).

Looking at open source community contributions only from the perspective of code will give you a misleading picture.

Verify your Comment

Previewing your Comment

This is only a preview. Your comment has not yet been posted.

Working...
Your comment could not be posted. Error type:
Your comment has been saved. Comments are moderated and will not appear until approved by the author. Post another comment

The letters and numbers you entered did not match the image. Please try again.

As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.

Having trouble reading this image? View an alternate.

Working...

Post a comment

Comments are moderated, and will not appear until the author has approved them.

Subscribe