www/licenses po/quick-guide-gplv3.translist po/...

[GNUN]

CVSROOT:        /web/www
Module name:    www
Changes by:     GNUN <gnun>     20/05/22 01:59:02

Modified files:
        licenses/po    : quick-guide-gplv3.translist 
                         quick-guide-gplv3.zh-cn.po 
Added files:
        licenses       : quick-guide-gplv3.zh-cn.html 
        licenses/po    : quick-guide-gplv3.zh-cn-en.html 

Log message:
        Automatic update by GNUnited Nations.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/quick-guide-gplv3.zh-cn.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/quick-guide-gplv3.translist?cvsroot=www&r1=1.16&r2=1.17
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/quick-guide-gplv3.zh-cn.po?cvsroot=www&r1=1.3&r2=1.4
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/quick-guide-gplv3.zh-cn-en.html?cvsroot=www&rev=1.1

Patches:
Index: po/quick-guide-gplv3.translist
===================================================================
RCS file: /web/www/www/licenses/po/quick-guide-gplv3.translist,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -b -r1.16 -r1.17
--- po/quick-guide-gplv3.translist      15 Mar 2020 18:34:44 -0000      1.16
+++ po/quick-guide-gplv3.translist      22 May 2020 05:59:02 -0000      1.17
@@ -10,6 +10,7 @@
 <span dir="ltr">[ja]&nbsp;<a lang="ja" hreflang="ja" 
href="/licenses/quick-guide-gplv3.ja.html">日本語</a> &nbsp;</span>
 <span dir="ltr">[pt-br]&nbsp;<a lang="pt-br" hreflang="pt-br" 
href="/licenses/quick-guide-gplv3.pt-br.html">português</a> &nbsp;</span>
 <span dir="ltr">[ru]&nbsp;<a lang="ru" hreflang="ru" 
href="/licenses/quick-guide-gplv3.ru.html">русский</a> &nbsp;</span>
+<span dir="ltr">[zh-cn]&nbsp;<a lang="zh-cn" hreflang="zh-cn" 
href="/licenses/quick-guide-gplv3.zh-cn.html">简体中文</a> &nbsp;</span>
 </p>
 </div>' -->
 <link rel="alternate" type="text/html" href="/licenses/quick-guide-gplv3.html" 
hreflang="x-default" />
@@ -21,4 +22,5 @@
 <link rel="alternate" type="text/html" lang="ja" hreflang="ja" 
href="/licenses/quick-guide-gplv3.ja.html" title="日本語" />
 <link rel="alternate" type="text/html" lang="pt-br" hreflang="pt-br" 
href="/licenses/quick-guide-gplv3.pt-br.html" title="português" />
 <link rel="alternate" type="text/html" lang="ru" hreflang="ru" 
href="/licenses/quick-guide-gplv3.ru.html" title="русский" />
+<link rel="alternate" type="text/html" lang="zh-cn" hreflang="zh-cn" 
href="/licenses/quick-guide-gplv3.zh-cn.html" title="简体中文" />
 <!-- end translist file -->

Index: po/quick-guide-gplv3.zh-cn.po
===================================================================
RCS file: /web/www/www/licenses/po/quick-guide-gplv3.zh-cn.po,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -b -r1.3 -r1.4
--- po/quick-guide-gplv3.zh-cn.po       22 May 2020 05:37:03 -0000      1.3
+++ po/quick-guide-gplv3.zh-cn.po       22 May 2020 05:59:02 -0000      1.4
@@ -13,7 +13,7 @@
 "Language: zh_CN\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
-"Content-Transfer-Encoding: 8bit"
+"Content-Transfer-Encoding: 8bit\n"
 
 #. type: Content of: <title>
 msgid "A Quick Guide to GPLv3 - GNU Project - Free Software Foundation"

Index: quick-guide-gplv3.zh-cn.html
===================================================================
RCS file: quick-guide-gplv3.zh-cn.html
diff -N quick-guide-gplv3.zh-cn.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ quick-guide-gplv3.zh-cn.html        22 May 2020 05:59:01 -0000      1.1
@@ -0,0 +1,234 @@
+<!--#set var="ENGLISH_PAGE" value="/licenses/quick-guide-gplv3.en.html" -->
+
+<!--#include virtual="/server/header.zh-cn.html" -->
+<!-- Parent-Version: 1.77 -->
+
+<!-- This file is automatically generated by GNUnited Nations! -->
+<title>GPLv3 快速指导 - GNU 工程 - 自由软件基金会</title>
+
+<!--#include virtual="/licenses/po/quick-guide-gplv3.translist" -->
+<!--#include virtual="/server/banner.zh-cn.html" -->
+<h2>GPLv3 快速指导</h2>
+
+<img class="imgright" src="/graphics/gplv3-127x51.png" alt="[GPLv3 æ ‡è¯†]" />
+
+<p><strong>Brett Smith</strong> 著</p>
+
+<p>[本文还有 <a href="/licenses/quick-guide-gplv3.pdf">PDF</a> 和 <a
+href="/licenses/quick-guide-gplv3.tar.gz">reStructuredText</a> æ ¼å¼ã€‚]</p>
+
+<p>经过一年半的公开咨询、数以千计的评论和四个草案，GNU 
通用公共许可证版本 3（<a class="reference external"
+href="/licenses/gpl-3.0.html">GPLv3</a>）终于在 2007 年 6 月 29
+日最后发布。虽然从第一个草案开始，该许可证就带来大量的讨论，但是对å
…¶ç»™å¼€å‘者
带来的好处并没有太多人论及。这个指导就是为了补足这块。我们将简要地回顾一下自由软件、copyleft
+和 GPL çš„ç›®æ ‡ã€‚ç„¶åŽï¼Œæˆ‘ä»¬å®¡é˜…
此版许可证的主要修改，看看它们如何推进这些目æ 
‡å¹¶ç»™å¼€å‘者带来什么好处。</p>
+<div class="section" id="the-foundations-of-the-gpl">
+<h3>GPL 的基础</h3>
+<p>软件不应限制å…
¶ç”¨æˆ·ã€‚每个用户都应该有四项基本自由：</p>
+<ul class="simple">
+<li>有自由按自己的意愿使用软件，</li>
+<li>有自由按自己的需要修改软件，</li>
+<li>有自由把软件分享给友邻，以及</li>
+<li>有自由分享自己对软件的修改。</li>
+</ul>
+<p>当一个程序为其用户提供所有这些自由时，我们称之为 <a 
class="reference external"
+href="/philosophy/free-sw.html">自由软件</a>。</p>
+<p>软件的开发者可以使用 GNU GPL 
发布自己的软件。当他们这æ 
·åšäº†ä¹‹åŽï¼Œè¯¥è½¯ä»¶å°±æ˜¯è‡ªç”±è½¯ä»¶ï¼Œå¹¶ä¸”ä¸€ç›´æ˜¯è‡ªç”±è½¯ä»¶ï¼Œæ— 
论是谁修改或发布该软件。我们称之为
+copyleft：该软件有版权，但是该版权不是象专有软件那æ 
·ç”¨æ¥é™åˆ¶ç”¨æˆ·ï¼Œæˆ‘们用它来保证所有用户的自由。</p>
+<p>我们会升级 GPL ä»¥å…æ³•å¾‹æˆ–æŠ€æœ¯çš„å‘å±•å¯¹å…¶é€ 
成逐步的削弱。最新版许可证保护用户不再受三个新到威胁的侵害：</p>
+<ul class="simple">
+<li>Tivoizationï¼šæœ‰äº›å…¬å¸åˆ¶é€ äº†è®¸å¤šä¸åŒçš„è¿è¡Œ GPL
+软件的设备，然后他们操纵这些硬件使之可以运行他们的软件，而ä½
 
的却不行。如果一个设备可以运行任何软件，那么它是通用计算机，而å
…¶æ‰€æœ‰è€…åº”è¯¥æŽ§åˆ¶è®¡ç®—æœºçš„æ‰€ä½œæ‰€ä¸ºã€‚å¦‚æžœä¸€ä¸ªè®¾å¤‡ä¸è®©ä½ 
这么做，我们就称之为
+tivoization。</li>
+<li>禁止自由软件的法律：诸如数字千禧版权法案（Digital 
Millennium Copyright Act）和 欧盟版权命令（European
+Union Copyright Directiveï¼‰ç­‰æ³•å¾‹ä½¿ç¼–å†™æˆ–åˆ†äº«ç ´è§£ 
DRM（数字限制管理；参看 <a
+href="#neutralizing-laws-that-prohibit-free-software-but-not-forbidding-drm">下文</a>）的软件非法。这些法律不应当干扰
+GPL èµ‹äºˆä½ çš„æƒåˆ©ã€‚</li>
+<li>æ­§è§†æ€§ä¸“åˆ©äº¤æ˜“ï¼šå¾®è½¯æœ€è¿‘å¼€å§‹å®£ä¼ ä»–ä»¬ä¸ä¼šå› 
为专利侵害而控告自由软件用户&mdash;&mdash;åªè¦ä½ 
是从向微软付费的供应商那里获得的软件。最终，微软试图为使用自由软件收取版税，这个干预了用户的自由。任何å
…¬å¸éƒ½ä¸åº”该这么做。</li>
+</ul>
+<p>版本 3 
ä¹Ÿåšä¸€äº›æ”¹è¿›ï¼Œä½¿ä¹‹æ›´å®¹æ˜“ç†è§£å’Œä½¿ç”¨ã€‚ä½†æ˜¯å³ä½¿åŠ 
上这些改进，GPLv3
+也不是一个å…
¨æ–°è®¸å¯è¯ï¼›å®ƒæ˜¯ä»¥å‰ç‰ˆæœ¬çš„演进。虽然文本改了很多，但是大多数只是澄æ¸
… GPLv2 的内容。考虑到这些之后，我们来审阅一下 GPLv3
+的主要改进，探讨一下它们如何为用户和开发者
改善了许可证。</p>
+</div>
+<div class="section" 
id="neutralizing-laws-that-prohibit-free-software-but-not-forbidding-drm">
+<h3>中立化禁止自由软件的法律&mdash;&mdash;但不是禁止DRM</h3>
+<p>ä½ ä¹Ÿè®¸ç†Ÿæ‚‰å’Œ DVD 等多媒体有å…
³çš„数字限制管理（DRMï¼‰ã€‚ä½ ä¹Ÿè®¸è¿˜ç†Ÿæ‚‰ä¸Žä¹‹ç›¸å…
³çš„法律，比如数字千禧版权法案和欧盟版权命令，它们使自己编写软件跳过
+DRM é™åˆ¶å˜å¾—éžæ³•ã€‚æ²¡æœ‰äººèƒ½å¤Ÿé˜»æ­¢ä½ ç¼–å†™ä»»ä½•è½¯ä»¶ï¼ŒGPLv3 
ä¿æŠ¤ä½ çš„æƒåˆ©ã€‚</p>
+<p>ä½ å¯ä»¥ä½¿ç”¨ GPL ä»£ç æ¥å®žçŽ° DRM。不过，如果有人编写了受 
GPLv3 ä¿æŠ¤çš„ä»£ç ï¼Œå…¶ç¬¬ 3 节说这个代ç 
å¹¶ä¸æž„成一个有效的技术
+&quot;保护&quot; æŽªæ–½ã€‚è¿™å°±æ„å‘³ç€å¦‚æžœä½ ç ´è§£äº† DRMï¼Œé‚£ä¹ˆä½ 
æœ‰æƒå‘å¸ƒä½ çš„è½¯ä»¶ï¼Œè€Œä¸”ä½ 
不会受到数字千禧版权法案（DMCA）或类似法律的威胁。</p>
+<p>一直以来，GNU GPL 
不限制人们用软件做什么；它只是阻止人们限制其他人。</p>
+</div>
+<div class="section" id="protecting-your-right-to-tinker">
+<h3>ä¿æŠ¤ä½ ä¿®æ”¹çš„æƒåˆ©</h3>
+<p>Tivoization 
æ˜¯å‰¥å¤ºç”¨æˆ·è‡ªç”±çš„å±é™©è¡Œä¸ºï¼šå¦‚æžœè®¡ç®—æœºä¸èƒ½è¿è¡Œä½ 
修改的软件，那么修改的权利就没有意义。GPLv3
+通过要求发布者提供安装
和运行修改版本的信息或数据来阻止
+tivoization。这可以是一些简单的指令，或者包
括一些帮助跳过硬件检查的密钥数据和信息。它依赖于硬件设计&mdash;&mdash;但æ—
 è®ºä½ éœ€è¦çš„æ˜¯ä»€ä¹ˆä¿¡æ¯ï¼Œä½ éƒ½åº”è¯¥å¾—åˆ°ã€‚</p>
+<p>这个要求是有范围限制的。发布者
è¿˜æ˜¯å¯ä»¥ä½¿ç”¨å¯†é’¥ï¼Œä»–ä»¬åªæ˜¯åœ¨ä½ éœ€è¦ä¿®æ”¹ä»–ä»¬æä¾›çš„ GPL 
软件时被要求公布一个密钥。GNU 工程本身也使用 GnuPG
+来证明它放在 FTP 站点的软件是正确的。GPLv3
+å¹¶ä¸é˜»æ­¢äººä»¬ä½¿ç”¨åŠ 
密；这个我们想都没想过。它只是要阻止人们剥夺该许可证赋予ä½
 
的权利&mdash;&mdash;不管他们是通过专利法剥夺、通过技术剥夺，还是通过å
…¶ä»–手段剥夺。</p>
+</div>
+<div class="section" id="stronger-protection-against-patent-threats">
+<h3>针对专利威胁的更强保护</h3>
+<p>从 GPLv2 发布依赖的 17 
年来，软件专利的版图已经发生了很大的变化，自由软件许可证也发展了对应的新策略。GPLv3
+ä¹Ÿåæ˜ äº†è¿™äº›æ”¹å˜ã€‚æ— 
论何时，只要有人输送了自写或修改版的 GPLv3 
软件，他们就必须为每个接收者提供他们实际
操作需要的、GPL
+赋予他们的任何专利许可证。此外，如果有专利授权者
想要通过专利诉讼阻止å…
¶ä»–用户实现他们的权利，那么她的许可证就会被中止。</p>
+<p>这个对于用户和开发者来说，就是他们能够从事 GPLv3 
çš„å·¥ä½œè€Œæ— éœ€æ‹…å¿ƒæœ‰å­¤æ³¨ä¸€æŽ·çš„å‘è¡Œè€…
想要通过专利侵权来告他们。有了这些改变，GPLv3
+给用户提供了比å…
¶ä»–自由软件许可证更多的对付专利攻击的保护。</p>
+</div>
+<div class="section" id="clarifying-license-compatibility">
+<h3>澄清许可证兼容性</h3>
+<p>å¦‚æžœä½ æƒ³æŠŠæŸä¸ªä»£ç ç»„åˆåˆ°ä¸€ä¸ª GPL 项目中，GPLv2 说该代ç 
çš„许可证不允许有任何 GPLv2 还没有包含的限制。如果是这æ 
·ï¼Œé‚£ä¹ˆæˆ‘们说该许可证兼容
+GPL。</p>
+<p>ä¸è¿‡ï¼Œæœ‰äº›è®¸å¯è¯çš„è¦æ±‚å…¶å®žå¹¶ä¸æ˜¯é™åˆ¶ï¼Œå› 
ä¸ºè¿™äº›è¦æ±‚éžå¸¸å®¹æ˜“æ»¡è¶³ã€‚ä¾‹å¦‚ï¼Œæœ‰äº›è®¸å¯è¯ä¸å…è®¸ä½ 
使用某些商æ 
‡ã€‚è¿™ä¸ªå¹¶ä¸æ˜¯ä¸€ä¸ªé¢å¤–çš„é™åˆ¶ï¼šå³ä½¿æ²¡æœ‰è¿™ä¸ªè¦æ±‚ï¼Œä½ 
ä¹Ÿæ²¡æœ‰èŽ·å¾—ä½¿ç”¨è¿™äº›å•†æ ‡çš„æŽˆæƒã€‚ä½ è¿˜æ˜¯ä¸èƒ½ä½¿ç”¨è¿™äº›å•†æ 
‡ã€‚我们说这种许可证也兼容
+GPLv2。</p>
+<p>现在，GPLv3 
明确授权每个人都可以使用带有此类要求的代ç 
ã€‚这些条款应该可以帮助澄清许可证兼容 GPL 
çš„é—®é¢˜ï¼Œä¸ºä»€ä¹ˆå…¼å®¹ï¼Œä»¥åŠä½ å¯ä»¥å¦‚ä½•å¤„ç†å…¼å®¹
+GPL çš„ä»£ç ã€‚</p>
+</div>
+<div class="section" id="new-compatible-licenses">
+<h3>新的兼容许可证</h3>
+<p>除了澄清已经兼容 GPL 的许可证，GPLv3 还新增一些å…
¼å®¹è®¸å¯è¯ã€‚Apache 许可证 2.0
+就是一个重要的例子。许多伟大的软件是基于该许可证的，而且å
…¶ç¤¾åŒºä¹Ÿå¾ˆå¼ºå¤§ã€‚我们希望 GPLv3
+的这个改变能够支持自由软件社区之间更多的合作和分享。下面的表æ
 ¼ç”¨æ¥å¸®åŠ©è®²è§£ä¸åŒè‡ªç”±è½¯ä»¶è®¸å¯è¯ä¹‹é—´çš„一些通用兼容性å…
³ç³»ã€‚</p>
+
+<!-- GNUN: localize URL /licenses/quick-guide-gplv3-compatibility.png -->
+<img alt="这是一个讲解不同自由软件许可证之间的兼容å…
³ç³»çš„è¡¨æ ¼ã€‚æ›´å¤šç»†èŠ‚ï¼Œè¯·å‚çœ‹ FSF 的许可证列表页面。" 
class="align-center" src="/licenses/quick-guide-gplv3-compatibility.png" 
style="width: 594px; height: 498px;" />
+<p>从一个许可证指向另一个许可证的箭头表示第一个许可证å
…¼å®¹ç¬¬äºŒä¸ªè®¸å¯è¯ã€‚这个对从一个许可证指向多个许可证的情
å†µä¹Ÿé€‚ç”¨ï¼›å› æ­¤ï¼Œæ¯”å¦‚ï¼ŒISC 许可证兼容
+GPLv3。如果某个 GPLv2 ç¨‹åºå…è®¸ä½ é€‰æ‹© GPL 的 
&quot;任何以后版本&quot;，那么 GPLv2 就兼容 GPLv3，使用
+GPLv2 çš„å¤§å¤šæ•°è½¯ä»¶éƒ½æ˜¯è¿™æ ·åšçš„ã€‚è¿™ä¸ªå›¾å¹¶ä¸è¯¦å°½ï¼ˆå‚çœ‹ <a 
class="reference external"
+href="/licenses/license-list.html">我们的许可证页面</a> 了解兼容 
GPLv2 和 GPLv3
+的更全面的许可证列表），但是它表达了 GPLv3 兼容 GPLv2 
的所有，并更多。</p>
+<p>GNU Affero GPL 版本 3 è¢«åŠ äº†è¿›æ¥ã€‚åˆå§‹ Affero GPL 
çš„è®¾è®¡æ˜¯ç”¨æ¥ä¿è¯ç½‘ç»œåº”ç”¨çš„ç”¨æˆ·å¯ä»¥èŽ·å¾—æºä»£ç ã€‚GNU Affero
+GPL 版本 3
+拓宽了这个目æ 
‡ï¼šå®ƒå¯ä»¥ç”¨äºŽæ‰€æœ‰ç½‘络交互软件，所以它也适用于诸如游戏服务器之类的程序。å
…¶å¢žåŠ 
的条款也更灵活，如果某人要在没有网络接口的程序里使用 
AGPL
+æºä»£ç ï¼Œé‚£ä¹ˆå¥¹åªéœ€æŒ‰ç…§ GPL 的要求提供源代ç 
ã€‚通过使这两个许可证兼容，网络交互软件的开发者
能够增强 copyleft，同时能够在成熟的 GPL
+ä»£ç åŸºç¡€ä¹‹ä¸Šè¿›è¡Œå‘å±•ã€‚</p>
+</div>
+<div class="section" id="more-ways-for-developers-to-provide-source">
+<h3>å¼€å‘è€…æœ‰æ›´å¤šæä¾›æºä»£ç çš„é€”å¾„</h3>
+<p>GPL çš„ä¸€ä¸ªåŸºæœ¬è¦æ±‚å°±æ˜¯å½“ä½ å‘ç”¨æˆ·æä¾›ç›®æ ‡ä»£ç æ—¶ï¼Œä½ 
ä¹Ÿå¿…é¡»æä¾›èŽ·å–æºä»£ç çš„æ–¹æ³•ã€‚GPLv2 æä¾›äº†å‡ ä¸ªæ–¹æ³•ï¼Œè€Œ 
GPLv3
+ç»´æŒè¿™äº›æ–¹æ³•å¹¶åšäº†æ¾„æ¸…ã€‚å®ƒè¿˜ä¸ºä½ é€šè¿‡ç½‘ç»œè¾“é€ç›®æ ‡ä»£ç 
æ—¶æä¾›äº†ç»™å‡ºæºä»£ç çš„æ–°æ–¹æ³•ã€‚ä¾‹å¦‚ï¼Œå½“ä½ 在网络或 FTP
+æœåŠ¡å™¨ä¸Šæ‰˜ç®¡ç›®æ ‡ä»£ç æ—¶ï¼Œä½ å¯ä»¥ç®€è¦åœ°å‘è®¿é—®è€…
提供如何从第三方服务器获取源代ç 
åœ°æŒ‡ä»¤ã€‚感谢这个新的选项，它让众多只对代ç 
åšå‡ºå°‘许改动的微小发布者更容易达成提供源代ç 
çš„要求。</p>
+<p>新许可证还让大家通过 BitTorrent è¾“é€ç›®æ ‡ä»£ç 
æ›´å®¹æ˜“。首先，仅在 torrent 
下载或播种的人被排除在许可证的输送软件要求之外。å…
¶æ¬¡ï¼Œå‘èµ·
+torrent 的人可以通过告知其他 torrent ç”¨æˆ·æºä»£ç åœ¨å“ªä¸ªå…¬å…
±ç½‘ç»œæœåŠ¡å™¨ä¸Šçš„æ–¹å¼æä¾›æºä»£ç ã€‚</p>
+<p>新选项既保持了 GPL æä¾›æºä»£ç çš„ç¤¾åŒºæ 
‡å‡†ï¼Œä¹Ÿæ²¡æœ‰è®©ç”¨æˆ·èŽ·å¾—æºä»£ç å˜å¾—æ›´å›°éš¾ã€‚</p>
+</div>
+<div class="section" 
id="less-source-to-distribute-new-system-libraries-exception">
+<h3>å‘å¸ƒæ›´å°‘çš„æºä»£ç ï¼šæ–°çš„ç³»ç»Ÿåº“ä¾‹å¤–</h3>
+<p>这两个版本的 GPL
+éƒ½è¦æ±‚ä½ æä¾›æž„å»ºè½¯ä»¶æ‰€å¿…é¡»çš„å…¨éƒ¨æºä»£ç ï¼ŒåŒ…
æ‹¬æ”¯æŒåº“ã€ç¼–è¯‘è„šæœ¬ç­‰ç­‰ã€‚å®ƒä»¬ä¹Ÿéƒ½å¯¹ç³»ç»Ÿåº“åšäº†åŒºåˆ†ï¼šä½ 
æ— éœ€æä¾›æ“ä½œç³»ç»Ÿç›¸å…³çš„æŸäº›æ ¸å¿ƒéƒ¨ä»¶çš„æºä»£ç ï¼Œæ¯”å¦‚ C 
库。</p>
+<p>GPLv3 对系统库的定义做了调整，使之包
含了操作系统不一定直接带有、但是å…
¨ä½“软件用户都合理期待的软件。比如，它现在也包含了象 
Python 和
+Ruby ç­‰é€šç”¨ç¼–ç¨‹è¯­è¨€çš„æ ‡å‡†åº“ã€‚</p>
+<p>æ–°çš„å®šä¹‰è¿˜æ¾„æ¸…äº†ä½ å¯ä»¥ç»„åˆ GPL 软件与不兼容 GPL 
的系统库，比如 OpenSolaris 的 C
+库，并合在一起发布。这大大方便了想为用户提供此类组合的自由软件发布è€
…。</p>
+</div>
+<div class="section" id="a-global-license">
+<h3>成为一个全球许可证</h3>
+<p>GPLv2 很多次使用 &quot;发布&quot;
+一词&mdash;&mdash;å½“ä½ å’Œä»–äººåˆ†äº«è½¯ä»¶æ—¶ï¼Œä½ 
æ˜¯åœ¨å‘å¸ƒã€‚ä½†è¯¥è®¸å¯è¯æ²¡æœ‰è¯´æ˜Žå‘å¸ƒæ˜¯ä»€ä¹ˆï¼Œå› 
为这个词是从美国版权法里借用过来的。我们原本想法官会到美国版权法里查找这个定义。后来我们发现å
…¶ä»–å›½å®¶çš„æ³•å¾‹ä¹Ÿä½¿ç”¨è¿™ä¸ªè¯ï¼Œä½†æ˜¯æ„ä¹‰ä¸åŒã€‚å› 
此，在这个国家的法官对
+GPLv2 的分析可能就会和美国法官不同。</p>
+<p>GPLv3 
使用了新的术语，&quot;输送&quot;，并提供了定义。&quot;输送&quot;
 和我们使用的 &quot;发布,&quot;
+æ„æ€ä¸€æ ·ï¼Œä½†æ˜¯å®ƒåœ¨è®¸å¯è¯é‡Œæœ‰ç›´æŽ¥çš„è§£é‡Šï¼Œè¿™æ 
·ä»»ä½•åœ°æ–¹çš„人都容易理解我们的意思。整个许可证还有一些小的改动，它们也有助于在å
…¨çƒèŒƒå›´å†…使用该许可证。</p>
+</div>
+<div class="section" 
id="when-the-rules-are-broken-a-smooth-path-to-compliance">
+<h3>当发生违规时：走向合规的坦途</h3>
+<p>在
+GPLv2ï¼Œå¦‚æžœä½ è¿åä»»ä½•è®¸å¯è¯çš„è¦æ±‚ï¼Œä½ å°†è‡ªåŠ¨æ°¸ä¹…
失去许可证权利。恢复权利的唯一办法是请求版权持有者
。虽然对违规的有力防御有å…
¶ä»·å€¼ï¼Œä½†æ˜¯è¿™ä¸ªæ”¿ç­–在有人不经意犯错时就可能导致很多麻烦。请求所有版权持有è€
…正式恢复许可证权利会是代价昂贵的负担：一个典型的
+GNU/Linux 发行版会是数千人工作的集合。</p>
+<p>GPLv3 ä¸ºæ‚”è¿‡è‡ªæ–°æä¾›äº†ç¼“æœŸæ‰§è¡Œï¼šå¦‚æžœä½ 
è¿åäº†è®¸å¯è¯ï¼Œä¸€æ—¦ä½ åœæ­¢è¿åï¼Œä½ 
就立即重新获得许可证权利，除非有版权所有者在 60
+å¤©å†…å’Œä½ è”ç³»ã€‚åœ¨ä½ æ”¶åˆ°é€šçŸ¥ä¹‹åŽï¼Œå¦‚æžœä½ æ˜¯åˆçŠ¯å¹¶ä¸”åœ¨ 30
+å¤©å†…ä¿®æ­£äº†é”™è¯¯ï¼Œé‚£ä¹ˆä½ å¯ä»¥æ¢å¤æƒåˆ©ã€‚å¦åˆ™ï¼Œä½ è¦å’Œä¸Žä½ 
联系的版权所有者具体问题å…
·ä½“解决，完成之后再恢复权利。</p>
+<p>维护 GPL 合规一直是 FSF
+合规实验室和世界上å…
¶ä»–许可证执法组织的首要任务。这些改变保证了维护合规仍然是执法è€
…的首要任务，并且给予违反者愿意悔过自新的理由。</p>
+</div>
+<div class="section" id="the-latest-and-greatest">
+<h3>压轴好戏</h3>
+<p>è¿™äº›æ”¹å˜å¯èƒ½å¯¹ä½ ä¸å¦‚å¯¹å…
¶ä»–人那么重要。不要紧。项目五花å…
«é—¨ï¼Œæ¯ä¸ªéƒ½éœ€è¦è®¸å¯è¯é‡Œé¢çš„不同营å…
»ã€‚ä½†æ˜¯è¿™é‡Œçš„æ”¹è¿›å¤§æ¦‚çŽ‡ä¼šå¸®åˆ°ä½ å’Œä½ çš„é¡¹ç›®ã€‚</p>
+<p>整体来看，所有这些升级代表：我们做出了一个更好的
+copyleft。它对用户自由的保护更多，但是也会促进更多的自由软件社区合作。升级许可证只是部分工作：为了让人们受益
+GPLv3ï¼Œå¼€å‘è€…åº”è¯¥åœ¨é¡¹ç›®ä¸­ä½¿ç”¨å®ƒã€‚ä½¿ç”¨æ­¤æ–°è®¸å¯è¯å‘å¸ƒä½ 
的软件，所有收到软件的人&mdash;&mdash;用户、其他开发者
、发布者、甚至是律师&mdash;&mdash;éƒ½ä¼šå—ç›Šã€‚æˆ‘ä»¬æœŸå¾…ä½ 
的下一个发布使用的是
+GPLv3。</p>
+<p>å¦‚æžœä½ æƒ³è¦æŠŠä½ çš„é¡¹ç›®å‡çº§åˆ° GPLv3，FSF 合规实验室很高å…
´å¸®åŠ©ä½ 。在 <a class="reference external"
+href="http://www.fsf.org/licensing/";>我们的网站</a>ï¼Œä½ å¯ä»¥æ‰¾åˆ° <a 
class="reference
+external"
+href="http://www.fsf.org/licensing/licenses/gpl-howto.html";>使用此许可证的基本指导</a>，以及人们提出的
+<a class="reference external"
+href="http://www.fsf.org/licensing/licenses/gpl-faq.html";>常见问题的解答</a>。如果ä½
 的情况比较复杂，请
+<a class="reference external"
+href="mailto:licensing&#64;fsf.org";>联系我们</a>ï¼Œæˆ‘ä»¬ä¼šåŠªåŠ›å¸®åŠ©ä½ 
进行升级。在一起，我们保护所有用户的自由。</p>
+</div>
+
+<div class="translators-notes">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.-->
+ </div>
+</div>
+
+<!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.zh-cn.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<p>请将有关自由软件基金会(FSF) &amp; 
GNU的一般性问题发送到<a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>。也可以通过<a
+href="/contact/">其他联系方法</a>联系自由软件基金会(FSF)。有å…
³å¤±æ•ˆé“¾æŽ¥æˆ–其他错误和建议，请发送邮件到<a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>。</p>
+
+<p>
+<!-- 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:address@hidden";>
+
+        &lt;address@hidden&gt;</a>.</p>
+
+        <p>For information on coordinating and submitting translations of
+        our web pages, see <a
+        href="/server/standards/README.translations.html">Translations
+        README</a>. -->
+我们尽最大努力来提供精准和高质量的翻译，但难å…
ä¼šå­˜åœ¨é”™è¯¯å’Œä¸è¶³ã€‚如果您在这方面有评论或一般性的建议，请发送至
 <a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>。</p><p>å…
³äºŽè¿›è¡Œåè°ƒä¸Žæäº¤ç¿»è¯‘的更多信息参见
+<a href="/server/standards/README.translators.html">《译者
指南》</a>。</p>
+</div>
+
+<!-- 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 3.0 US.  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 &copy; 2007, 2008, 2010, 2013, 2014 Free Software Foundation, 
Inc.</p>
+
+<p>本页面使用 <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/";>Creative Commons
+Attribution-NoDerivs 3.0 United States License</a> 授权。</p>
+
+<!--#include virtual="/server/bottom-notes.zh-cn.html" -->
+<div class="translators-credits">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.-->
+<b>翻译团队</b>：<a rel="team"
+href="https://savannah.gnu.org/projects/www-zh-cn/";>&lt;CTT&gt;</a>，2020。</div>
+
+<p class="unprintable"><!-- timestamp start -->
+最后更新：
+
+$Date: 2020/05/22 05:59:01 $
+
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>

Index: po/quick-guide-gplv3.zh-cn-en.html
===================================================================
RCS file: po/quick-guide-gplv3.zh-cn-en.html
diff -N po/quick-guide-gplv3.zh-cn-en.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ po/quick-guide-gplv3.zh-cn-en.html  22 May 2020 05:59:02 -0000      1.1
@@ -0,0 +1,347 @@
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.77 -->
+<title>A Quick Guide to GPLv3
+- GNU Project - Free Software Foundation</title>
+<!--#include virtual="/licenses/po/quick-guide-gplv3.translist" -->
+<!--#include virtual="/server/banner.html" -->
+<h2>A Quick Guide to GPLv3</h2>
+
+<img class="imgright" src="/graphics/gplv3-127x51.png" alt=" [GPLv3 Logo] " />
+
+<p>by <strong>Brett Smith</strong></p>
+
+<p>[This article is also available in <a
+href="/licenses/quick-guide-gplv3.pdf">PDF</a> and <a
+href="/licenses/quick-guide-gplv3.tar.gz">reStructuredText</a>
+formats.]</p>
+
+<p>After a year and a half of public consultation, thousands of comments, and
+four drafts, version 3 of the GNU General Public License (<a class="reference 
external" href="/licenses/gpl-3.0.html">GPLv3</a>) was
+finally published on June&nbsp;29, 2007.  While there's been a lot of 
discussion about
+the license since the first draft appeared, not many people have talked
+about the benefits that it provides developers.  We've published this guide
+to fill that gap.  We'll start with a brief refresher on free software,
+copyleft, and the goals of the GPL.  We'll then review the major changes in
+the license to see how they advance those goals and benefit developers.</p>
+<div class="section" id="the-foundations-of-the-gpl">
+<h3>The Foundations of the GPL</h3>
+<p>Nobody should be restricted by the software they use.  There are four
+freedoms that every user should have:</p>
+<ul class="simple">
+<li>the freedom to use the software for any purpose,</li>
+<li>the freedom to change the software to suit your needs,</li>
+<li>the freedom to share the software with your friends and neighbors, and</li>
+<li>the freedom to share the changes you make.</li>
+</ul>
+<p>When a program offers users all of these freedoms, we call it <a 
class="reference external" href="/philosophy/free-sw.html">free
+software</a>.</p>
+<p>Developers who write software can release it under the terms of the GNU
+GPL.  When they do, it will be free software and stay free software, no
+matter who changes or distributes the program.  We call this copyleft: the
+software is copyrighted, but instead of using those rights to restrict
+users like proprietary software does, we use them to ensure that
+every user has freedom.</p>
+<p>We update the GPL to protect its copyleft from being undermined by legal or
+technological developments.  The most recent version protects users from
+three recent threats:</p>
+<ul class="simple">
+<li>Tivoization: Some companies have created various different kinds of
+devices that run GPLed software, and then rigged the hardware so that
+they can change the software that's running, but you cannot.  If a device
+can run arbitrary software, it's a general-purpose computer, and its
+owner should control what it does.  When a device thwarts you from doing
+that, we call that tivoization.</li>
+<li>Laws prohibiting free software: Legislation like the Digital Millennium
+Copyright Act and the European Union Copyright Directive make it a crime
+to write or share software that can break DRM (Digital Restrictions
+Management; see 
+<a 
href="#neutralizing-laws-that-prohibit-free-software-but-not-forbidding-drm">below</a>).
  These laws should not
+interfere with the rights the GPL grants you.</li>
+<li>Discriminatory patent deals: Microsoft has recently started
+telling people that they will not sue free software users for patent
+infringement&mdash;as long as you get the software from a vendor
+that's paying Microsoft for the privilege.  Ultimately, Microsoft is
+trying to collect royalties for the use of free software, which
+interferes with users' freedom.  No company should be able to do
+this.</li>
+</ul>
+<p>Version 3 also has a number of improvements to make the license easier for
+everyone to use and understand.  But even with all these changes, GPLv3
+isn't a radical new license; instead it's an evolution of the previous
+version.  Though a lot of text has changed, much of it simply clarifies
+what GPLv2 said.  With that in mind, let's review the major changes in
+GPLv3, and talk about how they improve the license for users and
+developers.</p>
+</div>
+<div class="section" 
id="neutralizing-laws-that-prohibit-free-software-but-not-forbidding-drm">
+<h3>Neutralizing Laws That Prohibit Free Software &mdash; But Not
+Forbidding DRM</h3>
+<p>You're probably familiar with the Digital Restrictions Management
+(DRM) on
+DVDs and other media.  You're probably also familiar with the laws that
+make it illegal to write your own tools to bypass those restrictions, like
+the Digital Millennium Copyright Act and the European Union Copyright
+Directive.  Nobody should be able to stop you from writing any code that
+you want, and GPLv3 protects this right for you.</p>
+<p>It's always possible to use GPLed code to write software that implements
+DRM.  However, if someone does that with code protected by GPLv3, section 3
+says that the system will not count as an effective technological
+&quot;protection&quot; measure.  This means that if you break the DRM, you'll 
be free
+to distribute your own software that does that, and you won't be threatened
+by the DMCA or similar laws.</p>
+<p>As usual, the GNU GPL does not restrict what people do in software; it just
+stops them from restricting others.</p>
+</div>
+<div class="section" id="protecting-your-right-to-tinker">
+<h3>Protecting Your Right to Tinker</h3>
+<p>Tivoization is a dangerous attempt to curtail users' freedom: the
+right to modify your software will become meaningless if none of your
+computers let you do it.  GPLv3 stops tivoization by requiring the
+distributor to provide you with whatever information or data is
+necessary to install modified software on the device.  This may be as
+simple as a set of instructions, or it may include special data such
+as cryptographic keys or information about how to bypass an integrity
+check in the hardware.  It will depend on how the hardware was
+designed&mdash;but no matter what information you need, you must be
+able to get it.</p>
+<p>This requirement is limited in scope.  Distributors are still allowed to
+use cryptographic keys for any purpose, and they'll only be required to
+disclose a key if you need it to modify GPLed software on the device they
+gave you.  The GNU Project itself uses GnuPG to prove the integrity of all
+the software on its FTP site, and measures like that are beneficial to
+users.  GPLv3 does not stop people from using cryptography; we wouldn't
+want it to.  It only stops people from taking away the rights that the
+license provides you&mdash;whether through patent law, technology, or any
+other means.</p>
+</div>
+<div class="section" id="stronger-protection-against-patent-threats">
+<h3>Stronger Protection Against Patent Threats</h3>
+<p>In the 17 years since GPLv2 was published, the software patent landscape
+has changed considerably, and free software licenses have developed new
+strategies to address them.  GPLv3 reflects these changes too.  Whenever
+someone conveys software covered by GPLv3 that they've written or modified,
+they must provide every recipient with any patent licenses necessary to
+exercise the rights that the GPL gives them.  In addition to that, if any
+licensee tries to use a patent suit to stop another user from exercising
+those rights, their license will be terminated.</p>
+<p>What this means for users and developers is that they'll be able to work
+with GPLv3-covered software without worrying that a desperate contributor
+will try to sue them for patent infringement later.  With these changes,
+GPLv3 affords its users more defenses against patent aggression than any
+other free software license.</p>
+</div>
+<div class="section" id="clarifying-license-compatibility">
+<h3>Clarifying License Compatibility</h3>
+<p>If you found some code and wanted to incorporate it into a GPLed project,
+GPLv2 said that the license on the other code was not allowed to have any
+restrictions that were not already in GPLv2.  As long as that was the case,
+we said the license was GPL-compatible.</p>
+<p>However, some licenses had requirements that weren't really restrictive,
+because they were so easy to comply with.  For example, some licenses say
+that they don't give you permission to use certain trademarks.  That's not
+really an additional restriction: if that clause wasn't there, you still
+wouldn't have permission to use the trademark.  We always said those
+licenses were compatible with GPLv2, too.</p>
+<p>Now, GPLv3 explicitly gives everyone permission to use code that has
+requirements like this.  These new terms should help clear up
+misunderstandings about which licenses are GPL-compatible, why that is, and
+what you can do with GPL-compatible code.</p>
+</div>
+<div class="section" id="new-compatible-licenses">
+<h3>New Compatible Licenses</h3>
+<p>In addition to clarifying the rules about licenses that are already
+GPL-compatible, GPLv3 is also newly compatible with a few other licenses.
+The Apache License 2.0 is a prime example.  Lots of great free software is
+available under this license, with strong communities surrounding it.  We
+hope that this change in GPLv3 will foster more cooperation and sharing
+within the free software community.  The chart below helps illustrate some
+common compatibility relationships between different free software
+licenses:</p>
+<!-- GNUN: localize URL /licenses/quick-guide-gplv3-compatibility.png -->
+<img alt="A chart illustrating compatibility relationships between different 
free software licenses.  For details, see the FSF's license list page." 
class="align-center" src="/licenses/quick-guide-gplv3-compatibility.png" 
style="width: 594px; height: 498px;" />
+<p>Arrows pointing from one license to another indicate that the first license
+is compatible with the second.  This is true even if you follow multiple
+arrows to get from one license to the other; so, for example, the ISC
+license is compatible with GPLv3.  GPLv2 is compatible with GPLv3 if the
+program allows you to choose &quot;any later version&quot; of the GPL, which 
is the
+case for most software released under this license.  This diagram is not
+comprehensive (see <a class="reference external" 
href="/licenses/license-list.html">our licenses page</a> for a more complete 
list of licenses
+compatible with GPLv2 and GPLv3), but plainly illustrates that GPLv3
+is compatible with just about everything GPLv2 is, and then some.</p>
+<p>The GNU Affero GPL version 3 has also been brought into the fold.  The
+original Affero GPL was designed to ensure that all users of a web
+application would be able to receive its source.  The GNU Affero GPL
+version 3 broadens this goal: it is applicable to all network-interactive
+software, so it will also work well for programs like game servers.  The
+additional provision is also more flexible, so that if someone uses AGPLed
+source in an application without a network interface, they'll only have to
+provide source in the same sort of way the GPL has always required.
+By making these two licenses compatible, developers of network-interactive
+software will be able to strengthen their copyleft while still building on
+top of the mature body of GPLed code available to them.</p>
+</div>
+<div class="section" id="more-ways-for-developers-to-provide-source">
+<h3>More Ways for Developers to Provide Source</h3>
+<p>One of the fundamental requirements of the GPL is that when you distribute
+object code to users, you must also provide them with a way to get the
+source.  GPLv2 gave you a few ways to do this, and GPLv3 keeps those intact
+with some clarification.  It also offers you new ways to provide source
+when you convey object code over a network.  For instance, when you host
+object code on a web or FTP server, you can simply provide instructions
+that tell visitors how to get the source from a third-party server.  Thanks
+to this new option, fulfilling this requirement should be easier for many
+small distributors who only make a few changes to large bodies of source.</p>
+<p>The new license also makes it much easier to convey object code via
+BitTorrent.  First, people who are merely downloading or seeding the
+torrent are exempt from the license's requirements for conveying the
+software.  Then, whoever starts the torrent can provide source by simply
+telling other torrent users where it is available on a public network
+server.</p>
+<p>These new options help keep the GPL in line with community standards for
+offering source, without making it harder for users to get.</p>
+</div>
+<div class="section" 
id="less-source-to-distribute-new-system-libraries-exception">
+<h3>Less Source to Distribute: New System Libraries Exception</h3>
+<p>Both versions of the GPL require you to provide all the source necessary to
+build the software, including supporting libraries, compilation scripts,
+and so on.  They also draw the line at System Libraries: you're not
+required to provide the source for certain core components of the operating
+system, such as the C library.</p>
+<p>GPLv3 has adjusted the definition of System Library to include software
+that may not come directly with the operating system, but that all users of
+the software can reasonably be expected to have.  For example, it now also
+includes the standard libraries of common programming languages such as
+Python and Ruby.</p>
+<p>The new definition also makes it clear that you can combine GPLed software
+with GPL-incompatible System Libraries, such as OpenSolaris' C library, and
+distribute them both together.  These changes will make life easier for
+free software distributors who want to provide these combinations to their
+users.</p>
+</div>
+<div class="section" id="a-global-license">
+<h3>A Global License</h3>
+<p>GPLv2 talks about &quot;distribution&quot; a lot&mdash;when you
+share the program with someone else, you're distributing it.  The
+license never says what distribution is, because the term was borrowed
+from United States copyright law.  We expected that judges would look
+there for the definition.  However, we later found out that copyright
+laws in other countries use the same word, but give it different
+meanings.  Because of this, a judge in such a country might analyze
+GPLv2 differently than a judge in the United States.</p>
+<p>GPLv3 uses a new term, &quot;convey,&quot; and provides a definition for 
that term.
+&quot;Convey&quot; has the same meaning we intended for 
&quot;distribute,&quot; but now that
+this is explained directly in the license, it should be easy for people
+everywhere to understand what we meant.  There are other minor changes
+throughout the license that will also help ensure it is applied
+consistently worldwide.</p>
+</div>
+<div class="section" 
id="when-the-rules-are-broken-a-smooth-path-to-compliance">
+<h3>When the Rules Are Broken: A Smooth Path to Compliance</h3>
+<p>Under GPLv2, if you violated the license in any way, your rights were
+automatically and permanently lost.  The only way to get them back was to
+petition the copyright holder.  While a strong defense against violations
+is valuable, this policy could cause a lot of headache when someone
+accidentally ran afoul of the rules.  Asking all the copyright holders for
+a formal restoration of the license could be burdensome and costly: a
+typical GNU/Linux distribution draws upon the work of thousands.</p>
+<p>GPLv3 offers a reprieve for good behavior: if you violate the license,
+you'll get your rights back once you stop the violation, unless a copyright
+holder contacts you within 60 days.  After you receive such a notice, you
+can have your rights fully restored if you're a first-time violator and
+correct the violation within 30 days.  Otherwise, you can work out the
+issue on a case-by-case basis with the copyright holders who contacted you,
+and your rights will be restored afterward.</p>
+<p>Compliance with the GPL has always been the top priority of the FSF
+Compliance Lab and other groups enforcing the license worldwide.  These
+changes ensure that compliance remains the top priority for enforcers, and
+gives violators incentive to comply.</p>
+</div>
+<div class="section" id="the-latest-and-greatest">
+<h3>The Latest and Greatest</h3>
+<p>Some of these changes probably seem less important to you than others.
+That's okay.  Every project is different, and needs different things from
+its license.  But odds are that a number of these improvements will help
+you and your work.</p>
+<p>And taken as a whole, all these upgrades represent something more:
+we made a better copyleft.  It does more to protect users' freedom,
+but it also enables more cooperation in the free software community.
+But updating the license is only part of the job: in order for people
+to get the benefits it offers, developers need to use GPLv3 for their
+projects, too.  By releasing your own software under the new license,
+everyone who deals with it&mdash;users, other developers,
+distributors, even lawyers&mdash;will benefit.  We hope you'll use
+GPLv3 for your next release.</p>
+<p>If you'd like to learn more about upgrading your project to GPLv3, the FSF
+Compliance Lab would be happy to assist you.  On <a class="reference external" 
href="http://www.fsf.org/licensing/";>our web site</a>, you can
+find <a class="reference external" 
href="http://www.fsf.org/licensing/licenses/gpl-howto.html";>basic instructions 
for using the license</a>, and an <a class="reference external" 
href="http://www.fsf.org/licensing/licenses/gpl-faq.html";>FAQ addressing
+common concerns</a> that people have about it.  If your situation is more
+complicated than that, please <a class="reference external" 
href="mailto:licensing&#64;fsf.org";>contact us</a> and we'll do what we can to
+help you with your transition.  Together, we can help protect freedom for
+all users.</p>
+</div>
+
+</div><!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<p>Please send general FSF &amp; GNU inquiries to
+<a href="mailto:address@hidden";>&lt;address@hidden&gt;</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:address@hidden";>&lt;address@hidden&gt;</a>.</p>
+
+<p><!-- 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:address@hidden";>
+        &lt;address@hidden&gt;</a>.</p>
+
+        <p>For information on coordinating and submitting 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
+of this article.</p>
+</div>
+
+<!-- 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 3.0 US.  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 &copy; 2007, 2008, 2010, 2013, 2014
+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>
+
+<!--#include virtual="/server/bottom-notes.html" -->
+
+<p class="unprintable">Updated:
+<!-- timestamp start -->
+$Date: 2020/05/22 05:59:02 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>