Commentary

Serdar Yegulalp
 

'Gap Insurance' For Open Source

Over at Forbes.com I spied an article with the intriguing title "The Open-Source Collaboration Gap," which delves into the whole question of why the vast majority of contributions to open source projects come from individuals and not companies or institutions. Two questions came to my lips: 1) Is that the case? and 2) If so, why?

Over at Forbes.com I spied an article with the intriguing title "The Open-Source Collaboration Gap," which delves into the whole question of why the vast majority of contributions to open source projects come from individuals and not companies or institutions. Two questions came to my lips: 1) Is that the case? and 2) If so, why?


More Software Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Question #1 is in fact addressed in the article, based on conversations with folks who ran both commercial projects (Alfresco) and nonprofit ones (Eclipse). Both of them reported that far more individual than institutional users committed changes to their projects.

The reason for this was because the groups were often more interested in providing functionality that supported something they needed as a group rather than something an individual might want. Also, when you are part of a group, you're committing on behalf of the whole group, not just yourself. It's far easier to do that sort of thing when it's just you -- easier, even if doesn't always yield the breadth of results possible from having many hands at work.

What I'd like to see where possible is more companies setting up open source "incubators" that serve a dual purpose: to allow those in the incubator to contribute back changes both in an individual, maverick way and on behalf of the company as a whole. The time and resources they'd spend on each of these things would be negotiable, but by doing this they could enjoy the flexibility of being individual and corporate contributors in the same breath.

I doubt there's any one model for how this could work -- they could be a formal subdivision of the company, or a fully sponsored offshoot like Eclipse, depending on the scope of their involvement and their own inclinations. But having something of this variety is shaping up to be the latest version of, say, having a CIO at all.

The more you use open source, the greater your chances of giving back in some form -- and the more you give back, the better your chances of finding yourself in a position where you'll be able to shape what you use for the better instead of just consuming it.


Each year, InformationWeek honors the nation's 500 most innovative users of business technology. Companies with $250 million or more in revenue are invited to apply for the 2009 InformationWeek 500.


Follow me and the rest of InformationWeek on Twitter.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links