Commentary

Serdar Yegulalp
 

Open Source License Auditing Tools Still Need Someone Knowledgeable Behind The Wheel

Yesterday my colleague Charles Babcock brought us the news about HP's release of the FOSSology tool, a license-auditing application that promises to help organizations cut through the thickets of software licenses that can come with open source programs.  When you get down to it, though, it's just a tool: the real decisions about software licensing have to and always must be made by warm, breathing bodies.

Yesterday my colleague Charles Babcock brought us the news about HP's release of the FOSSology tool, a license-auditing application that promises to help organizations cut through the thickets of software licenses that can come with open source programs.  When you get down to it, though, it's just a tool: the real decisions about software licensing have to and always must be made by warm, breathing bodies.


More Software Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

As Charles explained in his summary, FOSSology is an application that analyzes source code repositories of software to determine what licensing schemes are in effect for that software.  The license scheme(s) used by a given piece of code is typically described in a header prepended to the code; FOSSology crunches this information and tries to determine as best it can what licenses are being used, how they vary, and where they may clash.  A single project can have a whole congeries of different software licenses in effect; it's not always obvious what's being used or even if the code a given license is attached to is being employed.

To that end, the program's also been attuned not only to look for the texts of known licenses like the GPL, but to look for key phrases that indicate a license may be in effect (e.g., "This program is licensed..."), but it can't determine what they are offhand, and so they're broken out into their category ("Phrases").  Found texts are highlighted with differences broken out so you can see what text the program has tagged as being a likely suspect for a license.

For an absorbing demonstration of how the program works, go check out the movies that have been posted on the FOSSology site.  My favorite, since it's the most concrete and easy to follow, is one where FOSSology is set loose on Abiword and appears to detect an incompatible license scheme in the source ... but the answer may be a little more complex than that.  Go watch the video; it's nifty just on the level of basic geekery, and it also gives you an idea of how nuanced this issue can be.  (The full rundown of screenshots and demos is available here.)

As you can see from the demo, FOSSology is just a way to break this information out and make it more digestible.  It doesn't make licensing decisions for you -- no more so than, say, a spellchecker or grammar program can force you to shed unorthodox spelling or enrich your vocabulary.  That means it has to be piloted and implemented by people who already have an understanding of what's compatible with what and why.

Proprietary and open software both carry different kinds of responsibilities with them for their use.  It's not uncommon for the plethora of licenses out there to be wielded as a cudgel against open source: e.g., you better watch out, or you'll discover you have to give your software away, or some variant on that.  The way I see it, FOSSology is just one more way to shut those people up.


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