Sun Leaves License Behind
One of the biggest headaches in the Open Source world is the myriad of licenses available , many of which are incompatible with one another. These incompatibilities are troublesome enough between two separate projects, but when multiple licenses are used within the same software, the difficulties grow exponentially. Yesterday was a blow against multiplicity, as Sun decided to do something about it.
The Open Source Initiative lists no less than sixty five licenses certified as Open Source through the Initiative's license review process. These include the ubiquitous GPL and its family of variants, the Apache License, at least BSD licenses, the Mozilla Public License, the MIT license, and a host of lesser-known but nonetheless complicating licenses. The list does not, of course, list the wide range of licenses that have not been reviewed. Attempting to work one's way through them all requires a machete, Tenzing Norgay, and an advance reservation for a padded room.
One project with a proliferation of licenses — though thankfully compatible — is X.org. We count some seventy-six separate licenses in the xorg/xserver's COPYING file, most of which are derivatives of the "standard" license, itself an MIT license. Most derivatives bear roughly the same language along with a single distinguishing feature:
...and that the name of [the copyright holder] not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission.
That file will soon have one less license, however, as Sun Microsystems' Alan Coopersmith announced yesterday that the company will begin licensing its contributions under the "standard" license, which does not bear the advertising/publicity provision. Further, Sun will re-license all of its prior contributions — some twenty-one years of substantial contribution — under the "standard" licenses, ridding the code entirely of its derivative license.
Coopersmith indicated that more than five hundred files will require editing. He noted, however, that contributors not affiliated with Sun should not change these notices, as the changelogs serve as an official record of the actions taken. In having specifically authorized Sun representatives make the changes, a paper trail of sorts is created, ensuring that any future issues regarding the licensing can be resolved quickly. He went on to say that if anyone has a pressing need for a particular file to be re-licensed posthaste, he can be contacted and will see that it is.
Justin Ryan is a Contributing Editor for Linux Journal.
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Sponsored by AMD
Built-in forensics, incident response, and security with Red Hat Enterprise Linux 6
Every security policy provides guidance and requirements for ensuring adequate protection of information and data, as well as high-level technical and administrative security requirements for a system in a given environment. Traditionally, providing security for a system focuses on the confidentiality of the information on it. However, protecting the data integrity and system and data availability is just as important. For example, when processing United States intelligence information, there are three attributes that require protection: confidentiality, integrity, and availability.
Learn more about catching the bad guy in this free white paper.
Sponsored by DLT Solutions
| Designing Electronics with Linux | May 22, 2013 |
| Dynamic DNS—an Object Lesson in Problem Solving | May 21, 2013 |
| Using Salt Stack and Vagrant for Drupal Development | May 20, 2013 |
| Making Linux and Android Get Along (It's Not as Hard as It Sounds) | May 16, 2013 |
| Drupal Is a Framework: Why Everyone Needs to Understand This | May 15, 2013 |
| Home, My Backup Data Center | May 13, 2013 |
- New Products
- Linux Systems Administrator
- Senior Perl Developer
- Technical Support Rep
- UX Designer
- Web & UI Developer (JavaScript & j Query)
- Designing Electronics with Linux
- Dynamic DNS—an Object Lesson in Problem Solving
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Using Salt Stack and Vagrant for Drupal Development
- Reply to comment | Linux Journal
2 hours 47 min ago - Reply to comment | Linux Journal
3 hours 3 min ago - Favorite (and easily brute-forced) pw's
4 hours 54 min ago - Have you tried Boxen? It's a
10 hours 46 min ago - seo services in india
15 hours 18 min ago - For KDE install kio-mtp
15 hours 18 min ago - Evernote is much more...
17 hours 18 min ago - Reply to comment | Linux Journal
1 day 2 hours ago - Dynamic DNS
1 day 2 hours ago - Reply to comment | Linux Journal
1 day 3 hours ago
Enter to Win an Adafruit Pi Cobbler Breakout Kit for Raspberry Pi

It's Raspberry Pi month at Linux Journal. Each week in May, Adafruit will be giving away a Pi-related prize to a lucky, randomly drawn LJ reader. Winners will be announced weekly.
Fill out the fields below to enter to win this week's prize-- a Pi Cobbler Breakout Kit for Raspberry Pi.
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- 5-21-13, Prototyping Pi Plate Kit: Philip Kirby
- Next winner announced on 5-27-13!
Featured Jobs
| Linux Systems Administrator | Houston and Austin, Texas | Host Gator |
| Senior Perl Developer | Austin, Texas | Host Gator |
| Technical Support Rep | Houston and Austin, Texas | Host Gator |
| UX Designer | Austin, Texas | Host Gator |
| Web & UI Developer (JavaScript & j Query) | Austin, Texas | Host Gator |
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?



Comments
What's the problem?
Sure, there are a lot of open source licenses. But, nearly every proprietary program out there has a custom license tailored to it. Is that situation somehow better? It seems to me that a mere 65 licenses is a vast improvement, especially when you consider that a handful of them account for most of the free software out there.
NOSA
Also see that the list contains NASA Open Source Agreement, an ugly non-free license.
I wonder how they could've reviewed it and still decide that it's "open".
That's one of the reasons I'll stick with "free".
P.S. The small tux on the right was automatically put here ;-)