diff options
Diffstat (limited to 'talermerchantdemos/blog/articles/en/assigning-copyright.html')
-rw-r--r-- | talermerchantdemos/blog/articles/en/assigning-copyright.html | 67 |
1 files changed, 47 insertions, 20 deletions
diff --git a/talermerchantdemos/blog/articles/en/assigning-copyright.html b/talermerchantdemos/blog/articles/en/assigning-copyright.html index e2e3ef8..be5ce3d 100644 --- a/talermerchantdemos/blog/articles/en/assigning-copyright.html +++ b/talermerchantdemos/blog/articles/en/assigning-copyright.html @@ -1,22 +1,31 @@ <!--#include virtual="/server/header.html" --> -<!-- Parent-Version: 1.77 --> +<!-- Parent-Version: 1.96 --> +<!-- This page is derived from /server/standards/boilerplate.html --> +<!--#set var="TAGS" value="essays licensing copyleft" --> +<!--#set var="DISABLE_TOP_ADDENDUM" value="yes" --> <title>When a Company Asks For Your Copyright - GNU Project - Free Software Foundation</title> <link rel="canonical" - href="http://www.fsf.org/blogs/rms/assigning-copyright" /> + href="https://www.fsf.org/blogs/rms/assigning-copyright" /> <!--#include virtual="/philosophy/po/assigning-copyright.translist" --> <!--#include virtual="/server/banner.html" --> +<!--#include virtual="/philosophy/ph-breadcrumb.html" --> +<!--GNUN: OUT-OF-DATE NOTICE--> +<!--#include virtual="/server/top-addendum.html" --> +<div class="article reduced-width"> <h2>When a Company Asks For Your Copyright</h2> +<div class="thin"></div> <p>Companies that develop free software and release it under the GNU GPL sometimes distribute some copies of the code in other ways. If they distribute the exact same code under a different license to certain users that pay for this, typically permitting including the code in -proprietary programs, we call it “selling exceptions”. If they +proprietary programs, we call it “selling exceptions.” If they distribute some version of the code solely in a proprietary manner, we call that releasing a purely proprietary version of the program.</p> -<p><a href="/philosophy/selling-exceptions.html">http://www.gnu.org/philosophy/selling-exceptions.html</a> explains why +<p>“<a href="/philosophy/selling-exceptions.html">Selling exceptions +to the GNU GPL</a>” explains why selling exceptions is acceptable, though only barely. By contrast, releasing a purely proprietary version is outright wrong, like any other proprietary software.</p> @@ -83,11 +92,11 @@ contains your code, but refuse to let the company release purely proprietary versions containing your code, you can insist on a condition more or less like this:</p> -<blockquote> +<blockquote class="emph-box"> <p>Any program based on (as defined in GNU General Public License version 3) Hacker's code that FOO distributes shall be made - available by FOO under a) the “GNU General Public License (GPL), - version 2 or later”, or b) the licensing in (a), above, but with “2” + available by FOO under <b>(a)</b> the “GNU General Public License (GPL), + version 2 or later,” or <b>(b)</b> the licensing in (a), above, but with “2” replaced by any higher existing GPL version number. Provided FOO makes the program available as source code gratis to the public in this way, it may also distribute the identical program to some of @@ -100,11 +109,11 @@ condition more or less like this:</p> might be released solely in a proprietary version, you can insist on a condition more or less like this:</p> -<blockquote> +<blockquote class="emph-box"> <p>Any program based on (as defined in GNU General Public License version 3) Hacker's code that FOO distributes shall be made - available by FOO under a) the “GNU General Public License (GPL), - version 2 or later”, or b) the licensing in (a), above, but with “2” + available by FOO under <b>(a)</b> the “GNU General Public License (GPL), + version 2 or later,” or <b>(b)</b> the licensing in (a), above, but with “2” replaced by any higher existing GPL version number. Provided FOO makes the program available as source code gratis to the public in this way, it may also distribute the same version of Hacker's code @@ -112,10 +121,10 @@ condition more or less like this:</p> </blockquote> <p>If the program is released under the GNU Affero GPL, then add “Affero” -before “General”, change “GPL” to “AGPL”, change “2 or” to “3 or”, and +before “General,” change “GPL” to “AGPL,” change “2 or” to “3 or,” and it could make sense to replace “that FOO distributes” with “that FOO distributes, or deploys on a server accessible to users other than -FOO”.</p> +FOO.”</p> <p>The FSF has had these texts reviewed by a lawyer, but you should get your own legal advice before using them.</p> @@ -125,10 +134,11 @@ will show you how far it plans to depart from the principles of free software. Then you can respond to ensure your work will contribute to the free software community and not be diverted into proprietary software.</p> +</div> </div><!-- for id="content", starts in the include above --> <!--#include virtual="/server/footer.html" --> -<div id="footer"> +<div id="footer" role="contentinfo"> <div class="unprintable"> <p>Please send general FSF & GNU inquiries to @@ -146,30 +156,47 @@ to <a href="mailto:webmasters@gnu.org"><webmasters@gnu.org></a>.</p> to <a href="mailto:web-translators@gnu.org"> <web-translators@gnu.org></a>.</p> - <p>For information on coordinating and submitting translations of + <p>For information on coordinating and contributing translations of our web pages, see <a href="/server/standards/README.translations.html">Translations README</a>. --> Please see the <a href="/server/standards/README.translations.html">Translations -README</a> for information on coordinating and submitting translations +README</a> for information on coordinating and contributing translations of this article.</p> </div> -<p>Copyright © 2014 Free Software Foundation, Inc.</p> +<!-- Regarding copyright, in general, standalone pages (as opposed to + files generated as part of manuals) on the GNU web server should + be under CC BY-ND 4.0. Please do NOT change or remove this + without talking with the webmasters or licensing team first. + Please make sure the copyright date is consistent with the + document. For web pages, it is ok to list just the latest year the + document was modified, or published. + + If you wish to list earlier years, that is ok too. + Either "2001, 2002, 2003" or "2001-2003" are ok for specifying + years, as long as each year in the range is in fact a copyrightable + year, i.e., a year in which the document was published (including + being publicly visible on the web or in a revision control system). + + There is more detail about copyright years in the GNU Maintainers + Information document, www.gnu.org/prep/maintain. --> + +<p>Copyright © 2010, 2014, 2021 Free Software Foundation, Inc.</p> <p>This page is licensed under a <a rel="license" -href="http://creativecommons.org/licenses/by-nd/3.0/us/">Creative -Commons Attribution-NoDerivs 3.0 United States License</a>.</p> +href="http://creativecommons.org/licenses/by-nd/4.0/">Creative +Commons Attribution-NoDerivatives 4.0 International License</a>.</p> <!--#include virtual="/server/bottom-notes.html" --> <p class="unprintable">Updated: <!-- timestamp start --> -$Date: 2014/07/13 21:47:00 $ +$Date: 2021/10/01 17:02:54 $ <!-- timestamp end --> </p> </div> -</div> +</div><!-- for class="inner", starts in the banner include --> </body> </html> |