www/licenses po/license-recommendations.transli...

[GNUN]

CVSROOT:        /web/www
Module name:    www
Changes by:     GNUN <gnun>     18/11/11 06:59:11

Modified files:
        licenses/po    : license-recommendations.translist 
Added files:
        licenses       : license-recommendations.zh-cn.html 
        licenses/po    : license-recommendations.zh-cn-en.html 

Log message:
        Automatic update by GNUnited Nations.

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

Patches:
Index: po/license-recommendations.translist
===================================================================
RCS file: /web/www/www/licenses/po/license-recommendations.translist,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -b -r1.16 -r1.17
--- po/license-recommendations.translist        27 Feb 2017 16:58:50 -0000      
1.16
+++ po/license-recommendations.translist        11 Nov 2018 11:59:10 -0000      
1.17
@@ -9,6 +9,7 @@
 <span dir="ltr"><a lang="ja" hreflang="ja" 
href="/licenses/license-recommendations.ja.html">日本語</a>&nbsp;[ja]</span> 
&nbsp;
 <span dir="ltr"><a lang="pt-br" hreflang="pt-br" 
href="/licenses/license-recommendations.pt-br.html">português&nbsp;do&nbsp;Brasil</a>&nbsp;[pt-br]</span>
 &nbsp;
 <span dir="ltr"><a lang="ru" hreflang="ru" 
href="/licenses/license-recommendations.ru.html">русский</a>&nbsp;[ru]</span>
 &nbsp;
+<span dir="ltr"><a lang="zh-cn" hreflang="zh-cn" 
href="/licenses/license-recommendations.zh-cn.html">简体中文</a>&nbsp;[zh-cn]</span>
 &nbsp;
 </p>
 </div>' -->
 <link rel="alternate" type="text/html" 
href="/licenses/license-recommendations.html" hreflang="x-default" />
@@ -19,4 +20,5 @@
 <link rel="alternate" type="text/html" lang="ja" hreflang="ja" 
href="/licenses/license-recommendations.ja.html" title="日本語" />
 <link rel="alternate" type="text/html" lang="pt-br" hreflang="pt-br" 
href="/licenses/license-recommendations.pt-br.html" title="português do 
Brasil" />
 <link rel="alternate" type="text/html" lang="ru" hreflang="ru" 
href="/licenses/license-recommendations.ru.html" title="русский" />
+<link rel="alternate" type="text/html" lang="zh-cn" hreflang="zh-cn" 
href="/licenses/license-recommendations.zh-cn.html" title="简体中文" />
 <!-- end translist file -->

Index: license-recommendations.zh-cn.html
===================================================================
RCS file: license-recommendations.zh-cn.html
diff -N license-recommendations.zh-cn.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ license-recommendations.zh-cn.html  11 Nov 2018 11:59:10 -0000      1.1
@@ -0,0 +1,211 @@
+<!--#set var="ENGLISH_PAGE" value="/licenses/license-recommendations.en.html" 
-->
+
+<!--#include virtual="/server/header.zh-cn.html" -->
+<!-- Parent-Version: 1.84 -->
+
+<!-- This file is automatically generated by GNUnited Nations! -->
+<title>å¦‚ä½•ä¸ºä½ çš„ä½œå“é€‰æ‹©ä¸€ä»½è®¸å¯è¯ - GNU 工程 - 
自由软件基金会</title>
+
+<!--#include virtual="/licenses/po/license-recommendations.translist" -->
+<!--#include virtual="/server/banner.zh-cn.html" -->
+<h2>å¦‚ä½•ä¸ºä½ çš„ä½œå“é€‰æ‹©ä¸€ä»½è®¸å¯è¯</h2>
+
+<!--#include virtual="/licenses/fsf-licensing.zh-cn.html" -->
+<blockquote><p>
+要得知一个特定的许可证是否自由，可参阅<a 
href="/licenses/license-list.html">我们的许可证列表</a>以及<a
+href="/philosophy/free-sw.html">自由软件的定义</a>。
+</p></blockquote>
+
+<h3 id="intro">前言</h3>
+
+<p>人们经常问我们，为他们的项目向他们推荐什么许可证。我们过去已经å
…¬å¼€åœ°å†™äº†å…³äºŽè¿™ä¸ªçš„æ–‡ç« ï¼Œä½†ä¿¡æ¯åœ¨ä¸åŒçš„æ–‡ç« ã€FAQ
+æ¡ç›®å’Œè®¸å¯è¯æ³¨é‡Šä¹‹é—´åˆ†æ•£å¼€äº†ã€‚è¿™ç¯‡æ–‡ç« 
收集所有的信息至一个单一的来源中，让人们更简单地跟着做并可以参考。</p>
+
+<p>这些推荐是用于设计来做实用工作的作品的。这包
括了软件、文档和一些å…
¶ä»–的东西。艺术作品、以及表达观点的作品，则不一æ 
·ï¼›GNU项目对它们该怎么发布没有通用的立场，除了它们应该在没有非自由软件的æƒ
…况下可以使用（特别是<a
+href="http://defectivebydesign.org/";>没有DRM</a>）。然而，对于和某个程序在一起的艺术作品，ä½
 可能需要听从这些推荐。</p>
+
+<p>è¿™äº›æŽ¨èå¯ä»¥ç”¨äºŽè®¸å¯ä¸€ä¸ªä½ 
创建的作品&mdash;不论是已有作品的修改版还是原创作品。它们不能解决结合已有不同许可证的材料的问题。如果ä½
 在寻求那方面的帮助，请查看
+<a href="/licenses/gpl-faq.html">GPL FAQ</a>。</p>
+
+<p>åœ¨ä½ çœ‹äº†æˆ‘ä»¬çš„æŽ¨èä¹‹åŽï¼Œå¦‚æžœä½ æƒ³è¦å»ºè®®ï¼Œä½ 
可以写邮件到 <a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>。注意许可证小组的回信可能需要å‡
 ä¸ªæ˜ŸæœŸï¼›å¦‚æžœä½ åœ¨ä¸€ä¸ªæœˆå†…æ²¡æœ‰å¾—åˆ°å›žå¤ï¼Œè¯·å†å†™ä¸€æ¬¡ã€‚</p>
+
+<h3 id="contributing">贡献到一个已有的项目</h3>
+
+<p>å½“ä½ è´¡çŒ®åˆ°ä¸€ä¸ªå·²æœ‰çš„é¡¹ç›®æ—¶ï¼Œä½ 
é€šå¸¸åº”è¯¥åœ¨å’ŒåŽŸä½œå“ç›¸åŒçš„è®¸å¯è¯ä¹‹ä¸‹å‘å¸ƒä½ 
ä¿®æ”¹è¿‡çš„ç‰ˆæœ¬ã€‚å’Œé¡¹ç›®çš„ç»´æŠ¤è€…åˆä½œæ˜¯ä»¶å¥½äº‹ï¼Œè€Œä¸ºä½ 
çš„ä¿®æ”¹ä½¿ç”¨ä¸åŒçš„è®¸å¯è¯ç»å¸¸ä¼šè®©åˆä½œå˜å¾—å›°éš¾ã€‚ä½ 
åªåº”åœ¨æœ‰å¼ºå¤§ç†ç”±æ”¯æŒçš„æ—¶å€™æ‰é‚£æ ·åšã€‚</p>
+
+<p>ä¸€ç§å¯ä»¥åˆç†ä½¿ç”¨ä¸åŒè®¸å¯è¯çš„æƒ…å½¢æ˜¯ï¼Œä½ åœ¨éž copyleft
+è®¸å¯è¯ä¸‹çš„ä½œå“ä¸Šåšå‡ºäº†ä¸»è¦ä¿®æ”¹ã€‚å¦‚æžœä½ 
åˆ›å»ºçš„è¿™ä¸ªç‰ˆæœ¬æ¯”åŽŸæ¥çš„ç‰ˆæœ¬æœ‰ç”¨å¾—å¤šï¼Œé‚£ä¹ˆå°±å€¼å¾—è®©ä½ 
的作品 copyleft 化，就和我们通常<a
+href="/copyleft/copyleft.html">推荐 copyleft
+çš„åŽŸå› </a>ä¸€æ ·ã€‚å¦‚æžœä½ æ˜¯åœ¨è¿™ç§æƒ…
况下，请遵循以下用于许可一个新项目的建议。</p>
+
+<p>æ— è®ºæ˜¯ä»€ä¹ˆç†ç”±ï¼Œå¦‚æžœä½ é€‰æ‹©ä»¥ä¸åŒè®¸å¯è¯å‘å¸ƒä½ 
çš„è´¡çŒ®ï¼Œä½ å¿…é¡»ç¡®ä¿åŽŸæœ‰çš„è®¸å¯è¯å…è®¸ç´ æå¯ä»¥åœ¨ä½ 
选择的许可证之下使用。至少从良心上讲，请明确地表示哪部分的作品是在哪种许可证之下。</p>
+
+<h3 id="software">软件</h3>
+
+<p>对不同的项目我们推荐不同的许可证，这主要依据软件的目的。通常来说，我们推荐使用最
 copyleft è€Œä¸å½±å“ç›®çš„çš„è®¸å¯è¯ã€‚æˆ‘ä»¬çš„æ–‡ç« <a
+href="/copyleft/copyleft.html">&ldquo;什么是copyleft?&rdquo;</a>更详细地解释了
+copyleft 的概念，以及为什么它通常是最好的许可方案</p>
+
+<p>å¯¹å¤§å¤šæ•°ç¨‹åºï¼Œæˆ‘ä»¬æŽ¨èä½ ä¸ºä½ çš„é¡¹ç›®ä½¿ç”¨æœ€æ–°ç‰ˆçš„ <a 
href="/licenses/gpl.html">GPL</a>。它强大的 copyleft
+适合所有类型的软件，并对用户的自由有很多保护。也请å…
è®¸ä½¿ç”¨ GPL 的未来版本&mdash;æ¢å¥è¯è¯´ï¼Œåœ¨è®¸å¯å£°æ˜Žä¸­å†™ä¸Šä½ 
的程序被 GPL v3
+或其更新版本覆盖。</p>
+
+<p>此处有关于<a href="/licenses/gpl-howto.html">如何在 GNU GPL 
之下发布程序</a>的更多建议。</p>
+
+<p>现在看看例外情形，这些情形下使用别的许可证比使用 
GPL 更好。</p>
+
+<h4 id="small">小程序</h4>
+
+<p>对大多数小程序，使用 copyleft 
是不值得的。我们用300行作为基准：当一个软件包的源ç 
æ¯”这个短，copyleft
+带来的好处通常太小，不足以对抗确保许可证的复本总是伴随软件的不便。</p>
+
+<p>对这些程序，我们推荐 <a 
href="http://www.apache.org/licenses/LICENSE-2.0";>Apache 2.0
+许可证</a>。这是一个
+pushover（非copyleft）软件许可证，它有用于避免贡献者
和分发者起诉专利侵权的条目。这并不会让软件避å…
æ¥è‡ªä¸“利的威胁（一个软件许可证是做不到的），但它避å…
äº†ä¸“利持有者打着自由的幌子发布软件，这种情
况下专利持有者
会相当于做了一次&ldquo;诱导转向&rdquo;，然后要求接受者
同意专利证书中的非自由条目。</p>
+
+<p>åœ¨ä¸ä¸¥æ ¼çš„ pushover 许可证中，Apache 2.0 
æ˜¯æœ€å¥½çš„ï¼›æ‰€ä»¥å¦‚æžœä½ è¦ç”¨ä¸€ä¸ªä¸ä¸¥æ ¼çš„ pushover
+è®¸å¯è¯ï¼Œä¸è®ºä»€ä¹ˆåŽŸå› ï¼Œæˆ‘ä»¬æŽ¨èç”¨è¿™ä¸€ä¸ªã€‚</p>
+
+<h4 id="libraries">库</h4>
+
+<p>对于库，我们分三种情形。</p>
+
+<p>ä¸€äº›å®žçŽ°äº†è‡ªç”±æ ‡å‡†çš„åº“ä¸Žé‚£äº›é™åˆ¶æ€§æ ‡å‡†ç«žäº‰ï¼Œä¾‹å¦‚ 
Ogg Vorbis（和 MP3 音频竞争）和 WebM（和 MPEG-4
+视频竞争）。对于这些项目，代ç 
çš„广泛使用对于推进自由软件事业非常重要，会比在项目代ç
 ä¸Šçš„ copyleft 有更多的好处。</p>
+
+<p>在这些特殊的情况，我们推荐 <a 
href="http://www.apache.org/licenses/LICENSE-2.0";>Apache
+2.0 许可证</a>。</p>
+
+<p>对所有其他的库，我们推荐某种 copyleft 
è®¸å¯è¯ã€‚å¦‚æžœå¼€å‘è€…å·²ç»ä½¿ç”¨çŽ°æœ‰çš„ä»¥éžè‡ªç”±æˆ–ä¸ä¸¥æ ¼çš„ 
pushover 许可证发布的库，那么我们建议使用
+<a href="/licenses/lgpl.html">GNU 宽通用公共许可证（LGPL）</a>。</p>
+
+<p>在第一种情形中，库实现了一个伦理上更优秀的æ 
‡å‡†ï¼Œä½†åœ¨è¿™é‡Œä¸åƒç¬¬ä¸€ç§æƒ…
形，库的广泛使用并不会达成实际好处，所以完å…
¨æ²¡æœ‰ç†ç”±é¿å…
+copyleftã€‚ç„¶è€Œï¼Œå¦‚æžœä½ è¦æ±‚ç”¨åº“çš„å¼€å‘è€…åœ¨ copyleft 
下发布整个程序，他们会简单地用另一个可用的库，那æ 
·ä¹Ÿä¸ä¼šæŽ¨è¿›æˆ‘们的事业。较为宽松的
+GPL（LGPL）是设计于填补这些情形中间地带的，å…
è®¸ç§æœ‰è½¯ä»¶å¼€å‘者使用其保护起来的库，但考虑到库代ç 
æœ¬èº«ï¼ŒLGPL 提供了给用户自由的弱
+copyleft。</p>
+
+<p>对于提供了特别设计，并且不会与现有非 copyleft 
或非自由库竞争的，我们推荐使用原始的 GNU GPLã€‚è¦çŸ¥é“åŽŸå› 
，请阅读<a
+href="/licenses/why-not-lgpl.html">&ldquo;ä¸ºä»€ä¹ˆä½ ä¸åº”è¯¥ä¸ºä½ 
下一个库用宽松的 GPL&rdquo;</a>。</p>
+
+<h4 id="server">服务器软件</h4>
+
+<p>å¦‚æžœå…¶ä»–äººå¾ˆæœ‰å¯èƒ½ä¼šç»™ä½ 
在服务器上跑的软件制作改进版并且不向å…
¶ä»–äººåˆ†å‘ä»–ä»¬çš„ç‰ˆæœ¬ï¼Œè€Œä¸”ä½ æ‹…å¿ƒè¿™å°†æŠŠä½ 
的版本置于一个不利的地位，我们推荐 <a
+href="/licenses/agpl.html">GNU Affero 通用公å…
±è®¸å¯è¯ï¼ˆAGPL）</a>。AGPL 的条目和 GPL
+å‡ 
乎相同；唯一实质的区别是它有一个额外的条件确保通过网络用这个软件的人们可以获得它的源代ç
 ã€‚</p>
+
+<p>对于<em>用户们</em>而言，AGPL 的要求没有解决当他们委托å…
¶è®¡ç®—或者
数据给别人的服务器时，会产生的问题。例如，它不会制止<a
+href="/philosophy/who-does-that-server-really-serve.html">作为软件替代品的服务（SaaSS）</a>拒绝给予用户的自由&mdash;但大多数服务器不做
+SaaSS。要想知道更多关于这些的问题，请阅读<a 
href="/licenses/why-affero-gpl.html">&ldquo;为什么用
+Affero GPL&rdquo;</a>。</p>
+
+<h3 id="documentation">文档</h3>
+
+<p>对教程、参考手册和其他大型文档工作，我们推荐 <a 
href="/licenses/fdl.html">GNU
+自由文档许可证</a>。对教育型工作，这是个很强的 copyleft
+许可证，最早为软件文档而编写，并包
含特别说明，即当这些作品被分发或修改时的常见问题。</p>
+
+<p>对于短的、次要的文档工作，例如参考卡片，最好使用 <a
+href="/licenses/license-list.html#GNUAllPermissive">GNU all-permissive
+许可证</a>ï¼Œå› ä¸ºä¸€ä»½ GFDL çš„å¤æœ¬éš¾ä»¥æ”¾è¿›ä¸€å¼ 
参考卡片里面。不要用CC-BYï¼Œå› ä¸ºå®ƒå’Œ GFDL 不兼容。</p>
+
+<p>对于 man 手册页面，如果页面很长，我们推荐 
GFDL，而如果它很短，则推荐 <a
+href="/licenses/license-list.html#GNUAllPermissive">GNU all-permissive
+许可证</a>。</p>
+
+<p>一些文档包括了软件源代ç 
ã€‚例如，一个编程语言的的手册可能包
æ‹¬è®©ç”¨æˆ·éµå¾ªçš„ä¾‹å­ã€‚ä½ åº”å½“æ—¢åœ¨ FDL
+之下在手册中包
含它们，又在另一个适合软件的许可证下发布它们。这æ 
·åšä½¿å¾—åœ¨å…¶ä»–é¡¹ç›®ä¸­ç”¨è¿™äº›ä»£ç å˜å¾—ç®€å•ã€‚æˆ‘ä»¬æŽ¨èä½ 用 <a
+href="http://creativecommons.org/about/cc0";>CC0</a>
+è´¡çŒ®å°æ®µçš„ä»£ç åˆ°å…¬æœ‰é¢†åŸŸï¼Œå¹¶åœ¨æœ‰å…
³è½¯ä»¶é¡¹ç›®ä½¿ç”¨çš„ç›¸åŒçš„è®¸å¯è¯ä¹‹ä¸‹åˆ†å‘å¤§æ®µçš„ä»£ç ã€‚</p>
+
+<h3 id="data">其他用于程序的数据</h3>
+
+<p>è¿™æ®µè®¨è®ºä½ ä¼šåŒ…æ‹¬åœ¨è½¯ä»¶ä¸­çš„æ‰€æœ‰å…
¶ä»–实用作品。例如图表和å…
¶ä»–åŠŸèƒ½æ€§æˆ–æœ‰ç”¨çš„å›¾åƒã€å­—ä½“å’Œåœ°ç†æ•°æ®ç­‰ã€‚ä½ 
ä¹Ÿå¯ä»¥åœ¨è‰ºæœ¯ä¸­éµå¾ªè¿™äº›ï¼Œå°½ç®¡ä½ ä¸è¿™æ 
·åšæˆ‘ä»¬ä¹Ÿä¸ä¼šæ‰¹è¯„ä½ 。</p>
+
+<p>å¦‚æžœä½ 
æ­£ç‰¹æ„ä¸ºä¸€ä¸ªè½¯ä»¶é¡¹ç›®åˆ›ä½œè¿™äº›ä½œå“ï¼Œæˆ‘ä»¬é€šå¸¸æŽ¨èä½ 
åœ¨å’Œè½¯ä»¶ä½¿ç”¨ç›¸åŒçš„è®¸å¯è¯ä¸‹å‘å¸ƒä½ 
的作品。用我们推荐的许可证这æ 
·åšä¸ä¼šæœ‰é—®é¢˜ï¼šGPLv3、LGPLv3、AGPLv3
+和 GPLv2
+都可以用于任何类型&mdash;不只是软件&mdash;只需受版权保护并对修改版有æ¸
…晰首选的形式。使用与软件相同的许可证会让分发者
更容易遵守规定，并可以避免任何对潜在的å…
¼å®¹æ€§é—®é¢˜çš„顾虑。如果提供了一些特别的实用的好处，比如和å
…
¶ä»–自由项目更好地合作，那么使用一个不同的许可证可能是合适的。</p>
+
+<p>å¦‚æžœä½ çš„ä½œå“ä¸æ˜¯ä¸ºæŸä¸ªç‰¹å®šçš„è½¯ä»¶é¡¹ç›®è€Œåˆ›ä½œçš„ï¼Œæˆ–è€…
ä½¿ç”¨å’Œé¡¹ç›®ç›¸åŒçš„è®¸å¯è¯ä¸åˆé€‚ï¼Œé‚£ä¹ˆæˆ‘ä»¬åªæŽ¨èä½ 
é€‰æ‹©ä¸€ä¸ªé€‚åˆä½ ä½œå“çš„ copyleft
+许可证。有一些<a
+href="/licenses/license-list.html#OtherLicenses">在我们的许可证列表中列出</a>。如果没有许可证看起来合适的，<a
+href="/licenses/license-list.html#ccbysa">创作共用署名-相同方式å…
±äº«è®¸å¯è¯ï¼ˆCC-BY-SA）</a>是一个可以用于很多不同种类作品的
+copyleft 许可证。</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="/server/standards/README.translations.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 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 &copy; 2011, 2013, 2014, 2015, 2017, 2018 Free Software
+Foundation, Inc.</p>
+
+<p>本页面使用<a rel="license"
+href="http://creativecommons.org/licenses/by-nd/4.0/";>Creative Commons
+Attribution-NoDerivatives 4.0 International 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.nongnu.org/projects/blug/";>BLUG</a>
+<b>翻译团队</b>：<a rel="team"
+href="https://savannah.gnu.org/projects/www-zh-cn/";>&lt;CTT&gt;</a>，2018。</div>
+
+<p class="unprintable"><!-- timestamp start -->
+最后更新：
+
+$Date: 2018/11/11 11:59:10 $
+
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>

Index: po/license-recommendations.zh-cn-en.html
===================================================================
RCS file: po/license-recommendations.zh-cn-en.html
diff -N po/license-recommendations.zh-cn-en.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ po/license-recommendations.zh-cn-en.html    11 Nov 2018 11:59:10 -0000      
1.1
@@ -0,0 +1,297 @@
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.84 -->
+<title>How to choose a license for your own work
+- GNU Project - Free Software Foundation</title>
+<!--#include virtual="/licenses/po/license-recommendations.translist" -->
+<!--#include virtual="/server/banner.html" -->
+<h2>How to choose a license for your own work</h2>
+
+<!--#include virtual="/licenses/fsf-licensing.html" -->
+
+<blockquote><p>
+To see whether a given license is free or not,
+see <a href="/licenses/license-list.html">our license list page</a>
+and the <a href="/philosophy/free-sw.html">definition of free software</a>.
+</p></blockquote>
+
+<h3 id="intro">Introduction</h3>
+
+<p>People often ask us what license we recommend they use for their
+project.  We've written about this publicly before, but the
+information has been scattered around between different essays, FAQ
+entries, and license commentaries.  This article collects all that
+information into a single source, to make it easier for people to
+follow and refer back to.</p>
+
+<p>These recommendations are for works designed to do practical jobs.
+Those include software, documentation, and some other things.  Works of
+art, and works that state a point of view, are different issues; the GNU
+Project has no general stand about how they should be released, except
+that they should all be usable without nonfree software (in
+particular, <a href="http://defectivebydesign.org/";>without DRM</a>).
+However, you might want to follow these recommendations for art works
+that go with a particular program.</p>
+
+<p>The recommendations apply to licensing a work that you
+create&mdash;whether that's a modification of an existing work, or a
+new original work.  They do not address the issue of combining
+existing material under different licenses.  If you're looking for
+help with that, please check <a href="/licenses/gpl-faq.html">our GPL
+FAQ</a>.</p>
+
+<p>After you see what we recommend here, if you'd like advice, you can
+write
+to <a href="mailto:address@hidden";>&lt;address@hidden&gt;</a>.
+Note that it will probably take a few weeks for the licensing team to
+get back to you; if you get no response in a month, please write
+again.</p>
+
+<h3 id="contributing">Contributing to an existing project</h3>
+
+<p>When you contribute to an existing project, you should usually release
+your modified versions under the same license as the original work.
+It's good to cooperate with the project's maintainers, and using a
+different license for your modifications often makes that cooperation
+very difficult.  You should only do that when there is a strong reason
+to justify it.</p>
+
+<p>One case where using a different license can be justified is when you make
+major changes to a work under a non-copyleft license.  If the version you've
+created is considerably more useful than the original, then it's worth
+copylefting your work, for all the same
+<a href="/copyleft/copyleft.html">reasons we normally recommend
+copyleft</a>.  If you are in this situation, please follow the
+recommendations below for licensing a new project.</p>
+
+<p>If you choose to release your contributions under a different
+license for whatever reason, you must make sure that the original
+license allows use of the material under your chosen license.  For
+honesty's sake, show explicitly which parts of the work are under
+which license.</p>
+
+<h3 id="software">Software</h3>
+
+<p>We recommend different licenses for different projects, depending
+mostly on the software's purpose.  In general, we recommend using the
+strongest copyleft license that doesn't interfere with that purpose.
+Our essay <a href="/copyleft/copyleft.html">&ldquo;What
+is Copyleft?&rdquo;</a> explains the
+concept of copyleft in more detail, and why it is generally the best
+licensing strategy.</p>
+
+<p>For most programs, we recommend that you use the most recent
+version of the <a href="/licenses/gpl.html">GNU General Public License
+(GPL)</a> for your project.  Its strong copyleft is appropriate for
+all kinds of software, and includes numerous protections for users'
+freedom.  Please give permission to use future license versions as
+well&mdash;in other words, make the license notice say that your
+program is covered by GPL version 3 or later.</p>
+
+<p>Here is more advice about <a href="/licenses/gpl-howto.html">how
+to release a program under the GNU GPL</a>.</p>
+
+<p>Now for the exceptions, where it is better to use some other
+licenses instead of the GNU GPL.</p>
+
+<h4 id="small">Small programs</h4>
+
+<p>It is not worth the trouble to use copyleft for most small
+programs.  We use 300 lines as our benchmark: when a software
+package's source code is shorter than that, the benefits provided by
+copyleft are usually too small to justify the inconvenience of making
+sure a copy of the license always accompanies the software.</p>
+
+<p>For those programs, we recommend
+the <a href="http://www.apache.org/licenses/LICENSE-2.0";>Apache
+License 2.0</a>.  This is a pushover (non-copyleft) software license
+that has terms to prevent contributors and distributors from suing for
+patent infringement.  This doesn't make the software immune to threats
+from patents (a software license can't do that), but it does prevent
+patent holders from setting up a &ldquo;bait and switch&rdquo; where
+they release the software under free terms then require recipients to
+agree to nonfree terms in a patent license.</p>
+
+<p>Among the lax pushover licenses, Apache 2.0 is best; so if you
+are going to use a lax pushover license, whatever the reason,
+we recommend using that one.</p>
+
+<h4 id="libraries">Libraries</h4>
+
+<p>For libraries, we distinguish three kind of cases.</p>
+
+<p>Some libraries implement free standards that are competing against
+restricted standards, such as Ogg Vorbis (which competes against MP3
+audio) and WebM (which competes against MPEG-4 video).  For these
+projects, widespread use of the code is vital for advancing the cause
+of free software, and does more good than a copyleft on the project's
+code would do.</p>
+
+<p>In these special situations, we recommend
+the <a href="http://www.apache.org/licenses/LICENSE-2.0";>Apache
+License 2.0</a>.</p>
+
+<p>For all other libraries, we recommend some kind of copyleft.  If
+developers are already using an established alternative library
+released under a nonfree license or a lax pushover license, then we
+recommend using the <a href="/licenses/lgpl.html">GNU Lesser General
+Public License (LGPL)</a>.</p>
+
+<p>Unlike the first case, where the library implements an ethically
+superior standard, here adoption for its own sake will not accomplish
+any special objective goal, so there's no reason to avoid copyleft
+entirely.  However, if you require developers who use your library to
+release their whole programs under copyleft, they'll simply use one of
+the alternatives available, and that won't advance our cause either.
+The Lesser GPL was designed to fill the middle ground between these
+cases, allowing proprietary software developers to use the covered
+library, but providing a weak copyleft that gives users freedom
+regarding the library code itself.</p>
+
+<p>For libraries that provide specialized facilities, and which do not
+face entrenched noncopylefted or nonfree competition, we recommend
+using the plain GNU GPL.  For the reasons why,
+read <a href="/licenses/why-not-lgpl.html">&ldquo;Why you shouldn't
+use the Lesser GPL for your next library&rdquo;</a>.</p>
+
+<h4 id="server">Server Software</h4>
+
+<p>If it is likely that others will make improved versions of your
+program to run on servers and not distribute their versions to anyone
+else, and you're concerned that this will put your released version at
+a disadvantage, we recommend the <a href="/licenses/agpl.html">GNU
+Affero General Public License (AGPL)</a>.  The AGPL's terms are almost
+identical to the GPL's; the sole substantive difference is that it has
+an extra condition to ensure that people who use the software over a
+network will be able to get the source code for it.</p>
+
+<p>The AGPL's requirement doesn't address the problems that can arise
+<em>for users</em> when they entrust their computing or their data to
+someone else's server.  For instance, it won't stop
+<a href="/philosophy/who-does-that-server-really-serve.html">Service
+as a Software Substitute (SaaSS)</a> from denying users'
+freedom&mdash;but most servers don't do SaaSS.  For more about these
+issues, read <a href="/licenses/why-affero-gpl.html">&ldquo;Why the
+Affero GPL&rdquo;</a>.</p>
+
+<h3 id="documentation">Documentation</h3>
+
+<p>We recommend the <a href="/licenses/fdl.html">GNU Free
+Documentation License (GFDL)</a> for tutorials, reference manuals and
+other large works of documentation.  It's a strong copyleft license
+for educational works, initially written for software manuals, and
+includes terms which specifically address common issues that arise
+when those works are distributed or modified.</p>
+
+<p>For short, secondary documentation works, such as a reference card,
+it is better to use
+the <a href="/licenses/license-list.html#GNUAllPermissive"> GNU
+all-permissive license</a>, since a copy of the GFDL could hardly fit
+in a reference card.  Don't use CC-BY, since it is incompatible with
+the GFDL.</p>
+
+<p>For man pages, we recommend the GFDL if the page is long, and
+the <a href="/licenses/license-list.html#GNUAllPermissive"> GNU
+all-permissive license</a> if it is short.</p>
+
+<p>Some documentation includes software source code.  For instance, a manual
+for a programming language might include examples for readers to follow.
+You should both include these in the manual under the FDL's terms, and
+release them under another license that's appropriate for software.  Doing
+so helps make it easy to use the code in other projects.  We recommend that
+you dedicate small pieces of code to the public domain using <a 
href="http://creativecommons.org/about/cc0";>CC0</a>, and
+distribute larger pieces under the same license that the associated
+software project uses.</p>
+
+<h3 id="data">Other data for programs</h3>
+
+<p>This section discusses all other works for practical use that you
+might include with software.  To give you some examples, this includes
+icons and other functional or useful graphics, fonts, and geographic
+data.  You can also follow them for art, though we wouldn't criticize
+if you don't.</p>
+
+<p>If you are creating these works specifically for use with a software
+project, we generally recommend that you release your work under the
+same license as the software.  There is no problem in doing so
+with the licenses we have recommended:
+GPLv3, LGPLv3, AGPLv3, and GPLv2 can all be applied to any kind of
+work&mdash;not just software&mdash;that is copyrightable and has a clear
+preferred form for modification.  Using the same license as the
+software will help make compliance easier for distributors, and avoids
+any doubt about potential compatibility issues.  Using a different
+free license may be appropriate if it provides some specific practical
+benefit, like better cooperation with other free projects.</p>
+
+<p>If your work is not being created for use with a particular software
+project, or if it wouldn't be appropriate to use the same license as
+the project, then we only recommend that you choose a copyleft license
+that's appropriate for your work.  We have some of these <a 
href="/licenses/license-list.html#OtherLicenses">listed on
+our license list</a>.  If no license seems especially
+appropriate, the <a href="/licenses/license-list.html#ccbysa">Creative Commons 
Attribution-ShareAlike</a>
+license is a copyleft that can be used for many different kinds of
+works.</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 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 &copy; 2011, 2013, 2014, 2015, 2017, 2018 Free Software 
Foundation, Inc.</p>
+
+<p>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>.</p>
+
+<!--#include virtual="/server/bottom-notes.html" -->
+
+<p class="unprintable">Updated:
+<!-- timestamp start -->
+$Date: 2018/11/11 11:59:10 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>