Commentary

Chris Murphy
Editor, InformationWeek  

Your Favorite Open Source Company's Acquired. Now What?

Like all wise people, my colleague Charles Babcock knows well what he doesn't know. In the many weeks he researched his recent article, in which he explores what happens after open source companies get acquired, he often would remind me we're in uncharted waters with this trend and don't know just how it will play out.

Like all wise people, my colleague Charles Babcock knows well what he doesn't know. In the many weeks he researched his recent article, in which he explores what happens after open source companies get acquired, he often would remind me we're in uncharted waters with this trend and don't know just how it will play out.That's what makes this article vital reading. Babcock spotlights how the risks and benefits to a business IT user are different when the company behind an open source product they're using gets acquired, compared with the acquisition of a conventional software startup. The open source model is more important than ever to business IT teams, and software vendors are snapping up open source companies as a result. That brings benefits, but also risks tensions with developers and users.

In looking at the new risks, benefits, and partnerships these deals create, none's more interesting than what's happening around Xen. The open source hypervisor, a key link in server virtualization, was at the center of Citrix's $500 million deal for XenSource. Now XenSource, as part of Citrix, is closely partnered with Microsoft and pushing proprietary products, while rivals Hewlett-Packard, IBM, Oracle, and Sun build their own proprietary options around the Xen code.


More Global CIO Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

It's a new world, with new risks. Babcock's articles point to what to watch for. We hope you'll read it, and share your own wisdom of where we're headed.


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