Commentary

Serdar Yegulalp
 

Will MS + Yahoo = The Death of Zimbra?

One of Yahoo's acquisitions back in September '07 was Zimbra, an open source (MPL) groupware product that's garnered a reputation as a solid alternative to Microsoft Exchange.  Now, with Microsoft prepping a potential buyout of Yahoo, there's real fear in the air that Zimbra may be one of the casualties.

One of Yahoo's acquisitions back in September '07 was Zimbra, an open source (MPL) groupware product that's garnered a reputation as a solid alternative to Microsoft Exchange.  Now, with Microsoft prepping a potential buyout of Yahoo, there's real fear in the air that Zimbra may be one of the casualties.


More Software Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

At first the picture doesn't seem so bleak.  Zimbra's open source, so we could just fork it and be done with it.  But there's key components of the commercial edition of Zimbra that are closed source, which many customers depend on, and can't be forked or relicensed as easily.

One of the concerns voiced by existing Zimbra users in an ongoing message thread is what will happen to customers who spent money on the commercial version.  If Microsoft's buyout goes through and it decides to let Zimbra die (or actively kill it), those people may be left twisting in the wind.

Zimbra, meanwhile, continues undaunted with the launch of the 5.0 version of its product.  I especially liked the line: "I can confidently say that the Zimbra movement is bigger than any one company."

Groklaw has its own analysis as well, and one sentence in particular stuck with me: "Now we see what mixed licensing results in. Trying to be [both] FOSS and proprietary is tricky."  Unfortunately, in a world like this, mixed licensing may be one of the more solid ways to get open source to gain traction with the people who can become its biggest and most important advocates.


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