# LANGUAGE translation of https://www.gnu.org/licenses/identify-licenses-clearly.html # Copyright (C) YEAR Free Software Foundation, Inc. # This file is distributed under the same license as the original article. # FIRST AUTHOR , YEAR. # #, fuzzy msgid "" msgstr "" "Project-Id-Version: identify-licenses-clearly.html\n" "POT-Creation-Date: 2022-01-22 18:25+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" "Language: \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=CHARSET\n" "Content-Transfer-Encoding: 8bit\n" #. type: Content of: msgid "" "Don't Say “Licensed under GNU GPL 2”! - GNU Project - Free " "Software Foundation" msgstr "" #. type: Content of: <div><h2> msgid "For Clarity's Sake, Please Don't Say “Licensed under GNU GPL 2”!" msgstr "" #. type: Content of: <div><address> msgid "by <a href=\"https://www.stallman.org/\">Richard Stallman</a>" msgstr "" #. type: Content of: <div><p> msgid "" "When I wrote the GNU General Public License (GNU GPL), in 1989, I recognized " "that changes might be necessary: the FSF might someday have reasons to " "publish a new version. So I called the license “version 1,” and " "set up a framework to enable users to upgrade programs to later license " "versions." msgstr "" #. type: Content of: <div><p> msgid "" "There was no customary way of doing this with a free license; as far as I " "know, it had never been done before. Developers had released a new version " "of a program under a different license, and maybe they had made new releases " "of old versions offering use under a different license, but they had never " "set up a systematic way to offer users the choice of using a future license " "version for already-released versions of a program." msgstr "" #. type: Content of: <div><p> msgid "" "I did not know how developers would respond to this innovation, so I decided " "to give each developer a choice about allowing future versions. This meant " "developers could release a program under GNU GPL version 1 <b>only</b>, or " "release it under GPL version 1 <b>or any later version</b>. The way " "developers state their choice is in the <b>license notice</b> that goes at " "the start of each source file. That's where the GPL says the decision is " "stated." msgstr "" #. type: Content of: <div><p> msgid "" "The Free Software Foundation urged developers to choose <b>or any later " "version</b>, since that meant users would be free to use that program under " "GNU GPL version 1, or under version 2 (once there was a version 2), or under " "version 3 (once there was a version 3). And they will be free to use it " "under version 4, if we ever have to make a version 4." msgstr "" #. type: Content of: <div><p> msgid "" "Since then, the FSF has released GNU GPL version 2 in 1991 and version 3 in " "2007. Each version offers developers the choice to insist on that one " "license version only, or permit use under future license versions. (GPL 3 " "also permits the “proxy” option, where a specified Web page can " "subsequently give permission to use a particular future version.)" msgstr "" #. type: Content of: <div><p> msgid "" "Publishing programs with license upgrade permission is vital to avoid " "incompatibility between programs released under different GPL versions." msgstr "" #. type: Content of: <div><p> msgid "" "Two different copyleft licenses are almost inevitably incompatible in the " "absence of some explicit compatibility mechanism. That is because each one " "necessarily requires modified versions of a program to be released under " "that very same license. As a consequence, code released under GPL version 2 " "only can't be merged with code released under GPL version 3 only." msgstr "" #. type: Content of: <div><p> msgid "" "The mechanism for compatibility between GPL versions is to release a program " "under “version N or any later version.” A program released under " "GPL-2.0-or-later can be merged with code under GPL-3.0-or-later, because " "“3 or later” is a subset of “2 or later.”" msgstr "" #. type: Content of: <div><p> msgid "" "Some developers say, “I will release now under GNU GPL version 3 " "only. When I see GPL version 4, if I like it, I will relicense my program " "to allow use under version 4.” That will work fine if you are the only " "author, provided you're still alive, healthy, contactable, and paying " "attention at that time. But copyright lasts an insanely long time nowadays; " "in the absence of major reforms, the copyright on your code will last 70 " "years after your death in the US (and 100 years in Mexico). Have you made " "arrangements for your heirs to consider the question of relicensing your " "code to GPL version 4 if you are no longer around to consider it?" msgstr "" #. type: Content of: <div><p> msgid "" "But trouble will happen even during your lifetime. What if we release GNU " "GPL version 4 ten years from now, and by that time 50 others have added to " "your program, releasing their added code under GPL-3.0-only simply because " "you did? You could approve GPL 4 for the program you initially released, but " "it would be a big job to contact the 50 subsequent developers at that time " "to get their permission for GPL 4 usage of their additions." msgstr "" #. type: Content of: <div><p> msgid "" "The way to avoid these problems is by approving future GPL versions in the " "license notice at the outset. Please put on each nontrivial file of the " "source release a license notice of the form shown at the end of the GPL " "version you are using." msgstr "" #. type: Content of: <div><p> msgid "" "Because we handle license compatibility this way, when people tell you a " "program is released “under GNU GPL version 2,” they are leaving " "the licensing of the program unclear. Is it released under GPL-2.0-only, or " "GPL-2.0-or-later? Can you merge the code with packages released under " "GPL-3.0-or-later?" msgstr "" #. type: Content of: <div><p> msgid "" "When sites such as GitHub invite developers to choose “GPL 3” or " "“GPL 2” among other license options, and don't raise the issue " "of future versions, this leads thousands of developers to leave their code's " "licensing unclear. Asking those users to choose between “only” " "and “or later” would lead them to make their code's licensing " "clear. It also provides an opportunity to explain how the latter choice " "avoids future incompatibility." msgstr "" #. type: Content of: <div><p> msgid "" "Abbreviated license indicators such as “GPL-2.0” or " "“GPL-3.0” will lead to confusion too. People and organizations " "that don't recognize the difference between “2 only” and " "“2 or later” will be prone to write “GPL-2.0” in " "both cases, not realizing there is a distinction to be made." msgstr "" #. type: Content of: <div><p> msgid "Therefore, when you use SPDX license indicators, please use these:" msgstr "" #. type: Content of: <div><ul><li> msgid "GPL-2.0-only or GPL-2.0-or-later" msgstr "" #. type: Content of: <div><ul><li> msgid "GPL-3.0-only or GPL-3.0-or-later" msgstr "" #. type: Content of: <div><ul><li> msgid "LGPL-2.0-only or LGPL-2.0-or-later" msgstr "" #. type: Content of: <div><ul><li> msgid "LGPL-2.1-only or LGPL-2.1-or-later" msgstr "" #. type: Content of: <div><ul><li> msgid "LGPL-3.0-only or LGPL-3.0-or-later" msgstr "" #. type: Content of: <div><ul><li> msgid "AGPL-3.0-only or AGPL-3.0-or-later" msgstr "" #. type: Content of: <div><ul><li> msgid "GFDL-1.3-only or GFDL-1.3-or-later" msgstr "" #. type: Content of: <div><p> msgid "" "Please do not use the old, ambiguous license indicators, which will be " "deprecated:" msgstr "" #. type: Content of: <div><ul><li> msgid "GPL-2.0" msgstr "" #. type: Content of: <div><ul><li> msgid "GPL-3.0" msgstr "" #. type: Content of: <div><ul><li> msgid "LGPL-2.0" msgstr "" #. type: Content of: <div><ul><li> msgid "LGPL-2.1" msgstr "" #. type: Content of: <div><ul><li> msgid "LGPL-3.0" msgstr "" #. type: Content of: <div><ul><li> msgid "AGPL-3.0" msgstr "" #. type: Content of: <div><ul><li> msgid "GFDL-1.3." msgstr "" #. type: Content of: <div><p> msgid "" "Giving developers the choice of GPL version “1 only” or GPL " "version “1 or later” seemed obligatory in 1989, but it has " "created a complexity that we would be better off without. Meanwhile, several " "licenses that unconditionally give users the choice to upgrade to later " "license versions have become widely accepted. These include the Mozilla " "Public License and the Eclipse Public License. Each version says that a " "user is free to use the work under later versions, if any, of the same " "license. The Creative Commons copyleft license, CC BY-SA, permits users to " "upgrade the license version when they modify the work." msgstr "" #. type: Content of: <div><p> msgid "" "Perhaps we should switch to that approach for future versions of the GNU " "GPL. But that is something to think about in the future." msgstr "" #. type: Content of: <div><p> msgid "" "We thank SPDX for deciding to change the short identifiers for the GNU " "family of licenses to make the “or later” versus " "“only” choice explicit. The upcoming version of the SPDX License " "List for license identifiers will use the identifiers recommended above. The " "confusing identifiers, such as “GPL-2.0,” will be deprecated. We " "ask people to replace them with the new unambiguous identifiers as soon as " "possible." msgstr "" #. type: Content of: <div><p> msgid "" "By using identifiers that are explicit as to <b>only</b> or <b>any later " "version</b>, we can make the community aware of the difference and encourage " "developers to state their decisions clearly." msgstr "" #. TRANSLATORS: Use space (SPC) as msgstr if you don't have notes. #. type: Content of: <div> msgid "*GNUN-SLOT: TRANSLATOR'S NOTES*" msgstr "" #. type: Content of: <div><div><p> msgid "" "Please send general FSF & GNU inquiries to <a " "href=\"mailto:gnu@gnu.org\"><gnu@gnu.org></a>. There are also <a " "href=\"/contact/\">other ways to contact</a> the FSF. Broken links and " "other corrections or suggestions can be sent to <a " "href=\"mailto:webmasters@gnu.org\"><webmasters@gnu.org></a>." msgstr "" #. TRANSLATORS: Ignore the original text in this paragraph, #. replace it with the translation of these two: # #. We work hard and do our best to provide accurate, good quality #. translations. However, we are not exempt from imperfection. #. Please send your comments and general suggestions in this regard #. to <a href="mailto:web-translators@gnu.org"> # #. <web-translators@gnu.org></a>.</p> # #. <p>For information on coordinating and contributing translations of #. our web pages, see <a #. href="/server/standards/README.translations.html">Translations #. README</a>. #. type: Content of: <div><div><p> msgid "" "Please see the <a " "href=\"/server/standards/README.translations.html\">Translations README</a> " "for information on coordinating and contributing translations of this " "article." msgstr "" #. type: Content of: <div><p> msgid "Copyright © 2017, 2020, 2022 Free Software Foundation, Inc." msgstr "" #. type: Content of: <div><p> msgid "" "This page is licensed under a <a rel=\"license\" " "href=\"http://creativecommons.org/licenses/by-nd/4.0/\">Creative Commons " "Attribution-NoDerivatives 4.0 International License</a>." msgstr "" #. TRANSLATORS: Use space (SPC) as msgstr if you don't want credits. #. type: Content of: <div><div> msgid "*GNUN-SLOT: TRANSLATOR'S CREDITS*" msgstr "" #. timestamp start #. type: Content of: <div><p> msgid "Updated:" msgstr ""