www-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

www/gnu old-gnu-structure/po/old-gnu-structure....


From: GNUN
Subject: www/gnu old-gnu-structure/po/old-gnu-structure....
Date: Sat, 28 Mar 2020 11:30:08 -0400 (EDT)

CVSROOT:        /web/www
Module name:    www
Changes by:     GNUN <gnun>     20/03/28 11:30:08

Modified files:
        gnu/old-gnu-structure/po: old-gnu-structure.translist 
                                  old-gnu-structure.zh-cn.po 
        gnu/po         : gnu-structure.translist gnu-structure.zh-cn.po 
Added files:
        gnu            : gnu-structure.zh-cn.html 
        gnu/old-gnu-structure: old-gnu-structure.zh-cn.html 
        gnu/old-gnu-structure/po: old-gnu-structure.zh-cn-en.html 
        gnu/po         : gnu-structure.zh-cn-en.html 

Log message:
        Automatic update by GNUnited Nations.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/gnu-structure.zh-cn.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/old-gnu-structure/old-gnu-structure.zh-cn.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/old-gnu-structure/po/old-gnu-structure.translist?cvsroot=www&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/old-gnu-structure/po/old-gnu-structure.zh-cn.po?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/old-gnu-structure/po/old-gnu-structure.zh-cn-en.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/gnu-structure.translist?cvsroot=www&r1=1.4&r2=1.5
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/gnu-structure.zh-cn.po?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/gnu/po/gnu-structure.zh-cn-en.html?cvsroot=www&rev=1.1

Patches:
Index: old-gnu-structure/po/old-gnu-structure.translist
===================================================================
RCS file: /web/www/www/gnu/old-gnu-structure/po/old-gnu-structure.translist,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- old-gnu-structure/po/old-gnu-structure.translist    22 Mar 2020 15:00:39 
-0000      1.4
+++ old-gnu-structure/po/old-gnu-structure.translist    28 Mar 2020 15:30:08 
-0000      1.5
@@ -5,10 +5,12 @@
 <span dir="ltr" class="original">[en]&nbsp;<a lang="en" hreflang="en" 
href="/gnu/old-gnu-structure/old-gnu-structure.en.html">English</a> 
&nbsp;</span>
 <span dir="ltr">[pt-br]&nbsp;<a lang="pt-br" hreflang="pt-br" 
href="/gnu/old-gnu-structure/old-gnu-structure.pt-br.html">português</a> 
&nbsp;</span>
 <span dir="ltr">[tr]&nbsp;<a lang="tr" hreflang="tr" 
href="/gnu/old-gnu-structure/old-gnu-structure.tr.html">Türkçe</a> 
&nbsp;</span>
+<span dir="ltr">[zh-cn]&nbsp;<a lang="zh-cn" hreflang="zh-cn" 
href="/gnu/old-gnu-structure/old-gnu-structure.zh-cn.html">简体中文</a> 
&nbsp;</span>
 </p>
 </div>' -->
 <link rel="alternate" type="text/html" 
href="/gnu/old-gnu-structure/old-gnu-structure.html" hreflang="x-default" />
 <link rel="alternate" type="text/html" lang="en" hreflang="en" 
href="/gnu/old-gnu-structure/old-gnu-structure.en.html" title="English" />
 <link rel="alternate" type="text/html" lang="pt-br" hreflang="pt-br" 
href="/gnu/old-gnu-structure/old-gnu-structure.pt-br.html" title="português" />
 <link rel="alternate" type="text/html" lang="tr" hreflang="tr" 
href="/gnu/old-gnu-structure/old-gnu-structure.tr.html" title="Türkçe" />
+<link rel="alternate" type="text/html" lang="zh-cn" hreflang="zh-cn" 
href="/gnu/old-gnu-structure/old-gnu-structure.zh-cn.html" title="简体中文" 
/>
 <!-- end translist file -->

Index: old-gnu-structure/po/old-gnu-structure.zh-cn.po
===================================================================
RCS file: /web/www/www/gnu/old-gnu-structure/po/old-gnu-structure.zh-cn.po,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- old-gnu-structure/po/old-gnu-structure.zh-cn.po     28 Mar 2020 15:05:49 
-0000      1.1
+++ old-gnu-structure/po/old-gnu-structure.zh-cn.po     28 Mar 2020 15:30:08 
-0000      1.2
@@ -6,7 +6,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: old-gnu-structure.html\n"
-"POT-Creation-Date: 2020-03-16 16:09+0800\n"
+"POT-Creation-Date: 2020-03-05 09:55+0000\n"
 "PO-Revision-Date: 2020-03-28 22:10+0800\n"
 "Last-Translator: Nios34 <address@hidden>\n"
 "Language-Team: Chinese <address@hidden>\n"

Index: po/gnu-structure.translist
===================================================================
RCS file: /web/www/www/gnu/po/gnu-structure.translist,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- po/gnu-structure.translist  17 Mar 2020 15:30:47 -0000      1.4
+++ po/gnu-structure.translist  28 Mar 2020 15:30:08 -0000      1.5
@@ -5,10 +5,12 @@
 <span dir="ltr" class="original">[en]&nbsp;<a lang="en" hreflang="en" 
href="/gnu/gnu-structure.en.html">English</a> &nbsp;</span>
 <span dir="ltr">[fr]&nbsp;<a lang="fr" hreflang="fr" 
href="/gnu/gnu-structure.fr.html">français</a> &nbsp;</span>
 <span dir="ltr">[tr]&nbsp;<a lang="tr" hreflang="tr" 
href="/gnu/gnu-structure.tr.html">Türkçe</a> &nbsp;</span>
+<span dir="ltr">[zh-cn]&nbsp;<a lang="zh-cn" hreflang="zh-cn" 
href="/gnu/gnu-structure.zh-cn.html">简体中文</a> &nbsp;</span>
 </p>
 </div>' -->
 <link rel="alternate" type="text/html" href="/gnu/gnu-structure.html" 
hreflang="x-default" />
 <link rel="alternate" type="text/html" lang="en" hreflang="en" 
href="/gnu/gnu-structure.en.html" title="English" />
 <link rel="alternate" type="text/html" lang="fr" hreflang="fr" 
href="/gnu/gnu-structure.fr.html" title="français" />
 <link rel="alternate" type="text/html" lang="tr" hreflang="tr" 
href="/gnu/gnu-structure.tr.html" title="Türkçe" />
+<link rel="alternate" type="text/html" lang="zh-cn" hreflang="zh-cn" 
href="/gnu/gnu-structure.zh-cn.html" title="简体中文" />
 <!-- end translist file -->

Index: po/gnu-structure.zh-cn.po
===================================================================
RCS file: /web/www/www/gnu/po/gnu-structure.zh-cn.po,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- po/gnu-structure.zh-cn.po   28 Mar 2020 15:02:43 -0000      1.1
+++ po/gnu-structure.zh-cn.po   28 Mar 2020 15:30:08 -0000      1.2
@@ -7,7 +7,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: gnu-structure.html\n"
-"POT-Creation-Date: 2020-03-16 07:43+0800\n"
+"POT-Creation-Date: 2020-03-03 20:25+0000\n"
 "PO-Revision-Date: 2020-03-28 22:11+0800\n"
 "Last-Translator: Wensheng Xie <address@hidden>\n"
 "Language-Team: Chinese <address@hidden>\n"
@@ -501,9 +501,9 @@
 "lists.  Most spam is caught by spam filters, but human moderators are also "
 "available to manage the queue of messages predicted not to be spam."
 msgstr ""
-"<a href=\"//savannah.gnu.org/maintenance/ListHelperAntiSpam/\">Listhelper</"
-"a>(列表助手)是一个过滤 GNU 
邮件列表中的垃圾邮件的半自动系统。该过滤器会捕获"
-"大部分垃圾邮件,但是还需要人工来处理剩下的邮件队列。"
+"<a href=\"//savannah.gnu.org/maintenance/ListHelperAntiSpam/\">Listhelper</a>"
+"(列表助手)是一个过滤 GNU 
邮件列表中的垃圾邮件的半自动系统。该过滤器会捕获大"
+"部分垃圾邮件,但是还需要人工来处理剩下的邮件队列。"
 
 #. type: Content of: <h4>
 msgid "GNU Volunteer Coordinators"

Index: gnu-structure.zh-cn.html
===================================================================
RCS file: gnu-structure.zh-cn.html
diff -N gnu-structure.zh-cn.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ gnu-structure.zh-cn.html    28 Mar 2020 15:30:07 -0000      1.1
@@ -0,0 +1,291 @@
+<!--#set var="ENGLISH_PAGE" value="/gnu/gnu-structure.en.html" -->
+
+<!--#include virtual="/server/header.zh-cn.html" -->
+<!-- Parent-Version: 1.91 -->
+
+<!-- This file is automatically generated by GNUnited Nations! -->
+<title>GNU 工程的结构和管理 - GNU 工程 - 
自由软件基金会</title>
+
+<!--#include virtual="/gnu/po/gnu-structure.translist" -->
+<!--#include virtual="/server/banner.zh-cn.html" -->
+<h2>GNU 工程的结构和管理</h2>
+
+<p class="byline">布兰登·因弗戈与理查德·斯托曼 著</p>
+
+<p class="big"><strong>Version 1.0.1</strong></p>
+
+<div class="announcement">
+<p>此文件还有一个 <a href="/gnu/gnu-structure.org">旧版</a>。</p>
+</div>
+
+<hr class="thin" />
+
+<p>GNU 工程开发并维护<a 
href="/gnu/about-gnu.html">GNU操作系统</a>。通过这项工作和å…
¶ä»–相关活动,GNU
+工程倡导和促进<a 
href="/philosophy/philosophy.html">软件自由</a>,这也是自由软件运动的æ
 ¸å¿ƒç†å¿µã€‚</p>
+
+<p>操作系统由许多软件组件组成,这些组件使计算机å…
±åŒå®Œæˆæœ‰ç”¨çš„工作。它包含用于底层功能的代码,比如内æ 
¸å’Œé©±åŠ¨åŠ 
系统库以及用户可明确运行的程序(实用程序、工å…
·ã€åº”用程序和游戏)。GNU
+操作系统包括全部这个范围内的软件。许多程序是由 GNU 
工程专门开发和发布的;这些被称为“GNU 包”。</p>
+
+<p>正如组成操作系统的程序必须协调一致地工作一样,GNU
+工程也必须协调地工作。大多数工作包
括开发特定的程序,但是这些程序不是独立的项目。它们必
须很好地结合在一起,以构成我们希望的 GNU
+系统。因此,在过去的几
十年中,我们已经开发了该项目的结构。此处所列并不是新创é€
 ï¼Œè€Œæ˜¯æˆ‘们第一次在统一的位置记录下这一切。</p>
+
+<p>自由软件基金会为 GNU 
工程提供许多种支持(设施、服务)。å…
¶ä¸­çš„工作方式不在本文的范围之内。</p>
+
+<h3 id="software-development-structure">软件开发结构</h3>
+
+<p>GNU 工程的大部分活动都由括软件包的开发构成。下面是 
GNU 软件开发的结构。</p>
+
+<h4 id="chief-gnuisance">首席 GNUisance</h4>
+
+<p>GNU 工程由首席 
GNUisance,项目的创始人,理查德·斯托曼领导。首席 GNUisance
+在原则上负责所有重大决定,包括总体理念和æ 
‡å‡†ï¼Œå¹¶æŒ‡å¯¼é¡¹ç›®æ¥å®žçŽ°å®ƒä»¬ã€‚首席 GNUisance 把软件包戏称为 
GNU
+包,或在必要时退役并任命他们的维护者。</p>
+
+<p>在实践中,首席 GNUisance 
会将许多此类决定和大多数任务委托给他人,并且很少干预 
GNU
+软件包的开发细节&mdash;&mdash;通常只是一个建议。</p>
+
+<h4 id="assistant-gnuisances">助理 GNUisances</h4>
+
+<p>一个叫做 <a href="mailto:address@hidden";>address@hidden</a> 
的队伍,可作为
+GNU 软件维护者
的第一联系点。他们跟踪整个项目的开发活动,确保及时发布,检查维护è€
…遵循 GNU 的 <a
+href="/philosophy/">哲学</a>
+和方针,并解决可能出现的任何冲突。他们也处理维护者
卸任或新志愿者自愿维护现有包的情况(在这种情
况下,他们可以代表首席 GNUisance
+任命新的维护者)。</p>
+
+<p>新成员在需要时从现有的 GNU 志愿者
中招募。但是,为特定任务提供帮助也是欢迎的,有兴趣的 
GNU 志愿者联系请联系我们。</p>
+
+<h4 id="maintainers">包维护者</h4>
+
+<p>每个 GNU 软件包都有被首席 GNUisance 或助理 GNUisance 
任命的特别维护者。包维护者是对首席 GNUisance
+负责的,在其管辖下被任命并在极少数情
况下被解除,他们代表 GNU 项目负责开发软件包。</p>
+
+<p>当一个程序被 <a href="/help/evaluation.html">接受为 GNU 包</a>
+时,维护人员的初始任命就完成了。他们通常是那些同意使该程序成为
 GNU 软件包的主要开发人员。</p>
+
+<p>随着时间的流逝,维护人员偶尔会下台。有时,唯一的维护è€
…会也退出该角色,从而使软件包变得无人维护。首席 
GNUisance 通常会委托助理
+GNUisance 寻找并任命新的维护者。<a
+href="/server/takeaction.html#unmaint">请查看当前无人维护的软件包
列表</a>。我们会让原来的维护者推荐新维护者
,并感谢他们的建议。</p>
+
+<p>软件包的维护者通常会招募其他人来为软件包
的开发做出贡献,并将一些技术决策委托给他们。但是,维护è€
…保留对整个程序包的主导全,这样他们就能够履行对 GNU
+工程的责任。</p>
+
+<p>一个维护者的主要责任是根据 GNU 
工程的理念、使命、政策和常规决策做好程序的开发和维护。维护人员还å¿
…须确保其软件包与 GNU
+系统的其余部分一起正常工作。更多信息,<a
+href="/help/evaluation.html#whatmeans">请了解维护人员的基本职责以及将程序作为
 GNU 软件包的含义</a>。</p>
+
+<p>通常,维护人员决定软件包所采用的技术方向,因
此他们会为软件包做出日常决策。
+同样,为了让程序包
能够很好地协同工作,维护人员可以彼此直接工作,我们鼓励他们这æ
 ·åšã€‚在少数情况下,首席 GNUisance
+会做出直接影响一个或多个GNU软件包
的决定。受到影响的软件包维护者有义务以 GNU 
工程的名义执行这些决定。</p>
+
+<p>有关维护人员的具体职责以及维护 GNU 
软件技术指导的更为完整的信息可以参看 <a 
href="/prep/maintain">GNU
+软件维护者须知</a> 和 <a href="/prep/standards">GNU 代码规范</a> 
等文档。</p>
+
+<p>我们不要求 GNU 软件包维护者
同意我们的理念或批准我们的政策——只需遵守它们。维护è€
…和贡献者在为 GNU
+软件工作时必须执行我们的理念、政策和具体决定。</p>
+
+<h3 id="package-development-support">支持 GNU 包的开发</h3>
+
+<p>多个团队会为 GNU 软件包
的开发和管理提供了各种支持。大多数团队都有协调员来指导他们;在大多数æƒ
…况下,除非另有说明,协调员直接向首席
+GNUisance 汇报。如有疑问,你可以联系 <a 
href="mailto:address@hidden";>GNU 志愿协调员</a> 来获得建议。</p>
+
+<h4 id="gnueval">软件评估</h4>
+
+<p><a href="mailto:address@hidden";>address@hidden</a> 
软件评估小组会对被推荐为 GNU
+软件包
的软件进行评估。这涉及对该软件的功能、软件自由相å…
³é—®é¢˜ä»¥åŠå®ƒå¦‚何与 GNU 系统整体适应等方面的认真评价。</p>
+
+<p>需要时会从现有的 GNU 志愿者中招募新成员。最好具有在 
Savannah 上进行非 GNU 软件评估的经验。</p>
+
+<h4 id="gnueval-security">软件安全性评估</h4>
+
+<p><a href="mailto:address@hidden";>address@hidden</a>
+软件安å…
¨æ€§è¯„估小组和软件评估小组一起工作。他们判断提供给 GNU 
的软件是否存在安全问题。</p>
+
+<p>需要时从现有的 GNU 志愿者中招募新成员。</p>
+
+<h4 id="security">安全小组</h4>
+
+<p> <a href="mailto:address@hidden";>安全小组</a> 帮助及时解决安å…
¨æ¼æ´žã€‚如果 GNU
+软件包的维护者未能响应有关安全漏洞的报告,则报告者
可以将该问题上报给安å…
¨å›¢é˜Ÿã€‚如果它确定问题很紧急,则可以开发补丁程序并发布修复版本。维护è€
…还可以要求安全团队提供保护其软件包的建议。</p>
+
+<p>需要时从现有的 GNU 志愿者中招募新成员。</p>
+
+<h4 id="platform-testers">平台测试</h4>
+
+<p><a
+href="//lists.gnu.org/mailman/listinfo/platform-testers">address@hidden</a>
+邮件列表的志愿者们在不同的硬件平台上测试 GNU 
软件预发行版,以确保其正常运行。</p>
+
+<p>欢迎新的志愿者。</p>
+
+<h4 id="mentors">导师</h4>
+
+<p>GNU 导师(<a 
href="mailto:address@hidden";>address@hidden</a>)自愿为新软件维护者
提供指导。</p>
+
+<p>我们要求 GNU 的长期维护者自愿参加。</p>
+
+<h4 id="proofreaders">校对员</h4>
+
+<p>校对者列表可通过校对英文文本来帮助 GNU 软件包维护者
。请写信给 <a
+href="mailto:address@hidden";>address@hidden</a> 来请求校对。</p>
+
+<h3 id="other-teams-services">其他小组和服务</h3>
+
+<p>其他几个团队支持或管理 GNU 
工程中的日常运作或推进项目的特定目标。</p>
+
+<h4 id="gac">GNU 咨询委员会</h4>
+
+<p><a 
href="/contact/gnu-advisory.html">GNU咨询委员会</a>(GAC)的存在是为了向首席
 GNUisance
+提供建议。咨询委员会委员由首席 GNUisance 
任命。咨询委员会通常代表首席 GNUisance 监视 GNU
+工程的运行状况,并提出潜在的问题进行讨论。</p>
+
+<h4 id="savannah-hackers">Savannah 黑客</h4>
+
+<p><a href="//savannah.gnu.org">Savannah</a> 是 GNU
+工程的软件工厂。它托管代码存储库、错误报告工å…
·ã€é‚®ä»¶åˆ—表界面等。Savannah 由 <a
+href="mailto:address@hidden";>Savannah 黑客</a>
+管理。他们保持软件工厂正常运转。除了确保 GNU 
软件的正常托管服务之外,Savannah 
黑客还会评估申请托管的非 GNU 软件。</p>
+
+<p>欢迎新的志愿者。</p>
+
+<h4 id="webmasters">网站管理员</h4>
+
+<p><a href="/people/webmeisters.html">GNU 网站管理员</a> 维护并更新 
<a
+href="/">https://www.gnu.org</a> 网页。</p>
+
+<p>网站管理员还会回答公众发出的有å…
³è‡ªç”±è½¯ä»¶å’Œè®¸å¯è¯ç­‰ä¸»é¢˜çš„各种问题(答案很明确时)。他们对发行版评估的请求进行初步筛选,审æ
 ¸æƒ³è¦æˆä¸ºç½‘站管理员的人员,并更新镜像列表。</p>
+
+<p>GNU 网站管理员组由向首席 GNUisance 报告的 <a
+href="mailto:address@hidden";>首席网管</a> 领导。欢迎新的志愿者
。请查看 <a
+href="/server/standards/webmaster-quiz.html">网管志愿者测试</a>。</p>
+
+<h4 id="web-translators">网页翻译</h4>
+
+<p>每种语言都有一个翻译团队,由团队协调员指导。请查看 
<a
+href="/server/standards/README.translations.html">《www.gnu.org 
网页翻译指南》</a>
+来了解更多信息。团队协调员报告给向首席 GNUisance 报告的 
<a
+href="mailto:address@hidden";>GNU 翻译经理</a>。</p>
+
+<h4 id="list-helpers">列表助手</h4>
+
+<p><a
+href="//savannah.gnu.org/maintenance/ListHelperAntiSpam/">Listhelper</a>(列表助手)是一个过滤
+GNU 
邮件列表中的垃圾邮件的半自动系统。该过滤器会捕获大部分垃圾邮件,但是还需要人工来处理剩下的邮件队列。</p>
+
+<p>需要时从现有的 GNU 志愿者中招募新成员。</p>
+
+<h4 id="gvc">GNU 志愿协调员</h4>
+
+<p>GNU 志愿协调员(<a 
href="mailto:address@hidden";>address@hidden</a>)帮助指导新志愿者在 
GNU
+工程中从事合适的工作</p>
+
+<p>欢迎新的 GVC 志愿者,但是强烈建议有 GNU 志愿者
经验的人(因此对 GNU 工程有广泛了解)担当。</p>
+
+<h4 id="education">GNU 教育小组</h4>
+
+<p><a href="/education/">GNU 教育小组</a> 促进在教育环境中采用 
GNU 操作系统。它还会评估学校并与学校管理人员对话。</p>
+
+<p>欢迎新的志愿者。</p>
+
+<h4 id="standards">GNU 标准组</h4>
+
+<p>GNU 标准组评估更新 GNU 代码æ 
‡å‡†çš„建议。任何人都可以通过 <a
+href="//lists.gnu.org/mailman/listinfo/bug-standards">bug-standards</a>
+邮件列表提交建议。然后,小组讨论并评估该建议,以澄清
所有细节和含义。然后,他们将建议提交给首席
+GNUisance,由他做出决定。该小组还负责对文档实施更改以及更新网站文档。</p>
+
+<p>需要时,从现有 GNU 志愿者中招募。</p>
+
+<h3 id="correcting-errors">更正错误</h3>
+
+<p>如果我们发现现有结构的描述有错误或遗漏,由于以前没有集中的文档,这是可能的,那么我们将做出更新,åŒ
…括 <a
+href="/gnu/gnu-structure.org">Org 版本</a> 和 <a
+href="/gnu/gnu-structure.html">HTML 
版本</a>,并提高第三位版本号。老版本也会放到 <a
+href="/gnu/old-gnu-structure/">此文件夹</a>。</p>
+
+<h3 id="future-changes">行政结构的未来变化</h3>
+
+<p>经过适当的 GNU 工程讨论列表与 GNU 贡献者
进行磋商之后,GNU 工程行政结构的改变由首席 GNUisance
+做出决定。这些磋商的目的是考虑可能的替代方案,并预测它们可能带来的好与坏的影响,从而做出明智的决定。</p>
+
+<p>我们将通过更新此文档来报告更改是否被采纳,Org 
版文档和 HTML 
版文档(参看以上)都会更新,并提高第一和/或第二位版本号。</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 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; 2020 Brandon Invergo and Richard Stallman</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
+href="mailto:address@hidden";>&lt;Nios34&gt;</a>,2020。<br></br>
+<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/03/28 15:30:07 $
+
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+<!-- for class="inner", starts in the banner include -->
+</body>
+</html>

Index: old-gnu-structure/old-gnu-structure.zh-cn.html
===================================================================
RCS file: old-gnu-structure/old-gnu-structure.zh-cn.html
diff -N old-gnu-structure/old-gnu-structure.zh-cn.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ old-gnu-structure/old-gnu-structure.zh-cn.html      28 Mar 2020 15:30:07 
-0000      1.1
@@ -0,0 +1,93 @@
+<!--#set var="ENGLISH_PAGE" 
value="/gnu/old-gnu-structure/old-gnu-structure.en.html" -->
+
+<!--#include virtual="/server/header.zh-cn.html" -->
+<!-- Parent-Version: 1.91 -->
+
+<!-- This file is automatically generated by GNUnited Nations! -->
+<title>GNU 工程的结构和管理的旧版本 - GNU 工程 - 
自由软件基金会</title>
+
+<!--#include virtual="/gnu/old-gnu-structure/po/old-gnu-structure.translist" 
-->
+<!--#include virtual="/server/banner.zh-cn.html" -->
+<h2>GNU 工程的结构和管理的旧版本</h2>
+
+<p>目前没有旧版本。请参看 <a 
href="/gnu/gnu-structure.html">当前版本</a>。</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 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; 2020 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
+href="mailto:address@hidden";>&lt;Nios34&gt;</a>,2020。<br></br>
+<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/03/28 15:30:07 $
+
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+<!-- for class="inner", starts in the banner include -->
+</body>
+</html>

Index: old-gnu-structure/po/old-gnu-structure.zh-cn-en.html
===================================================================
RCS file: old-gnu-structure/po/old-gnu-structure.zh-cn-en.html
diff -N old-gnu-structure/po/old-gnu-structure.zh-cn-en.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ old-gnu-structure/po/old-gnu-structure.zh-cn-en.html        28 Mar 2020 
15:30:08 -0000      1.1
@@ -0,0 +1,76 @@
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.91 -->
+<title>Old versions of The Structure and Administration of the GNU 
+Project - GNU Project - Free Software Foundation</title>
+ <!--#include virtual="/gnu/old-gnu-structure/po/old-gnu-structure.translist" 
-->
+<!--#include virtual="/server/banner.html" -->
+<h2>Old versions of The Structure and Administration of the GNU 
+Project</h2>
+
+<p>There are currently no old versions. Please refer to <a 
+href="/gnu/gnu-structure.html">the current version</a>.</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; 2020 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: 2020/03/28 15:30:08 $
+<!-- timestamp end -->
+</p>
+</div>
+</div><!-- for class="inner", starts in the banner include -->
+</body>
+</html>

Index: po/gnu-structure.zh-cn-en.html
===================================================================
RCS file: po/gnu-structure.zh-cn-en.html
diff -N po/gnu-structure.zh-cn-en.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ po/gnu-structure.zh-cn-en.html      28 Mar 2020 15:30:08 -0000      1.1
@@ -0,0 +1,397 @@
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.91 -->
+<title>The Structure and Administration of the GNU Project
+- GNU Project - Free Software Foundation</title>
+ <!--#include virtual="/gnu/po/gnu-structure.translist" -->
+<!--#include virtual="/server/banner.html" -->
+<h2>The Structure and Administration of the GNU Project</h2>
+
+<p class="byline">by Brandon Invergo and Richard Stallman</p>
+
+<p class="big"><strong>Version 1.0.1</strong></p>
+
+<div class="announcement">
+<p>An <a href="/gnu/gnu-structure.org">Org version</a> of this
+document is also available.</p>
+</div>
+
+<hr class="thin" />
+
+<p>The GNU Project develops and maintains the
+<a href="/gnu/about-gnu.html">GNU operating system</a>.  Through this
+work, and other related activities, the GNU Project advocates and
+promotes <a href="/philosophy/philosophy.html">software freedom</a>,
+the core philosophy of the free software movement.</p>
+
+<p>An operating system consists of many software components that
+together make a computer do useful jobs.  It includes code for
+low-level functionality, such as the kernel and drivers, plus system
+libraries, as well as the programs (utilities, tools, applications,
+and games) that users explicitly run.  The GNU operating system
+comprises software across this entire spectrum.  Many of the programs
+are specifically developed and released by the GNU Project; these are
+termed &ldquo;GNU packages&rdquo;.  The GNU system also includes
+components that are <a href="/philosophy/categories.html">free
+programs</a> released by other developers, outside of the GNU
+Project.</p>
+
+<p>Just as the programs composing an operating system must work
+together coherently, the GNU Project must operate coherently.  Most of
+the work consists of developing specific programs, but these programs
+are not independent projects; they must fit well together to
+constitute the GNU system we wish for.  Therefore, over the course of
+decades, we have developed structure for the project.  None of it is
+new, but this is the first time we have documented all of it in one
+place.</p>
+
+<p>The Free Software Foundation provides many kinds of support
+(facilities, services) to the GNU Project.  How that works is outside
+the scope of this document.</p>
+
+<h3 id="software-development-structure">Software Development Structure</h3>
+
+<p>Most of the GNU Project's activity consists of development of
+software packages.  Here is how GNU software development is
+structured.</p>
+
+<h4 id="chief-gnuisance">The Chief GNUisance</h4>
+
+<p>The GNU Project is led by the Chief GNUisance, Richard Stallman,
+the founder of the project.  The Chief GNUisance is responsible in
+principle for all significant decisions, including the overall
+philosophy and standards, and directs the project in carrying them
+out.  The Chief GNUisance dubs software packages as GNU packages, or
+decommission one when necessary, and appoints their maintainers.</p>
+
+<p>In practice, the Chief GNUisance delegates many of these decisions
+and most of the tasks to others, and only rarely intervenes in the
+specifics of development of a GNU package&mdash;and usually that is
+with a suggestion.</p>
+
+<h4 id="assistant-gnuisances">Assistant GNUisances</h4>
+
+<p>This team, residing at
+<a href="mailto:address@hidden";>address@hidden</a>, is
+available as a first point-of-contact for maintainers of GNU Software.
+They keep track of development activity across the entire project,
+ensuring timely releases, checking that the maintainers follow
+GNU's <a href="/philosophy/">philosophy</a> and guidelines, and
+resolving any conflicts that might arise.  They also handle cases when
+a maintainer steps down or when a new volunteer steps up to maintain
+an existing package (in which case they can appoint a new maintainer
+on behalf of the Chief GNUisance).</p>
+
+<p>New members are recruited from existing GNU volunteers when needed.
+However, help is often welcome for specific tasks and interested GNU
+volunteers are welcome to get in touch.</p>
+
+<h4 id="maintainers">Package maintainers</h4>
+
+<p>Each GNU software package has specific maintainers, appointed by
+the Chief GNUisance or the assistant GNUisances.  The package
+maintainers are responsible to the Chief GNUisance, under whose
+authority they are appointed and on rare occasions dismissed, and they
+are in charge of developing their packages on behalf of the GNU
+Project.</p>
+
+<p>The initial appointment of maintainers is done when a program is
+<a href="/help/evaluation.html">accepted as a GNU package</a>.  These
+are normally some of the main developers who agreed to make the
+program a GNU package.</p>
+
+<p>Over time, maintainers occasionally step down.  In some cases, the
+sole maintainer steps down from the role, leaving the package
+unmaintained.  The Chief GNUisance usually delegates finding and
+appointing new maintainers to the assistant GNUisances.
+<a href="/server/takeaction.html#unmaint">See the list of currently
+unmaintained packages</a>.  We ask the old maintainers to recommend
+new maintainers, and we consider those suggestions appreciatively.</p>
+
+<p>The maintainers of a package often recruit others to contribute to
+its development, and delegate some technical decisions to them.
+However, the maintainers retain authority over the whole of the
+package so they can carry out their responsibility to the GNU
+Project.</p>
+
+<p>A maintainer's primary responsibility is to do a good, practical
+job of developing and maintaining the program in accord with the GNU
+Project's philosophy, mission, policies, and general decisions.
+Maintainers must also ensure that their packages work well with the
+rest of the GNU System.  For more information,
+<a href="/help/evaluation.html#whatmeans">read about maintainers'
+basic duties and what it means for a program to be a GNU
+package</a>.</p>
+
+<p>In general, maintainers determine the technical directions that the
+software packages take and thus they make the day-to-day decisions for
+the packages.  Likewise, in making their packages work well together,
+maintainers can work directly with each other, and we encourage them
+to do so.  Rarely, the Chief GNUisance will make a decision that
+directly affects one or more GNU packages.  The maintainers of the
+affected packages have the responsibility to execute the decision on
+behalf of the GNU Project.</p>
+
+<p>More complete information about the specific responsibilities of
+maintainers and technical guidance for maintaining GNU software can be
+found in the <a href="/prep/maintain">Information for Maintainers of
+GNU Software</a> and <a href="/prep/standards">GNU Coding
+Standards</a> documents.</p>
+
+<p>We do not require that GNU package maintainers agree with our
+philosophy, or approve of our policies&mdash;only to follow them.
+Maintainers and contributors must carry out our philosophy, policies
+and occasional specific decisions in their work on GNU software.</p>
+
+<h3 id="package-development-support">Support for GNU Package Development</h3>
+
+<p>Several teams provide various kinds of support to the development
+and management of GNU packages.  Most of these teams have a
+coordinator to direct them; in most cases, the coordinator reports
+directly to the Chief GNUisance unless otherwise stated.  When in
+doubt, you can contact the <a href="mailto:address@hidden";>GNU Volunteer
+Coordinators</a> for advice.</p>
+
+<h4 id="gnueval">Software Evaluation</h4>
+
+<p>The software evaluation team at
+<a href="mailto:address@hidden";>address@hidden</a> evaluates
+software packages proposed as GNU packages.  This involves a careful
+assessment of the software's functionality as well as pertinent issues
+related to software freedom and how the program fits with the GNU
+system.</p>
+
+<p>New members are recruited from existing GNU volunteers when needed.
+Prior experience with non-GNU software evaluation on Savannah is
+preferable.</p>
+
+<h4 id="gnueval-security">Software Security Evaluation</h4>
+
+<p>The software security evaluation team at
+<a href="mailto:address@hidden";>address@hidden</a>
+works with the software evaluation team.  They determine whether there
+are any security concerns in software that has been offered to
+GNU.</p>
+
+<p>New members are recruited from existing GNU volunteers when
+needed.</p>
+
+<h4 id="security">Security Team</h4>
+
+<p>The <a href="mailto:address@hidden";>Security Team</a> helps to
+resolve security bugs in a timely fashion.  If the maintainer of a GNU
+package fails to respond to a report of a security flaw, the reporter
+can escalate the issue to the security team.  If it decides the issue
+is urgent, it can develop a patch and publish a fixed release of the
+package.  Maintainers can also ask the security team for advice in
+securing their packages.</p>
+
+<p>New members are recruited from existing GNU volunteers when
+needed.</p>
+
+<h4 id="platform-testers">Platform Testers</h4>
+
+<p>Volunteers behind the
+<a href="//lists.gnu.org/mailman/listinfo/platform-testers">address@hidden</a>
+mailing list test GNU software pre-releases on different hardware
+platforms to ensure that it functions correctly.</p>
+
+<p>New volunteers are welcome.</p>
+
+<h4 id="mentors">Mentors</h4>
+
+<p>The GNU Mentors
+(<a href="mailto:address@hidden";>address@hidden</a>) volunteer to
+provide guidance for new software maintainers.</p>
+
+<p>We ask long-time GNU maintainers to volunteer.</p>
+
+<h4 id="proofreaders">Proofreaders</h4>
+
+<p>The proofreaders list is available to help GNU package maintainers
+by proofreading English text.  To request proofreading, write to
+<a href="mailto:address@hidden";>address@hidden</a>.</p>
+
+<h3 id="other-teams-services">Other Teams and Services</h3>
+
+<p>Several other teams facilitate or manage the day-to-day operations
+within the GNU Project, or advance specific goals of the project.</p>
+
+<h4 id="gac">GNU Advisory Committee</h4>
+
+<p>The <a href="/contact/gnu-advisory.html">GNU Advisory Committee</a>
+(GAC) exists to provide advice to the Chief GNUisance.  Members of the
+Advisory Committee are appointed by the Chief GNUisance.  The Advisory
+Committee generally monitors the health of the GNU Project on behalf
+of the Chief GNUisance and they raise potential issues for
+discussion.</p>
+
+<h4 id="savannah-hackers">Savannah Hackers</h4>
+
+<p><a href="//savannah.gnu.org">Savannah</a> is the GNU Project's
+software forge.  It hosts code repositories, bug reporting tools,
+mailing list interfaces and more.  Savannah is administered by the
+<a href="mailto:address@hidden";>Savannah Hackers</a>.
+They keep the forge software up and running.  In addition to ensuring
+that GNU software is properly hosted in the service, the Savannah
+Hackers also evaluate non-GNU software that applies to be hosted on
+the forge.</p>
+
+<p>New volunteers are welcome.</p>
+
+<h4 id="webmasters">Webmasters</h4>
+
+<p>The <a href="/people/webmeisters.html">GNU Webmasters</a> maintain
+and update the web pages at <a href="/">https://www.gnu.org</a>.</p>
+
+<p>Webmasters also answer various kinds of questions sent by the
+public, regarding topics such as free software and licenses (when the
+answer is clear).  They do initial filtering of requests to evaluate a
+distro, evaluate people who would like to become webmasters, and
+update the list of mirrors.</p>
+
+<p>The GNU Webmaster Group is led by
+the&nbsp;<a href="mailto:address@hidden";>Chief Webmaster</a>
+who reports to&nbsp; the Chief GNUisance.  New volunteers are welcome.
+See <a href="/server/standards/webmaster-quiz.html">the Volunteer
+Webmaster Quiz</a>.</p>
+
+<h4 id="web-translators">Web Translators</h4>
+
+<p>Each language has a translation team, directed by a team
+coordinator.
+See <a href="/server/standards/README.translations.html">the Guide to
+Translating Web Pages on www.gnu.org</a> for more information.  The
+team coordinators report to
+the&nbsp;<a href="mailto:address@hidden";>GNU Translations
+Manager</a>, who&nbsp;reports to the Chief GNUisance.</p>
+
+<h4 id="list-helpers">List Helpers</h4>
+
+<p><a href="//savannah.gnu.org/maintenance/ListHelperAntiSpam/">Listhelper</a>
+is a system for semi-automatically managing spam sent to GNU mailing
+lists.  Most spam is caught by spam filters, but human moderators are
+also available to manage the queue of messages predicted not to be
+spam.</p>
+
+<p>New members are recruited from existing GNU volunteers when
+needed.</p>
+
+<h4 id="gvc">GNU Volunteer Coordinators</h4>
+
+<p>The GNU Volunteer Coordinators
+(<a href="mailto:address@hidden";>address@hidden</a>) help to guide new
+volunteers towards suitable jobs within the GNU Project</p>
+
+<p>New GVC volunteers are welcome, but prior experience volunteering
+within GNU (and thus broad knowledge of the GNU Project) is highly
+recommended.</p>
+
+<h4 id="education">GNU Education Team</h4>
+
+<p>The <a href="/education/">GNU Education Team</a> promotes the
+adoption of the GNU Operating System in educational environments.  It
+also evaluates schools and speaks to school administrators.</p>
+
+<p>New volunteers are welcome.</p>
+
+<h4 id="standards">GNU Standards Group</h4>
+
+<p>The GNU Standards Group evaluates proposals to update the GNU
+coding standards.  Anyone can submit a proposal via the
+<a href="//lists.gnu.org/mailman/listinfo/bug-standards">bug-standards</a>
+mailing list.  The group then discusses and evaluates the proposal to
+work out all the details and implications.  They then present the
+proposal and a recommendation to the Chief GNUisance, who makes the
+decision.  The group is also responsible for installing changes to the
+document as well as updating the document on the web.</p>
+
+<p>New volunteers are recruited from existing GNU volunteers when
+needed.</p>
+
+<h3 id="correcting-errors">Correcting Errors</h3>
+
+<p>If we find errors or omissions in this description of the existing
+structure, which are possible since it previously had no centralized
+documentation, we will update this document, both
+<a href="/gnu/gnu-structure.org">the Org version</a> and
+<a href="/gnu/gnu-structure.html">the HTML version</a>, advancing the
+third version number.  We will keep older versions available
+in <a href="/gnu/old-gnu-structure/">a subdirectory</a>.</p>
+
+<h3 id="future-changes">Future Changes in Administrative Structure</h3>
+
+<p>Changes in the GNU Project administrative structure are decided on
+by the Chief GNUisance after starting consultations with GNU
+contributors, usually on appropriate GNU Project discussion lists.
+The aim of these consultations is to consider possible alternatives
+and anticipate what good and bad effects they would have, so as to
+make a wise decision.</p>
+
+<p>To report changes that are adopted, we will update this document, 
+both the Org version and the HTML version (see previous section), 
+advancing the first and/or second version number.</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; 2020 Brandon Invergo and Richard Stallman</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: 2020/03/28 15:30:08 $
+<!-- timestamp end -->
+</p>
+</div>
+</div><!-- for class="inner", starts in the banner include -->
+</body>
+</html>



reply via email to

[Prev in Thread] Current Thread [Next in Thread]