Search results
Results from the WOW.Com Content Network
Organizations usually approve specific versions of software licenses. For instance, a FSF approval means that the Free Software Foundation (FSF) considers a license to be free-software license. The FSF recommends at least "Compatible with GPL" and preferably copyleft.
GPLv3 improved compatibility with several free software licenses such as the Apache License, version 2.0, and the GNU Affero General Public License, which GPLv2 could not be combined with. [42] However, GPLv3 software could only be combined and share code with GPLv2 software if the GPLv2 license used had the optional "or later" clause and the ...
Some weak copyleft licenses can be used under the GPL and are said to be GPL-compatible. GPL software can only be used under the GPL or AGPL. [77] Permissive licenses are broadly compatible because they can cover separate parts of a project. Multiple licenses including the GPL and Apache License have been revised to enhance compatibility. [80]
Pages in category "Software using the GNU General Public License" The following 200 pages are in this category, out of approximately 437 total. This list may not reflect recent changes .
Cost LyX: The LyX Project: 1995 GNU/Linux 2.4.3 [22] 2025-01-16 GPL-2.0-or-later: No cost: Mariner Write Mariner software 1996 macOS 3.7.2 Proprietary: Cost Mellel: RedleX: 2002 macOS 5.1.2 [23] 2022-05-27 Proprietary: Cost Microsoft Word: Microsoft Corporation: Android 16 2021 Proprietary: Cost 1985 AT&T Unix PC 1986 Atari ST 1.05 1986 1983 ...
[9] [10] The original BSD license is also one of the first free-software licenses, dating to 1988. In 1989, version 1 of the GNU General Public License (GPL) was published. Version 2 of the GPL, released in 1991, went on to become the most widely used free-software license. [11] [12] [13]
License compatibility is a legal framework that allows for pieces of software with different software licenses to be distributed together. The need for such a framework arises because the different licenses can contain contradictory requirements, rendering it impossible to legally combine source code from separately-licensed software in order to create and publish a new program.
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, [ 1 ] can contain contradictory clauses.