Commentary

Serdar Yegulalp
 

Bruce Perens's GPL Beef

Those who egregiously violate open source software licensing agreements, like the GPL, are targets for legal action that's just as vigilant as those that defend proprietary software. But the most recent round of GPL legal action comes with a curious twist.

Those who egregiously violate open source software licensing agreements, like the GPL, are targets for legal action that's just as vigilant as those that defend proprietary software. But the most recent round of GPL legal action comes with a curious twist.


More Software Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

First, the lawsuits. The Software Freedom Law Center has filed suit against a number of consumer electronics companies for using the BusyBox application -- a condensed set of tools used in many Linux-based devices -- without complying with the GPL. This sort of thing has happened before (here's a post from me about a previous incident), and in each case the SFLC or the copyright owners try to work with the offender to get them to fix things before resorting to legal action.

Now comes the twist. Enter Bruce Perens.

For those in the open source world, Bruce needs no introduction; he's one of the Founding Fathers of open source as we currently know it. He was also, according to a blog post he made about the above lawsuit and its ilk, the original creator of BusyBox, and is rather miffed that the current legal actions don't identify him at all as one of the aggrieved.

Bruce may no longer be one of the active developers of the program, but he insists that he still has a compilation copyright interest in the work in question -- especially the specific (earlier) versions of BusyBox named in the suit, which credits Erik Andersen and no one else as the current author.

Bruce's words:

The version 0.60.3 of Busybox upon which Mr. Andersen claims copyright registration in the lawsuits is to a great extent my own work and that of other developers. I am not party to the registration. It is not at all clear that Mr. Andersen holds a majority interest in that work.

Mr. Andersen, his past employers and Mr. Landley appear to have removed some of the copyright statements of other Busybox developers, and appear to have altered license statements, in apparent violation of various laws. Mr. Landley once claimed that all of my contribution had been completely removed from the Busybox program, using a misinterpretation of Judge Walker's methods for identifying non-literal copying to justify his claim. As far as I'm aware, he was incorrect.

I would like to believe -- me being a believer in people being mostly decent -- that the SFLC and Mr. Andersen have simply made honest omissions. Their response to this will be as telling as the responses -- or lack thereof -- of the very companies named in suits like these.

Our "A New IT Manifesto" report looks at a variety of new approaches and technologies that let IT rebels take on a whole new role, enhancing their companies' competitiveness and engaging their entire organizations more intimately with customers. Download the report here (registration required).

Twitter: Me | InformationWeek
Facebook: InformationWeek


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