www/licenses po/rms-why-gplv3.translist po/rms-...

[GNUN]

CVSROOT:        /web/www
Module name:    www
Changes by:     GNUN <gnun>     20/05/26 04:32:08

Modified files:
        licenses/po    : rms-why-gplv3.translist rms-why-gplv3.zh-cn.po 
Added files:
        licenses       : rms-why-gplv3.zh-cn.html 
        licenses/po    : rms-why-gplv3.zh-cn-en.html 

Log message:
        Automatic update by GNUnited Nations.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/rms-why-gplv3.zh-cn.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/rms-why-gplv3.translist?cvsroot=www&r1=1.15&r2=1.16
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/rms-why-gplv3.zh-cn.po?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/rms-why-gplv3.zh-cn-en.html?cvsroot=www&rev=1.1

Patches:
Index: po/rms-why-gplv3.translist
===================================================================
RCS file: /web/www/www/licenses/po/rms-why-gplv3.translist,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -b -r1.15 -r1.16
--- po/rms-why-gplv3.translist  17 May 2020 09:29:01 -0000      1.15
+++ po/rms-why-gplv3.translist  26 May 2020 08:32:08 -0000      1.16
@@ -11,6 +11,7 @@
 <span dir="ltr">[pt-br]&nbsp;<a lang="pt-br" hreflang="pt-br" 
href="/licenses/rms-why-gplv3.pt-br.html">português</a> &nbsp;</span>
 <span dir="ltr">[ru]&nbsp;<a lang="ru" hreflang="ru" 
href="/licenses/rms-why-gplv3.ru.html">русский</a> &nbsp;</span>
 <span dir="ltr">[tr]&nbsp;<a lang="tr" hreflang="tr" 
href="/licenses/rms-why-gplv3.tr.html">Türkçe</a> &nbsp;</span>
+<span dir="ltr">[zh-cn]&nbsp;<a lang="zh-cn" hreflang="zh-cn" 
href="/licenses/rms-why-gplv3.zh-cn.html">简体中文</a> &nbsp;</span>
 </p>
 </div>' -->
 <link rel="alternate" type="text/html" href="/licenses/rms-why-gplv3.html" 
hreflang="x-default" />
@@ -23,4 +24,5 @@
 <link rel="alternate" type="text/html" lang="pt-br" hreflang="pt-br" 
href="/licenses/rms-why-gplv3.pt-br.html" title="português" />
 <link rel="alternate" type="text/html" lang="ru" hreflang="ru" 
href="/licenses/rms-why-gplv3.ru.html" title="русский" />
 <link rel="alternate" type="text/html" lang="tr" hreflang="tr" 
href="/licenses/rms-why-gplv3.tr.html" title="Türkçe" />
+<link rel="alternate" type="text/html" lang="zh-cn" hreflang="zh-cn" 
href="/licenses/rms-why-gplv3.zh-cn.html" title="简体中文" />
 <!-- end translist file -->

Index: po/rms-why-gplv3.zh-cn.po
===================================================================
RCS file: /web/www/www/licenses/po/rms-why-gplv3.zh-cn.po,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- po/rms-why-gplv3.zh-cn.po   26 May 2020 07:59:23 -0000      1.1
+++ po/rms-why-gplv3.zh-cn.po   26 May 2020 08:32:08 -0000      1.2
@@ -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 "Why Upgrade to GPLv3 - GNU Project - Free Software Foundation"

Index: rms-why-gplv3.zh-cn.html
===================================================================
RCS file: rms-why-gplv3.zh-cn.html
diff -N rms-why-gplv3.zh-cn.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ rms-why-gplv3.zh-cn.html    26 May 2020 08:32:08 -0000      1.1
@@ -0,0 +1,168 @@
+<!--#set var="ENGLISH_PAGE" value="/licenses/rms-why-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/rms-why-gplv3.translist" -->
+<!--#include virtual="/server/banner.zh-cn.html" -->
+<h2>为什么要升级到 GPLv3</h2>
+
+<p><strong>Richard Stallman</strong> 著</p>
+
+<p><a href="/licenses/gpl.html">GNU 通用公共许可证第三版</a>（GNU 
GPL）发布了，它使自由软件包可以从 GPL
+版本 2 升级到版本 
3。本文解释为什么这次许可证升级是重要的。</p>
+
+<p id="choice">
+首先，重点要说明的是升级是一个选择。GPL 版本 2 
仍然是一个有效的许可证，如果有的程序还使用 GPLv2 
而另外一些程序升级到 GPLv3
+å¹¶ä¸ä¼šé€ æˆç¾éš¾ã€‚è™½ç„¶è¿™ä¸¤ä¸ªè®¸å¯è¯ä¸å…¼å®¹ï¼Œä½†è¿™ä¸æ˜¯æ 
¹æœ¬æ€§é—®é¢˜ã€‚</p>
+
+<p id="incompatibility">
+当我们说 GPLv2 和 GPLv3 不å…
¼å®¹ï¼Œæˆ‘们的意思是没有合法的手段把 GPLv2 ä»£ç å’Œ GPLv3 代ç 
åˆå¹¶æˆä¸€ä¸ªç¨‹åºã€‚å› 为 GPLv2 和
+GPLv3 都是 copyleft
+许可证：它们都表达了，&ldquo;å¦‚æžœä½ åœ¨è¾ƒå¤§çš„ç¨‹åºé‡ŒåŒ…
å«äº†æœ¬è®¸å¯è¯çš„ä»£ç ï¼Œé‚£ä¹ˆè¿™ä¸ªè¾ƒå¤§çš„ç¨‹åºå¿…
须也使用本许可证。&rdquo;没有办法使它们å…
¼å®¹ã€‚虽然我们可以在
+GPLv3 é‡ŒåŠ ä¸€æ¡å…¼å®¹ GPLv2 çš„æ¡æ¬¾ï¼Œä½†æ˜¯ä¹Ÿä¸èƒ½è§£å†³é—®é¢˜ï¼Œå› 
为 GPLv2 里也需要类似的条款。</p>
+
+<p>æ‰€å¹¸çš„æ˜¯ï¼Œè®¸å¯è¯çš„å…¼å®¹æ€§åªåœ¨ä½ 
想链接、混合或合并两个不同程序为一个程序时才有影响。在一个操作系统中同时有
 GPLv3 和 GPLv2
+的程序是没有问题的。比如，TeX 许可证和 Apache 
许可证都不兼容 GPLv2，但是这个并不影响我们在同一个 
Linux、Bash 和 GCC
+下运行 TeX 和 Apacheã€‚å› ä¸ºå®ƒä»¬æ˜¯å•ç‹¬çš„ç¨‹åºã€‚åŒæ ·ï¼ŒBash 和 
GCC 升级到 GPLv3，而 Linux 保留在 GPLv2，也没有冲突。</p>
+
+<p>一个程序保留在 GPLv2 ä¸ä¼šåˆ¶é€ éº»çƒ¦ã€‚å‡çº§çš„åŽŸå› åœ¨äºŽ 
GPLv3 要解决的已知问题。</p>
+
+<p id="tivoization">
+GPLv3 阻止的一个主要危险是 tivoization。Tivoization 是指有些 
&ldquo;设备&rdquo;（其中带有计算机）包含
+GPL è½¯ä»¶ï¼Œä½†æ˜¯ä½ æ— æ³•æœ‰æ•ˆæ›´æ”¹ï¼Œå› 
为该设备检测到软件修改后会关机。Tivoization
+的动机通常是供应商知道å…
¶ä¸­ä¸€äº›è½¯ä»¶åŠŸèƒ½äººä»¬æƒ³è¦ä¿®æ”¹ï¼Œè€Œä»–们的目的就是不让人修改。这些供应商利用了自由软件提供的自由，但是却不想给别人同æ
 ·çš„自由。</p>
+
+<p>有人会争辩说自由市场的竞争会使设备上较差的功能降到很低的水平。竞争本身也许会避å
…è¯¸å¦‚，&ldquo;每周二下午一点到五点必须关机&rdquo;
+ä¹‹ç±»éšæ„çš„ã€æ— 
厘头的差劲功能，但即便如此，由别人来主导也不是自由。自由意味着
 <em>ä½ </em>
+æ¥æŽ§åˆ¶ä½ çš„è½¯ä»¶åšä»€ä¹ˆï¼Œè€Œä¸ä»…ä»…æ˜¯ä½ èƒ½å¤Ÿç¥ˆæ±‚æˆ–è€…
èƒè¿«åˆ«äººä¸ºä½ åšå†³å®šã€‚</p>
+
+<p id="drm">
+在数字限制管理（DRM）&mdash;&mdash;è¿™æ˜¯é™åˆ¶ä½ 
使用自己电脑上的数据的恶劣功能&mdash;&mdash;等严é…
·çš„é¢†åŸŸï¼Œç«žäº‰æ²¡æœ‰ç”¨ï¼Œå› 为相å…
³çš„竞争被禁止了。在诸如数字千禧版权法案之类的法律中，在美国和许多å
…¶ä»–å›½å®¶ï¼Œå¦‚æžœä½ 没有按照“DVD
+阴谋”的官方规则（网站 <a
+href="http://www.dvdcca.org/";>http://www.dvdcca.org/</a>，但是规则看来并没有放上去）发布限制用户的
+DVD æ’­æ”¾å™¨ï¼Œé‚£ä¹ˆä½ æ˜¯éžæ³•çš„ã€‚å…¬ä¼—æ— æ³•é€šè¿‡è´­ä¹°éž DRM 
的播放器来拒绝
+DRMï¼Œå› ä¸ºæ²¡æœ‰è¿™æ ·çš„æ’­æ”¾å™¨ã€‚æ— è®ºæœ‰å¤šå°‘ç§äº§å“ä¾›ä½ 
选择，它们都是带有数字枷锁的。</p>
+
+<p>GPLv3 ä¿è¯ä½ æœ‰åˆ é™¤æž·é”çš„è‡ªç”±ã€‚å®ƒä¸ç¦æ­¢
+DRMï¼Œä¹Ÿä¸ç¦æ­¢ä»»ä½•åŠŸèƒ½ã€‚å®ƒä¸é™åˆ¶ä½ ä¸ºç¨‹åºæ·»åŠ æˆ–åˆ 
é™¤é‡å¤§çš„åŠŸèƒ½ã€‚åè¿‡æ¥ï¼Œå®ƒä¿è¯ä½ æœ‰åŒæ ·çš„è‡ªç”±å‘å¸ƒåˆ 
é™¤å·®åŠ²åŠŸèƒ½çš„ç‰ˆæœ¬å’Œæ·»åŠ å·®åŠ²åŠŸèƒ½çš„ç‰ˆæœ¬ã€‚Tivoization
+正是要剥夺这种自由；为了保护自由，GPLv3 禁止 
tivoization。</p>
+
+<p>对 tivoization 的禁止适用于任何有消费者
的产品，即使只是偶尔用到。GPLv3 å¯ä»¥å®¹å¿é‚£äº›å‡ 
乎专门用于商业和组织的产品上的
+tivoization。</p>
+
+<p id="patent-deals">
+GPLv3 要反抗的另一个威胁是诸如 Novell-Microsoft 
协议之类的专利交易。Microsoft
+想用其拥有的成千上万的专利来迫使用户付费来运行 
GNU/Linux，并且企图通过此类专利交易达到目的。该交易对 
Novell 用户使用
+Microsoft 专利的保护非常有限。</p>
+
+<p>Microsoft 在此交易中犯了一些错误，GPLv3 反过来以å…
¶äººä¹‹é“来对付
+Microsoft，将这个有限的专利保护扩展到整个社区。为了利用这个保护，程序应该使用
 GPLv3。</p>
+
+<p>Microsoft 的律师不是傻子，下次他们就可能不会再犯这æ 
·çš„é”™è¯¯äº†ã€‚å› 此，GPLv3 说他们不会再有 
&ldquo;下一次&rdquo;。按照
+GPL 版本 3 发布的程序禁止 Microsoft 
将来企图通过再发布来向该程序的用户收取 Microsoft 
版税。</p>
+
+<p id="patent-protection">
+GPLv3 还为用户提供了来自程序贡献者和发布者
的明确专利保护。使用 
GPLv2ï¼Œç”¨æˆ·ä¾èµ–æ½œåœ¨çš„ä¸“åˆ©è®¸å¯è¯æ¥ä¿è¯å‘å¸ƒè€…ä¸å› 
专利侵犯而起诉。</p>
+
+<p>我们并不想要 GPLv3 的明确专利许可证发挥到极致。理想情
况是，我们希望每个 GPL ä»£ç çš„å†å‘å¸ƒè€…éƒ½æ”¾å¼ƒå…
¨éƒ¨çš„软件专利，同时每个非 GPL
+ä»£ç çš„å‘å¸ƒè€…ä¹Ÿæ”¾å¼ƒå…¨éƒ¨çš„è½¯ä»¶ä¸“åˆ©ï¼Œå› 
为本来就不应该有软件专利。软件专利是一个恶毒而可笑的体系，它让所有开发è€
…éƒ½é¢ä¸´è¢«ç´ 昧平生的公司起诉的风险，当然更包括被超
级大å…
¬å¸èµ·è¯‰çš„风险。大型程序一般都集成了成千上万个想法，这些想法已有数百个专利并不意外。è¶
…级大å…
¬å¸æŽŒæ¡ä¸Šä¸‡ä¸ªä¸“利，并使用这些专利来霸凌弱小的开发者
ã€‚ä¸“åˆ©å·²ç„¶åœ¨é˜»æŒ è‡ªç”±è½¯ä»¶çš„å¼€å‘ã€‚</p>
+
+<p>让软件开发安å…
¨çš„唯一出路是废除软件专利，我们希望将来这个目æ 
‡èƒ½å¤Ÿå®žçŽ°ã€‚但是我们不能通过软件专利实现这个目æ 
‡ã€‚ä¸€ä¸ªç¨‹åºï¼Œæ— 
论自由与否，都会被不相干的软件专利持有者
干掉，而该程序的许可证不能阻止这个。只有法庭命令或专利法的变革才能让软件开发å
…é™¤ä¸“利之危险。如果我们寄希望于
+GPLv3，那么不会成功。</p>
+
+<p>å› æ­¤ï¼ŒGPLv3 是在寻求限制和疏导这种危险的方法。å…
·ä½“来看，我们是在尽力挽救自由软件，使之不要落å…
¥ç”Ÿä¸å¦‚死的境地：通过专利变成了专有软件。GPLv3
+的明确专利许可证确保使用 GPL
+的å…
¬å¸ç»™äºˆç”¨æˆ·å››é¡¹åŸºæœ¬è‡ªç”±ï¼Œä¸èƒ½åæ‚”，不能使用专利告诉某些用户，&ldquo;这个不åŒ
…æ‹¬ä½ 们。&rdquo;它也阻止大公司和其他专利持有者
串通起来这么干。</p>
+
+<p id="further-advantages">
+GPLv3 的其他优势还包括更好的国际
化、更温和的中止条款、支持 BitTorrent 以及兼容 Apache 
许可证。总之，升级的理由很充分。</p>
+
+<p id="gpl4">
+GPLv3 
发布之后还可能会有变化。如果用户自由有了新的威胁，那么我们还会开发
 GPL 版本 4。如果我们要撰写
+GPLv4，那么保证程序的许可证升级没有问题是重要的。</p>
+
+<p id="future-proofing">
+其中一个方法是让程序按照 &ldquo;GPL 版本 3 
或任何以后版本&rdquo; 发布。另一个方法是程序的所有贡献者
声明一个能够决定升级 GPL
+将来版本的代理。第三个方法是所有贡献者
将版权转让给一个指定的版权持有者，该版权持有者
å°†å¤„ç†è®¸å¯è¯ç‰ˆæœ¬å‡çº§çš„é—®é¢˜ã€‚æ— 
论采取哪一种方法，程序都应该提供应对将来版本的
+GPL 许可证的灵活性。</p>
+
+<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, 2009, 2014 Richard Stallman</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/26 08:32:08 $
+
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>

Index: po/rms-why-gplv3.zh-cn-en.html
===================================================================
RCS file: po/rms-why-gplv3.zh-cn-en.html
diff -N po/rms-why-gplv3.zh-cn-en.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ po/rms-why-gplv3.zh-cn-en.html      26 May 2020 08:32:08 -0000      1.1
@@ -0,0 +1,228 @@
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.77 -->
+<title>Why Upgrade to GPLv3
+- GNU Project - Free Software Foundation</title>
+<!--#include virtual="/licenses/po/rms-why-gplv3.translist" -->
+<!--#include virtual="/server/banner.html" -->
+<h2>Why Upgrade to GPLv3</h2>
+
+<p>by <strong>Richard Stallman</strong></p>
+
+<p><a href="/licenses/gpl.html">Version 3 of the GNU General Public
+License</a> (GNU GPL) has been released, enabling free software packages to
+upgrade from GPL version 2.  This article explains why upgrading the
+license is important.</p>
+
+<p id="choice">
+First of all, it is important to note that upgrading is a choice.  GPL
+version 2 will remain a valid license, and no disaster will happen if
+some programs remain under GPLv2 while others advance to GPLv3.  These
+two licenses are incompatible, but that isn't a fundamental problem.</p>
+
+<p id="incompatibility">
+When we say that GPLv2 and GPLv3 are incompatible, it means there is
+no legal way to combine code under GPLv2 with code under GPLv3 in a
+single program.  This is because both GPLv2 and GPLv3 are copyleft
+licenses: each of them says, &ldquo;If you include code under this license
+in a larger program, the larger program must be under this license
+too.&rdquo;  There is no way to make them compatible.  We could add a
+GPLv2-compatibility clause to GPLv3, but it wouldn't do the job,
+because GPLv2 would need a similar clause.</p>
+
+<p>Fortunately, license incompatibility matters only when you want to
+link, merge or combine code from two different programs into a single
+program.  There is no problem in having GPLv3-covered and
+GPLv2-covered programs side by side in an operating system.  For
+instance, the TeX license and the Apache license are incompatible with
+GPLv2, but that doesn't stop us from running TeX and Apache in the
+same system with Linux, Bash and GCC.  This is because they are all
+separate programs.  Likewise, if Bash and GCC move to GPLv3, while
+Linux remains under GPLv2, there is no conflict.</p>
+
+<p>Keeping a program under GPLv2 won't create problems.  The reason to
+migrate is because of the existing problems that GPLv3 will address.</p>
+
+<p id="tivoization">
+One major danger that GPLv3 will block is tivoization.  Tivoization
+means certain &ldquo;appliances&rdquo; (which have computers inside)
+contain GPL-covered software that you can't effectively change, because the
+appliance shuts down if it detects modified software.  The usual
+motive for tivoization is that the software has features the
+manufacturer knows people will want to change, and aims
+to stop people from changing them.  The manufacturers of
+these computers take advantage of the freedom that free software
+provides, but they don't let you do likewise.</p>
+
+<p>Some argue that competition between appliances in a free market should
+suffice to keep nasty features to a low level.  Perhaps competition
+alone would avoid arbitrary, pointless misfeatures like &ldquo;Must shut
+down between 1pm and 5pm every Tuesday&rdquo;, but even so, a choice of
+masters isn't freedom.  Freedom means <em>you</em> control what your software
+does, not merely that you can beg or threaten someone else who decides
+for you.</p>
+
+<p id="drm">
+In the crucial area of Digital Restrictions Management (DRM)&mdash;nasty 
features
+designed to restrict your use of the data in your
+computer&mdash;competition is no help, because relevant competition is
+forbidden.  Under the Digital Millennium Copyright Act and similar
+laws, it is illegal, in the US and many other countries, to distribute
+DVD players unless they restrict the user according to the official
+rules of the DVD conspiracy (its web site is <a 
href="http://www.dvdcca.org/";>http://www.dvdcca.org/</a>,
+but the rules do not seem to be published there).  The public can't
+reject DRM by buying non-DRM players because none are available.  No
+matter how many products you can choose from, they all have equivalent
+digital handcuffs.</p>
+
+<p>GPLv3 ensures you are free to remove the handcuffs.  It doesn't forbid
+DRM, or any kind of feature.  It places no limits on the substantive
+functionality you can add to a program, or remove from it.  Rather, it
+makes sure that you are just as free to remove nasty features as the
+distributor of your copy was to add them.  Tivoization is the way they
+deny you that freedom; to protect your freedom, GPLv3 forbids
+tivoization.</p>
+
+<p>The ban on tivoization applies to any product whose use by consumers is to 
be expected, even occasionally.  GPLv3 tolerates tivoization
+only for products that are almost exclusively meant for businesses and
+organizations.</p>
+
+<p id="patent-deals">
+Another threat that GPLv3 resists is that of patent deals like the
+Novell-Microsoft pact.  Microsoft wants to use its thousands of
+patents to make users pay Microsoft for the privilege of running
+GNU/Linux, and made this pact to try to achieve that.  The deal offers
+rather limited protection from Microsoft patents to Novell's customers.</p>
+
+<p>Microsoft made a few mistakes in the Novell-Microsoft deal, and GPLv3
+is designed to turn them against Microsoft, extending that limited
+patent protection to the whole community.  In order to take advantage
+of this protection, programs need to use GPLv3.</p>
+
+<p>Microsoft's lawyers are not stupid, and next time they may manage to
+avoid those mistakes.  GPLv3 therefore says they don't get a &ldquo;next
+time&rdquo;.  Releasing a program under GPL version 3 protects it from
+Microsoft's future attempts to make redistributors collect Microsoft
+royalties from the program's users.</p>
+
+<p id="patent-protection">
+GPLv3 also provides users with explicit patent protection from
+the program's contributors and redistributors.  With GPLv2, users rely
+on an implicit patent license to make sure that the company which
+provided them a copy won't sue them, or the people they redistribute
+copies to, for patent infringement.</p>
+
+<p>The explicit patent license in GPLv3 does not go as far as we might
+have liked.  Ideally, we would make everyone who redistributes
+GPL-covered code give up all software patents, along with everyone
+who does not redistribute GPL-covered code, because there should be
+no software patents.  Software patents are a
+vicious and absurd system that puts all software developers in danger
+of being sued by companies they have never heard of, as well as by all
+the megacorporations in the field.  Large programs typically combine
+thousands of ideas, so it is no surprise if they implement ideas
+covered by hundreds of patents.  Megacorporations collect thousands of
+patents, and use those patents to bully smaller developers.  Patents
+already obstruct free software development.</p>
+
+<p>The only way to make software development safe is to abolish software
+patents, and we aim to achieve this some day.  But we cannot do this
+through a software license.  Any program, free or not, can be killed
+by a software patent in the hands of an unrelated party, and the
+program's license cannot prevent that.  Only court decisions or
+changes in patent law can make software development safe from patents.
+If we tried to do this with GPLv3, it would fail.</p>
+
+<p>Therefore, GPLv3 seeks to limit and channel the danger.  In
+particular, we have tried to save free software from a fate worse than
+death: to be made effectively proprietary, through patents.  The
+explicit patent license of GPLv3 makes sure companies that use the GPL
+to give users the four freedoms cannot turn around and use their
+patents to tell some users, &ldquo;That doesn't include you.&rdquo;
+It also stops
+them from colluding with other patent holders to do this.</p>
+
+<p id="further-advantages">
+Further advantages of GPLv3 include better internationalization, gentler
+termination, support for BitTorrent, and compatibility with the Apache
+license.  All in all, plenty of
+reason to upgrade.</p>
+
+<p id="gpl4">
+Change is unlikely to cease once GPLv3 is released.  If new threats to
+users' freedom develop, we will have to develop GPL version 4.  It is
+important to make sure that programs will have no trouble upgrading to
+GPLv4 if and when we write one.</p>
+
+<p id="future-proofing">
+One way to do this is to release a program under &ldquo;GPL version 3 or any
+later version&rdquo;.  Another way is for all the contributors to a program
+to state a proxy who can decide on upgrading to future GPL versions.
+The third way is for all the contributors to assign copyright to one
+designated copyright holder, who will be in a position to upgrade the
+license version.  One way or another, programs should provide this
+flexibility for future GPL versions.</p>
+
+</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, 2009, 2014 Richard Stallman</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/26 08:32:08 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>