Commentary

Serdar Yegulalp
 

From Many Models To A Few?

In my last post I talked a bit about an ongoing effort to build a taxonomy of open source business models. As with open source licenses, one could argue that over time there will be a consolidation of business models, too -- so if that does happen, which ones will lead the pack?

In my last post I talked a bit about an ongoing effort to build a taxonomy of open source business models. As with open source licenses, one could argue that over time there will be a consolidation of business models, too -- so if that does happen, which ones will lead the pack?


More Software Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

From the list in question, three stand out the most by virtue of being the most broadly or visibly adopted: dual licensing, open core, and support providers. These are the three business methods that get the lion's share of discussion and adoption from what I've seen, and which lend themselves to being the most used if only because they've yielded the most visibly reliable results.

But are they likely to become the only ways to go? The question comes to mind because of the corresponding narrowing-down in OSS licensing: the great swath of licenses out there (sometimes competing, conflicting, and contradictory) is winnowing itself down to a select, easily-identified few. Most of that comes from simple trial and error: we all tried out different ways of licensing, and found after a while that the vast majority of what we might want to accomplish could be covered by a few basic approaches: GPL, Apache, MIT / copyleft / public domain, etc.

If there's to be a corresponding narrowing of commercial open source approaches, it may not be for a bit yet. The reason we've started to see such an aggressive winnowing of licensing schemes is because the work done in this regard has been happening for a lot longer, and with extremely fierce and contentious discussion, than commercial open source providers have been doing their thing. Give commercial OSS a few more years, time enough for the different approaches to show their strengths through good times and bad, and the field may narrow down.

I say "may" because from what I've seen, I don't think the business models are going to narrow down to the extent that licensing will. One basic reason for this stands out: the exact choice of business model tends to only affect the business in question, but the choice of licensing affects everyone.

If anything, I'd expect the variety of commercial OSS models to broaden, not narrow down with time -- both to reflect the variegated demands of the market, and the ingenuity of those making OSS into something we all use.


InformationWeek Analytics has published an independent analysis of the challenges around virtualization management. Download the report here (registration required).


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