www/software devel.html

[Karl Berry]

CVSROOT:        /web/www
Module name:    www
Changes by:     Karl Berry <karl>       10/04/22 18:45:55

Modified files:
        software       : devel.html 

Log message:
        reformat

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/software/devel.html?cvsroot=www&r1=1.29&r2=1.30

Patches:
Index: devel.html
===================================================================
RCS file: /web/www/www/software/devel.html,v
retrieving revision 1.29
retrieving revision 1.30
diff -u -b -r1.29 -r1.30
--- devel.html  27 Nov 2009 20:06:25 -0000      1.29
+++ devel.html  22 Apr 2010 18:45:53 -0000      1.30
@@ -4,46 +4,30 @@
 <!--#include virtual="/server/banner.html" -->
 <h2>GNU Development Resources</h2>
 
-<!-- This document uses XHTML 1.0 Strict, but may be served as -->
-<!-- text/html.  Please ensure that markup style considers -->
-<!-- appendex C of the XHTML 1.0 standard. See validator.w3.org. -->
-
-<!-- Please ensure links are consistent with Apache's MultiView. -->
-<!-- Change include statements to be consistent with the relevant -->
-<!-- language, where necessary. -->
-
-<h3 id="Introduction">Introduction</h3>
-
-<p>
-  This page describes the development services available for GNU
-  developers on GNU Project machines. If you would like to make use of
-  one of these services for development of a GNU package, please contact
-  the address listed for the particular service. For full details of the
-  privileges and responsibilities of GNU maintainers, please see the
-  <a href="/prep/maintain_toc.html">Information for GNU Maintainers</a>
-  document. (The <a href= "/prep/standards_toc.html"
-      >GNU Coding Standards</a> may also be of interest, and the 
-  <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>This page describes the development services available for GNU
+developers on GNU Project machines. If you would like to make use of one
+of these services for development of a GNU package, please contact the
+address listed for the particular service. For full details of the
+privileges and responsibilities of GNU maintainers, please see the <a
+href="/prep/maintain_toc.html">Information for GNU Maintainers</a>
+document. (The <a href="/prep/standards/">GNU Coding Standards</a> may
+also be of interest, and the <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>
 
-<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>
 
@@ -61,56 +45,40 @@
 
 <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 this
-  package.
-</p>
-
-<p>
-  Each GNU software package ought to have at least a bug-reporting
-  list with the canonical name <code>bug-<em>name</em>@gnu.org</code>,
-  plus whatever other aliases 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, for asking for help,
-  for posting related source code, for discussion among users, or
-  whatever the package maintainer thinks is useful.
-</p>
-
-<p>
-  Mailing list archives for automatically-managed lists are available at
-  <a href= "http://lists.gnu.org/";>http://lists.gnu.org</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>We operate mailing lists for GNU software packages as needed,
+including both hand-managed lists and automatically managed lists.</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>
+<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 this
+package.</p>
+
+<p>Each GNU software package ought to have at least a bug-reporting list
+with the canonical name <code>bug-<em>name</em>@gnu.org</code>, plus
+whatever other aliases 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, for asking for help,
+for posting related source code, for discussion among users, or whatever
+the package maintainer thinks is useful.</p>
+
+<p>Mailing list archives for automatically-managed lists are available
+at <a href="http://lists.gnu.org/";>http://lists.gnu.org</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 Server</h3>
 
-<p>
-  Our master web server is located at <a href=
-      "http://www.gnu.org/";>http://www.gnu.org/</a>, and has <a href=
-      "/server/list-mirrors.html">mirrors</a> around the world. We would
-  like to host pages on this server about each and every GNU software
-  package.
-</p>
+<p>Our master web server is <a
+href="http://www.gnu.org/";>http://www.gnu.org/</a>.  We would like to
+host pages on this server about each and every GNU software package.</p>
 
 <p>The machine which serves the <code>www.gnu.org</code> web pages is
 separate from the rest of the GNU machines.  GNU packages should use
@@ -124,34 +92,26 @@
 
 <h3 id="FTP">FTP</h3>
 
-<p>
-  We can also provide an FTP site for any GNU software package on
-  <a href="http://ftp.gnu.org/";><code>http://ftp.gnu.org/</code></a>,
-  which is <a href="/order/ftp.html">mirrored worldwide</a>.
-</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_toc.html"
-  >Information for GNU Maintainers</a> document has complete details on
-  the FTP upload process.
-</p>
+<p>We can also provide an FTP site for any GNU software package on <a
+href="http://ftp.gnu.org/";><code>http://ftp.gnu.org/</code></a>, which
+is <a href="/order/ftp.html">mirrored worldwide</a>.</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_toc.html">Information for GNU
+Maintainers</a> document has complete details on the FTP upload
+process.</p>
 
 
 <h3 id="LoginAccounts">Login Accounts</h3>
 
-<p>
-  We give out 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.
-  Please read <a href="README.accounts.html">access methods for GNU
-  machines</a> in order to obtain an account.
-</p>
+<p>We give out 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.  Please read <a href="README.accounts.html">access methods
+for GNU machines</a> in order to obtain an account.</p>
 
 
 <!-- If needed, change the copyright block at the bottom. In general,
@@ -176,19 +136,15 @@
 README</a> for information on coordinating and submitting translations
 of this article.</p>
 
-<p>
-Copyright &copy; 2004, 2006, 2007, 2008, 2009 Free Software Foundation, Inc.,
-</p>
-<address>51 Franklin St, Fifth Floor, Boston, MA 02110, USA</address>
+<p>Copyright &copy; 2010 Free Software Foundation, Inc.</p>
+
 <p>Verbatim copying and distribution of this entire article are
 permitted worldwide, without royalty, in any medium, provided this
-notice, and the copyright notice, are preserved.
-</p>
+notice, and the copyright notice, are preserved.</p>
 
-<p>
-Updated:
+<p>Updated:
 <!-- timestamp start -->
-$Date: 2009/11/27 20:06:25 $
+$Date: 2010/04/22 18:45:53 $
 <!-- timestamp end -->
 </p>
 </div>