www help/evaluation.html software/devel.html so...

[karl]

CVSROOT:        /web/www
Module name:    www
Changes by:     karl <karl>     14/11/05 18:53:33

Modified files:
        help           : evaluation.html 
        software       : devel.html software.html maintainer-tips.html 

Log message:
        link to maintainer-tips.html

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/help/evaluation.html?cvsroot=www&r1=1.40&r2=1.41
http://web.cvs.savannah.gnu.org/viewcvs/www/software/devel.html?cvsroot=www&r1=1.56&r2=1.57
http://web.cvs.savannah.gnu.org/viewcvs/www/software/software.html?cvsroot=www&r1=1.214&r2=1.215
http://web.cvs.savannah.gnu.org/viewcvs/www/software/maintainer-tips.html?cvsroot=www&r1=1.4&r2=1.5

Patches:
Index: help/evaluation.html
===================================================================
RCS file: /web/www/www/help/evaluation.html,v
retrieving revision 1.40
retrieving revision 1.41
diff -u -b -r1.40 -r1.41
--- help/evaluation.html        4 May 2014 18:22:29 -0000       1.40
+++ help/evaluation.html        5 Nov 2014 18:53:32 -0000       1.41
@@ -48,8 +48,8 @@
 freedom.</p>
 
 <p>So, in addition to the questionnaire, please read the GNU policies in
-the <a href="/prep/maintain_toc.html">Information for Maintainers of GNU
-Software</a> as well as the <a href="/prep/standards_toc.html">GNU
+the <a href="/prep/maintain/">Information for Maintainers of GNU
+Software</a> as well as the <a href="/prep/standards/">GNU
 Coding Standards</a>.  A <a href="#whatmeans">summary of the major
 policies</a> given below, but please also look through the full
 documents.</p>
@@ -148,6 +148,10 @@
 together.  This probably will happen less than once a year, but please
 make sure we can contact you in case it does happen.</p>
 
+<p>This short list of <a href="/software/maintainer-tips.html">tips for
+GNU maintainers</a> may be a useful overview of some things to do after
+your package becomes part of GNU.</p>
+
 <p>Finally, if you decide to step down as maintainer at any time, please
 <a href="/prep/maintain/html_node/Stepping-Down.html">inform
 us</a>.</p>
@@ -332,7 +336,7 @@
 
 <p class="unprintable">Updated:
 <!-- timestamp start -->
-$Date: 2014/05/04 18:22:29 $
+$Date: 2014/11/05 18:53:32 $
 <!-- timestamp end -->
 </p>
 </div>

Index: software/devel.html
===================================================================
RCS file: /web/www/www/software/devel.html,v
retrieving revision 1.56
retrieving revision 1.57
diff -u -b -r1.56 -r1.57
--- software/devel.html 12 Apr 2014 12:40:55 -0000      1.56
+++ software/devel.html 5 Nov 2014 18:53:32 -0000       1.57
@@ -6,14 +6,15 @@
 <!--#include virtual="/server/banner.html" -->
 <h2>GNU Development Resources</h2>
 
-<p>This page describes the development services available for GNU
-developers on GNU Project machines.  For full details of the privileges
-and responsibilities of GNU maintainers, please see the <a
+<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="/help/evaluation.html#whatmeans">overview of what it means to be a
-GNU package</a>.</p>
+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
@@ -65,9 +66,11 @@
 maintainer finds to be 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>
+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
@@ -268,7 +271,7 @@
 
 <p class="unprintable">Updated:
 <!-- timestamp start -->
-$Date: 2014/04/12 12:40:55 $
+$Date: 2014/11/05 18:53:32 $
 <!-- timestamp end -->
 </p>
 </div>

Index: software/software.html
===================================================================
RCS file: /web/www/www/software/software.html,v
retrieving revision 1.214
retrieving revision 1.215
diff -u -b -r1.214 -r1.215
--- software/software.html      14 Oct 2014 08:40:54 -0000      1.214
+++ software/software.html      5 Nov 2014 18:53:32 -0000       1.215
@@ -121,15 +121,11 @@
 
 <h3 id="develop">Develop GNU software</h3>
 
-<p>If you are developing a GNU package, please take a look at the
-available <a href="/software/devel.html">GNU software developer
-resources</a>.</p>
-
-<p>Although not strictly about official GNU software, we maintain a list
-of <a href="http://www.fsf.org/campaigns/priority.html";>high-priority
-free software projects</a>.  Please help with these projects if you can.
-For other ways to contribute to GNU, including taking over unmaintained
-GNU packages and helping with development, see the <a
+<p>The FSF maintains a list of <a
+href="http://www.fsf.org/campaigns/priority.html";>high-priority free
+software projects</a>; please help with these projects if you can.  For
+other ways to contribute to GNU, including reviving unmaintained GNU
+packages and helping with development, see the <a
 href="/help/help.html">GNU help wanted</a> page.</p>
 
 <p>If you're writing a new program and would like to make your software
@@ -137,6 +133,13 @@
 href="/help/evaluation.html">evaluation information and submission
 form</a>.</p>
 
+<p>If you're maintaining or developing a GNU package, whether newly
+dubbed or of long standing, this short list of <a
+href="/software/maintainer-tips.html">tips for GNU maintainers</a> may
+be useful, along with this information about <a
+href="/software/devel.html">GNU software developer resources</a>.</p>
+
+
 
 <h3><a id="allgnupkgs">All GNU packages</a></h3>
 
@@ -313,7 +316,7 @@
 
 <p class="unprintable">Updated:
 <!-- timestamp start -->
-$Date: 2014/10/14 08:40:54 $
+$Date: 2014/11/05 18:53:32 $
 <!-- timestamp end -->
 </p>
 </div>

Index: software/maintainer-tips.html
===================================================================
RCS file: /web/www/www/software/maintainer-tips.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -b -r1.4 -r1.5
--- software/maintainer-tips.html       1 Nov 2014 07:49:00 -0000       1.4
+++ software/maintainer-tips.html       5 Nov 2014 18:53:32 -0000       1.5
@@ -16,13 +16,12 @@
 
 <p>Of course, what's listed here just skims the surface of GNU
 maintainership.  Please be sure to read the <a
-href="https://gnu.org/prep/maintain/";>GNU Maintainers Guide</a> and the
-<a href="https://gnu.org/prep/standards/";>GNU Coding Standards</a>.
-Indeed, you should have read them already, but they are densely enough
-written that careful re-readings are useful.  In addition, a few
-experienced GNU contributors have volunteered to answer questions about
-GNU maintenance via <a href="mailto:address@hidden";>address@hidden</a>
-as well as <a
+href="/prep/maintain/">GNU Maintainers Guide</a> and the <a
+href="/prep/standards/">GNU Coding Standards</a>.  Indeed, you should
+have read them already, but they are densely enough written that careful
+re-readings are useful.  In addition, a few experienced GNU contributors
+have volunteered to answer questions about GNU maintenance via <a
+href="mailto:address@hidden";>address@hidden</a> as well as <a
 href="mailto:address@hidden";>address@hidden</a>.</p>
 
 <h3>First steps for new maintainers</h3>
@@ -54,7 +53,7 @@
 be on any or all of a Savannah bug tracker, a mailing list (mbox
 archives are available via <a href="ftp://lists.gnu.org/";>ftp</a> and <a
 href="rsync://lists.gnu.org/mbox/">rsync</a>), or at the <a
-href="https://debbugs.gnu.org";>GNU debbugs server</a>.  (<a
+href="https://debbugs.gnu.org/";>GNU debbugs server</a>.  (<a
 href="/prep/maintain/html_node/Replying-to-Mail.html">About replying to
 bug reports.</a>)</li>
 
@@ -96,7 +95,9 @@
 <li><b>Focus on fixing outstanding bugs first.</b>  An excellent way to
 begin to learn a new codebase is to fix some outstanding bugs to get a
 feel for how the system works.  Besides, new features shouldn't be given
-much focus if notable problems already exist.</li>
+much focus if notable problems already exist.  (<a
+href="/software/devel.html">About resources for GNU
+developers.</a>)</li>
 
 <li><b>Don't try to rewrite the entire thing.</b>  If you've adopted
 a package, we strongly recommend that you not set out to rewrite the
@@ -198,7 +199,7 @@
 
 <p class="unprintable">Updated:
 <!-- timestamp start -->
-$Date: 2014/11/01 07:49:00 $
+$Date: 2014/11/05 18:53:32 $
 <!-- timestamp end -->
 </p>
 </div>