www/software devel.zh-cn.html po/devel.zh-cn.po...

[GNUN]

CVSROOT:        /web/www
Module name:    www
Changes by:     GNUN <gnun>     17/09/04 10:29:56

Modified files:
        software       : devel.zh-cn.html 
        software/po    : devel.zh-cn.po 
Added files:
        software/po    : devel.zh-cn-en.html 

Log message:
        Automatic update by GNUnited Nations.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/software/devel.zh-cn.html?cvsroot=www&r1=1.16&r2=1.17
http://web.cvs.savannah.gnu.org/viewcvs/www/software/po/devel.zh-cn.po?cvsroot=www&r1=1.22&r2=1.23
http://web.cvs.savannah.gnu.org/viewcvs/www/software/po/devel.zh-cn-en.html?cvsroot=www&rev=1.1

Patches:
Index: devel.zh-cn.html
===================================================================
RCS file: /web/www/www/software/devel.zh-cn.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -b -r1.16 -r1.17
--- devel.zh-cn.html    26 May 2015 05:58:19 -0000      1.16
+++ devel.zh-cn.html    4 Sep 2017 14:29:56 -0000       1.17
@@ -1,38 +1,24 @@
-<!--#set var="PO_FILE"
- value='<a href="/software/po/devel.zh-cn.po">
- http://www.gnu.org/software/po/devel.zh-cn.po</a>'
- --><!--#set var="ORIGINAL_FILE" value="/software/devel.html"
- --><!--#set var="DIFF_FILE" value=""
- --><!--#set var="OUTDATED_SINCE" value="2012-01-12" --><!--#set 
var="ENGLISH_PAGE" value="/software/devel.en.html" -->
-
+<!--#set var="ENGLISH_PAGE" value="/software/devel.en.html" -->
  
 <!--#include virtual="/server/header.zh-cn.html" -->
+<!-- Parent-Version: 1.77 -->
 
 <!-- This file is automatically generated by GNUnited Nations! -->
-<!--#set var="DISABLE_TOP_ADDENDUM" value="yes" -->
-
-<title>GNU开发资源 - GNU工程 - 自由软件基金会(FSF)</title>
+<title>GNU开发资源 - GNU工程 - 自由软件基金会</title>
 
-<!-- Fixed by hand on June 26, 2014:
-     - disable top-addendum,
-     - remove #translations,
-     - translist before banner,
-     - partially update footer.
--->
 <!--#include virtual="/software/po/devel.translist" -->
 <!--#include virtual="/server/banner.zh-cn.html" -->
-<!--#include virtual="/server/outdated.zh-cn.html" -->
- 
 <h2>GNU开发资源</h2>
 
-<p>本页面旨在为GNU工程的开发人员介绍GNU为他们提供的服务。想要了解GNU维护人员的详细权利和责任，请参看<a
-href="/prep/maintain">GNU维护人员参考信息</a>。且需遵循<a
-href="/prep/standards/">GNUç¼–ç è§„èŒƒ</a>。同时，也许这篇<a
+<p>本页面旨在为GNU工程的开发人员介绍GNU为他们提供的诸多开发资源。想要了解GNU维护人员的详细职责，请参看<a
+href="/prep/maintain">GNU维护人员参考信息</a>，且需遵循<a
+href="/prep/standards/">GNUç¼–ç è§„èŒƒ</a>。同时，这篇<a
+href="/software/maintainer-tips.html">GNU维护人员技巧</a>和这篇<a
 href="/help/evaluation.html#whatmeans">什么是GNU软件包
</a>也会有帮助。</p>
 
 <p>随着能运行<a 
href="/gnu/linux-and-gnu.html">GNU/Linux</a>的廉价计算机的丰富,
 ä»¥åŠå› ç‰¹ç½‘è®¿é—®æœåŠ¡å®žç”¨æ€§çš„å¢žå¼º,
-许多GNU志愿者今天拥有他们所需要的å…
¨éƒ¨è®¡ç®—机设施。可是，拥有中央计算机仍然有它的优点，在这儿GNU志愿è€
…们可以在一起工作而不必把他们自己机器的权限给别人。 
</p>
+许多GNU志愿者今天拥有他们所需要的å…
¨éƒ¨è®¡ç®—机设施。可是，拥有中央计算机仍然有它的优点，在这儿，GNU志愿è€
…们可以在一起工作而不必把他们自己机器的权限给别人。 
</p>
 
 <p>å› ä¸ºè¿™ä¸ªåŽŸå› 
，自由软件基金会(FSF)鼓励GNU软件工程像在家一æ 
·ä½¿ç”¨gnu.org上的机器。对这些机器的使用也间接的有利于GNU工程，通过增åŠ
 公众对GNUçš„æ³¨æ„ï¼Œä¼ 
播为了有利于每一个人的在一起工作的思想。</p>
 
@@ -41,7 +27,7 @@
 
 <p>倘若您在开发GNU的官方软件，我们强烈建议您使用<a
 href="http://savannah.gnu.org/";>Savannah</a>为您提供的å…
¬å¼€çš„版本控制系统。若要使用它，首先请<a
-href="https://savannah.gnu.org/account/register.php";>创建一个个人帐号</a>。之后，您可以选择一个版本控制系统，创建一些网页，给代ç
 è´¡çŒ®è€…不同权限，以及其他的相关设置。</p>
+href="https://savannah.gnu.org/account/register.php";>创建一个个人账号</a>。之后，您可以选择一个版本控制系统，创建一些网页，给代ç
 è´¡çŒ®è€…不同权限，以及其他的相关设置。</p>
 
 
 <h3 id="MailLists">邮件列表</h3>
@@ -49,26 +35,26 @@
 <p>我们为GNU软件包提供必须的邮件列表，包
括手动管理列表和自动管理列表。 </p>
 
 <p>当GNU软件包在<a href="http://savannah.gnu.org/";>Savannah</a>注册时,
-一个网络界面允许开发者建立和管理该软件包
专用的邮件列表。 </p>
+会有一个网络界面允许开发者建立和管理该软件包
专用的邮件列表。 </p>
 
-<p>对于每个GNU软件，倘若å…
¶åä¸º<em>name</em>，那么至少得有个叫做<code>bug-<em>name</em>@gnu.org</code>address@hidden</p>
+<p>对于每个GNU软件，倘若å…
¶åä¸º<em>name</em>，那么至少得有个叫做<code>bug-<em>name</em>@gnu.org</code>address@hidden</p>
 
-<p>软件包能拥有用于公告、寻求帮助、放入相关的源代ç 
ã€ç”¨æˆ·é—´è®¨è®ºä»¥åŠå…¶ä»–软件包的维护者
认为有用的邮件列表。</p>
+<p>软件包可以拥有用于公告、寻求帮助、放入相关的源代ç 
ã€ç”¨æˆ·é—´è®¨è®ºä»¥åŠå…¶ä»–软件包的维护者
认为有用的邮件列表。</p>
 
-<p>自动管理的邮件列表档案保存在<a
-href="http://lists.gnu.org/";>http://lists.gnu.org</a>上，也可以通过列表管理程序访问。手动维护的列表档案保存在<code>/come/archive</code>上。</p>
+<p>自动管理的邮件列表归档于<a 
href="http://lists.gnu.org/";>lists.gnu.org</a>（<a
+href="rsync://lists.gnu.org/">mbox的归档可以通过rsync</a>和<a
+href="ftp://lists.gnu.org/";>ftp</a>获取），也可以通过列表管理获取。手动管理的邮件列表归档于GNU机器的<code>/com/archive</code>。</p>
 
-<p>当邮件列表太大了而不能证明å…
¶æœ‰æ•ˆæ€§ï¼Œæˆ‘们可以建立一个gnu.*的新组，它可以双方向连接到邮件列表中。</p>
+<p>当邮件列表太大了而不能证明å…
¶æœ‰æ•ˆæ€§ï¼Œæˆ‘们可以建立一个<code>gnu.*</code>的新闻组，它双向链接到邮件列表中。</p>
 
 
-<h3 id="WebServer">Web服务器</h3>
+<h3 id="WebServer">网页服务</h3>
 
 <p>GNU的主站点位于<a
-href="/">http://www.gnu.org/</a>，我们强烈建议GNU软件包
使用<tt>http://www.gnu.org/software/</tt><i>package</i>
-作为它们的官方首页。</p>
+href="http://www.gnu.org/";>http://www.gnu.org/</a>。我们强烈建议GNU软件åŒ
…
使用<tt>http://www.gnu.org/software/</tt><i>package</i>作为它们的官方首页。</p>
 
-<p>使用Savannah，开发人员可以使用上述url，通过CVS的&ldquo;网页仓库&rdquo;来创建和维护他们的项目主页。这个仓库和软件åŒ
…的主仓库是分开的。<a
-href="/prep/maintain/maintain.html#Web-Pages">å…
³äºŽGNU网页维护的更多信息</a></p>
+<p>使用Savannah，开发人员可以使用上述url，通过CVS的&ldquo;网页仓库&rdquo;来创建和维护他们的项目主页。这个仓库和软件åŒ
…的主仓库（它可以使用å…
¶ä»–受支持的版本管理程序）是分开的。请参看<a
+href="/prep/maintain/maintain.html#Web-Pages">å…
³äºŽGNU网页维护的更多信息。</a></p>
 
 
 <h3 id="FTP">FTP</h3>
@@ -84,16 +70,17 @@
 
href="/prep/maintain/maintain.html#Automated-FTP-Uploads">GNU维护人员手册</a>中，描述了详细的FTP上ä¼
 的整个流程。这在上述服务器中均适用。</p>
 
 
-<h3 id="LoginAccounts">登录帐号</h3>
+<h3 id="LoginAccounts">登录账号</h3>
 
-<p>倘若GNU软件开发人员需要shell登录，我们可以为他们提供此服务，让他们登录到GNU的机器上。不过需要注意，使用这æ
 ·çš„登录账户既拥有权利，也同时肩负着责任。这些帐号必
须只能用来做和GNU工程相关的工作。详情参考<a
-href="README.accounts.html">如何获得登录帐号</a>。</p>
+<p>倘若GNU软件开发人员需要shell登录，我们可以为他们提供此服务，让他们登录到GNU的机器上。不过需要注意，使用这æ
 ·çš„登录账户既拥有权利，也同时肩负着责任。这些账号必
须只能用来做和GNU工程相关的工作。详情参考<a
+href="README.accounts.html">如何获得登录账号</a>。</p>
 
 <p>在所登陆的计算机上，<a
-href="/software/gsrc/">gsrc</a>的开发者们维护着一个当前GNU软件包
的资料库。这些软件均直接编译自各个软件的源代ç 
ã€‚若要使用，请<tt>/gd/gnu/gnusys/live/setup</tt>。</p>
+href="/software/gsrc/">gsrc</a>的开发者们维护着一个当前GNU软件包
的资料库。这些软件均直接编译自各个软件的源代ç 
ã€‚若要使用，请输入命令source
+<tt>/gd/gnu/gnusys/live/setup</tt>。</p>
 
 <p>您也可以<a
-href="http://www.fsf.org/about/systems/sending-mail-via-fencepost";>使用一个GNU帐号来发邮件</a></p>
+href="http://www.fsf.org/about/systems/sending-mail-via-fencepost";>使用一个GNU账号来发邮件</a>。</p>
 
 
 <h3 id="Hydra">Hydra: 持续构建（Continuous 
builds）与可移植性测试</h3>
@@ -104,29 +91,38 @@
 <p><a href="http://nixos.org/hydra/";>Hydra</a>是一款基于<a
 href="http://nixos.org/nix/";>Nix</a>的自由的持续构建工具。<a
 
href="http://nixos.org/hydra/";>代尔夫特理工大学Hydra项目组</a>的管理员们æ
…·æ…¨åœ°ä¸º<a
-href="http://hydra.nixos.org/project/gnu";>GNU项目提供了一片空间</a>。</p>
+href="http://hydra.nixos.org/project/gnu";>GNU项目提供了一片空间</a>。Hydra管理的项目会对每次<em>提交</em>或依赖å
…³ç³»æ›´æ”¹ï¼ˆä¾èµ–关系<em>包括</em>æ 
‡å‡†æž„建环境，就是指GCC更新、GNU&nbsp;make更新等等）进行重新集成。</p>
+
+<p>目前，Hydra支持在GNU/Linux（<tt>i686</tt>和<tt>x86_64</tt>）、FreeBSD、Darwin、Solaris以及Cygwin下构建软件，同时也支持交叉编译å
…
¶ä»–体系结构或MinGW上的GNU/Hurd、GNU/Linux系统。它提供利用LCOV生成的代ç
 è¦†ç›–æŠ¥è¡¨ã€‚é™¤äº†æºä»£ç åŽ‹ç¼©åŒ…å’ŒNix包
以外，它还可以为基于<code>deb</code>-或<code>RPM</code>软件包
的发行版打包。软件包
可以基于最新的依赖库来构建。比如，GnuTLS需要用到GNU&nbsp;libtasn1和GNU&nbsp;libcrypt，那么就可以基于这两个库的最新版本来构建它。</p>
+
+<p>除了<a
+href="http://hydra.nixos.org/project/gnu";>网络界面</a>以外，Hydra可以在项目构建状态发生改变的时候，通过电子邮件来提醒管理人员&mdash;比如，从<code>SUCCEEDED</code>状态变为了<code>FAILED</code>）。当构建失败时，日志和构建æ
 ‘可以通过网络界面获取；后者å…
è®¸å®¡æŸ¥å·²åˆ›å»ºçš„文件（比如，<code>config.log</code>或<code>testsuite.log</code>），这æ
 ·å°±å¯ä»¥èŽ·å¾—处理故障的信息。</p>
+
+<p>任何一个GNU软件包
都可以申请在Hydra上的一片空间。每个软件包必
须提供一份&ldquo;构建策略&rdquo;。该策略使用Nix语言编写（用Nix的术语来说，就是<em>Nix表达式</em>）。<a
+href="http://git.savannah.gnu.org/cgit/nix/hydra-recipes.git";>GNU项目通用Nix表达式范本</a>可以在git上获取。对于简单的项目来说，使用æ
 
‡å‡†çš„GNU构建程序的话，比如Automake和Autoconf，这份构建策略通常非常简单。比如可以参考这个<a
+href="http://git.savannah.gunu.org/cgit/nix/hydra-recipes.git/tree/patch/release.nix";>GNU&nbsp;Patch构建策略</a>。对此您有任何问题，欢迎向<a
+href="mailto:address@hidden";>address@hidden</a>提问。</p>
+
+<p>在编写完您的构建策略之后，请把它发至<a
+href="http://lists.gnu.org/mailman/listinfo/hydra-users";>address@hidden</a>，并要求把它åŠ
 入到Hyra。同时确保它是<a
+href="https://savannah.gnu.org/projects/hydra-recipes/";><code>hydra-recipes</code>Savannah项目</a>的成员。这æ
 ·ä½ 就可以直接定制自己项目的构建工作了。</p>
+
+<p> 关于Hydra的技术信息，请参考<a
+href="http://hydra.nixos.org/job/hydra/trunk/tarball/latest/download-by-type/doc/manual";>Hydra手册</a>（<a
+href="http://hydra.nixos.org/job/hydra/trunk/tarball/latest/download-by-type/doc-pdf/manual";>PDF</a>）。更多细节，请参考<a
+href="http://hydra.nixos.org/job/nix/trunk/tarball/latest/download/1/nix/manual.html";>Nix手册</a>。</p>
 
-<p>现在，Hydra支持在GNU/Linux（i686和x86_64），FreeBSD，Darwin，以及Cygwin下构建软件，同时也支持交叉编译到å
…¶ä»–体系结构或MinGW上的GNU/Hurd,
-GNU/Linux系统。它提供利用LCOV的代ç 
è¦†ç›–æŠ¥è¡¨ç”Ÿæˆã€‚é™¤äº†æºä»£ç åŽ‹ç¼©åŒ…ï¼ŒNix包
以外，它还可以为基于<code>deb</code>-或<code>RPM</code>软件包
的发行版打包。软件包
可以基于最新的依赖库或软件来构建。比如，GnuTLS需要用到GNU&nbsp;libtasn1和GNU&nbsp;libcrypt，那么就可以基于这两个库的最新版本来构建它。除了web界面以外，Hydra可以在项目构建状态发生改变的时候，通过电子邮件来提醒管理人员。（比如，从<code>SUCCEEDED</code>状态变为了<code>FAILED</code>）</p>
 
-<p>任何一个GNU软件包都可以申请在 Hydra
-上的一篇空间。每个软件包必
须提供一份&ldquo;构建策略&rdquo;。该策略使用Nix语言编写（用Nix的术语来说，就是<em>Nix表达式</em>）。<a
-href="https://svn.nixos.org/repos/nix/hydra-config/gnu/trunk";>GNU项目通用Nix表达式范本</a>可以在svn上获取。对于简单的项目来说，使用æ
 
‡å‡†çš„GNU构建程序的话，比如Automake和Autoconf，这份构建策略通常非常简单。比如可以参考这个<a
-href="https://svn.nixos.org/repos/nix/hydra-config/gnu/trunk/patch/release.nix";>软件补丁构建策略</a>。对此您有任何问题，欢迎向<a
-href="mailto:address@hidden";>address@hidden</a>提问。在编写完您的构建策略之后，请把它发至<a
-href="http://lists.gnu.org/mailman/listinfo/hydra-users";>address@hidden</a>，并要求把它åŠ
 入到Hyra</p>
-
-<p> 想要获得更多关于Nix，Hydra和Nixpkgs的技术信息，请访问<a
-href="http://hydra.nixos.org/job/nix/trunk/tarball/latest/download/1/nix/manual.html";>Nix手册</a>和<a
-href="http://hydra.nixos.org/job/nixpkgs/trunk/tarball/latest/download/2/manual.html";>Nixpkgs手册</a>。</p>
-
-<!-- If needed, change the copyright block at the bottom. In general,
-     all pages on the GNU web server should have the section about
-     verbatim copying.  Please do NOT remove this without talking
-     with the webmasters first.
-     Please make sure the copyright date is consistent with the document
-     and that it is like this: "2001, 2002", not this: "2001-2002". -->
-<div style="font-size: small;">
+<h3 id="platform-testers">平台测试者：手动可移植性测试</h3>
+
+<p>另一项发布前测试选项是<a
+href="http://lists.gnu.org/mailman/listinfo/platform-testers";>平台测试者
邮件列表</a>。如果时间允许，该邮件列表成员会æ 
¹æ®éœ€æ±‚在多种平台上构建预å…
ˆå‘å¸ƒç‰ˆæœ¬ã€‚ï¼ˆæˆ‘ä»¬å¾æ±‚æµ‹è¯•å¿—æ„¿è€…ï¼åªéœ€åŠ å…
¥è¯¥é‚®ä»¶åˆ—表就可以开始介入了。）</p>
+
+<p>和Hydra不同，平台测试者
主要进行手动测试，两种方法各有优劣。另外，平台测试者
比Hydra有更多种类的平台和编译器。</p>
+
+<p>æ‰€ä»¥ï¼Œå¦‚æžœä½ æœ‰é¢„å‘å¸ƒç‰ˆï¼Œä½ 
可以发信给邮件列表，提供(1)&nbsp;压缩包
的url，(2)&nbsp;计划的发布日期，和(3)&nbsp;收取构建报告的电子邮件地址。构建和报告都有列表里的志愿è€
…手动完成。</p>
+
+<div class="translators-notes">
 
 <!--TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.-->
  </div>
@@ -137,35 +133,64 @@
 <div id="footer">
 <div class="unprintable">
 
-<p>请将有关自由软件基金会(FSF) &amp; GNU 的查询 &amp; 
问题发送到<a
+<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>，å…
¶ä»–问题发送到<a
-href="mailto:address@hidden";>&lt;address@hidden&gt;</a></p>
+href="/contact/">其他联系方法</a> 
联系自由软件基金会(FSF)。有关失效链接或å…
¶ä»–错误和建议，请发送邮件到<a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>。</p>
 
-<p>若您想翻译本文，请参看<a 
href="/server/standards/README.translations.html">翻译手册</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>
 
-<p>Copyright &copy; 2011 Free Software Foundation, Inc.</p>
+<!-- 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; 2014 Free Software Foundation, Inc.</p>
 
-<p>This page is licensed under a <a rel="license"
+<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" -->
+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.-->
-第一版中文翻译：刘智敏
-ç¬¬ä¸€ç‰ˆç¿»è¯‘æ ¡æ­£ï¼šåˆ˜æ˜­å®
-ç¬¬äºŒç‰ˆä¸­æ–‡ç¿»è¯‘ï¼šé‚“æ¥ </div>
+<b>翻译</b>：刘智敏<br></br>
+<b>å®¡æ ¡</b>：刘昭宏，2002ï¼›é‚“æ¥ ï¼Œ2010。<br></br>
+<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: 2015/05/26 05:58:19 $
+$Date: 2017/09/04 14:29:56 $
 
 <!-- timestamp end -->
 </p>

Index: po/devel.zh-cn.po
===================================================================
RCS file: /web/www/www/software/po/devel.zh-cn.po,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -b -r1.22 -r1.23
--- po/devel.zh-cn.po   4 Sep 2017 14:17:44 -0000       1.22
+++ po/devel.zh-cn.po   4 Sep 2017 14:29:56 -0000       1.23
@@ -16,7 +16,6 @@
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"Outdated-Since: 2012-01-12 04:25-0500\n"
 
 # type: Content of: <title>
 #. type: Content of: <title>
@@ -155,8 +154,8 @@
 "hand-maintained lists are generally kept in <code>/com/archive</code> on the "
 "GNU machines."
 msgstr ""
-"自动管理的邮件列表归档于<a 
href=\"http://lists.gnu.org/\";>lists.gnu.org</"
-"a>（<a 
href=\"rsync://lists.gnu.org/\">mbox的归档可以通过rsync</a>和<a href="
+"自动管理的邮件列表归档于<a 
href=\"http://lists.gnu.org/\";>lists.gnu.org</a>"
+"（<a href=\"rsync://lists.gnu.org/\">mbox的归档可以通过rsync</a>和<a 
href="
 
"\"ftp://lists.gnu.org/\";>ftp</a>获取），也可以通过列表管理获取。手动管理的邮"
 "件列表归档于GNU机器的<code>/com/archive</code>。"
 
@@ -440,9 +439,9 @@
 "and (3)&nbsp;the email address to which build reports should be sent.  The "
 "builds and reports are made by hand by the volunteers on the list."
 msgstr ""
-"æ‰€ä»¥ï¼Œå¦‚æžœä½ æœ‰é¢„å‘å¸ƒç‰ˆï¼Œä½ 
可以发信给邮件列表，提供(1)&nbsp;压缩包的url，"
-"(2)&nbsp;计划的发布日期，和(3)&nbsp;收取构建报告的电子邮件地址。构建和报告都"
-"有列表里的志愿者手动完成。"
+"æ‰€ä»¥ï¼Œå¦‚æžœä½ æœ‰é¢„å‘å¸ƒç‰ˆï¼Œä½ 
可以发信给邮件列表，提供(1)&nbsp;压缩包的url，(2)"
+"&nbsp;计划的发布日期，和(3)&nbsp;收取构建报告的电子邮件地址。构建和报告都有列"
+"表里的志愿者手动完成。"
 
 # type: Content of: <div>
 #. TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.

Index: po/devel.zh-cn-en.html
===================================================================
RCS file: po/devel.zh-cn-en.html
diff -N po/devel.zh-cn-en.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ po/devel.zh-cn-en.html      4 Sep 2017 14:29:56 -0000       1.1
@@ -0,0 +1,278 @@
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.77 -->
+<title>GNU Development Resources
+- GNU Project - Free Software Foundation</title>
+<!--#include virtual="/software/po/devel.translist" -->
+<!--#include virtual="/server/banner.html" -->
+<h2>GNU Development Resources</h2>
+
+<p>This page describes many of the development resources available for
+GNU developers on GNU Project machines.  For full details of the
+privileges and responsibilities of GNU maintainers, please see the <a
+href="/prep/maintain/">Information for GNU Maintainers</a> document, and
+also follow the <a href="/prep/standards/">GNU Coding Standards</a>.
+Also interesting to review may be the <a
+href="/software/maintainer-tips.html">tips for GNU maintainers</a> and
+<a href="/help/evaluation.html#whatmeans">overview of what it means to
+be a GNU package</a>.</p>
+
+<p>With the abundance of inexpensive computers that can run <a
+href="/gnu/linux-and-gnu.html">GNU/Linux</a>, as well as the greater
+availability of Internet access, many GNU volunteers today have all the
+computer facilities they need. However, there are still advantages to
+having central computers where GNU volunteers can work together without
+having to make their own machines accessible to others.</p>
+
+<p>For that reason, the Free Software Foundation strongly encourages GNU
+software projects to use the machines at <code>gnu.org</code> as a home
+base.  Using these machines also benefits the GNU Project indirectly, by
+increasing public awareness of GNU, and spreading the idea of working
+together for the benefit of everyone.</p>
+
+
+<h3 id="CVS">Savannah and version control</h3>
+
+<p>If you are developing an official GNU package, we strongly recommend
+using a public source control repository on <a
+href="http://savannah.gnu.org/";>Savannah</a>, the GNU hosting server.
+To do this, first <a
+href="https://savannah.gnu.org/account/register.php";>create yourself an
+account</a> and then <a
+href="http://savannah.gnu.org/register/";>register your GNU package</a>.
+After it is created, you will be able to choose a version control
+system, create web pages for your package, manage permissions for
+contributors to the pages, and many other features.</p>
+
+
+<h3 id="MailLists">Mailing lists</h3>
+
+<p>We operate mailing lists for GNU software packages as needed,
+including both hand-managed lists and automatically managed lists.</p>
+
+<p>When a GNU package is registered on <a
+href="http://savannah.gnu.org/";>Savannah</a>, a web interface allows
+developers to create and manage mailing lists dedicated to their
+package.</p>
+
+<p>Each GNU package <em>name</em> ought to have at least a bug-reporting
+list with the canonical name <code>bug-<em>name</em>@gnu.org</code>,
+plus any aliases that may be useful. Using Savannah, you can create
+lists for your package with names like this.  Some packages share the
+list address@hidden but we now encourage packages to set up their
+own individual lists.</p>
+
+<p>Packages can have other lists for announcements, asking for help,
+posting source code, for discussion among users, or whatever the package
+maintainer finds to be useful.</p>
+
+<p>Mailing list archives for automatically-managed lists are available
+at <a href="http://lists.gnu.org/";>lists.gnu.org</a> (<a
+href="rsync://lists.gnu.org/">mbox archives available through rsync</a>
+and <a href="ftp://lists.gnu.org/";>ftp</a>), as well as through the list
+manager. Archives for hand-maintained lists are generally kept in
+<code>/com/archive</code> on the GNU machines.</p>
+
+<p>When a mailing list becomes large enough to justify it, we can set up
+a <code>gnu.*</code> newsgroup with a two-way link to the mailing
+list.</p>
+
+
+<h3 id="WebServer">Web pages</h3>
+
+<p>The master GNU web server is <a
+href="http://www.gnu.org/";>http://www.gnu.org/</a>.  We very strongly
+recommend that GNU packages use
+<tt>http://www.gnu.org/software/</tt><i>package</i> as their primary
+home page.</p>
+
+<p>Using Savannah, developers can create and maintain their own pages at
+that url via a CVS &ldquo;web repository&rdquo;, separate from the
+package's main source repository (which can use any supported version
+control system).  <a href="/prep/maintain/maintain.html#Web-Pages">More
+information on maintaining GNU web pages</a>.</p>
+
+
+<h3 id="FTP">FTP</h3>
+
+<p>The primary ftp site for GNU software on <a
+href="http://ftp.gnu.org/gnu";><code>http://ftp.gnu.org/</code></a>,
+which is <a href="/prep/ftp.html">mirrored worldwide</a>.  We very
+strongly recommend that all GNU packages upload their releases here (in
+addition to any other location you find convenient).</p>
+
+<p>We use a different server for test releases, so that people won't
+install them thinking they are ready for prime time. This server is <a
+href="ftp://alpha.gnu.org/";><code>ftp://alpha.gnu.org/</code></a>.</p>
+
+<p>The <a
+href="/prep/maintain/maintain.html#Automated-FTP-Uploads">Information
+for GNU Maintainers</a> document has complete details on the ftp upload
+process, which is the same for both servers.</p>
+
+
+<h3 id="LoginAccounts">Login accounts</h3>
+
+<p>We provide shell login access to GNU machines to people who need them
+for work on GNU software.  Having a login account is both a privilege and
+a responsibility, and they should be used only for your work on GNU.
+<a href="README.accounts.html">Instructions for obtaining an account
+machines</a> are written separately.</p>
+
+<p>On the general login machine, the <a href="/software/gsrc/">gsrc</a>
+package developers maintain a hierarchy of the current GNU package
+releases (<tt>/gd/gnu/gnusys/live</tt>), compiled from the original
+sources.  To use it, source <tt>/gd/gnu/gnusys/live/setup</tt>.</p>
+
+<p>You can also <a
+href="http://www.fsf.org/about/systems/sending-mail-via-fencepost";>use a
+GNU account for email</a>.</p>
+
+
+<h3 id="Hydra">Hydra: Continuous builds and portability testing</h3>
+
+<p>Continuous build tools (often referred to as continuous integration
+tools) allow programming errors to be spotted soon after they are
+introduced in a software project, which is particularly useful for
+cooperatively developed software.</p>
+
+<p><a href="http://nixos.org/hydra/";>Hydra</a> is a free continuous
+build tool based on the <a href="http://nixos.org/nix/";>Nix</a> package
+manager.  Administrators of the <a href="http://hydra.nixos.org/";>Hydra
+instance at the Delft University of Technology</a> have generously
+offered <a href="http://hydra.nixos.org/project/gnu";>slots for the GNU
+Project</a>.  Projects on Hydra get re-built <em>at each commit</em>
+or change in their dependencies, whichever comes first (dependencies
+<em>include</em> the standard build environment being used, which
+itself contains recent released versions of GCC, GNU&nbsp;make,
+etc.)</p>
+
+<p>Currently it can build software on GNU/Linux (<tt>i686</tt> and
+<tt>x86_64</tt>) as well as FreeBSD, Darwin, Solaris, and Cygwin, and
+can cross-build for GNU/Hurd, GNU/Linux on other architectures, and
+MinGW.  It can provide code coverage reports produced using LCOV.  In
+addition to source tarballs and Nix packages, it can build packages for
+<code>deb</code>- and <code>RPM</code>-based distributions.  Packages
+can be built against the latest versions of their dependencies; for
+instance, GnuTLS is built using GNU&nbsp;libtasn1 and GNU&nbsp;libgcrypt
+builds corresponding to their latest revision.</p>
+
+<p>In addition to the <a href="http://hydra.nixos.org/project/gnu";>web
+interface</a>, Hydra can send notifications by email when the build
+status of a project changes&mdash;e.g., from <code>SUCCEEDED</code> to
+<code>FAILED</code>.  When a build fails, its log and build tree are
+accessible from the web interface; the latter allows generated files
+(for example, <code>config.log</code> or <code>testsuite.log</code>) to
+be inspected, which provides debugging hints.</p>
+
+<p>Any GNU software package can request a slot on Hydra.  Each package
+must provide its own &ldquo;build recipe&rdquo; written in the Nix
+language (a <em>Nix expression</em>, in Nix parlance).  <a
+href="http://git.savannah.gnu.org/cgit/hydra-recipes.git";>Nix
+expressions for GNU projects</a> are available via Git.  For simple
+projects using standard GNU build tools such as Automake and Autoconf,
+the recipe is usually fairly simple.  For example, see the <a
+href="http://git.savannah.gnu.org/cgit/hydra-recipes.git/tree/patch/release.nix";>recipe
+for GNU&nbsp;Patch</a>.  You are welcome to ask for guidance on <a
+href="mailto:address@hidden";>address@hidden</a>.</p>
+
+<p>After constructing your build recipe, email <a
+href="http://lists.gnu.org/mailman/listinfo/hydra-users";>address@hidden</a>
+and ask to be included in Hydra.  Also make sure to become a member of
+the <a
+href="https://savannah.gnu.org/projects/hydra-recipes/";><code>hydra-recipes</code>
+project at Savannah</a>.  This will allow you to customize your
+project's build job directly.</p>
+
+<p> For technical information about Hydra, please consult the <a
+href="http://hydra.nixos.org/job/hydra/trunk/tarball/latest/download-by-type/doc/manual";>
+manual of Hydra</a> (<a
+href="http://hydra.nixos.org/job/hydra/trunk/tarball/latest/download-by-type/doc-pdf/manual";>PDF</a>).
+For more details, please refer to the <a
+href="http://hydra.nixos.org/job/nix/trunk/tarball/latest/download/1/nix/manual.html";>Nix
+manual</a>.</p>
+
+
+<h3 id="platform-testers">platform-testers: Manual portability testing</h3>
+
+<p>Another useful option for pre-release testing is the <a
+href="http://lists.gnu.org/mailman/listinfo/platform-testers";>platform-testers
+mailing list</a>.  Time permitting, the people on this list build
+pre-releases on a wide variety of platforms upon request.  (Volunteers
+to handle testing requests are needed!  Just subscribe to the list and
+start participating.)</p>
+
+<p>In contrast to the Hydra tool described above, the platform-testers
+list works essentially by hand, so each method has its advantages and
+disadvantages.  Also, the platform-testers crew has access to a wider
+variety of platforms and compilers than the Hydra setup.</p>
+
+<p>So, if you have a pre-release, you can write to the mailing list,
+providing (1)&nbsp;the url to the tarball, (2)&nbsp;the planned date of
+the release, and (3)&nbsp;the email address to which build reports
+should be sent.  The builds and reports are made by hand by the
+volunteers on the list.</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; 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: 2017/09/04 14:29:56 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>