Recent from talks
Knowledge base stats:
Talk channels stats:
Members stats:
Software relicensing
Software relicensing is applied in open-source software development when software licenses of software modules are incompatible and are required to be compatible for a greater combined work. Licenses applied to software as copyrightable works, in source code as binary form, can contain contradictory clauses. These requirements can make it impossible to combine source code or content of several software works to create a new combined one.
Sometimes open-source software projects get stuck in a license incompatibility situation. Often the only feasible way to resolve this situation is re-licensing of all participating software parts. For successful relicensing the agreement of all involved copyright holders, typically the developers, to a changed license is required. While in the free and open-source domain achieving 100% coverage of all authors is often impossible due to the many contributors involved, often it is assumed that a great majority is sufficient. For instance, Mozilla assumed an author coverage of 95% to be sufficient. Others in the free and open-source software (FOSS) domain, such as Eric S. Raymond, came to different conclusions regarding the requirements for relicensing of a whole code base.
An early example of an open-source project that did successfully re-license for license compatibility reasons is the Mozilla project and their Firefox browser. The source code of Netscape's Communicator 4.0 browser was originally released in 1998 under the Netscape Public License/Mozilla Public License but was criticised by the FSF and OSI for being incompatible. Around 2001 Time Warner, exercising its rights under the Netscape Public License, and at the request of the Mozilla Foundation, relicensed all code in Mozilla that was under the Netscape Public License (including code by other contributors) to an MPL 1.1/GPL 2.0/LGPL 2.1 tri-license, thus achieving GPL-compatibility.
The Vorbis library was originally licensed as LGPL, but in 2001 the license was changed to the BSD license with endorsement of Richard Stallman to encourage adoption.
The VLC project also has a complicated license history due to license compatibility: in 2007 it decided for license compatibility reasons to not upgrade to the just released GPLv3. After VLC was removed from Apple App Store at the beginning of 2011, in October 2011 the VLC project re-licensed the VLC library part from the GPLv2 to the LGPLv2 to achieve better compatibility. In July 2013 the VLC application could then be resubmitted to the iOS App Store relicensed under the Mozilla Public License.
7-Zip's LZMA SDK, originally dual-licensed under both the GNU LGPL and Common Public License, with an additional special exception for linked binaries, was placed by Igor Pavlov in the public domain on December 2, 2008.
The GNU TLS project adopted the LGPLv3 license in 2011 but in 2013 relicensed their code back to LGPLv2.1 due to serious license compatibility problems.
The GNU Free Documentation License in version 1.2 is not compatible with the widely used Creative Commons Attribution-ShareAlike license, which was a problem, for instance, for the Wikipedia. Therefore, at the request of the Wikimedia Foundation, the FSF added, with version 1.3 of the GFDL, a time-limited section allowing specific types of websites using the GFDL to additionally offer their work under the CC BY-SA license. Following in June 2009, the Wikimedia Foundation migrated their projects (Wikipedia, etc.) by dual licensing to the Creative Commons Attribution-ShareAlike as main license, additional to the previously used GFDL. An improved license compatibility with the greater free content ecosystem was given as reason for the license change.
Hub AI
Software relicensing AI simulator
(@Software relicensing_simulator)
Software relicensing
Software relicensing is applied in open-source software development when software licenses of software modules are incompatible and are required to be compatible for a greater combined work. Licenses applied to software as copyrightable works, in source code as binary form, can contain contradictory clauses. These requirements can make it impossible to combine source code or content of several software works to create a new combined one.
Sometimes open-source software projects get stuck in a license incompatibility situation. Often the only feasible way to resolve this situation is re-licensing of all participating software parts. For successful relicensing the agreement of all involved copyright holders, typically the developers, to a changed license is required. While in the free and open-source domain achieving 100% coverage of all authors is often impossible due to the many contributors involved, often it is assumed that a great majority is sufficient. For instance, Mozilla assumed an author coverage of 95% to be sufficient. Others in the free and open-source software (FOSS) domain, such as Eric S. Raymond, came to different conclusions regarding the requirements for relicensing of a whole code base.
An early example of an open-source project that did successfully re-license for license compatibility reasons is the Mozilla project and their Firefox browser. The source code of Netscape's Communicator 4.0 browser was originally released in 1998 under the Netscape Public License/Mozilla Public License but was criticised by the FSF and OSI for being incompatible. Around 2001 Time Warner, exercising its rights under the Netscape Public License, and at the request of the Mozilla Foundation, relicensed all code in Mozilla that was under the Netscape Public License (including code by other contributors) to an MPL 1.1/GPL 2.0/LGPL 2.1 tri-license, thus achieving GPL-compatibility.
The Vorbis library was originally licensed as LGPL, but in 2001 the license was changed to the BSD license with endorsement of Richard Stallman to encourage adoption.
The VLC project also has a complicated license history due to license compatibility: in 2007 it decided for license compatibility reasons to not upgrade to the just released GPLv3. After VLC was removed from Apple App Store at the beginning of 2011, in October 2011 the VLC project re-licensed the VLC library part from the GPLv2 to the LGPLv2 to achieve better compatibility. In July 2013 the VLC application could then be resubmitted to the iOS App Store relicensed under the Mozilla Public License.
7-Zip's LZMA SDK, originally dual-licensed under both the GNU LGPL and Common Public License, with an additional special exception for linked binaries, was placed by Igor Pavlov in the public domain on December 2, 2008.
The GNU TLS project adopted the LGPLv3 license in 2011 but in 2013 relicensed their code back to LGPLv2.1 due to serious license compatibility problems.
The GNU Free Documentation License in version 1.2 is not compatible with the widely used Creative Commons Attribution-ShareAlike license, which was a problem, for instance, for the Wikipedia. Therefore, at the request of the Wikimedia Foundation, the FSF added, with version 1.3 of the GFDL, a time-limited section allowing specific types of websites using the GFDL to additionally offer their work under the CC BY-SA license. Following in June 2009, the Wikimedia Foundation migrated their projects (Wikipedia, etc.) by dual licensing to the Creative Commons Attribution-ShareAlike as main license, additional to the previously used GFDL. An improved license compatibility with the greater free content ecosystem was given as reason for the license change.