The Changing Face of Open Source



Email    print   
January 1, 2006 —  (Page 1 of 2)
The term “open source” may evoke a romantic image of programmers working late into the night on projects that have caught their interest. In the footsteps of Richard Stallman and Linus Torvalds, they selflessly toil away, contributing their work freely to the greater good, both in binary and source code form, all the while forgoing any remuneration. This enduring and endearing image, alas, is steadily losing any connection to the real world of open-source products as they exist today. And understanding the differences is key to finding your way around the open-source landscape, as we’ll see shortly.

First, the reality. Open-source programming today is almost entirely a commercial affair. On most projects, the majority of the code is written by full-time developers whose employers are interested in providing support to a specific project.

Earlier this year, I attempted to find out exactly how much these paid developers contribute when compared with independent contributors. I spoke with Marc Fleury, who heads up JBoss, the now-company that once built a full J2EE suite using the old-style community model with Fleury leading the effort. He told me that today, no more than 1 percent of the code comes from independent developers. Mike Milinkovich, who leads the Eclipse Foundation, speculated that the source-code contributions of independents was even less than that. (But, he pointed out, independents do make terrific beta testers.)

This shift from amateurs (in the word’s original sense of doing something for the love of it) to paid professionals has several causes.

The first derives from the complexity of programming today. Most developers must learn daunting codebases to find the routine to which they can add value. And even when they find it, making sure they are actually adding value is another complex process entirely. Only developers who really need the software feature have the motivation to consecrate so much time and effort to making small changes. (Large feature changes are, in many cases, insuperably difficult.)




Pages 1 2 


Share this link: http://sdt.bz/29050
 
Most Read Latest News Blog Resources

Add comment


Name*
Email*  
Country     


  • Comment
Loading




close
NEXT ARTICLE
Git changes how developers manage source code versions
At this year's Git Together, developers praise the platform's convenience and its ability to make source control easier. Changes for the future will focus on making it more Web 2.0-compatible by offering more on-demand repositories on GitHub Read More...
 
 
 
 
News on Monday
more>>
SharePoint Tech Report
more>>


   

 
 

Download Current Issue
FEBRUARY 2012 PDF ISSUE

Need Back Issues?
DOWNLOAD HERE

Want to subscribe?


 
blogs tab
Are you at risk for burnout?
Burnout is a severe problem and it can strike at any time. Here's how to tell if you are nearing the edge.
02/09/2012 02:16 PM EST

Agility, mom, and apple pie
If we're to evaluate the state-of-the-art in software development, we should start with the values espoused in the Agile Manifesto.
02/07/2012 11:57 AM EST

RIM woos developers with free tablet
How do you get more apps ported to the BlackBerry PlayBook? By giving every developer a free tablet, of course!
02/04/2012 01:57 PM EST

GitHire: Use Headhunters to Find Your Perfect Programmer
Are you a hiring manager tired of scouring the job boards? Check out this new service that will find 5 people interested in your jobs.
02/03/2012 12:17 PM EST

Facebook claims hacker cred
Facebook's SEC S-1 filing form includes a short essay on the Hacker Way by Mark Zuckerberg himself.
02/02/2012 08:26 AM EST

Ryan Dahl steps down
Ryan Dahl, creator of Node.js, steps back from his position as gatekeeper for the project.
02/01/2012 04:58 PM EST

 
Events calendar tab
2/13/2012 to 2/16/2012
Santa Clara
TechWeb

2/26/2012 to 2/29/2012
San Francisco
BZ Media

2/27/2012 to 3/2/2012
San Francisco
RSA

3/4/2012 to 3/7/2012
Las Vegas
IBM Tivoli

3/5/2012 to 3/9/2012
San Francisco
TechWeb