How Open Source Licenses Affect Your Business and Your Developers

For most of the 2000s, copyleft licenses (in particular the GPLv2) were the most popular choice for new open source projects. In the last few years, developers and companies seem to be trending away from the GPL in favor of permissive licenses for open source projects. What's behind that, does it impact your business and what licenses should you choose for new projects? Let's take a look.

The GPL is in decline, sort of. As Matthew Aslett reported last year, the number of projects using the GPL family has increased in real terms.

However, the usage of the GPL as a percent of all open source projects is in decline. According to Aslett, in 2008 the GPL family was 70 percent of licenses. As of December of 2011, it was 57 percent. Clearly, there is a trend at least for now towards permissive licenses.

Defining Permissive Licenses and Copyleft

To continue reading, register here to become an Insider. You'll get free access to premium content from CIO, Computerworld, CSO, InfoWorld, and Network World. See more Insider content or sign in.

For most of the 2000s, copyleft licenses (in particular the GPLv2) were the most popular choice for new open source projects. In the last few years, developers and companies seem to be trending away from the GPL in favor of permissive licenses for open source projects. What's behind that, does it impact your business and what licenses should you choose for new projects? Let's take a look.

The GPL is in decline, sort of. As Matthew Aslett reported last year, the number of projects using the GPL family has increased in real terms.

However, the usage of the GPL as a percent of all open source projects is in decline. According to Aslett, in 2008 the GPL family was 70 percent of licenses. As of December of 2011, it was 57 percent. Clearly, there is a trend at least for now towards permissive licenses.

Defining Permissive Licenses and Copyleft

For those who don't spend a lot of time thinking about open source licensing, let's look at the differences between permissive licenses and copyleft.

Copyleft licenses look to protect developer and user rights. As the Free Software Foundation puts it, the GPL protects the "four freedoms":

• The freedom to run the program, for any purpose.
• The freedom to study how the program works and change it so it does your computing as you wish.
• The freedom to redistribute copies so you can help your neighbor.
• The freedom to distribute copies of your modified versions to others.

You can do all of those things with a permissively licensed project, but what the permissive licenses do not do is carry any requirement that the recipient of the software pass those freedoms on to their users.

For example, companies that work with the Linux kernel and distribute it are obligated to make source available to their users. This is frequently a problem when companies distribute modified GPL'ed software like the Linux kernel or Busybox in embedded devices and neglect to make source available.

Why Companies Like Permissive Licenses

On the other hand, this is not a problem for companies that are distributing software under a permissive license. There are some requirements around copyright notices for some permissive licenses, but they don't require companies to distribute modifications.

In the eyes of some companies and developers, the permissive licenses have several practical advantages.

First, they allow companies to create proprietary versions of software if they choose. Some companies want the option to distribute a proprietary version and don't like the idea of having to use the GPL for derivative works.

In some cases, it's simply a matter of convenience. The GPL doesn't always mix well with other open source licenses. Dealing with the licensing questions that come along with GPL software can be a headache for companies.

Compliance is also a bit of a headache for companies that are not adept at dealing with open source. Ensuring that your company distributes the source and complies fully with the GPL, including making sure that if the GPL is combined with other works that it is license-compatible, can require a fair amount of attention.