The Full Wiki

License proliferation: Wikis


Note: Many of our articles have direct quotes from sources you can cite, within the Wikipedia article! This article doesn't yet, but we're working on it! See more info or our list of citable articles.


From Wikipedia, the free encyclopedia

License proliferation refers to the problems created when additional software licenses are written for software packages. License proliferation affects the free software community. Often when a software developer would like to merge portions of different software programs they are unable to do so because the licenses are incompatible. When software under two different licenses can be combined into a larger software work, the licenses are said to be compatible. As the number of licenses increases, the probability that a FOSS developer will want to merge software together that are available under incompatible licenses increases. There is also a greater cost to companies that wish to evaluate every FOSS license for software packages that they use. Strictly speaking no one is in favor of license proliferation. Rather the issue stems from the tendency for organizations to write new licenses in order to address real or perceived needs for their software releases.


Compatible licenses

The Free Software Foundation who maintains the GNU General Public License (GPL) also maintains a list of the licenses that are compatible with the GPL. Another popular FOSS license is the Apache License, the Apache Foundation has a page discussing the fact that the Apache License is listed as incompatible with the GPL.

Vanity licenses

Vanity licenses is a term that refers to a license that is written by a company or person for no other reason than to write their own license. If a new license is created that has no obvious improvement or difference over another more common FOSS license it can often be criticized as a vanity license.

As of 2008, many people create a custom new license for their newly released program, without knowing the requirements for a FLOSS license and without realizing that using a nonstandard license can make that program almost useless to others. [1]

Google's stance

To limit license proliferation, Google limits the licenses that its source repository system would accept to the following:[2]

They also highly recommend choosing the Apache License or GPLv3 for projects. [3]

OSI's stance

Open Source Initiative (OSI) consider themselves the keepers of what licenses can be called open source. They maintain a list of licenses that are OSI Approved Licenses, and early in their history, contributed some to license proliferation by assisting in the production and approving vanity licenses. Indeed, some including Mark Shuttleworth argue that the OSI is largely responsible for the license proliferation problem by continuing to accept new licenses. The OSI License Proliferation Project has prepared a License Proliferation Report.

FSF's stance

Richard Stallman, president of FSF, and Bradley M. Kuhn, former Executive Director, have argued against license proliferation since 2000, when they instituted the FSF license list, which urged developers to use only licenses considered GPL compatible.[4]

FSFE's stance

Ciaran O'Riordan argues that the main thing that the FSF can do to prevent license proliferation is to reduce the reasons for making new licenses in the first place, in an editorial entitled How GPLv3 tackles license proliferation. Generally the FSF Europe consistently recommends the use of the GNU GPL as much as possible, and when that is not possible, to use GPL-compatible licenses.

See also

External links




Got something to say? Make a comment.
Your name
Your email address