Commentary

Serdar Yegulalp
 

Microsoft and Linux Foundation Agree To ... Agree!

Is that flapping sound I hear the wings of pigs? Microsoft and the Linux Foundation both agree on something? Yes. In this case, it's proposed guidelines for software licensing that would make both open source and proprietary software authors that much more liable.

Is that flapping sound I hear the wings of pigs? Microsoft and the Linux Foundation both agree on something? Yes. In this case, it's proposed guidelines for software licensing that would make both open source and proprietary software authors that much more liable.


More Software Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

This tidbit actually came my way courtesy of sister pub CRN:

The [American Law Institute] is proposing that two new "non-disclaimable" warranties be added to best practice guidelines for software licensing. One warranty would make software developers liable for infringing on patents and copyrights, while the other would make contributors to open-source software liable for material defects in the software. The law currently allows contributors and licensors of open source to avoid liability by offering their wares on an "as-is" basis.

... The ALI's proposal would also take away commercial software vendors' ability to draw up End User License Agreements (EULAs) that distance themselves from any kind of warranty that their software is bug-free, Locke added.

Neither Jim Zemlin nor Microsoft's chief of counsel thinks this is a good idea, and they drafted a joint letter detailing their dismay with the whole thing.

If the purpose here is to insure that software authors cannot duck responsibility for writing bad software, there are better ways to do it. Example: pressuring software makers to provide more software in trials forms, for instance, where you can run it provisionally to determine if it suits your needs before spending money. I hardly need to recap how this is the case for a good deal of open source, but many people are not aware that many of Microsoft's own full products come in time-limited (30, 90, 120 days) editions. (It gets that much easier with virtualization, too, although that's not always the most straightforward process.)

I can't find anyone (apart from a lawyer) who actually likes EULAs or click-to-agree licensing, but let's face it: a certain amount of CYA paperwork is inevitable. Disclaimers like the ones offered in the GPL -- or in any number of other software products, for that matter -- exist precisely because software is so malleable. It's a great thing when people are able to void the warranty on something in a creative way. It's not a great thing when they mistakenly kill the neighbor's cat in the process. Since nobody who creates a piece of software can possibly account for or foresee all of its future or even present use, these kinds of disclaimers are inevitable.


InformationWeek Analytics has published an independent analysis of the current state of open source adoption. 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