www/distros po/free-system-distribution-guideli...

[GNUN]

CVSROOT:        /web/www
Module name:    www
Changes by:     GNUN <gnun>     17/10/28 07:59:27

Modified files:
        distros/po     : free-system-distribution-guidelines.translist 
Added files:
        distros        : free-system-distribution-guidelines.zh-cn.html 
        distros/po     : 
                         free-system-distribution-guidelines.zh-cn-en.html 

Log message:
        Automatic update by GNUnited Nations.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/distros/free-system-distribution-guidelines.zh-cn.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/distros/po/free-system-distribution-guidelines.translist?cvsroot=www&r1=1.18&r2=1.19
http://web.cvs.savannah.gnu.org/viewcvs/www/distros/po/free-system-distribution-guidelines.zh-cn-en.html?cvsroot=www&rev=1.1

Patches:
Index: po/free-system-distribution-guidelines.translist
===================================================================
RCS file: 
/web/www/www/distros/po/free-system-distribution-guidelines.translist,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -b -r1.18 -r1.19
--- po/free-system-distribution-guidelines.translist    28 Aug 2015 07:02:23 
-0000      1.18
+++ po/free-system-distribution-guidelines.translist    28 Oct 2017 11:59:27 
-0000      1.19
@@ -17,6 +17,7 @@
 <span dir="ltr"><a lang="ro" hreflang="ro" 
href="/distros/free-system-distribution-guidelines.ro.html">română</a>&nbsp;[ro]</span>
 &nbsp;
 <span dir="ltr"><a lang="ru" hreflang="ru" 
href="/distros/free-system-distribution-guidelines.ru.html">русский</a>&nbsp;[ru]</span>
 &nbsp;
 <span dir="ltr"><a lang="uk" hreflang="uk" 
href="/distros/free-system-distribution-guidelines.uk.html">українська</a>&nbsp;[uk]</span>
 &nbsp;
+<span dir="ltr"><a lang="zh-cn" hreflang="zh-cn" 
href="/distros/free-system-distribution-guidelines.zh-cn.html">简体中文</a>&nbsp;[zh-cn]</span>
 &nbsp;
 </p>
 </div>' -->
 <link rel="alternate" type="text/html" 
href="/distros/free-system-distribution-guidelines.html" hreflang="x-default" />
@@ -35,4 +36,5 @@
 <link rel="alternate" type="text/html" lang="ro" hreflang="ro" 
href="/distros/free-system-distribution-guidelines.ro.html" title="română" />
 <link rel="alternate" type="text/html" lang="ru" hreflang="ru" 
href="/distros/free-system-distribution-guidelines.ru.html" 
title="русский" />
 <link rel="alternate" type="text/html" lang="uk" hreflang="uk" 
href="/distros/free-system-distribution-guidelines.uk.html" 
title="українська" />
+<link rel="alternate" type="text/html" lang="zh-cn" hreflang="zh-cn" 
href="/distros/free-system-distribution-guidelines.zh-cn.html" 
title="简体中文" />
 <!-- end translist file -->

Index: free-system-distribution-guidelines.zh-cn.html
===================================================================
RCS file: free-system-distribution-guidelines.zh-cn.html
diff -N free-system-distribution-guidelines.zh-cn.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ free-system-distribution-guidelines.zh-cn.html      28 Oct 2017 11:59:24 
-0000      1.1
@@ -0,0 +1,228 @@
+<!--#set var="ENGLISH_PAGE" 
value="/distros/free-system-distribution-guidelines.en.html" -->
+
+<!--#include virtual="/server/header.zh-cn.html" -->
+<!-- Parent-Version: 1.77 -->
+
+<!-- This file is automatically generated by GNUnited Nations! -->
+<title>自由系统发布指南（GNU FSDG）- GNU工程 - 
自由软件基金会</title>
+<link rel="alternate" title="自由的GNU/Linux发行版"
+      href="http://www.gnu.org/distros/distros.rss";
+      type="application/rss+xml" />
+
+<!--#include 
virtual="/distros/po/free-system-distribution-guidelines.translist" -->
+<!--#include virtual="/server/banner.zh-cn.html" -->
+<h2>自由系统发布指南（GNU FSDG）</h2>
+
+<!--#include virtual="/licenses/fsf-licensing.zh-cn.html" -->
+<h3 id="introduction">简介</h3>
+
+<p>本指南的目的是解释什么是一个可安装的系统发布（象<a
+href="/gnu/linux-and-gnu.html">GNU/Linux</a>发行版），以及发布怎æ 
·æ‰ç¬¦åˆ<a
+href="/philosophy/free-sw.html">自由</a>的要求，还包括帮助开发者
使其发行版符合自由的要求。</p>
+
+<p>本指南并不完备。我们讨论了目前已知的问题，但是肯定还有更多å
…¶ä»–é—®é¢˜ã€‚æˆ‘ä»¬ä¼šåœ¨é‡åˆ°é—®é¢˜æ—¶ä¸æ–­æ·»åŠ 进来。</p>
+
+<p>我们感谢Fedora项目对这些政策的专注，也感谢他们让我们使用å
…¶è®¸å¯è¯æŒ‡å—作为本文档的基础。</p>
+
+<h3 id="complete-distros">完整发行版</h3>
+
+<p>我们所指的发布是可以安装到电脑的系统。所以，它只包
括完整的、可用的发行版。如果一个发行版不完整&mdash;它需要进一步开发，或è€
…要求预先安装其他软件&mdash;那么它不包
括在此，即使它是自由软件。</p>
+
+<p>本要求以及以上自托管的要求对<em>小系统发布</em>列外，小系统发行版针对资源有限的设备开发，比如路由器。å›
 为给这些设备设计完备或自托管系统并不实际
，所以它们不必遵守以上要求，但是它们必
须可以在我们列出的自由完备系统发布上开发和制备，或许还需要和小系统发行版一起发行的自由工å
…·çš„支持。</p>
+
+<h3 id="license-rules">许可证规则</h3>
+
+<p>&ldquo;实际使用的信息&rdquo;包括软件、文档、字体和å…
¶ä»–有直接功能的数据。它不包
括美化（而不是功能）目的的艺术工作，也不包
括意见或判断。</p>
+
+<p>所有的实际使用信息都必
须有源文件形式可用。（&ldquo;源文件&rdquo;表示信息的形式有利于对它做修改。）</p>
+
+<p>信息和源文件必须按照合适的<a
+href="/philosophy/free-sw.html">自由许可证</a>提供。我们评价了一些特定许可证并将我们的决定列在<a
+class="reference"
+href="/licenses/license-list.html">许可证列表</a>处，å…
¶ä¸­ä¸“门列出了适用于软件、文档、字体和å…
¶ä»–有用工作的许可证。如果信息和源文件按ç…
§åˆ†ç¦»çš„许可证发布，只要å…
¶ä¸­è‡³å°‘有一个自由许可证，那么发布就是自由的；系统开发è€
…应该依照其中的自由许可证来发布或修改信息和源文件。</p>
+
+<p>自由发行版一定不能为了实用而引导用户获取任何非自由信息，也不能鼓励用户这么做。该发行版不应该带有非自由软件的资源库或安è£
…非自由软件的指导。该发行版也不应该指向不承诺只包
含自由软件的第三方资源库；即使它们目前只有自由软件，将来也可能会变化。该发行版的程序不应该推荐安è£
…非自由的插件、文档等等。</p>
+
+<p>比如，一个自由发行版一定不能有实现EME<sup><a
+href="#TransNote1">1</a></sup>åŠŸèƒ½çš„æµè§ˆå™¨ï¼Œè¯¥åŠŸèƒ½å°±æ˜¯ä¸ºåŠ 
è½½DRM<sup><a
+href="#TransNote2">2</a></sup>模块而设计的。</p>
+
+<p>è‡ªç”±ç³»ç»Ÿå‘å¸ƒåº”è¯¥æ˜¯è‡ªæ‰˜ç®¡çš„ã€‚å°±æ˜¯è¯´ï¼Œä½ å¿…
须能够利用系统提供的工å…
·æ¥å¼€å‘和构建这个系统。作为结果，自由系统发布不能包
含只能由非自由软件构建的自由软件。</p>
+
+<p>今天，大多数自由系统发行版都有很大的代ç 
é‡ï¼›è¦ç›´æŽ¥å®¡æ ¸å®ƒä»¬å¯¹å¤§å¤šæ•°å›¢é˜Ÿæ˜¯ä¸å®žé™…
的。过去，有些非自由软件意外地被包
æ‹¬åœ¨æŸäº›è‡ªç”±ç³»ç»Ÿå‘è¡Œç‰ˆä¸­ã€‚æˆ‘ä»¬å¹¶æœªå› 
此将这些发行版排除在自由系统发行版的列表之外；我们只是要求这些发行版的开发è€
…尽力避å…
éžè‡ªç”±è½¯ä»¶ï¼Œå¹¶æ‰¿è¯ºä¸€æ—¦å‘现有非自由程序就移除。</p>
+
+<p>有些许可证情
况值得那些创建或考虑创建自由软件发行版的开发者
ç‰¹åˆ«æ³¨æ„ï¼›ä»¥ä¸‹ç« èŠ‚ä¼šè®¨è®ºå®ƒä»¬ã€‚</p>
+
+<h3 id="nonfree-firmware">非自由固件</h3>
+
+<p>有些应用和驱动需要固件才能工作，而有时该固件只以目æ
 ‡ä»£ç çš„形式发布，å…
¶è®¸å¯è¯ä¹Ÿæ˜¯éžè‡ªç”±çš„。我们称这些固件为&ldquo;blobs&rdquo;。在大多数GNU/Linux系统中，ä½
 会发现它们在Linux内æ 
¸ä¸­å’ŒæŸäº›é©±åŠ¨è½¯ä»¶ä¸€èµ·å‘布。这些固件应该要从自由的系统发行版中被移除。</p>
+
+<p>Blobs有很多形式。有时，它们以单独的文件提供。有时，它们结合在驱动软件自身的代ç
 ä¸­&mdash;æ¯”å¦‚ï¼Œå®ƒä»¬å¯èƒ½ä»¥å¤§æ•°ç»„çš„å½¢å¼ç¼–ç ã€‚ä½†æ˜¯ï¼Œæ— 
è®ºå¦‚ä½•ç¼–ç ï¼Œä»»ä½•éžè‡ªç”±çš„å›ºä»¶éœ€è¦ä»Žè‡ªç”±ç³»ç»Ÿä¸­ç§»é™¤ã€‚</p>
+
+<p>（澄清
一下，不是驱动中的每个数组都是固件。在决定自由软件中的数组是否恰当之前，很重要的一点就是要理解å
…¶ç›®çš„。）</p>
+
+<p>Brian Brazil、Jeff Moe和Alexandre Oliva为官方的Linux内æ 
¸ç‰ˆæœ¬å¼€å‘了一系列<a class="reference"
+href="http://www.fsfla.org/svn/fsfla/software/linux-libre/scripts/";>移除非自由固件的脚本</a>。如果ä½
 
要开发自己的自由的GNU/Linux发行版，它们会很有用&mdash;虽然我们的建议是åŠ
 å…
¥å·²æœ‰çš„自由发行版的开发，而不要分散精力去开始一个新的发行版。也有完å
…¨ä¸å«éžè‡ªç”±blob的Linuxå†…æ ¸ç‰ˆæœ¬ï¼›ä½ å¯ä»¥åœ¨<a
+class="reference"
+href="http://directory.fsf.org/project/linux/";>自由软件目录</a>å­¦ä¹ 
更多关于该项目的知识。</p>
+
+<h3 id="non-functional-data">非功能性数据</h3>
+
+<p>非功能性数据不执行实际的工作，只是作为软件的装
饰而非软件的部件。所以，我们不坚持对非功能性数据应用自由的许可证。只要å
…¶è®¸å¯è¯å…è®¸ä½ 复制和再发布，这些数据可以包
含在自由系统发行版中，商用和非商用都行。比如，有些按GNU
+GPL发布的游戏引擎会带有游戏信息&mdash;虚拟世界的地图、游戏图形等等&mdash;它们以å
…
¨æ–‡å¤åˆ¶è®¸å¯è¯å‘布。此类数据可以作为自由系统发行版的一部分，å›
 为它们是非功能性的，即使其许可证不是自由许可证。</p>
+
+<h3 id="trademarks">å•†æ ‡</h3>
+
+<p>æœ‰äº›è½¯ä»¶å¸¦æœ‰å•†æ ‡ã€‚ä¾‹å¦‚ï¼Œç¨‹åºçš„åç§°å¯èƒ½æ˜¯å•†æ ‡ï¼Œæˆ–è€…
å…¶ç•Œé¢ä¼šæ˜¾ç¤ºå•†æ ‡æ ‡è¯†ã€‚é€šå¸¸ï¼Œä½¿ç”¨è¿™äº›å•†æ 
‡ä¼šå—到某种限制；在个别情况下，开发者
ä¼šè¢«è¦æ±‚ä»Žä»–ä»¬æ‰€ä¿®æ”¹çš„è½¯ä»¶ä¸­åˆ é™¤å•†æ ‡çš„å¼•ç”¨ã€‚</p>
+
+<p>在极端情况下，这些限制会使该程序实际
ä¸Šå˜æˆéžè‡ªç”±è½¯ä»¶ã€‚å¦‚æžœå•†æ ‡æ•£å¸ƒåœ¨æ•´ä¸ªæºä»£ç 
é‡Œï¼Œé‚£ä¹ˆè®©ä½ 在修改程序时移除它们有失公å…
ã€‚不过，如果实际的要求是合理的，自由系统发行版可以包
å«è¿™äº›ç¨‹åºï¼Œæ— è®ºæ˜¯å¦å¸¦æœ‰å•†æ ‡ã€‚</p>
+
+<p>类似地，发行版自己也可以带有特定的商æ 
‡ã€‚å¦‚æžœç§»é™¤å•†æ ‡ä¸ä¼šå½±å“åŠŸèƒ½ï¼Œé‚£ä¹ˆè¦æ±‚ä¿®æ”¹ç‰ˆç§»é™¤å•†æ 
‡å°±ä¸æ˜¯é—®é¢˜ã€‚</p>
+
+<p>但是，使用商æ 
‡æ¥é™åˆ¶é€å­—复制和重新发布整个发行版或å…
¶ä¸€éƒ¨åˆ†æ˜¯ä¸å¯æŽ¥å—的。</p>
+
+<h3 id="documentation">文档</h3>
+
+<p>自由系统发行版的所有文档必
须使用适当的自由许可证来发布。另外，它还必
须注意不能推荐非自由软件。</p>
+
+<p>一般地，帮助非自由软件用户更好地使用自由软件是可接受的，但是鼓励自由软件用户安è£
…非自由软件是不可接受的。</p>
+
+<p>例如，自由系统发行版可以有帮助用户设置双启动系统的文档。它可以解释如何访问专属操作系统、导å
…¥å…
¶è®¾ç½®ç­‰ç­‰ã€‚这些可以帮助人们在已有专属软件的计算机上安è£
…自由系统发行版，这是一件好事。</p>
+
+<p>向人们阐述如何在该系统上安装
非自由软件的指导文档或者论及这æ 
·åšå¯èƒ½ä¼šå¸¦æ¥æ–¹ä¾¿æ˜¯ä¸å¯æŽ¥å—的。</p>
+
+<p>作为界限，明确和严肃地告诫用户不要使用非自由软件就是站在可接受的一边。</p>
+
+<h3 id="patents">专利</h3>
+
+<p>自由软件开发者和发行者实际
上不可能知道软件是否侵犯了某个专利：专利太多了，专利在各个国家又有所不同，专利的描述就是要让人难以判断它究竟涵盖哪些东西，要辨别哪个是有效的æƒ
…况不是简单的事情
。所以，我们一般不要求自由发行版排除可能带有专利风险的软件。另一方面，我们也不反对发行è€
…为避免专利风险而排除一些软件。</p>
+
+<h3 id="no-malware">没有恶意软件</h3>
+
+<p>发行版必须没有DRM、没有后门、没有间谍软件。</p>
+
+<h3 id="mistakes">修复错误的承诺</h3>
+
+<p>大多数发行版的开发团队没有资源来针对所有这些条件进行å
…
¨é¢æ£€æŸ¥ã€‚我们也没有。所以，发行版有时可能带有错误：非自由软件漏了进来，等等。我们不会å›
 为带有错误而拒绝一个发行版。我们的要求是发行版开发者
要坚定的承诺他们会在接到报告后及时解决问题。</p>
+
+<h3 id="maintenance">维护</h3>
+
+<p>要进å…
¥åˆ—表，发行版应该有活跃的维护，而且应该给GNU工程一个明确和确定的报告非自由软件的途径。它还应该在解决问题后通知我们。</p>
+
+<h3 id="name-confusion">名称的困扰</h3>
+
+<p>我们不会列出那些名字会和非自由发行版混淆的发行版。比如，如果Foobar
+Light是自由发行版，而Foobar是非自由发行版，那么我们就不会列出Foobar
 Lightã€‚å› 
为我们认为它们之间的区别会在沟通过程中消失。</p>
+
+<p>特别需要指出，自由发行版的主要名称（&ldquo;Foobar&rdquo;，为例）不应该和任何非自由发行版名称近似。</p>
+
+<p>æœ‰äº›äººå¯èƒ½ä¼šæƒ³åœ¨è‡ªç”±å‘è¡Œç‰ˆä¸Šæ·»åŠ 
&ldquo;GNU&rdquo;的名字来区别于非自由发行版。这有两个问题。第一，两个名字的区别还是不够大，å›
 为主要的名字还是类似的。</p>
+
+<p>第二，这会促进对&ldquo;GNU&rdquo;含义的误解。<a
+href="/gnu/linux-and-gnu.html">GNU是一个操作系统</a>，典型的情
况是使用Linux内æ 
¸ï¼Œå¹¶ä¸”基本上所有的叫做&ldquo;Linux&rdquo;的发行版实际
上都是GNU/Linux发行版。在这种情
况下，<em>两个</em>版本都是GNU/Linux，而省去å…
¶ä¸­ä¸€ä¸ªçš„&ldquo;GNU&rdquo;就会形成误导。</p>
+
+<h3 id="upstream">å¦‚æžœä½ æ˜¯ä¸‹æ¸¸ï¼Œè¯·å’Œä¸Šæ¸¸æ²Ÿé€š</h3>
+
+<p>向某个GNU软件包提交过缺陷报告的发行版开发者（或å…
¶ä»–äººï¼‰ï¼šå¦‚æžœè½¯ä»¶åŒ…ç»´æŠ¤è€…å¯¹ä½ 
的缺陷报告没有在合理的时间内给予回复（请至少å…
è®¸ä¸¤ä¸ªæ˜ŸæœŸï¼‰ï¼Œä½ 
可以向&lt;address@hidden&gt;å†™ä¿¡å‡çº§ç¼ºé™·æŠ¥å‘Šã€‚å¦‚æžœä½ 
æ²¡æœ‰çœ‹åˆ°è¯¥è½¯ä»¶åŒ…ç»´æŠ¤è€…è¿‘æœŸçš„æ´»è·ƒæƒ…å†µï¼Œé‚£ä¹ˆä½ å°¤å…
¶è¦å‡çº§ç¼ºé™·æŠ¥å‘Šã€‚</p>
+
+<h3 id="teaching">请教育用户自由软件</h3>
+
+<p>要建立长久的自由，仅仅
给予用户自由是不够的。教育用户自由意味着什么以及如何获得自由也是å¿
…è¦çš„ã€‚å› 
此，我们建议并敦促自由发行版在登录屏幕、在登录之后的默认桌面，突出地宣告å
…
³äºŽè‡ªç”±çš„声明，比如&ldquo;本系统是尊重自由的自由软件&rdquo;或è€
…类似的说明，并展示指向gnu.org或gnu.org/philosophy的链接或图æ 
‡ï¼Œä»¥å‘ŠçŸ¥ç”¨æˆ·å“ªé‡Œå¯ä»¥èŽ·å–关于该声明的进一步信息。</p>
+
+<h3 id="words-to-avoid">请避免重复一些鼓吹和迷惑性语言</h3>
+
+<p>请参考我们的<a
+href="/philosophy/words-to-avoid.html">需要避å…
çš„词汇</a>列表，这些词汇有的是带偏见的、有些是方向不对的，还有些是误导性的。请尽量在ä½
 的公众阐述和讨论中避免这些词汇。</p>
+
+<h3 id="final-notes">最后说明</h3>
+
+<p>我们尽我们所知维护着一个<a
+href="/distros/free-distros.html">自由的GNU系统发行版</a>列表。如果ä½
 所知的自由发行版没有列出，请让其开发者写信给&lt;<a
+class="reference"
+href="mailto:address@hidden";>address@hidden</a>&gt;，并给出系统介绍和网站链接。</p>
+
+<p>我们还列出了<a
+href="/distros/free-non-gnu-distros.html">自由的非GNU系统发行版</a>，它们也遵从同æ
 ·çš„道德条件。</p>
+
+<p>å¦‚æžœä½ å¯¹æœ¬æŒ‡å—æœ‰é—®é¢˜æˆ–å»ºè®®ï¼Œè¯·å¤§èƒ†å†™ä¿¡ç»™&lt;<a 
class="reference"
+href="mailto:address@hidden";>address@hidden</a>&gt;ã€‚æˆ‘ä»¬å¸Œæœ›ä½ 
çš„é—®é¢˜æˆ–å»ºè®®èƒ½å¤Ÿå¸®åŠ©æ‰€æœ‰äººæ›´å¥½åœ°ç†è§£è¿™ä¸ªæ¦‚å¿µï¼Œå› 
ä¸ºå®ƒå¯¹è‡ªç”±ç³»ç»Ÿå‘è¡Œç‰ˆæ˜¯é‡è¦çš„ï¼Œè€Œæˆ‘ä»¬æœŸå¾…å°†æ¥èƒ½å¤Ÿå®£ä¼ 
æ›´å¤šè¿™æ ·çš„å‘è¡Œç‰ˆã€‚</p>
+
+<div class="translators-notes">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.-->
+<h3>译注</h3>
+<ol>
+<li id="TransNote1">EMEï¼Œåª’ä½“åŠ å¯†æ‰©å±•ã€‚</li>
+<li id="TransNote2">DRM，数字版权管理。</li>
+</ol></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; 2014, 2015, 2017 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.gnu.org/projects/www-zh-cn/";>&lt;CTT&gt;</a>，2017。</div>
+
+<p class="unprintable"><!-- timestamp start -->
+最后更新：
+
+$Date: 2017/10/28 11:59:24 $
+
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>

Index: po/free-system-distribution-guidelines.zh-cn-en.html
===================================================================
RCS file: po/free-system-distribution-guidelines.zh-cn-en.html
diff -N po/free-system-distribution-guidelines.zh-cn-en.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ po/free-system-distribution-guidelines.zh-cn-en.html        28 Oct 2017 
11:59:27 -0000      1.1
@@ -0,0 +1,363 @@
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.77 -->
+<title>Free System Distribution Guidelines (GNU FSDG) - GNU Project - Free 
Software Foundation</title>
+<link rel="alternate" title="Free GNU/Linux distributions"
+      href="http://www.gnu.org/distros/distros.rss";
+      type="application/rss+xml" />
+<!--#include 
virtual="/distros/po/free-system-distribution-guidelines.translist" -->
+<!--#include virtual="/server/banner.html" -->
+<h2>Free System Distribution Guidelines (GNU FSDG)</h2>
+<!--#include virtual="/licenses/fsf-licensing.html" -->
+
+<h3 id="introduction">Introduction</h3>
+
+<p>The purpose of these guidelines is to explain what it means for an
+installable system distribution (such as a <a 
href="/gnu/linux-and-gnu.html">GNU/Linux</a> distribution) to
+qualify as <a href="/philosophy/free-sw.html">free</a> (libre), and
+help distribution developers make their distributions qualify.</p>
+
+<p>These guidelines are not complete.  We have mentioned the issues we
+are aware of now, but we're sure there are more.  We will add them
+when we come across them.</p>
+
+<p>We would like to thank the Fedora Project for their help in focusing
+these policies, and allowing us to use their own distribution license
+guidelines as a basis for this document.</p>
+
+<h3 id="complete-distros">Complete Distros</h3>
+
+<p>Our list of distributions is a guide for systems you can install in
+a computer.  Therefore, it only includes distributions that are
+complete in themselves and ready to use.  If a distribution is
+incomplete &mdash; if it requires further development, or presupposes
+installing other software as well &mdash; then it is not listed here,
+even if it is free software.</p>
+
+<p>An exception to this requirement and to the self-hosting
+requirement above is for <em>small system distributions</em>, which
+are distros designed for devices with limited resources, like a
+wireless router for example. Free small system distributions do not
+need to be self-hosting or complete, because it is impractical to do
+development on such a system, but it must be developable and buildable
+on top of a free complete system distribution from our list of
+distributions, perhaps with the aid of free tools distributed
+alongside the small system distribution itself.</p>
+
+<h3 id="license-rules">License Rules</h3>
+
+<p>&ldquo;Information for practical use&rdquo;
+includes software, documentation, fonts, and other data that has
+direct functional applications.  It does not include artistic works
+that have an aesthetic (rather than functional) purpose, or statements
+of opinion or judgment.</p>
+
+<p>All information for practical use in a free distribution must be
+available in source form.  (&ldquo;Source&rdquo; means the form of the
+information that is preferred for making changes to it.)</p>
+
+<p>The information, and the source, must be provided under an
+appropriate <a href="/philosophy/free-sw.html">free license</a>.  We
+evaluate specific licenses and list our determinations
+in <a class="reference" href="/licenses/license-list.html">our license
+list</a>, with separate sections for licenses that are suitable for
+software, documentation, fonts, and other useful works.  If such a
+work is released under a disjunction of licenses, the work is free as
+long as at least one of its licenses is free; the system developers
+should follow the terms of the applicable free license(s) when they
+distribute and/or modify it.</p>
+
+<p>A free system distribution must not steer users towards obtaining
+any nonfree information for practical use, or encourage them to do so.
+The system should have no repositories for nonfree software and no
+specific recipes for installation of particular nonfree programs. Nor
+should the distribution refer to third-party repositories that are not
+committed to only including free software; even if they only have free
+software today, that may not be true tomorrow.  Programs in the system
+should not suggest installing nonfree plugins, documentation, and so
+on.</p>
+
+<p>For instance, a free system distribution must not contain browsers
+that implement EME, the browser functionality designed to load DRM
+modules.</p>
+
+<p>A free system distribution should be self-hosting.  This means that
+you must be able to develop and build the system with tools that the
+system provides you.  As a result, a free system distribution cannot
+include free software that can only be built by using nonfree
+software.</p>
+
+<p>There's a lot of code in most free system distributions today; the
+amount of effort it would take to audit it all directly is impractical
+for most teams.  In the past, some nonfree code has accidentally been
+included in free system distributions.  We don't de-list distributions
+because of this; instead, we only ask that a distribution's developers
+make a good faith effort to avoid including nonfree software, and
+commit themselves to removing such programs if any are discovered.</p>
+
+<p>Certain kinds of license situations merit special attention for people
+creating or considering free software distributions; those are
+discussed in the sections below.</p>
+
+<h3 id="nonfree-firmware">Nonfree Firmware</h3>
+
+<p>Some applications and drivers require firmware to function, and
+sometimes that firmware is distributed only in object code form, under
+a nonfree license.  We call these firmware programs
+&ldquo;blobs.&rdquo; On most GNU/Linux systems, you'll typically find
+these accompanying some drivers in the kernel Linux.  Such firmware
+should be removed from a free system distribution.</p>
+
+<p>Blobs can take many forms.  Sometimes, they will be provided in
+separate files.  Other times, they may be incorporated into the source
+of the driver itself&mdash;for example, it could be encoded as a large
+array of numbers.  But no matter how it's encoded, any nonfree
+firmware needs to be removed from a free system.</p>
+
+<p>(To be clear, not every array of numbers in a driver is firmware.
+It's important to understand the purpose of the data before deciding
+whether or not it's appropriate for a free system.)</p>
+
+<p>Brian Brazil, Jeff Moe, and Alexandre Oliva have developed a series
+of <a class="reference"
+href="http://www.fsfla.org/svn/fsfla/software/linux-libre/scripts/";>scripts
+to remove nonfree firmware</a> from a stock version of the Linux kernel.
+You may find them helpful if you would like to develop your own free
+GNU/Linux distribution&mdash;although we recommend joining development
+of an existing free distro rather than fragmenting effort by starting a
+new one.  The complete source for a blob-free version of the Linux
+kernel is also available; you can learn more about this project from the
+<a class="reference" href="http://directory.fsf.org/project/linux/";>Free
+Software Directory</a>.</p>
+
+<h3 id="non-functional-data">Non-functional Data</h3>
+
+<p>Data that isn't functional, that doesn't do a practical job, is
+more of an adornment to the system's software than a part of it.
+Thus, we don't insist on the free license criteria for non-functional
+data.  It can be included in a free system distribution as long as its
+license gives you permission to copy and redistribute, both for
+commercial and non-commercial purposes.  For example, some game
+engines released under the GNU GPL have accompanying game
+information&mdash;a fictional world map, game graphics, and so
+on&mdash;released under such a verbatim-distribution license.  This
+kind of data can be part of a free system distribution, even though
+its license does not qualify as free, because it is non-functional.</p>
+
+<h3 id="trademarks">Trademarks</h3>
+
+<p>Trademarks are associated with some software.  For example, the
+name of a program may be trademarked, or its interface may display a
+trademarked logo.  Often, the use of these marks will be controlled
+in some way; in particular, developers are commonly asked to remove
+references to the trademark from the software when they modify
+it.</p>
+
+<p>In extreme cases, these restrictions may effectively render the
+program nonfree.  It is unfair for someone to ask you to remove a
+trademark from modified code if that trademark is scattered all
+throughout the original source.  As long as the practical
+requirements are reasonable, however, free system distributions may
+include these programs, either with or without the trademarks.</p>
+
+<p>Similarly, the distribution itself may hold particular trademarks.
+It is not a problem if modification requires removal of these
+trademarks, as long as they can readily be removed without losing
+functionality.</p>
+
+<p>However, it is unacceptable to use trademarks to restrict verbatim
+copying and redistribution of the whole distribution, or any part.</p>
+
+<h3 id="documentation">Documentation</h3>
+
+<p>All the documentation in a free system distribution must be released
+under an appropriate free license.  Additionally, it must take care
+not to recommend nonfree software.</p>
+
+<p>In general, something that helps people who already use nonfree
+software to use the free software better with it is acceptable, but
+something that encourages users of the free software to install
+nonfree software is not.</p>
+
+<p>For example, a free system distribution may have documentation for
+users setting up dual boot systems.  It could explain how to access
+filesystems of the proprietary operating system, import settings
+from it, and so on.  That would be helping people install a free
+system distribution on a machine which already has proprietary
+software, which is good.</p>
+
+<p>What would be unacceptable is for the documentation to give people
+instructions for installing a nonfree program on the system, or
+mention conveniences they might gain by doing so.</p>
+
+<p>For a borderline case, a clear and serious exhortation not to use the
+nonfree program would move it to the acceptable side of the line.</p>
+
+<h3 id="patents">Patents</h3>
+
+<p>It is effectively impossible for free software developers and
+distributors to know whether or not a given piece of software
+infringes any patents: there are too many of them, they vary from
+country to country, they're often worded so as to make it hard to tell
+what they do or don't cover, and it isn't easy to tell which ones are
+valid.  Therefore, we don't generally ask free system distributions to
+exclude software because of possible threats from patents.  On the
+other hand, we also don't object if a distributor chooses to omit some
+software in order to avoid patent risk.</p>
+
+<h3 id="no-malware">No Malware</h3>
+
+<p>The distro must contain no DRM, no back doors, and no spyware.</p>
+
+<h3 id="mistakes">Commitment to Correct Mistakes</h3>
+
+<p>Most distribution development teams don't have the resources to
+exhaustively check that their distribution meet all these criteria.
+Neither do we.  So we expect distros to occasionally contain mistakes:
+nonfree software that slipped through, etc.  We don't reject a
+distribution over mistakes.  Our requirement is for the distribution
+developers to have a firm commitment to promptly correct any mistakes
+that are reported to them.</p>
+
+<h3 id="maintenance">Maintenance</h3>
+
+<p>To be listed, a distribution should be actively maintained,
+and should give the GNU Project a clear and specific way to report problems
+of nonfree software that we find out about.  It should also
+inform us when the problems we have reported are fixed.</p>
+
+<h3 id="name-confusion">Name Confusion</h3>
+
+<p>We will not list a distribution whose name makes confusion with
+nonfree distributions likely.  For example, if Foobar Light is a free
+distribution and Foobar is a nonfree distribution, we will not list
+Foobar Light.  This is because we expect that the distinction between
+the two would be lost in the process of communicating the message.</p>
+
+<p>In particular, the principal name of the free distribution
+(&ldquo;Foobar&rdquo;, in this example) should not be part of the name
+of any nonfree distribution.</p>
+
+<p>Some people have thought of adding the name &ldquo;GNU&rdquo; to a
+free distro name to distinguish it from a nonfree one.  This has two
+problems.  First, the two names would not be sufficiently different,
+since the principal word in both names would be the same.</p>
+
+<p>Second, this would promote a misunderstanding of what
+&ldquo;GNU&rdquo; means.  <a href="/gnu/linux-and-gnu.html">GNU is an
+operating system</a>, typically used with Linux as the kernel, and
+essentially all so-called &ldquo;Linux&rdquo; distributions are really
+GNU/Linux distributions.  In this scenario,
+<em>both</em> versions are GNU/Linux, and it would be misleading to
+omit &ldquo;GNU&rdquo; from the name of one of them.</p>
+
+<h3 id="upstream">Contacting Upstream If You're Downstream</h3>
+
+<p>For distro developers (or anyone else) who have sent an important bug
+report for a GNU package: if it has gone unheeded by the package
+maintainer after a reasonable time (please allow at least two weeks),
+you can escalate the bug by writing to &lt;address@hidden&gt;.
+This is especially warranted if you can't find evidence of recent
+activity by the package maintainer.</p>
+
+<h3 id="teaching">Please Teach Users about Free Software</h3>
+
+<p>To establish lasting freedom, just giving users freedom isn't
+sufficient.  It is necessary also to teach them to understand what it
+means and to demand it.  Thus, we suggest and urge that free distros
+announce prominently on the screen, before login and on the default
+desktop after login, a prominent statement about freedom, such as
+&ldquo;This system is freedom-respecting free/libre software&rdquo; or
+something comparable, and to present a link or icon pointing at
+gnu.org or gnu.org/philosophy for further information about the
+issue.</p>
+
+<h3 id="words-to-avoid">Please Avoid Repeating Propaganda and Confusion</h3>
+
+<p>Please see our list
+of <a href="/philosophy/words-to-avoid.html">words to avoid</a>, which
+are either biased, misguided or misleading, and try to avoid them in
+your public statements and discussions with the public.</p>
+
+<h3 id="final-notes">Final Notes</h3>
+
+<p>We maintain a list of the <a href="/distros/free-distros.html">free
+GNU system distributions</a> we know about.  If you know about a free
+distribution that isn't listed there, please ask its developers write
+to &lt;<a class="reference"
+href="mailto:address@hidden";>address@hidden</a>&gt; with a description of
+their system and a link to their web page.</p>
+
+<p>We also list <a href="/distros/free-non-gnu-distros.html">free
+non-GNU system distributions</a> on the same ethical conditions.</p>
+
+<p>If you have questions or comments about these guidelines
+themselves, feel free to send those to &lt;<a class="reference"
+href="mailto:address@hidden";>address@hidden</a>&gt;.  We hope
+that they help everyone better understand the issues that are important
+for free system distributions, and we look forward to promoting more
+of them in the future.</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; 2014, 2015, 2017 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: 2017/10/28 11:59:27 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>