Просмотр кода страницы Английская Википедия:Copyleft

{{Английская Википедия/Панель перехода}}
{{short description|Practice of mandating free use in all derivatives of a work}}
{{Use dmy dates|date=June 2023}}
[[File:Copyleft.svg|thumb|alt=Small letter c turned 180 degrees, surrounded by a single line forming a circle.|Copyleft symbol]]
{{Intellectual property}}
{{Copyleft sidebar}}
'''Copyleft''' is the legal technique of granting certain freedoms over copies of [[copyright]]ed works with the requirement that the same rights be preserved in [[derivative work]]s. In this sense, ''freedoms'' refers to the use of the work for any purpose, and the ability to modify, copy, share, and redistribute the work, with or without a fee. [[License]]s which implement copyleft can be used to maintain copyright conditions for works ranging from [[computer software]], to [[documents]], [[art]], scientific discoveries and even [[Patentleft|certain patents]].<ref>{{cite journal|last=Newman|first=John|date=29 December 2011|title=Copyright and Open Access at the Bedside|journal=NEJM|volume=365|issue=26|pages=2447–2449|doi=10.1056/NEJMp1110652|pmid=22204721}}</ref>

Copyleft [[software license]]s are considered ''protective'' or ''reciprocal'' in contrast with [[permissive free software licence|permissive]] [[free software]] licenses,<ref name="redhat2005">{{webarchive |url=https://web.archive.org/web/*/https://www.redhat.com/f/summitfiles/presentation/May31/Open%20Source%20Dynamics/Troan_OpenSourceProprietyPersp.pdf |date=* |title=Open Source from a Proprietary Perspective }}</ref> and require that information necessary for reproducing and modifying the work must be made available to recipients of the software program, which are often distributed as [[executable]]s. This information is most commonly in the form of [[source code]] files, which usually contain a copy of the license terms and acknowledge the authors of the code. Copyleft help ensuring everyone's rights to freely use the product but is prohibited from owning, registering copyright and earning royalties from copyright.

Notable copyleft licenses include the [[GNU General Public License]] (GPL), originally written by [[Richard Stallman]], which was the first software copyleft license to see extensive use,<ref>{{Cite web|url=https://www.gnu.org/copyleft/gpl.html |title=GNU General Public License |website=GNU Project |first=Richard |last=Stallman |date=29 June 2007 |access-date=1 May 2017}}</ref> the [[Mozilla Public License]], the [[Free Art License]],<ref>{{Cite web|title=Free Art License 1.3|url=https://artlibre.org/licence/lal/en/|access-date=6 October 2021|website=Copyleft Attitude}}</ref> and the [[Creative Commons]] [[share-alike|share-alike license condition]],<ref name="cc-by-sa">{{Cite web|title=Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)|url=https://creativecommons.org/licenses/by-sa/4.0/|access-date=14 August 2015|website=Creative Commons}}</ref> with the last two being intended for other types of works, such as documents and pictures, both academic or artistic in nature.

== History ==
The concept of copyleft was described in [[Richard Stallman]]'s ''[[GNU Manifesto]]'' in 1985, where he wrote:

{{blockquote|
GNU is not in the public domain. Everyone will be permitted to modify and redistribute GNU, but no distributor will be allowed to restrict its further redistribution. That is to say, proprietary modifications will not be allowed. I want to make sure that all versions of GNU remain free.
}}

Stallman's motivation was that a few years earlier he had worked on a [[Lisp programming language|Lisp]] interpreter. [[Symbolics]] asked to use the Lisp interpreter, and Stallman agreed to supply them with a [[Public domain software|public domain]] version of his work. Symbolics extended and improved the Lisp interpreter, but when Stallman wanted access to the improvements that Symbolics had made to his interpreter, Symbolics refused. Stallman then, in 1984, proceeded to work towards eradicating this emerging behavior and culture of [[proprietary software]], which he named ''software hoarding''. This was not the first time Stallman had dealt with proprietary software, but he deemed this interaction a "turning point". He justified software sharing, protesting that when sharing, the software online can be copied without the loss of the original piece of work. The software can be used multiple times without ever being damaged or worn out.<ref name="Carver 2005" /><ref>{{Cite book|last=Williams|first=Sam|url=https://archive.org/details/freeasinfreedomr00will|title=Free as in Freedom – Richard Stallman's Crusade for Free Software|date=March 2002|publisher=[[O'Reilly Media]]|isbn=978-0-596-00287-9|chapter=7|author-link=Sam Williams (American journalist)|chapter-url=http://www.oreilly.com/openbook/freedom/ch07.html|url-access=registration}}</ref>

As Stallman deemed it impractical in the short term to eliminate current copyright law and the wrongs he perceived it to perpetuate, he decided to work within the framework of existing [[law]]; in 1985,<ref>{{cite book|last=Moody|first=Glyn|title=Rebel Code|date=2002|page=26|author-link=Glyn Moody}}</ref> he created his own copyright license, the Emacs General Public License,<ref>{{cite web|date=5 July 2001|title=Emacs General Public License|url=http://www.free-soft.org/gpl_history/emacs_gpl.html|access-date=23 August 2008}}</ref> the first copyleft license. This later evolved into the [[GNU General Public License]], which is now one of the most popular free-software licenses. For the first time, a copyright holder had taken steps to ensure that the maximal number of rights be perpetually transferred to a program's users, no matter what subsequent revisions anyone made to the original program. This original GPL did not grant rights to the public at large, only those who had already received the program; but it was the best that could be done under existing law.

The new license was not at this time given the copyleft label.<ref name="autogenerated1">{{cite web|last=Stallman|first=Richard|author-link=Richard Stallman|date=21 January 2008|title=About the GNU Project|url=https://www.gnu.org/gnu/thegnuproject.html|access-date=1 May 2017|publisher=[[Free Software Foundation]]}}</ref> Richard Stallman stated that the use of "Copyleft" comes from [[Don Hopkins]], who mailed him a letter in 1984 or 1985, on which was written: "Copyleft&nbsp;– all rights reversed", which is [[All rights reversed|a pun on the common copyright disclaimer]].<ref name="autogenerated1" />

In [[France]], a series of meetings taking place in 2000 under the title "Copyleft Attitude" gave birth to the [[Free Art License]] (FAL),<ref>{{Cite web|title=Free Art License &ndash; Frequently Asked Questions|url=https://artlibre.org/faq_eng/|access-date=6 October 2021|website=Copyleft Attitude}}</ref> theoretically valid in any jurisdiction bound by the [[Berne Convention]] and recommended by Stallman's own [[Free Software Foundation]].<ref>{{Cite web|title=Licenses|url=https://www.gnu.org/licenses/licenses.html|access-date=6 October 2021|website=GNU Project}}: "''We don't take the position that artistic or entertainment works must be free, but if you want to make one free, we recommend the Free Art License.''"</ref> Shortly thereafter, a separate, unrelated initiative in the [[United States]] yielded the [[Creative Commons license]], available since 2001 in several different versions (only some of which can be described as copyleft) and more specifically tailored to U.S. law.

==Copyleft principles==

=== Freedom ===
While copyright law gives software authors control over copying, distribution and modification of their works, the goal of copyleft is to give all users of the work the freedom to carry out all of these activities. These freedoms (from the [[Free Software Definition]]) include:<ref name="Carver 2005" /><ref>{{Cite web|date=30 July 2019|title=What is free software?|url=https://www.gnu.org/philosophy/free-sw.html|access-date=22 July 2020|website=GNU }}</ref>

;Freedom 0
:the freedom to use the work
;Freedom 1
:the freedom to study the work
;Freedom 2
:the freedom to copy and share the work with others
;Freedom 3
:the freedom to modify the work, and the freedom to distribute modified and therefore derivative works

Similar terms are present in the [[Open Source definition|Open Source Definition]], a separate definition that contains similar freedoms. The vast majority of copyleft licenses satisfy both definitions, that of the Free Software Definition and Open Source Definition.<ref name="Carver 2005" /> By guaranteeing viewers and users of a work the freedom and permission to reproduce, [[Derivative work|adapt]], or distribute it, copyleft licenses are distinct from other types of copyright licenses that limit such freedoms.

=== Reciprocity ===
Instead of allowing a work to fall completely into the [[public domain]], where no ownership of copyright is claimed, copyleft allows authors to impose restrictions on the use of their work. One of the main restrictions imposed by copyleft is that [[Derivative work|derived works]] must also be released under a compatible copyleft license.<ref name="Carver 2005" />

This is due to the underlying principle of copyleft: that anyone can benefit freely from the previous work of others, but that any modifications to that work should benefit everyone else as well, and thus must be released under similar terms. For this reason, copyleft licenses are also known as [[reciprocity (social psychology)|reciprocal]] licenses: any modifiers of a copyleft-licensed work are expected to reciprocate the author's action of copyleft-licensing the software by also copyleft-licensing any derivatives they might have made. Because of this requirement, copyleft licenses have also been described as "viral" due to their self-perpetuating terms.<ref>{{cite web
 |url=http://www.microsoft.com/presspass/exec/craig/05-03sharedsource.mspx 
 |title=Prepared Text of Remarks by Craig Mundie, Microsoft Senior Vice President – The Commercial Software Model 
 |date=3 May 2001 |publisher=[[New York University Stern School of Business]] 
 |first=Craig 
 |last=Mundie 
 |author-link=Craig Mundie 
 |access-date=1 October 2009 |url-status=dead 
 |archive-url=https://web.archive.org/web/20050621082004/http://www.microsoft.com/presspass/exec/craig/05-03sharedsource.mspx 
 |archive-date=21 June 2005  
}}</ref>

In addition to restrictions on copying, copyleft licenses address other possible impediments. They ensure that rights cannot be later [[revoke]]d, and require the work and its derivatives to be provided in a form that allows further modifications to be made. In [[Computer software|software]], this means requiring that the [[source code]] of the derived work be made available together with the software itself.<ref name="Carver 2005">{{cite journal |last=Carver |first=Brian W. |title=Share and Share Alike: Understanding and Enforcing Open Source and Free Software Licenses |date=5 April 2005 |url=https://lawcat.berkeley.edu/record/1119855?ln=en |access-date=27 June 2023 |journal=Berkeley Technology Law Journal |doi=10.15779/Z388T19 |ssrn=1586574 |s2cid=153900462 }}</ref>

=== Economic incentive ===
The economic incentives to work on copyleft content can vary. Traditional copyright law is designed to promote progress by providing economic benefits to creators. When choosing to copyleft their work, content creators may seek complementary benefits like recognition from their peers.

In the world of computer programming, copyleft-licensed computer programs are often created by programmers to fill a need they have noticed. Such programs are often published with a copyleft license simply to ensure that subsequent users can also freely use modified versions of that program. This is especially true for creators who wish to prevent "open source hijacking", or the act of reusing open-source code and then adding extra restrictions to it, an action prevented by copyleft-licensing the software. Some creators, such as [[Elastic NV|Elastic]],<ref>[https://www.nytimes.com/2019/12/15/technology/amazon-aws-cloud-competition.html The New York Times]. Retrieved 23 April 2022</ref> feel that preventing [[Corporation|commercial]] enterprises from using and then selling their product under a proprietary license is also an incentive.

Furthermore, the [[Open source|open-source]] culture of programming has been described as a [[gift economy]], where social power is determined by an individual's contributions.<ref>{{cite web|last=Maher|first=Marcus|date=2000|title=Open Source Software: The Success of an Alternative Intellectual Property Incentive Paradigm|url=http://iplj.net/blog/wp-content/uploads/2009/09/Article-OPEN-SOURCE-SOFTWARE-THE-SUCCESS-OF-AN-ALTERNATIVE-INTELLECTUAL-PROPERTY-INCENTIVE-PARADIGM.pdf|url-status=dead|archive-url=https://web.archive.org/web/20140502033143/http://iplj.net/blog/wp-content/uploads/2009/09/Article-OPEN-SOURCE-SOFTWARE-THE-SUCCESS-OF-AN-ALTERNATIVE-INTELLECTUAL-PROPERTY-INCENTIVE-PARADIGM.pdf|archive-date=2 May 2014|access-date=1 May 2014|publisher=[[Fordham Intellectual Property, Media & Entertainment Law Journal]]}}</ref> Contributing to or creating open-source, copyleft-licensed software of high quality can lead to contributors gaining valuable experience and can lead to future career opportunities.<ref>{{Cite web|last=Sarmah|first=Harshajit|date=23 September 2019|title=5 Reasons Why Contributing To Open Source Projects Helps In Landing A Job|url=https://analyticsindiamag.com/5-reasons-why-contributing-to-open-source-projects-helps-in-landing-a-job/|access-date=22 July 2020|website=Analytics India Magazine }}</ref>

Copyleft software has economic effects beyond individual creators. The presence of quality copyleft software can force proprietary software developers to increase the quality of their software to compete with free software.<ref>{{cite web|last=Mustonen|first=Mikko|author-link=Mikko Mustonen|title=Copyleft - The Economics of Linux and Other Open Source Software|url=http://www.cyberinet05.inet-tr.org.tr/telekom/MI_mustonen.pdf|url-status=dead|archive-url=https://web.archive.org/web/20140502032254/http://www.cyberinet05.inet-tr.org.tr/telekom/MI_mustonen.pdf|archive-date=2 May 2014|access-date=1 May 2014|publisher=[[Information Economics and Policy]]}}</ref> This may also have the effect of preventing monopolies in areas dominated by proprietary software. However, competition with proprietary software can also be a reason to forgo copyleft. The [[Free Software Foundation]] recommends that when "widespread use of the code is vital for advancing the cause of free software",<ref>{{cite web|title=How to choose a license for your own work|url=https://www.gnu.org/licenses/license-recommendations.html#libraries|access-date=1 May 2017|publisher=[[Free Software Foundation]]'s Licensing and Compliance Lab}}</ref> allowing the code to be copied and used freely is more important than a copyleft.

== Copyleft application ==
Common practice for using copyleft is to codify the copying terms for a work with a [[license]]. Any such license typically includes all the provisions and principles of copyleft inside the license's terms. This includes the freedom to use the work, study the work, copy and share the work with others, modify the work, and distribute exact or modified versions of that work, with or without a fee.<ref>{{cite web |title=What is Copyleft? |url=https://www.gnu.org/copyleft/ |publisher=GNU Project}}</ref><ref>{{Cite web |title=Scheibner, James – "What price freedom (of software)? A guide for Australian legal practitioners on open source licensing" [2017] PrecedentAULA 23; (2017) 139 Precedent 39 |url=http://classic.austlii.edu.au/au/journals/PrecedentAULA/2017/23.html |access-date=27 November 2021 |website=classic.austlii.edu.au}}</ref>

Unlike similar permissive licenses that also grant these freedoms, copyleft licenses also ensure that any modified versions of a work covered by a copyleft license must also grant these freedoms. Thus, copyleft licenses have conditions: that modifications of any work licensed under a copyleft license must be distributed under a compatible copyleft scheme and that the distributed modified work must include a means of modifying the work. Under [[fair use]], however, copyleft licenses may be superseded, just like regular copyrights. Therefore, any person utilizing a source licensed under a copyleft license for works they invent is free to choose any other license (or none at all) provided they meet the fair use standard.<ref>
{{Cite book
 |author1=Kirk St.Amant |author2=Brian Still
 |name-list-style=amp | chapter = Examining Open Source Software Licenses through the Creative Commons Licensing Model
 | title = Handbook of Research on Open Source Software: Technological, Economic, and Social Perspectives
 | publisher = Information Science Reference
 |date= 2008
 | pages = 382 of 728
 | isbn = 978-1-59140-999-1}}</ref>

Copyleft licenses necessarily make creative use of relevant rules and laws to enforce their provisions. For example, when using copyright law, those who contribute to a work under copyleft usually must gain, defer, or assign copyright holder status.{{citation needed|date=June 2022}} By submitting the copyright of their contributions under a copyleft license, they deliberately give up some of the rights that normally follow from copyright, including the right to be the unique distributor of copies of the work.

Some laws used for copyleft licenses vary from one country to another, and may also be granted in terms that vary from country to country. For example, in some countries, it is acceptable to sell a software product without warranty, in standard [[GNU General Public License]] style, while in most [[European countries]] it is not permitted for a software distributor to [[waiver|waive]] all warranties regarding a sold product.{{citation needed|date=June 2022}} For this reason, the extent of such warranties is specified in most European copyleft licenses, for example, the [[European Union Public Licence]] (EUPL),<ref>{{cite web|title=The EUPL – European Union Public Licence|url=http://www.osor.eu/eupl/european-union-public-licence-eupl-v.1.1|access-date=9 January 2007|publisher=European Commission}}</ref> or the [[CeCILL license]],<ref>{{cite web|title=Free Software Licensing Agreement CeCILL|url=http://www.inria.fr/valorisation/logiciels/Licence.CeCILL-V1.US.pdf|access-date=24 August 2010|publisher=INRIA|archive-url=https://web.archive.org/web/20100808040542/http://www.inria.fr/valorisation/logiciels/Licence.CeCILL-V1.US.pdf|archive-date=8 August 2010|url-status=dead}}</ref> a license that allows one to use GNU GPL in combination with a limited warranty.

For projects which will be run over a network, a variation of the GNU GPL, called the [[Affero General Public License]] (GNU AGPL), ensures that the source code is available to users of software over a network.

==Types and relation to other licenses==
{{See also|Free-software licence#Restrictions}}
{| class="wikitable"
!rowspan=2|
! colspan="3" | [[Free software|Free]]
! colspan="3" | [[Proprietary software|Non-free]]
|-
![[Public domain]]  & [[Public-domain-equivalent license|equivalents]]
! width=|{{nowrap|[[Permissive license]]}} !! {{yes|}}Copyleft (protective license) !! width=|{{nowrap|[[Non-commercial activity|Noncommercial]] license}} !! [[Proprietary license]] !! [[Trade secret]]
|-
! scope=row | Description
| Grants all rights || Grants use rights, including right to relicense (allows proprietization, [[license compatibility]]) || {{yes|}} Grants use rights, forbids [[proprietization]] || Grants rights for noncommercial use only. May be combined with share-alike. || Traditional use of [[copyright]]; certain rights may or may not be granted || No information made public
|-
! scope=row | For software
| PD, [[Unlicense]], [[CC0]] || [[BSD licenses|BSD]], [[MIT License|MIT]], [[Apache License|Apache]] ||{{yes|}}[[GPL]], [[GNU Affero General Public License|AGPL]] || [[Java Research License|JRL]], [[Aladdin Free Public License|AFPL]] || [[Proprietary software]], no public license || Private, internal software
|-
! scope=row | For other creative works
| PD, [[CC0]] || [[CC BY]] || {{yes|}} [[CC BY-SA]], [[Free Art License|FAL]] || [[CC BY-NC]] || [[Copyright]], no public license, [[Creative Commons license|CC BY-ND]]|| Unpublished
|}
[[File:Cc-sa.svg|thumb|upright=0.5|The [[Creative Commons]] icon for Share-Alike, a variant of the copyleft symbol]]

Copyleft is a distinguishing feature of some [[free software]] licenses, while other [[Free software license|free-software licenses]] are not copyleft licenses because they do not require the licensee to distribute derivative works under the same license. There is an ongoing debate as to which class of license provides the greater degree of freedom. This debate hinges on complex issues, such as the definition of freedom and whose freedoms are more important: the potential future recipients of a work (freedom from proprietization) or just the initial recipient (freedom to proprietize). However, current copyright law and the availability of both types of licenses, copyleft and permissive, allow authors to choose the type under which to license the works they invent.

For documents, art, and other works other than software and code, the [[Share-alike|Creative Commons share-alike licensing system]] and the [[GNU Free Documentation License]] (GFDL) allow authors to apply limitations to certain sections of their work, exempting some parts of the work from the full copyleft mechanism. In the case of the GFDL, these limitations include the use of invariant sections, which may not be altered by future editors. The initial intention of the GFDL was as a device for supporting the [[documentation]] of copylefted software. However, the result is that it can be used for any kind of document.

===Strong and weak copyleft===
The strength of the copyleft license governing a work is determined by the extent to which its provisions can be imposed on all kinds of derivative works. Thus, the term "weak copyleft" refers to licenses where not all derivative works inherit the copyleft license; whether a derivative work inherits or not often depends on how it was derived.

"Weak copyleft" licenses are often used to cover [[Library (computing)|software libraries]]. This allows other software to link to the library and be redistributed without the requirement for the linking software to also be licensed under the same terms. Only changes to the software licensed under a "weak copyleft" license become subject itself to copyleft provisions of such a license. This allows programs of any license to be compiled and linked against copylefted libraries such as [[GNU C Library|glibc]] and then redistributed without any re-licensing required. The concrete effect of strong vs. weak copyleft has yet to be tested in court.<ref>{{cite web|author=Patrice-Emmanuel Schmitz|date=3 April 2015|title=The meaning of "Copyleft" in EUPL|url=https://joinup.ec.europa.eu/community/eupl/news/meaning-%E2%80%9Ccopyleft%E2%80%9D-eupl|work=Joinup}}</ref> Free-software licenses that use "weak" copyleft include the [[GNU Lesser General Public License]] and the [[Mozilla Public License]].

The [[GNU General Public License]] is an example of a license implementing strong copyleft. A stronger copyleft license is the [[GNU Affero General Public License|AGPL]], which requires the publishing of the source code for [[software as a service]] use cases.<ref>For some of the philosophy behind the term "SaaSS", see the "Server Software" section of {{cite web|url=https://www.gnu.org/licenses/license-recommendations.html | title=How to choose a license for your own work |publisher=GNU Project |date=20 December 2015 |access-date=1 May 2017}}</ref><ref>{{cite web|url=https://www.gnu.org/philosophy/who-does-that-server-really-serve.html |title=Who does that server really serve? |last=Stallman|first=Richard|author-link=Richard Stallman|publisher=[[GNU Project]] |date=18 November 2016 |access-date=1 May 2017}}</ref><ref>{{cite web|url=https://www.gnu.org/licenses/why-affero-gpl.html |title=Why the Affero GPL |publisher=[[GNU Project]] |date=10 May 2015 |access-date=1 May 2017}}</ref><ref name="fsf2">[https://www.gnu.org/philosophy/license-list.html#AGPL List of free-software licences on the GNU website]: "''We recommend that developers consider using the GNU AGPL for any software which will commonly be run over a network''".</ref>

The [[Sybase Open Watcom Public License]] is one of the strongest copyleft licenses, as this license closes the so-called "private usage" loophole of the GPL, and requires the publishing of source code in any use case. For this reason, the license is considered non-free by the [[Free Software Foundation]],  the [[GNU Project]], and the [[Debian]] project.<ref name="fsf-watcom">{{cite web|url=https://www.gnu.org/licenses/license-list.html#Watcom |title=Various Licenses and Comments about Them - Sybase Open Watcom Public License version 1.0 (#Watcom) |publisher=GNU |access-date=23 December 2015 |quote= This is not a free software license. It requires you to publish the source code publicly whenever you "Deploy" the covered software, and "Deploy" is defined to include many kinds of private use.}}</ref> However, the license is accepted as [[open source]] by the [[Open Source Initiative|OSI]].

The [[Design Science License]] (DSL) is a strong copyleft license that applies to any work, not only software or documentation, but also literature, artworks, music, photography, and video. DSL was written by Michael Stutz after he took an interest in applying GNU-style copyleft to non-software works, which later came to be called [[libre content|libre works]]. In the 1990s, it was used on music recordings, visual art, and even novels. It is not considered compatible with the GNU GPL by the Free Software Foundation.<ref name="fsf">{{cite web|title=Various Licenses and Comments about Them|url=https://www.gnu.org/licenses/license-list.html#dsl|publisher=GNU Project}}</ref>

===Full and partial copyleft===
"Full" and "partial" copyleft relate to another issue. Full copyleft exists when all parts of a work (except the license itself) may only be modified and distributed under the terms of the work's copyleft license. Partial copyleft, by contrast, exempts some parts of the work from the copyleft provisions, permitting distribution of some modifications under terms other than the copyleft license, or in some other way does not impose all the principles of copylefting on the work. An example of partial copyleft is the GPL linking exception made for some software packages.

===Share-alike===
The "[[share-alike]]" condition in some licenses imposes the requirement that any freedom that is granted regarding the original work must be granted on exactly the same or compatible terms in any derived work.

This implies that any copyleft license is automatically a share-alike license but not the other way around, as some share-alike licenses include further restrictions such as prohibiting commercial use. Another restriction is that not everyone wants to share their work, and some share-alike agreements require that the whole body of work be shared, even if the author only wants to share a certain part. The plus side for an author of source code is that any modification to the code will not only benefit the original author but that the author will be recognized and ensure the same or compatible license terms cover the changed code.<ref>{{cite journal|last=Engelfriet|first=Arnoud|date=2010|title=Choosing an Open Source License|journal=IEEE Software|publisher=Athens University of Economics and Business|volume=27|pages=48–49|doi=10.1109/MS.2010.5|s2cid=36712745}}</ref> Some Creative Commons licenses are examples of share-alike copyleft licenses.

=== Permissive licenses ===
{{Main|Permissive software license}}

Those licenses grant users of the software the same freedoms as copyleft licenses but do not require modified versions of that software to also include those freedoms. They have minimal restrictions on how the software can be used, modified, and redistributed, and are thus not copyleft licenses. Examples of this type of license include the [[X11 license]], [[Apache License|Apache license]], [[MIT license|Expat license]], and the various [[BSD licenses]].

== Debate and controversy ==
It has been suggested that copyleft has become a divisive issue in the ideological strife between the [[Open Source Initiative]] and the [[free software movement]].<ref>{{cite web|last=Biancuzzi|first=Federico|date=30 June 2005|title=ESR: "We Don't Need the GPL Anymore"|url=http://www.onlamp.com/pub/a/onlamp/2005/06/30/esr_interview.html|access-date=23 August 2008|publisher=ONLamp.com|archive-url=https://web.archive.org/web/20180306105402/http://www.onlamp.com/pub/a/onlamp/2005/06/30/esr_interview.html|archive-date=6 March 2018}}</ref> However, there is evidence that copyleft is both accepted and proposed by both parties:
* Both the OSI and the FSF have copyleft and non-copyleft licenses in their respective lists of accepted licenses.<ref name="osi">{{cite web|last=Tiemann|first=Michael|author-link=Michael Tiemann|date=18 September 2006|title=Licenses by Name|url=http://www.opensource.org/licenses/alphabetical|access-date=23 August 2008}}</ref><ref name="fsf" />
* The OSI's original Legal Counsel [[Lawrence Rosen (attorney)|Lawrence Rosen]] has written a copyleft license, the [[Open Software License]].
* The OSI's licensing how-to recognises the GPL as a "best practice" license.<ref>{{cite web|last=Raymond|first=Eric Steven|author-link=Eric S. Raymond|date=9 November 2002|title=Licensing HOWTO|url=http://www.catb.org/~esr/Licensing-HOWTO.html#choosing|access-date=23 August 2008}}</ref>
* Some of the software programs of the GNU Project are published under non-copyleft licenses.<ref>{{cite web|date=8 March 2007|title=What the GPLv3 Means for MS-Novell Agreement|url=http://yro.slashdot.org/comments.pl?sid=225606&cid=18272276|access-date=14 May 2014|publisher=Yro.slashdot.org}}</ref>
* Stallman himself has endorsed the use of non-copyleft licenses in certain circumstances, most recently in the case of the [[Ogg Vorbis]] [[Relicensing|license change]].<ref>{{cite web|last=Stallman|first=Richard|author-link=Richard Stallman|date=26 February 2001|title=LWN.net: RMS on the Ogg Vorbis license|url=https://lwn.net/2001/0301/a/rms-ov-license.php3|access-date=23 August 2008|quote=[M]y agreement with the idea of a lax [Ogg/Vorbis] license in this special case is just as pragmatic as my preference for the GPL in most cases. In both cases it is a matter of how we can attain freedom.}}</ref>

=== Viral licensing ===
{{Main|Viral license}}
''Viral license'' is a pejorative name for copyleft licenses.<ref>{{cite web|url=http://news.cnet.com/2100-1001-268889.html|title=Microsoft license spurns open source|publisher=CBS Interactive|work=CNET}}</ref><ref>{{cite magazine|url=https://www.wired.co.uk/news/archive/2011-12/16/alternatives-to-copyright|title=Some rights reserved: the alternatives to copyright|magazine=Wired UK}}</ref><ref>{{cite web|url=http://a2knetwork.org/glossary|archive-url=https://web.archive.org/web/20090426091132/http://a2knetwork.org/glossary|url-status=dead|archive-date=26 April 2009|title=Glossary|work=a2knetwork.org}}</ref><ref>{{cite web | url=http://www.friedfrank.com/siteFiles/Publications/ACC-GNY_Newsletter_OpenSourceInMATransactions.pdf | title=Inoculating Your Purchase – Contractual Protection from Viral Licenses in M&A Transactions | date=March 2013 | access-date=10 June 2016 | author1=Jason Greenberg | author2= Daniel Glazer |work=Fried Frank|publisher= Association of Corporate Counsel}}</ref><ref>{{cite web | url=http://www.buddlefindlay.com/article/2013/07/01/legal-update-on-information-and-communication-technology-%E2%80%93-july-2013 | title=Legal update on Information and Communication Technology – July 2013 | date=1 July 2013 | access-date=10 June 2016 | archive-url=https://web.archive.org/web/20130921110256/http://www.buddlefindlay.com/article/2013/07/01/legal-update-on-information-and-communication-technology-%E2%80%93-july-2013 | archive-date=21 September 2013 | url-status=dead |author1=Philip Wood|author2=Amy Ryburn|author3=Allan Yeoman|author4=Andrew Matangi|author5=Steve Nightingale}}</ref> It originates from the terms 'General Public Virus' or 'GNU Public Virus' (GPV), which dates back to 1990, a year after the GPLv1 was released.<ref>{{cite web|url=http://psg.com/lists/namedroppers/namedroppers.2006/msg00246.html |title=Re: Section 5.2 (IPR {{sic|hide=n|nolink=y|reason=error in source|encumberance}}) in TAK rollover requirement draft |first=Paul |last=Vixie |author-link=Paul Vixie |publisher=[[Internet Engineering Task Force|IETF]] Namedroppers mailing list |date=6 March 2006 |access-date=29 April 2007 |archive-url=https://web.archive.org/web/20070927175628/http://psg.com/lists/namedroppers/namedroppers.2006/msg00246.html |archive-date=27 September 2007 }}</ref><ref>{{cite web|url=http://catb.org/esr/jargon/oldversions/jarg221.txt |title=General Public Virus |work=[[Jargon File]] 2.2.1 |date=15 December 1990 |access-date=29 April 2007}}</ref><ref>{{Cite journal|url=http://devlinux.org/lw-gnu-published.html |title=Reverse-engineering the GNU Public Virus – Is copyleft too much of a good thing? |first=Stig |last=Hackvän |journal=[[Linux Journal]] |date=September 1999 |access-date=29 April 2007 |url-status=dead |archive-url=https://web.archive.org/web/20110718132324/http://devlinux.org/lw-gnu-published.html |archive-date=18 July 2011 }}</ref> The name "[[viral license]]s" refers to the fact that any works derived from a copyleft work must preserve the copyleft permissions when distributed.

Some advocates of the various [[BSD Licenses]] used the term derisively in regards to the GPL's tendency to absorb BSD-licensed code without allowing the original BSD work to benefit from it, while at the same time promoting itself as "freer" than other licenses.<ref>{{cite web |url=http://cypherpunks.venona.com/date/1998/10/msg00429.html |title=Re: propose: 'cypherpunks license' (Re: Wanted: Twofish source code) |first=Bill |last=Stewart |publisher=[[Cypherpunk]]s mailing list |date=8 October 1998 |access-date=29 April 2007 |url-status=dead |archive-url=https://web.archive.org/web/20070529202454/http://cypherpunks.venona.com/date/1998/10/msg00429.html |archive-date=29 May 2007  }}</ref><ref>{{cite web|url=https://gcc.gnu.org/ml/gcc/2000-10/msg00198.html |title=Re: Using of parse tree externally |first=Joe |last=Buck |publisher=[[GNU Compiler Collection|GCC]] mailing list|date=10 October 2000 |access-date=29 April 2007}}</ref><ref>{{cite web |url=http://themes.freshmeat.net/articles/view/172#comment-5548 |title=The GNU Public Virus |first=L. Adrian |last=Griffis |date=15 July 2000 |access-date=29 April 2007 |archive-date=9 November 2017 |archive-url=https://web.archive.org/web/20171109004114/http://themes.freshmeat.net/articles/view/172#comment-5548 |url-status=dead }}</ref> [[Microsoft]] vice-president [[Craig Mundie]] remarked, "This viral aspect of the GPL poses a threat to the intellectual property of any organization making use of it."<ref>{{cite web|url=http://www.microsoft.com/presspass/exec/craig/05-03sharedsource.mspx |title=Speech Transcript – Craig Mundie |publisher=[[New York University Stern School of Business]] |date=3 May 2001 |first=Craig |last=Mundie |author-link=Craig Mundie |access-date=23 August 2008 |url-status=dead |archive-url=https://web.archive.org/web/20050621082004/http://www.microsoft.com/presspass/exec/craig/05-03sharedsource.mspx |archive-date=21 June 2005  }}</ref> In another context, [[Steve Ballmer]] declared that code released under GPL is useless to the commercial sector, since it can only be used if the resulting surrounding code is licensed under a GPL-compatible license, and described it thus as "a cancer that attaches itself in an intellectual property sense to everything it touches".<ref>{{Cite web
| first=Dave
| last=Newbart
| title=Microsoft CEO takes launch break with the Sun-Times
| date=1 June 2001
| publisher=Chicago Sun-Times
| url=http://suntimes.com/output/tech/cst-fin-micro01.html
| archive-url=https://web.archive.org/web/20010615205548/http://suntimes.com/output/tech/cst-fin-micro01.html
| archive-date=15 June 2001
}}(Internet archive link)</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>{{cite wikisource |title=Free Software Leaders Stand Together}}</ref> According to [[Free Software Foundation|FSF]] compliance engineer David Turner, the term "viral license" creates a misunderstanding and a fear of using copylefted free software.<ref>{{cite web|url=http://www.linuxtoday.com/developer/2006082902126OSHLLL |title=IT Manager's Journal: 10 Common Misunderstandings About the GPL |first=Bruce |last=Byfield |date=29 August 2006 |access-date=23 August 2008}}</ref> While a person can catch a virus without active action, license conditions take effect upon effective usage or adoption.<ref>{{Cite web|url=https://lu.is/blog/2012/02/02/the-license-term-smorgasbord-copyleft-share-alike-reciprocal-viral-or-hereditary/|title=The license term smorgasbord: copyleft, share-alike, reciprocal, viral, or hereditary? – Luis Villa: Open Law and Strategy|website=lu.is|date=3 February 2012 |access-date=22 August 2018}}</ref> David McGowan has also written that there is no reason to believe the GPL could force proprietary software to become free software, but could "try to enjoin the firm from distributing commercially a program that combined with the GPL'd code to form a derivative work, and to recover damages for infringement." If the firm "actually copied code from a GPL'd program, such a suit would be a perfectly ordinary assertion of copyright, which most private firms would defend if the shoe were on the other foot."<ref>
{{Cite book
 |first=David |last=McGowan
 | chapter = Legal Aspects of Free and Open Source Software
 | title = Perspectives on Free and Open Source Software
 | url = https://archive.org/details/perspectivesonfr00fell
 | url-access = limited
 |editor1=Joseph Feller |editor2=Brian Fitzgerald |editor3=Scott A. Hissam |editor4=Karim R. Lakahani |publisher=MIT Press
 |date= 2005
 | page = [https://archive.org/details/perspectivesonfr00fell/page/n395 382]
 | isbn = 978-0-262-06246-6}}</ref> Richard Stallman has described this view with an analogy, saying, "The GPL's domain does not spread by proximity or contact, only by deliberate inclusion of GPL-covered code in your program. It spreads like a [[Chlorophytum comosum|spider plant]], not like a virus."<ref>{{cite web|last=Poynder|first=Richard|date=21 March 2006|title=The Basement Interviews: Freeing the Code|url=https://archive.org/stream/The_Basement_Interviews/Richard_Stallman_Interview_djvu.txt|access-date=5 February 2010}}</ref>

Popular copyleft licenses, such as the GPL, have a clause allowing components to interact with non-copyleft components as long as the communication is abstract,{{Failed verification|date=May 2020|reason=source does not use word abstract once and it also does not lay out clear guidelines, just gives some rather vague examples}} such as executing a command-line tool with a set of switches or interacting with a web server.<ref>{{cite web|url=https://www.gnu.org/licenses/gpl-faq.html#MereAggregation |title=Frequently Asked Questions about the GNU Licenses |publisher=[[Free Software Foundation]] |date=24 June 2008 |access-date=1 May 2017}}</ref> As a consequence, even if one module of an otherwise non-copyleft product is placed under the GPL, it may still be legal for other components to communicate with it in ways such as these.{{clarify |date=May 2020 |reason=it may also not be legal, this is written to favour one point of view}} This allowed communication may or may not include reusing libraries or routines via [[Library (computing)|dynamic linking]]&nbsp;– some commentators say it does,<ref>{{cite web|url=http://www.catb.org/~esr/Licensing-HOWTO.html#id2789302 |title=Licensing HOWTO |date=9 November 2002 |first=Eric Steven |last=Raymond |author-link=Eric S. Raymond |access-date=21 March 2010}}</ref> the FSF asserts it does not and explicitly adds an [[GPL linking exception|exception allowing it]] in the license for the [[GNU Classpath]] re-implementation of the Java library. This ambiguity is an important difference between the GPL and the [[LGPL]], in that the LGPL specifically allows linking or compiling works licensed under terms that are not compatible with the LGPL, with works covered by the LGPL.<ref name="not_use_LGPL">Stallman, Richard. "[https://www.gnu.org/licenses/why-not-lgpl.html Why you shouldn't use the Lesser GPL for your next library]". [[GNU Project]].</ref>

==Symbol==
{{Contains special characters|Uncommon Unicode|section|compact=y}}
{{Infobox symbol
|mark=<span style="display:inline-block; transform: scaleX(-1);" title="Reversed U+00A9">©</span> <span title="U+1F12F">{{not a typo|🄯}}</span>
|name=Copyleft symbol
|unicode={{Unichar|1F12F|COPYLEFT SYMBOL}}<br />{{nowrap|1=Alternative symbol: (ɔ)}}
|see also=<!--see text  U+0254 ɔ LATIN SMALL LETTER OPEN O -->
|different from={{unichar|00A9|Copyright Sign|nlink=Copyright symbol}}
}}
The copyleft symbol is a mirrored version of the [[copyright symbol]], {{char|©}}: a reversed C in a circle.<ref>{{Cite web |title=The Unicode Standard, Version 15.0: Enclosed Alphanumeric Supplement |url=https://www.unicode.org/charts/PDF/U1F100.pdf |website=unicode.org}}</ref> A 2016 proposal to add the symbol to a future version of Unicode was accepted by the [[Unicode Technical Committee]].<ref>{{cite web|url=https://www.unicode.org/L2/L2016/16059-copyleft.pdf |title=Proposal to add the Copyleft Symbol to Unicode}}</ref><ref name=UnicodePipeline>{{cite web |title=Proposed New Characters: Pipeline Table |url=http://unicode.org/alloc/Pipeline.html |website=Unicode Character Proposals |publisher=Unicode Consortium |access-date=18 April 2017}}</ref> The code point {{Unichar|1F12F|COPYLEFT SYMBOL}} was added in [[Unicode 11]].<ref name=UnicodePipeline/><ref>{{Cite web|url=http://blog.unicode.org/2018/06/announcing-unicode-standard-version-110.html|title=Announcing The Unicode Standard, Version 11.0|website=The Unicode Blog |access-date=6 June 2018}}</ref> The copyleft symbol has no legal status.<ref>{{Cite book |last=Hall |first=G. Brent |url=https://books.google.com/books?id=JZNuu8XODQMC&pg=PA29 |title=Open Source Approaches in Spatial Data Handling |publisher=Springer |date=2008 |isbn=9783540748311 |page=29 |bibcode=2008osas.book.....H}}</ref> 

{{As of|2018|post=,}} it is largely unimplemented in fonts, but can be approximated with character {{Unichar|2184|LATIN SMALL LETTER REVERSED C}} between parenthesis {{char|(ɔ)}} or, if supported, by combining a reversed C with the character {{Unichar|20DD|COMBINING ENCLOSING CIRCLE|cwith=◌}}: {{char|ↄ⃝}}.<ref>{{cite web |url=http://unicode.org/mail-arch/unicode-ml/Archives-Old/UML022/0846.html |title=Unicode copyleft inquiry |date=6 May 2000}}</ref>

''For a list of fonts that include this glyph, see {{section link|Unicode fonts|List of SMP Unicode fonts}} and then row "[[Enclosed Alphanumeric Supplement]] (173: 1F100–1F1FF)"  (This list is not guaranteed to be current).''

==See also==
{{Portal|Free and open-source software}}
{{Div col}}
* {{Category|Copyleft software licenses|List of copyleft software licenses}}
* [[All rights reversed]]
* [[Anti-copyright notice]]
* [[Commercial use of copyleft works]]
* [[Comparison of open source and closed source]]
* [[Copyfraud]]
* [[Copyright abolition]]
* [[Copyright alternatives]]
* [[Intellectual property#Criticisms|Criticism of intellectual property]]
* [[Internet freedom]]
* [[Free content]]
* [[Free Culture movement]]
* [[Free software movement]]
* [[History of free and open-source software]]
* [[Opposition to copyright]]
* [[Public copyright license]]
* [[Free video]]
* ''[[Steal This Film]]''
{{Div col end}}

== References ==
{{Reflist}}

{{Commons category|Copyleft}}
{{Wiktionary|copyleft}}

{{FOSS}}
{{Intellectual property activism}}

[[Category:Copyleft| ]]
[[Category:Copyright law]]
[[Category:Free and open-source software licenses]]
[[Category:Free and open-source software]]
[[Category:Intellectual property activism]]
[[Category:Typographical symbols]]
{{Навигационная таблица/Портал/Английская Википедия}}
[[Категория:Английская Википедия]]
[[Категория:Википедия]]
[[Категория:Статья из Википедии]]
[[Категория:Статья из Английской Википедии]]