Commentary

Serdar Yegulalp
 

Copyright Ruling For Open Source: Good And Bad News?

The other week, the open source community enthusiastically welcomed a court ruling that set a strong precedence for open source licensing. Not everyone was enthusiastic, though. Among the cautionary dissenters is Michael P. Bennett, partner, Wildman Harrold (Chicago). To Michael, it's a two-edged sword that can harm as much as it can help.

The other week, the open source community enthusiastically welcomed a court ruling that set a strong precedence for open source licensing. Not everyone was enthusiastic, though. Among the cautionary dissenters is Michael P. Bennett, partner, Wildman Harrold (Chicago). To Michael, it's a two-edged sword that can harm as much as it can help.


More Software Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

In a prepared statement released earlier in the week, Michael put it this way:

As a result of this  ruling, it is much more likely that courts will treat future violations of open source licenses as copyright infringement, and that they will grant injunctive relief to copyright holders seeking to enforce their rights under those licenses.

Plaintiffs now have a ready-made argument that violations of the conditions of open source licenses should be treated as copyright infringement and accused infringers will have to face the prospect that shipment of their software or products containing software alleged to infringe an open source license could be instantly stopped by injunction.

I got in touch with Michael and asked him a few further questions:

Q: As I understand it, the case in question established that a copyright infringement case can be brought against someone who violates an open source license. Is your reading of it that anyone who feels they have a copyright infringement case against a given piece of OSS can create real problems for the authors of the software -- making this, in effect, a two-edged sword?

A: In some ways, open source software is like any other software. Authors of OSS must take care in how they create their software. In any dispute, there will be important facts that affect the rights of the parties. Was the copied code expressive? Was it functional? Was it distributed? Like anyone else, if an OSS author copies another author's work, the copier could be sued for infringement. The bottom line is that all authors, OSS authors included, must take care.

Q: The open source community has a history of attempting to negotiate with potential violators first, rather than resort to legal action immediately. Do you think this would change that?

A: Recently, both domestically and internationally, some elements of the open source community have been more aggressive in pursuing disputes in courts. For years there were no cases dealing with substantive open source issues. Recently, seven cases have been filed in the U.S alone. Many important questions remain related to OSS and there are always risks for both parties when pursuing resolution through the courts.

Q: Most of the existing OSS licenses use copyright (as opposed to Creative Commons / "copyleft") as part of their methodology. Do you feel this ruling might compel a rethinking of this?

A: Copyright is the basis for all open source license models. This decision should prompt companies who use or distribute OSS to carefully evaluate each piece of licensed intellectual property they use or distribute and establish a proactive licensing compliance plan. Some companies will be comfortable using "copyleft" software, while others won't. The important thing is that each company thoughtfully evaluates its options when licensing new software, whether it be permissively licensed open source software, "copyleft" software, or a traditional commercial software.

I'll definitely have more to say about this subject shortly, but for now I'm curious to see what the readers think.


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