Commentary

Serdar Yegulalp
 

Canola's GPL Trick

The name Canola probably makes you think of vegetable oil, but it's also the name of a newly open sourced media-center application for tablet-style PCs that run Linux. And whenever something is newly open sourced, that almost inevitably means close attention is paid to the terms of the licensing.

The name Canola probably makes you think of vegetable oil, but it's also the name of a newly open sourced media-center application for tablet-style PCs that run Linux. And whenever something is newly open sourced, that almost inevitably means close attention is paid to the terms of the licensing.


More Software Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

The first striking point: the license the Canola developers chose is the GPLv3 -- a derivate of the broadly-used GPLv2. V3 tightens up a number of loopholes (those revolving around what's been labeled the "Tivoization" issues), but the exact implementation of any stock software licensing scheme is of course up to the licensor. I couldn't tell you how many variations I've seen of the BSD three-clause license, some of which were intentionally hilarious (along the lines of "Do not use this software to do bad things or I will come over to your house and shaving-cream your car") -- but that's another story.

Where things get interesting is the exact application of the license. The Canola team went with GPLv3, but added an exemption: the licensee isn't obliged to include installation information and source code along with the program when they redistribute it. In short, it's a fusion of v2 and v3, and the license experts who eyeballed the changes are A-OK with that.

What I'm now bracing for is a backlash from the rest of the community -- from people who have made hard decisions about choosing v2 vs. v3, and are now going to excoriate Canola for "fence-straddling" or something equally imbecilic. If it doesn't happen, I'll be pleasantly surprised -- but changes to licensing and arguments over licensing seem, historically, to go hand-in-hand.


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