License compatibility

License compatibility

License compatibility refers to the problem with licenses of software packages which can contain contradictory requirements, rendering it impossible to combine source code from such packages in order to create new software packages. [ [http://www.linuxdevices.com/articles/AT7188273245.html How GPLv3 tackles license proliferation ] ]

For example, if one license says "modified versions must mention the developers in any advertising materials", and another license says "modified versions cannot contain additional attribution requirements", then, if someone combined a software package which uses one license with a software package which uses the other, it would be impossible to distribute the combination because the two requirements cannot be simultaneously fulfilled. Thus, these two packages would be license-incompatible. [cite web
url=http://fsfeurope.org/projects/gplv3/fisl-rms-transcript#license-compatibility
title=Stallman explains license compatibility while discussing GPLv3|
]

Not all licenses approved by OSI or by the Free Software Foundation are compatible with each other, thus not all the code under OSI or FSF approved licenses can be mixed. For example code under Mozilla Public License can't be mixed with code under GNU General Public License (both licenses are OSI and FSF approved). The "FLOSS License Slide" shows if some common licenses are compatible [ [http://www.dwheeler.com/essays/floss-license-slide.html The Free-Libre / Open Source Software (FLOSS) License Slide ] ] .

GPL compatibility

Many of the most common free software licenses, such as the original MIT/X license, the BSD license (in its current 3-clause form), and the LGPL, are "GPL-compatible". That is, their code can be combined with a program under the GPL without conflict (the new combination would have the GPL applied to the whole). However, some free/open source software licenses are not GPL-compatible. Many have strongly advocated that free/open source software developers use only GPL-compatible licenses, because doing otherwise makes it difficult to reuse software in larger wholes [ [http://www.dwheeler.com/essays/gpl-compatible.html Make Your Open Source Software GPL-Compatible. Or Else ] ] .

Also see the list of FSF approved software licenses for examples of compatible and incompatible licenses.

See also

*License proliferation

References


Wikimedia Foundation. 2010.

Игры ⚽ Поможем сделать НИР

Look at other dictionaries:

  • Compatibility — may refer to: Astrological compatibility Compatibilism – a philosophical position Compatibility (geochemistry) Compatibility (chemical) Compatibility (mechanics) Electromagnetic compatibility Interpersonal compatibility Computing Pin… …   Wikipedia

  • 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… …   Wikipedia

  • Mozilla Public License — Author Mozilla Foundation Version 1.1 Publisher Mozilla Foundation DFSG compatible Yes[1] …   Wikipedia

  • GNU General Public License — infobox software license name = GNU General Public License caption = The GNU logo author = Free Software Foundation version = 3 copyright = Free Software Foundation, Inc. date = 29 June 2007 OSI approved = Yes Debian approved = Yes Free Software …   Wikipedia

  • Technology Compatibility Kit — A Technology Compatibility Kit (TCK) is a suite of tests that at least nominally checks a particular alleged implementation of a Java Specification Request (JSR) for compliance. It is one of the three required pieces for a ratified JSR in the… …   Wikipedia

  • Apache License — infobox software license name = Apache License caption = The Apache logo author = Apache Software Foundation version = 2.0 copyright = Apache Software Foundation date = January 2004 OSI approved = Yes Debian approved = Yes Free Software = Yes GPL …   Wikipedia

  • Affero General Public License — infobox software license name = GNU Affero General Public License caption = The GNU logo author = Free Software Foundation version = 3 copyright = Free Software Foundation, Inc. date = 2007 11 19 Free Software = Yes GPL compatible = Yes (permits… …   Wikipedia

  • Ricoh Source Code Public License — The Ricoh Source Code Public License is a software license, generally compatible with the GPL, intended for open source software creation.OverviewRPL : Ricoh Silicon Valley, Inc., a California corporation, wrote the license. It is used for a… …   Wikipedia

  • Microsoft Compatibility UI — Infobox Software name = Microsoft Compatibility UI caption = Microsoft Compatibility UI running on Windows XP SP2 developer = Microsoft latest release version = 1985 latest release date = Nov. 1985 operating system = Microsoft Windows, Mac OS… …   Wikipedia

  • MIT License — Author Massachusetts Institute of Technology Publisher Massachusetts Institute of Technology Published 1988 DFSG compatible Yes Free software …   Wikipedia

Share the article and excerpts

Direct link
Do a right-click on the link above
and select “Copy Link”