Visualizza wikitesto di GNU General Public License

{{redirect|GPL}}
{{ infobox software license
| name            = GNU General Public License
| image           = [[Image:GNU General Public License 3 Logo.svg|200px]]
| caption         = GNU GPLv3 Logo
| author          = [[Free Software Foundation]]
| version         = 3
| copyright       = Free Software Foundation, Inc.
| date            = June 29, 2007
| OSI approved    = Yes
| Debian approved = Yes
| Free Software   = Yes
| copyleft        = Yes
| linking         = No
}}

The '''GNU General Public License''' ('''GNU GPL''' or simply '''GPL''') is a widely used [[free software license]], originally written by [[Richard Stallman]] for the [[GNU project]]. The GPL is the most popular and well-known example of the type of strong [[copyleft]] license that requires derived works to be available under the same copyleft. Under this philosophy, the GPL grants the recipients of a [[computer program]] the rights of the [[The Free Software Definition|free software definition]] and uses copyleft to ensure the freedoms are preserved, even when the work is changed or added to. This is in distinction to [[permissive free software licenses]], of which the [[BSD licenses]] are the standard examples.

The [[GNU Lesser General Public License]] (LGPL) is a modified, more permissive, version of the GPL, originally intended for some [[library (computing)|software libraries]]. There is also a [[GNU Free Documentation License]], which was originally intended for use with documentation for GNU software, but has also been adopted for other uses, such as the [[Wikipedia]] project.

The [[Affero General Public License]] (GNU AGPL) is a similar license with a focus on networking server software. The GNU AGPL is similar to the GNU General Public License, except that it additionally covers the use of the software over a computer network, requiring that the complete source code be made available to any network user of the AGPLed work, for example a web application. The Free Software Foundation recommends that this license is considered for any software that will commonly be run over the network.

==History==
The GPL was written by Richard Stallman in 1989 for use with programs released as part of the GNU project. The original GPL was based on a unification of similar licenses used for early versions of [[GNU Emacs]], the [[GNU Debugger]] and the [[GNU Compiler Collection|GNU C Compiler]]. These licenses contained similar provisions to the modern GPL, but were specific to each program, rendering them incompatible, despite being the same license.<ref name="gplv3conf2stallman-before-gnu-gpl">[http://fsfeurope.org/projects/gplv3/fisl-rms-transcript.en.html#before-gnu-gpl Presentation] by Richard Stallman, made on April 21, 2006, at the second international GPLv3 conference, held in Porto Alegre. Direct link to the section about the prehistory of the GPL.</ref> Stallman's goal was to produce one license that could be used for any project, thus making it possible for many projects to share code.

As of August 2007, the GPL accounted for nearly 65% of the 43,442 free software projects listed on [[Freshmeat]],<ref>{{cite web
|url=http://freshmeat.net/stats/
|title=Freshmeat's statistics page
}}</ref> and {{As of|2006|alt=as of January 2006}}, about 68% of the projects listed on [[SourceForge.net]].<ref>{{cite web|url=http://www.dwheeler.com/frozen/sourceforge-stats-20031110.html |title=SourceForge.net: Software Map |publisher=Dwheeler.com |date= |accessdate=2008-11-17}}</ref> Similarly, a 2001  survey of [[Red Hat Linux]] 7.1 found that 50% of the source code was licensed under the GPL<ref>{{cite web
|url=http://www.dwheeler.com/sloc/redhat62-v1/redhat62sloc.html
|title=Estimating Linux's Size
|author=David A. Wheeler
}}</ref> and a 1997 survey of [[Ibiblio|MetaLab]], then the largest free software archive, showed that the GPL accounted for about half of the software licensed there in. One survey of a large repository of open-source software reported that in July 1997, about half the software packages with explicit license terms used the GPL.<ref>Eric S. Raymond’s "Homesteading the Noosphere," referenced in [http://www.dwheeler.com/essays/gpl-compatible.html Make Your Open Source Software GPL-Compatible. Or Else] By [[David A. Wheeler]]</ref> Prominent free software programs licensed under the GPL include the [[Linux kernel]] and the [[GNU Compiler Collection]] (GCC). Some other free software programs are [[dual-licensed]] under multiple licenses, often with one of the licenses being the GPL.

Some observers believe that the strong [[copyleft]] provided by the GPL was crucial to the success of Linux, giving the programmers who contributed to it the confidence that their work would benefit the whole world and remain free, rather than being exploited by software companies that would not have to give anything back to the community.<ref>{{cite web
|url=http://www.dwheeler.com/blog/2006/09/01/#gpl-bsd
|title=why the GPL rocketed Linux to success
|quote=So while the BSDs have lost energy every time a company gets involved, the GPL'ed programs gain every time a company gets involved.
}}</ref>

The second version of the license, version 2, was released in 1991. Over the following 15 years, some members of the [[free software community|FOSS (Free and Open Source Software) community]] came to believe that some software and hardware vendors were finding loopholes in the GPL, allowing GPL-licensed software to be exploited in ways that were contrary to the intentions of the programmers. These concerns included [[tivoization]] (the inclusion of GPL-licensed software in hardware that will refuse to run modified versions of its software); the use of unpublished, modified versions of GPL software behind web interfaces; and patent deals between [[Microsoft]] and Linux and Unix distributors that may represent an attempt to use patents as a weapon against competition from Linux.

Version 3 was developed to attempt to address these concerns. It was [http://www.fsf.org/news/gplv3_launched officially released] on June 29, 2007.

==Versions==
===Version 1===
Version 1 of the GNU GPL, released in January 1989, prevented what were then the two main ways that software distributors restricted the freedoms that define free software.  The first problem was that distributors may publish [[binary file]]s only&nbsp;– executable, but not readable or modifiable by humans.  To prevent this, GPLv1 said that any vendor distributing binaries must also make the human readable source code available under the same licensing terms.

The second problem was the distributors might add additional restrictions, either by adding restrictions to the license, or by combining the software with other software which had other restrictions on its distribution.  If this was done, then the union of the two sets of restrictions would apply to the combined work, thus unacceptable restrictions could be added.  To prevent this, GPLv1 said that modified versions, as a whole, had to be distributed under the terms in GPLv1. Therefore, software distributed under the terms of GPLv1 could be combined with software under more permissive terms, as this would not change the terms under which the whole could be distributed, but software distributed under GPLv1 could not be combined with software distributed under a more restrictive license, as this would conflict with the requirement that the whole be distributable under the terms of GPLv1.

===Version 2===
According to Richard Stallman, the major change in GPLv2 was the "Liberty or Death" clause, as he calls it&nbsp;— Section 7.<ref name="gplv3conf2stallman-liberty-or-death">[http://fsfeurope.org/projects/gplv3/fisl-rms-transcript.en.html#liberty-or-death Presentation] by Richard Stallman, made on April 21, 2006, at the second international GPLv3 conference, held in Porto Alegre.  Direct link to the section about the "Liberty or Death" clause.</ref>  This section says that if somebody has restrictions imposed that ''prevent'' him or her from distributing GPL-covered software in a way that respects other users' freedom (for example, if a legal ruling states that he or she can only distribute the software in binary form), he or she cannot distribute it at all.

By 1990, it was becoming apparent that a less restrictive license would be strategically useful for some software libraries; when version 2 of the GPL (GPLv2) was released in June 1991, therefore, a second license — the Library General Public License — was introduced at the same time and numbered with version 2 to show that both were complementary.  The version numbers diverged in 1999  when version 2.1 of the LGPL was released, which renamed it the GNU Lesser General Public License to reflect its place in the philosophy.

=== Version 3 ===<!-- This section is linked from [[Software patent]] -->
[[image:Stallman_GPLv3_launch_MIT_060116.jpg |thumb|[[Richard Stallman]] at the launch of the first draft of the GNU GPLv3. MIT, Cambridge,  Massachusetts, USA|right]]
In late 2005, the [[Free Software Foundation]] (FSF) announced work on version 3 of the GPL (GPLv3).  On January 16, 2006, the first "discussion draft" of GPLv3 was published, and the public consultation began.  The public consultation was originally planned for nine to fifteen months but finally stretched to eighteen months with four drafts being published.  The official GPLv3 was released by FSF on June 29, 2007.  GPLv3 was written by Richard Stallman, with legal counsel from [[Eben Moglen]] and [[Software Freedom Law Center]].<ref name="fosdem2006stallman">[http://www.ifso.ie/documents/rms-gplv3-2006-02-25.html Presentation] by Richard Stallman on February 25, 2006 in [[Brussels]], [[Belgium]] - the first day of that year's [[FOSDEM]] conference.</ref>

According to Stallman, the most important changes are in relation to [[Software patents and free software|software patents]], [[free software license]] compatibility, the definition of "source code", and hardware restrictions on software modification ("[[tivoization]]").<ref name="fosdem2006stallman"/><ref name="FSMag-RMS-Interview">[http://www.freesoftwaremagazine.com/articles/interview_with_richard_stallman Interview with Richard Stallman], Free Software Magazine, January 23, 2008.</ref>  Other changes relate to  internationalisation, how license violations are handled, and how additional permissions can be granted by the copyright holder.

Other notable changes include allowing authors to add certain additional conditions or requirements to their contributions.  One of those new optional requirements, sometimes referred to as the Affero clause, is intended to fulfill a request regarding [[software as a service]]; the permitting addition of this requirement makes GPLv3 compatible with the Affero General Public License.

The public consultation process was coordinated by the Free Software Foundation with assistance from Software Freedom Law Center, [[Free Software Foundation Europe]],<ref>{{cite web
|url=http://fsfeurope.org/projects/gplv3/
|title=GPLv3: Drafting version 3 of the GNU General Public License
|publisher=Free Software Foundation Europe
}}</ref> and other free software groups. Comments were collected from the public via the gplv3.fsf.org web portal.<ref>{{cite web
|url=http://gplv3.fsf.org/comments/gplv3-draft-4.html
|title=gplv3.fsf.org comments for discussion draft 4
}}</ref>  That portal runs purpose-written software called [[stet (software)|stet]].  These comments were passed to four committees comprising approximately 130 people, including supporters and detractors of FSF's goals.  Those committees researched the comments submitted by the public and passed their summaries to Stallman for a decision on what the license would do.

During the public consultation process, 962 comments were submitted for the first draft.<ref>{{cite web
|url=http://gplv3.fsf.org/comments/gplv3-draft-1
|title=gplv3.fsf.org comments for draft 1
|quote=Showing comments in file 'gplv3-draft-1' [...] found 962
}}</ref>
By the end, a total of 2,636 comments had been submitted.<ref>{{cite web
|url=http://gplv3.fsf.org/comments/gplv3-draft-2.html
|title=gplv3.fsf.org comments for draft 2
|quote=Showing comments in file 'gplv3-draft-1' [...] found 727
}}</ref><ref>{{cite web
|url=http://gplv3.fsf.org/comments/gplv3-draft-3
|title=gplv3.fsf.org comments for draft 3
|quote=Showing comments in file 'gplv3-draft-3' [...] found 649
}}</ref><ref>{{cite web
|url=http://gplv3.fsf.org/comments/gplv3-draft-4.html
|title=gplv3.fsf.org comments for draft 4
|quote=Showing comments in file 'gplv3-draft-4' [...] found 298
}}</ref>

The third draft was released on March 28, 2007.<ref>[http://gplv3.fsf.org/gpl3-dd3-guide Guide to the third draft of GPLv3]</ref> This draft included language intended to prevent patent cross-licenses like the controversial [[Novell#Agreement with Microsoft|Microsoft-Novell patent agreement]] and restricts the anti-tivoization clauses to a legal definition of a "User" or "consumer product." It also explicitly removed the section on "Geographical Limitations", whose probable removal had been announced at the launch of the public consultation.

The fourth discussion draft,<ref>[http://gplv3.fsf.org/gpl-draft-2007-05-31.html Final Discussion Draft], accessed June 4, 2007</ref> which was the last, was released on May 31, 2007.  It introduced [[Apache License]] compatibility, clarified the role of outside contractors, and made an exception to avoid the perceived problems of a Microsoft-Novell style agreement, saying in section 11 paragraph 6 that

{{quote|You may not convey a covered work if you are a party to an arrangement with a third party that is in the business of distributing software, under which you make payment to the third party based on the extent of your activity of conveying the work, and under which the third party grants, to any of the parties who would receive the covered work from you, a discriminatory patent license [...]}}

This aims to make future such deals ineffective.  The license is also meant to cause Microsoft to extend the patent licenses it grants to Novell customers for the use of GPLv3 software to ''all'' users of that GPLv3 software; this is possible only if Microsoft is legally a "conveyor" of the GPLv3 software.<ref>[http://gplv3.fsf.org/dd3-faq GPLv3 FAQ], accessed June 4, 2007.  This is from the FAQ instead of the license, for readability purposes.</ref><ref>[http://gplv3.fsf.org/gpl3-dd4-rationale.pdf Fourth Discussion Draft Rationale], accessed June 4, 2007.</ref>

Others, notably some high-profile developers of the [[Linux kernel]], commented to the mass media and made public statements about their objections to parts of discussion drafts 1 and 2.<ref>[http://lwn.net/Articles/200422/ Kernel developers' position on GPLv3 -- http://lwn.net/Articles/200422/], accessed June 4, 2007. </ref>.

==Terms and conditions==
The terms and conditions of the GPL are available to anybody receiving a copy of the work that has a GPL applied to it ("the licensee"). Any licensee who adheres to the terms and conditions is given permission to modify the work, as well as to copy and redistribute the work or any derivative version. The licensee is allowed to charge a fee for this service, or do this free of charge. This latter point distinguishes the GPL from software licenses that prohibit commercial redistribution. The FSF argues that free software should not place restrictions on commercial use,<ref>{{cite web|url=http://www.gnu.org/philosophy/selling.html|title=Selling Free Software|publisher=Free Software Foundation}}</ref> and the GPL explicitly states that GPL works may be sold at any price.

The GPL additionally states that a distributor may not impose "further restrictions on the rights granted by the GPL". This forbids activities such as distributing of the software under a non-disclosure agreement or contract.  Distributors under the GPL also grant a license for any of their patents practiced by the software, to practice those patents in GPL software.

Section three of the license requires that programs distributed as pre-compiled binaries are accompanied by a copy of the source code, a written offer to distribute the source code via the same mechanism as the pre-compiled binary or the written offer to obtain the source code that you got when you received the pre-compiled binary under the GPL.

===Copyleft===
{{main|Copyleft}}
The distribution rights granted by the GPL for modified versions of the work are not unconditional.  When someone distributes a GPL'd work plus their own modifications, the requirements for distributing the whole work cannot be any greater than the requirements that are in the GPL.

This requirement is known as copyleft.  It earns its legal power from the use of [[copyright]] on software programs. Because a GPL work is copyrighted, a licensee has no right to redistribute it, not even in modified form (barring [[fair use]]), except under the terms of the license.  One is only required to adhere to the terms of the GPL if one wishes to exercise rights normally restricted by copyright law, such as redistribution.  Conversely, if one distributes copies of the work without abiding by the terms of the GPL (for instance, by keeping the source code secret), he or she can be [[lawsuit|sued]] by the original author under copyright law.

Copyleft thus uses copyright law to accomplish the opposite of its usual purpose: instead of imposing restrictions, it grants rights to other people, in a way that ensures the rights cannot subsequently be taken away. It also ensures that unlimited redistribution rights are not granted, should any legal flaw be found in the copyleft statement.

Many distributors of GPL'ed programs bundle the source code with the [[executable]]s. An alternative method of satisfying the copyleft is to provide a written offer to provide the source code on a physical medium (such as a CD) upon request. In practice, many GPL'ed programs are distributed over the [[Internet]], and the source code is made available over [[File Transfer Protocol|FTP]] or [[Hypertext Transfer Protocol|HTTP]]. For Internet distribution, this complies with the license.

Copyleft applies only when a person seeks to redistribute the program. One is allowed to make private modified versions, without any obligation to divulge the modifications as long as the modified software is not distributed to anyone else. Note that the copyleft applies only to the software and not to its output (unless that output is itself a derivative work of the program). For example, a public web portal running a modified derivative of a GPL'ed [[content management system]] is not required to distribute its changes to the underlying software because its output is not a derivative. A counter example is the GPL'ed [[GNU Bison]]: the parsers it outputs ''do'' contain parts of itself and are therefore derivatives which would fall under the GPL, if it were not for a special exception granted by GNU Bison.<ref>{{cite web |title=Bison 2.3 |url=http://www.gnu.org/software/bison/manual/html_mono/bison.html |quote=Conditions for Using Bison |accessdate=2008-12-11}}</ref>

==Licensing and contractual issues==
The GPL was designed as a [[license]], rather than a [[contract]].<ref>{{cite web
|url=http://www.gnu.org/philosophy/no-ip-ethos.html
|title=Essay by Stallman explaining why a license is more suitable than a contract
}}</ref><ref>{{cite web
|url=http://fsfeurope.org/projects/gplv3/barcelona-moglen-transcript.en.html#q7-a-contract
|title=Eben Moglen explaining why the GPL is a licence and why it matters
}}</ref> In some [[Common Law]] jurisdictions, the legal distinction between a license and a contract is an important one: contracts are enforceable by [[contract law]], whereas licenses are enforced under [[copyright law]].  However, this distinction is not useful in the many jurisdictions where there are no differences between contracts and licenses, such as [[Civil law (legal system)|Civil Law]] systems.<ref>
{{cite journal
  | last = Guadamuz-Gonzalez
  | first = Andres
  | title = Viral contracts or unenforceable documents? Contractual validity of copyleft licences
  | journal = European Intellectual Property Review
  | volume = 26
  | issue = 8
  | pages = 331–339
  | date = 2004
  | url = http://papers.ssrn.com/sol3/papers.cfm?abstract_id=569101}}
</ref>

Those who do not agree to the GPL's terms and conditions do not have permission, under copyright law, to copy or distribute GPL licensed software or derivative works. However, if they do not redistribute the GPL:ed program, they may still use the software within their organisation however they like, and products constructed by the use of the program are not covered by this license.<!-- "however they like" but not "to copy or distribute GPL licensed software or derivative works."? This seems self-contradictory and needs a better explanation. Is it intended to mean use for personal use only? -- YES I PRESUME SO (sqreamed Rursus). -->

==Copyright holders==
The text of the GPL is itself copyrighted, and the copyright is held by the Free Software Foundation. However, the FSF does not hold the copyright for a work released under the GPL, unless an author explicitly assigns copyrights to the FSF (which seldom happens except for programs that are part of the GNU project). Only the individual copyright holders have the authority to sue when a license violation takes place.

The FSF permits people to create new licenses based on the GPL, as long as the derived licenses do not use the GPL preamble without permission. This is discouraged, however, since such a license is generally incompatible with the GPL.<ref>{{cite web
|url=http://www.fsf.org/licensing/licenses/gpl-faq.html#ModifyGPL
|title=GPL FAQ: Can I modify the GPL and make a modified license?
}}</ref> (See the [http://www.fsf.org/licenses/gpl-faq.html#ModifyGPL GPL FAQ] for more information.)

Other licenses created by the GNU project include the [[GNU Lesser General Public License]] and the [[GNU Free Documentation License]].

==Linking and derived works==
A key dispute related to the GPL is whether or not non-GPL software can be [[dynamic linking|dynamically linked]] to GPL libraries. The GPL is clear in requiring that all [[derivative work]]s of code under the GPL must themselves be under the GPL.  While it is understood that [[static linking]] produces derivative works, it is not clear whether an executable that dynamically links to a GPL code should be considered a derivative work (see [[Copyleft#Strong and weak copyleft|Weak Copyleft]]). The free/open-source software community is split on this issue. The FSF asserts that such an executable is indeed a derivative work if the executable and GPL code "make function calls to each other and share data structures,"<ref>[http://www.gnu.org/licenses/gpl-faq.html#GPLPluginsInNF Can I apply the GPL when writing a plug-in for a non-free program?], GPL FAQ, Free Software Foundation.</ref> with certain others agreeing (e.g. Jerry Epplin<ref>[http://www.linuxdevices.com/articles/AT9161119242.html Using GPL software in embedded applications], ''LinuxDevices.com'' (March 4, 2001).</ref>), while some (e.g. [[Linus Torvalds]]) agree that dynamic linking can create derived works but disagree over the circumstances.<ref>Linus Torvalds, [http://lkml.org/lkml/2006/12/17/79 GPL only modules], ''linux-kernel'' mailing list (December 17, 2006).</ref> On the other hand, some experts have argued that the question is still open: one [[Novell]] lawyer has written that dynamic linking not being derivative "makes sense" but is not "clear-cut,"<ref>Matt Asay, [http://www.novell.com/coolsolutions/feature/1532.html The GPL: Understanding the License that Governs Linux], ''Novell Cool Solutions Feature'' (Jan 16. 2004).</ref> but that evidence for good-intentioned dynamic linking can be seen by the existence of proprietary Linux kernel drivers. [[Lawrence Rosen]] has claimed that a court of law would "probably" exclude dynamic linking from derivative works although "there are also good arguments" on the other side and  "the outcome is not clear"<ref>Lawrence Rosen, [http://www.linuxjournal.com/article/6366 Derivative Works], ''Linux Journal'' (January 1, 2003).</ref> (on a later occasion, he argued that "market-based" factors are more important than the linking technique<ref>Lawrence Rosen, [http://www.rosenlaw.com/lj19.htm Derivative Works], ''rosenlaw.com'' (May 25, 2004)</ref>).  This is ultimately a question not of the GPL ''per se'', but of how copyright law defines derivative works.  In ''[[Galoob v. Nintendo]]'' the [[Ninth Circuit Court of Appeals]] defined a derivative work as having "'form' or permanence" and noted that "the infringing work must incorporate a portion of the copyrighted work in some form," but there have been no clear court decisions to resolve this particular conflict.

==The GPL in court==

In 2002, MySQL AB sued Progress NuSphere for copyright and trademark infringement in [[U.S. District Court for the District of Massachusetts|United States district court]].  NuSphere had allegedly violated MySQL's copyright by linking code for the Gemini table type into the MySQL server. After a preliminary hearing before Judge Patti Saris on February 27, 2002, the parties entered settlement talks and eventually settled. At the hearing, Judge Saris "saw no reason" that the GPL would not be enforceable.<ref>See ''Progress Software Corporation v. MySQL AB'', 195 F. Supp. 2d 328 (D. Mass. 2002), on defendant's motion for preliminary injunction.</ref>

In August 2003, the [[SCO Group]] stated that they believed the GPL to have no legal validity, and that they intended to take up lawsuits over sections of code supposedly copied from SCO Unix into the [[Linux kernel]].  This was a problematic stand for them, as they had distributed Linux and other GPL'ed code in their [[Caldera OpenLinux]] distribution, and there is little evidence that they had any legal right to do so except under the terms of the GPL. For more information, see [[SCO-Linux controversies]] and [[SCO v. IBM]].

In April 2004  the [[netfilter/iptables]] project was granted a preliminary [[injunction]] against Sitecom Germany by [[Munich]] District Court after Sitecom refused to desist from distributing Netfilter's GPL'ed software in violation of the terms of the GPL. On July 2004, the German court confirmed this injunction as a final ruling against Sitecom.<ref>[http://www.groklaw.net/article.php?story=20040725150736471 Harald Welte vs. Sitecom, final order, translated from German by Jens Maurer]</ref>  The court's justification was that:

:''Defendant has infringed on the copyright of plaintiff by offering the software 'netfilter/iptables' for download and by advertising its distribution, without adhering to the license conditions of the GPL.  Said actions would only be permissible if defendant had a license grant... This is independent of the questions whether the licensing conditions of the GPL have been effectively agreed upon between plaintiff and defendant or not. If the GPL were not agreed upon by the parties, defendant would notwithstanding lack the necessary rights to copy, distribute, and make the software 'netfilter/iptables' publicly available.''

Harald Welte was represented by [[ifrOSS]] co-founder Till Jaeger.  This exactly mirrored the predictions given previously by the FSF's Eben Moglen.  This ruling was important because it was the first time that a court had confirmed that violating terms of the GPL could affect copyright violation.

In May 2005, Daniel Wallace [[Wallace versus International Business Machines et al.|filed suit]] against the Free Software Foundation in the [[U.S. District Court for the Southern District of Indiana|Southern District of Indiana]], contending that the GPL is an illegal attempt to fix prices (at zero). The suit was dismissed in March 2006, on the grounds that Wallace had failed to state a valid anti-trust claim; the court noted that "the GPL encourages, rather than discourages, free competition and the distribution of computer operating systems, the benefits of which directly pass to consumers."<ref name="groklawwallacevsfsfdismiss">[http://www.groklaw.net/pdf/WallaceFSFGrantingDismiss.pdf Dismissal] of Wallace v. FSF. From [http://www.groklaw.net/article.php?story=20060320201540127 this article] on Groklaw.</ref> Wallace was denied the possibility of further amending his complaint, and was ordered to pay the FSF's legal expenses.

On September 8, 2005, Seoul Central District Court ruled that GPL has no legal relevance concerning the case dealing with [[trade secret]] derived from GPL-licensed work.<ref>[http://web.archive.org/web/20071018211119/http://korea.gnu.org/gv/sentence.html Seoul Central District Court ruling (?) (in Korean)]</ref> Defendants argued that since it is impossible to maintain trade secret while being compliant with GPL and distributing the work, they aren't in breach of trade secret. This argument was considered without ground.

On September 6, 2006, the [[gpl-violations.org]] project prevailed in court litigation against D-Link Germany GmbH regarding D-Link's copyright infringing use of parts of the [[Linux Kernel]] in [[Network-attached storage|storage]] devices they distributed.<ref>[http://gpl-violations.org/news/20060922-dlink-judgement_frankfurt.html http://gpl-violations.org/news/20060922-dlink-judgement_frankfurt.html]</ref> The judgment provided legal precedent that the GPL is valid, legally binding, and stands in German court.<ref>[http://www.jbb.de/urteil_lg_muenchen_gpl.pdf D-Link Judgement]</ref>

In late 2007, the [[BusyBox]] developers and the Software Freedom Law Center embarked upon a program to gain GPL compliance from distributors of BusyBox in [[embedded system]]s, suing those who would not comply. These were claimed to be the first US uses of courts for enforcement of GPL obligations. ''See'' [[BusyBox#GPL lawsuits|BusyBox GPL lawsuits]].

==Compatibility and multi-licensing==
[[Image:quick-guide-gplv3-compatibility.svg|350px|thumb|Quick Guide of license compatibility with GPL]]
Many of the most common free software licenses, such as the original [[MIT License|MIT/X license]], the [[BSD license]] (in its current 3-clause form), and the LGPL, are "GPL-[[License compatibility|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 GPL proponents 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.  Note that this issue only arises in concurrent use of licenses which impose conditions on their manner of combination.  Some licenses, such as the BSD license, impose no conditions on the manner of their combination.

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

A number of businesses use [[dual-licensing]] to distribute a GPL version and sell a [[proprietary software|proprietary]] license to companies wishing to combine the package with proprietary code, using dynamic linking or not. Examples of such companies include [[MySQL AB]], [[Nokia]] ([[Qt (toolkit)|Qt toolkit]]),  [[Namesys]] ([[ReiserFS]]) and [[Red Hat]] ([[Cygwin]]).

==Adoption==
The Open Source License Resource Center maintained by [[Black Duck Software]] shows that GPL is the license used in about 60% of all software packages released under a [[free software license|free software]] / open source license.<ref>{{cite web|url=http://www.blackducksoftware.com/oss |title=Open Source License Resource Center &#124; Black Duck Software |publisher=Blackducksoftware.com |date= |accessdate=2008-11-17}}</ref>  The vast majority of projects are released under GPL 2 with 3000 free software / open source projects having migrated to GPL 3.

==Use for text and other media==
It is possible to use the GPL for text documents instead of computer programs, or more generally for all kinds of media, if it is clear what constitutes the source code (defined as "the preferred form of the work for making changes in it").<ref>Free Software Foundation: [http://www.gnu.org/licenses/gpl-faq.html#GPLOtherThanSoftware Frequently Asked Questions about the GNU Licenses: Can I use the GPL for something other than software?] Accessed June 20, 2009</ref> For manuals and textbooks, though, the FSF recommends to use the [[GNU Free Documentation License]] (GFDL) instead, which it created for this purpose.<ref>GNU project: [http://www.gnu.org/licenses/gpl-faq.html#WhyNotGPLForManuals Frequently Asked Questions about the GNU Licenses: Why don't you use the GPL for manuals?] (Accessed June 20, 2009)</ref> Nevertheless, the [[Debian]] developers recommended (in a resolution adopted in 2006) to license documentation for their project under the GPL, because of the incompatibility of the GFDL with the GPL (text licensed under the GFDL cannot be incorporated into GPL software).<ref>Debian Project: [http://www.debian.org/vote/2006/vote_001.en.html#amendmenttexta Resolution: Why the GNU Free Documentation License is not suitable for Debian]. Voted February-March 2006. (Accessed June 20, 2009)</ref> Also, the [[FLOSS Manuals]] foundation, an organization devoted to creating manuals for free software, decided to eschew the GFDL in favor of the GPL for its texts in 2007.<ref>FLOSS Manuals foundation: [http://en.flossmanuals.net/bin/view/Blog/LicenseChange License Change] June 6, 2007. (Accessed June 20, 2009)</ref>

==Criticism==
In 2001, [[Microsoft]] CEO [[Steve Ballmer]] referred to Linux as "a cancer that attaches itself in an intellectual property sense to everything it touches."<ref>{{cite news
| first=Dave
| last=Newbart
| pages= 
| title=Microsoft CEO takes launch break with the Sun-Times
| date=2001-06-01
| publisher=[[Chicago Sun-Times]]
| url=http://suntimes.com/output/tech/cst-fin-micro01.html
| archiveurl=http://web.archive.org/web/20010615205548/http://suntimes.com/output/tech/cst-fin-micro01.html
| archivedate=2001-06-15
}}(Internet archive link)</ref> Critics of Microsoft claimed that the real reason Microsoft dislikes the GPL is that the GPL resists proprietary vendors' attempts to "[[embrace, extend and extinguish]]".<ref>{{cite news
|url=http://www.economist.com/displayStory.cfm?Story_ID=298112
|title=Deadly embrace|publisher=The Economist
|date=2000-03-30
|accessdate=2006-03-31
}}</ref> Microsoft has released [[Microsoft Windows Services for UNIX]] which contains GPL-licensed code.<ref>[http://www.dwheeler.com/frozen/microsoft-interix-gpl.txt text of GPL v1 with reference to source code download site at microsoft.com ]</ref> In response to Microsoft's attacks on the GPL, several prominent Free Software developers and advocates released a joint statement supporting the license.<ref>[http://www.perens.com/Articles/StandTogether.html Free Software Leaders Stand Together]</ref>

The GPL has been described as being [[Copyleft#Viral licensing|"viral"]] by many of its critics<ref>"[http://www.microsoft.com/presspass/exec/craig/05-03sharedsource.mspx Speech Transcript - Craig Mundie, The New York University Stern School of Business]", ''Prepared Text of Remarks by [[Craig Mundie]]'', Microsoft Senior Vice President, The Commercial Software Model The New York University Stern School of Business May 3, 2001</ref> because the GPL only allows conveyance of whole programs, which means that programmers are not allowed to convey programs that [[GPL linking exception|link]] to libraries having GPL-incompatible licenses.  The so-called "viral" effect of this is that under such circumstances disparately licensed software cannot be combined unless one of the licenses is changed.  Although theoretically either license could be changed, in the "viral" scenario the GPL cannot be practically changed (because the software may have so many contributors, some of whom will likely refuse), whereas the license of the other software ''can'' be practically changed. According to Richard Stallman the picture of a "virus" is not only offending, but also wrong: Software under the GPL never "attacks" and "infects" other software.{{Fact|date=April 2009}} Rather, software under the GPL is like a spider plant: If one takes a piece of it and puts it somewhere else, it grows there, too.{{Fact|date=April 2009}}

This is part of a [[BSD and GPL licensing|philosophical difference]] between the GPL and permissive free software licenses such as the BSD-style licenses, which do not put such a requirement on modified versions.  While proponents of the GPL believe that free software should ensure that its freedoms are preserved all the way from the developer to the user, others believe that intermediaries between the developer and the user should be free to redistribute the software as non-free software.  More specifically, the GPL requires that redistribution occur subject to the GPL, whereas more "permissive" licenses allow redistribution to occur under licenses more restrictive than the original license.

While the GPL does allow commercial distribution of GPL software, the market price will settle near the price of distribution—near zero—since the purchasers may redistribute the software and its source code for their cost of redistribution.  This could be seen to inhibit commercial use of GPL'ed code by others wishing to use that code for proprietary purposes—if they don't wish to avail themselves of GPL'ed code, they will have to re-implement it themselves.  Microsoft has included anti-GPL terms in their open source software.<ref>[http://www.theregister.co.uk/2002/04/17/microsoft_antigpl_fine_print_threatens/ Microsoft anti-GPL fine print threatens competition | The Register]</ref>

In addition, the [[FreeBSD]] project has stated that "a less publicized and unintended use of the GPL is that it is very favorable to large companies that want to undercut software companies. In other words, the GPL is well suited for use as a marketing weapon, potentially reducing overall economic benefit and contributing to monopolistic behavior".<ref>[http://www.freebsd.org/doc/en_US.ISO8859-1/articles/bsdl-gpl/article.html#GPL-ADVANTAGES GPL Advantages and Disadvantages], FreeBSD: doc/en_US.ISO8859-1/articles/bsdl-gpl/article.sgml,v 1.5 2006/10/16 12:35:23 keramida Exp</ref>

The GPL has no [[Indemnity|indemnification]] clause explicitly protecting maintainers and developers from litigation resulting from unscrupulous contribution.  (If a developer submits existing patented or copyright work to a GPL project claiming it as their own contribution, all the project maintainers and even other developers can be held legally responsible for damages to the copyright or patent holder.)  Lack of indemnification is one criticism that led Mozilla to create the [[Mozilla Public License]] rather than use the GPL or LGPL.{{Fact|date=October 2007}}  However, Mozilla later relicensed their work under a GPL/LGPL/MPL triple license, due to problems with the GPL-incompatibility of the MPL.

Some software developers have found the extensive scope of the GPL to be too restrictive. For example, Bjørn Reese and Daniel Stenberg felt that their choice of the GPL for their software created a "quodque pro quo" (Latin, "Everything in return for something") for the developers of other software that linked with theirs. For that reason, in 2001 they abandoned the GPLv2 in favor of less restrictive copyleft licenses. <ref>Bjørn Reese and Daniel Stenberg, [http://www.oreillynet.com/pub/a/policy/2001/12/12/transition.html?page=1 Working Without Copyleft] (December 19, 2001)</ref>

As a specific example of license incompatibility, [[Sun Microsystems]]' [[ZFS]] cannot be included in the GPL-licensed Linux kernel, because it is licensed under the GPL-incompatible CDDL.  Furthermore, ZFS is protected by patents, and a GPL-ed implementation would violate Sun's patent license.<ref>[http://kerneltrap.org/node/8066 Linux: ZFS, Licenses and Patents | KernelTrap]</ref>

Some have also argued that the GPL is unnecessarily confusing for lay readers, and could be simplified while retaining the same conditions and legal force.<ref>{{cite web
|url=http://radar.oreilly.com/archives/2007/05/gplv3_clarity_a.html
|author=Allison Randal
|title=GPLv3, Clarity and Simplicity
}}</ref>

==See also==
{{Portal|Free software|Free Software Portal Logo.svg}}
* [[GNU Lesser General Public License]]
* [[BSD license]]
* [[List of software licenses]]
* [[Permissive and copyleft licenses]]
* [[Dual-licensing]]
* [[European Union Public Licence]]

==References==
{{reflist|2}}

==External links==
{{Wikibooks|FOSS Licensing}}
* [http://www.gnu.org/licenses/old-licenses/gpl-1.0.txt GNU General Public License v1.0] - This version is [[deprecation|deprecated]] by the FSF.
* [http://www.gnu.org/licenses/old-licenses/gpl-2.0.txt GNU General Public License v2.0] - This version is [[deprecation|deprecated]] by the FSF but is still used by many software projects, including Linux and GNU packages
* [http://www.gnu.org/licenses/gpl-3.0.txt GNU General Public License v3.0]
* [http://www.softwarefreedom.org/resources/2008/compliance-guide.html A Practical Guide to GPL Compliance] (Covers GPLv2 and v3) - from the Software Freedom Law Center
* [http://www.sapnakumar.org/EnfGPL.pdf A paper on enforcing the GPL]
* [http://www.perens.com/Articles/StandTogether.html Free Software Leaders Stand Together], a joint statement in support of the GPL
* [http://www.gnu.org/licenses/gpl-faq.html Frequently Asked Questions about the GPL]
* [http://www.dwheeler.com/blog/2006/09/01/#gpl-bsd GPL, BSD, and NetBSD - why the GPL rocketed Linux to success] by David A. Wheeler
* [http://www.rattlesnake.com/software-law/GNU-GPL-and-Commentaries.html GNU General Public License and Commentaries] -  Edited by [[Robert Chassell]].
* [http://www.gnu.org/copyleft/lesser.html GNU Lesser General Public License v2.1]
* [http://www.free-soft.org/gpl_history/ History of the GPL]
* [http://fsfe.org/transcripts#licenses List of presentation transcripts about the GPL and free software licenses]
* [http://www.dwheeler.com/essays/gpl-compatible.html Make Your Open Source Software GPL-Compatible. Or Else.] (David A. Wheeler, April 7, 2004)&nbsp;— why a GPL-compatible license is important to the health of a project
* [http://www.free-soft.org/gpl_history/emacs_gpl.html The Emacs General Public License], a February 1988 version, a direct predecessor of the GNU GPL

{{GNU}}
{{FOSS}}

[[Category:Computer law]]
[[Category:Free content licenses]]
[[Category:Free software licenses]]
[[Category:GNU project]]
[[Category:Open source licenses]]
[[Category:Copyleft licensing]]
[[Category:Libre]]

[[af:GNU Algemene Publieke Lisensie]]
[[ar:رخصة جنو العمومية]]
[[ast:GNU General Public License]]
[[bs:GNU General Public License]]
[[bg:GNU General Public License]]
[[ca:GPL]]
[[cs:GNU General Public License]]
[[cy:Trwydded Gyhoeddus Gyffredinol GNU]]
[[da:GNU General Public License]]
[[de:GNU General Public License]]
[[et:GNU GPL]]
[[el:GNU General Public License]]
[[es:GNU General Public License]]
[[eo:GPL]]
[[eu:GNU General Public License]]
[[fa:اجازه‌نامه عمومی همگانی گنو]]
[[fr:Licence publique générale GNU]]
[[gl:General Public License]]
[[ko:GNU 일반 공중 사용 허가서]]
[[hr:GNU General Public License]]
[[ilo:GPL]]
[[id:Lisensi Publik Umum GNU]]
[[it:GNU General Public License]]
[[he:הרישיון הציבורי הכללי של גנו]]
[[ka:GNU General Public License]]
[[lt:GNU GPL]]
[[lmo:GPL]]
[[hu:GNU General Public License]]
[[ml:ഗ്നൂ സാര്‍വ്വജനിക അനുവാദപത്രം]]
[[ms:Lesen Awam Am GNU]]
[[mn:GNU GPL]]
[[nl:GNU General Public License]]
[[ja:GNU General Public License]]
[[no:GNU General Public License]]
[[nn:GNU General Public License]]
[[pl:GNU General Public License]]
[[pt:GNU General Public License]]
[[ro:Licenţa Publică Generală GNU]]
[[ru:GNU General Public License]]
[[sc:Lissentzia GPL]]
[[simple:General Public License]]
[[sk:GNU General Public License]]
[[sl:GNU General Public License]]
[[szl:GNU General Public License]]
[[sr:ГНУ-ова општа јавна лиценца]]
[[fi:GNU GPL]]
[[sv:GNU General Public License]]
[[tl:GNU General Public License]]
[[ta:க்னூ பொதுமக்கள் உரிமம்]]
[[th:สัญญาอนุญาตสาธารณะทั่วไปของกนู]]
[[tr:GNU Genel Kamu Lisansı]]
[[uk:GNU General Public License]]
[[vi:Giấy phép Công cộng GNU]]
[[zh:GNU通用公共许可证]]