www/server source/source.html standards/README....

[Karl Berry]

CVSROOT:        /web/www
Module name:    www
Changes by:     Karl Berry <karl>       09/11/18 17:07:58

Modified files:
        server/source  : source.html 
        server/standards: README.html README.webmastering.html 

Log message:
        README merge continues: scripts

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/server/source/source.html?cvsroot=www&r1=1.19&r2=1.20
http://web.cvs.savannah.gnu.org/viewcvs/www/server/standards/README.html?cvsroot=www&r1=1.60&r2=1.61
http://web.cvs.savannah.gnu.org/viewcvs/www/server/standards/README.webmastering.html?cvsroot=www&r1=1.93&r2=1.94

Patches:
Index: source/source.html
===================================================================
RCS file: /web/www/www/server/source/source.html,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -b -r1.19 -r1.20
--- source/source.html  31 Mar 2007 11:04:27 -0000      1.19
+++ source/source.html  18 Nov 2009 17:07:49 -0000      1.20
@@ -22,7 +22,7 @@
 </p>
 
 <HR>
-<P>
+<P>(This page needs updating.  Please update it.)
 
 <H4>Table of contents</H4>
 <UL>
@@ -168,11 +168,9 @@
        after a "cvs update" to fix the symbolic links according to the
        specifications included in the ".symlinks" files.
 
-<P>
-      Complete information about this script can be found in
-      the <a href="../standards/README.html#SEC01">Symbolic Links</a>
-      section of the GNU Webmaster Guidelines.
-<P>
+<P>More information about this script can be found in the <a
+href="/server/standards/README.webmaster.html#symlinks">Symbolic
+Links</a> section of the GNU Webmaster Guidelines.
 
 <P>
 <H4><A HREF="#TOCsavannahusers" NAME="savannahusers">savannahusers</A></H4>
@@ -233,7 +231,7 @@
 permitted in any medium, provided this notice is preserved.<P>
 Updated:
 <!-- timestamp start -->
-$Date: 2007/03/31 11:04:27 $
+$Date: 2009/11/18 17:07:49 $
 <!-- timestamp end -->
 <HR>
 </BODY>

Index: standards/README.html
===================================================================
RCS file: /web/www/www/server/standards/README.html,v
retrieving revision 1.60
retrieving revision 1.61
diff -u -b -r1.60 -r1.61
--- standards/README.html       17 Nov 2009 17:39:26 -0000      1.60
+++ standards/README.html       18 Nov 2009 17:07:54 -0000      1.61
@@ -32,7 +32,6 @@
   <a id="TOC9" href="README.html#SEC9">Update GNUs Flashes on the
   home page http://www.gnu.org/</a>
 </li>
-<li><a id="TOC13" href="README.html#SEC13">Scripts</a></li>
 <li><a id="TOC16" href="README.html#SEC16">Audio and video files</a></li>
 <li><a id="TOC17" href="README.html#SEC17">Adding an Event</a></li>
 </ul>
@@ -131,17 +130,6 @@
 <a 
href="/server/standards/README.webmastering.html#polnews">/server/standards/README.webmastering.html</a>.
 </p>
 
-<h4><a id="SEC13" href="README.html#TOC13">Scripts</a></h4>
-
-<p>
-For a description of scripts/software that is used on
-www.gnu.org, please read
-<a href="/server/source/source.html">
-http://www.gnu.org/server/source/source.html</a>.
-Be sure to read that before trying to write any scripts that work
-with the website, such as programs that automatically updated pages.
-</p>
-
 <h4>
   <a id="SEC16" href="README.html#TOC16">Audio and video files</a>
 </h4>
@@ -271,7 +259,7 @@
 <p>
 Updated:
 <!-- timestamp start -->
-$Date: 2009/11/17 17:39:26 $
+$Date: 2009/11/18 17:07:54 $
 <!-- timestamp end -->
 </p>
 </div>

Index: standards/README.webmastering.html
===================================================================
RCS file: /web/www/www/server/standards/README.webmastering.html,v
retrieving revision 1.93
retrieving revision 1.94
diff -u -b -r1.93 -r1.94
--- standards/README.webmastering.html  17 Nov 2009 17:39:26 -0000      1.93
+++ standards/README.webmastering.html  18 Nov 2009 17:07:54 -0000      1.94
@@ -111,7 +111,7 @@
 </p>
 
 
-<h3>Handling Press Releases</h3>
+<h3>Handling press releases</h3>
 
 <p>Occasionally, the webmasters are asked to handle press releases.  These
 are in the <a href="/press">/press</a> directory.  You should always make
@@ -168,7 +168,7 @@
 </ul>
 
 
-<h3>Webmaster Organization</h3>
+<h3>Webmaster organization</h3>
 
 <p>
 The following organizational rules are not rigid; they are designed to
@@ -216,7 +216,7 @@
 </p>
 
 
-<h3>Leaving Webmasters</h3>
+<h3>Leaving webmasters</h3>
 
 <p>
 We realize that people's lives change, and we know that you may not want
@@ -250,7 +250,7 @@
 this, just mail www-discuss.</p>
 
 <a name="rtguide"></a>
-<h4>RT - Quick Guide</h4>
+<h4>RT - quick guide</h4>
 
 <p>First and foremost: use your judgment, rather than blindly following
 procedures.  If the action on a particular ticket seems questionable to
@@ -326,7 +326,7 @@
 
 </ul>
 
-<h4>RT - Correspondence vs. Comments</h4>
+<h4>RT - correspondence vs. comments</h4>
 
 <p>
 You can attach two kinds of information to a ticket: correspondence and
@@ -390,7 +390,7 @@
 format.  Please check with www-discuss for these.
 </p>
 
-<h4>RT - Coordination With Others</h4>
+<h4>RT - coordination with others</h4>
 
 <p>
 You will often need to ask other people for more information about how to
@@ -425,7 +425,7 @@
 </p>
 
 
-<h4>RT - Ticket Status</h4>
+<h4>RT - ticket status</h4>
 
 <p>Here are the possible ticket statuses in RT:</p>
 
@@ -468,7 +468,7 @@
 </ul>
 
 
-<h4>RT - Ticket Escalation</h4>
+<h4>RT - ticket escalation</h4>
 
 <p>If you'd like to handle a request but aren't sure how to go about it,
 or think a request is important and may have been overlooked, leave the
@@ -476,7 +476,7 @@
 
 
 <a name="rtmisdirected"></a>
-<h4>RT - Misdirected Tickets</h4>
+<h4>RT - misdirected tickets</h4>
 
 <p>Sometimes people send mail to webmasters which is best handled
 elsewhere.  When this happens, you can do one of two things: redirect
@@ -544,7 +544,7 @@
 email.</p>
 
 
-<h4>RT - Spam Quarantine</h4>
+<h4>RT - spam quarantine</h4>
 
 <p>The spam quarantine is a collection of mails to address@hidden
 that are caught by our spam filter, and should be checked daily for
@@ -570,7 +570,7 @@
 <!-- appropriate portion, or combine it with the guidelines section. -->
 
 
-<h3>Other Webmastering Procedures and Policies to Consider</h3>
+<h3>Other webmastering procedures and policies</h3>
 
 <p>
 There are certain procedures and policies which take hold over the entire
@@ -578,7 +578,7 @@
 standards.  Bear these in mind when working on the page.
 </p>
 
-<h4>Inter-site Structure and Navigation</h4>
+<h4>Inter-site structure and navigation</h4>
 
 <p>
 The site is divided up into directories by topic&mdash;there's a directory for
@@ -727,7 +727,7 @@
 
 
 <a id="distros"></a>
-<h4>Links to free GNU/Linux Distributions</h4>
+<h4>Links to free GNU/Linux distributions</h4>
 
 <p>Suggestions for links to GNU/Linux distributions that come to
 address@hidden should be forwarded to the Free Software Directory
@@ -738,67 +738,7 @@
 approval.</p>
 
 
-<a id="symlinks"></a>
-<h4>Symbolic links</h4>
-
-<p>Since CVS is not able to handle symbolic links directly, a separate
-mechanism has been implemented to allow webmasters to maintain symbolic
-links, as follows.  (Actual symbolic links are no longer created on
-<tt>www.gnu.org</tt>; mod_rewrite rules are used instead.  But we'll
-keep this discussion talking about symlinks since it is easier to
-understand that way.)</p>
-
-<p>Special files, named .symlinks, can be committed to the CVS tree that
-are interpreted as specificiations to build symbolic links.  On commit,
-the current directory is searched recursively for .symlinks files.  Only
-directories containing a .symlinks file are handled.</p>
-
-<p>Each symbolic link specification from the .symlinks file is honored,
-i.e., the symbolic link is created if it does not exist yet. If a
-symbolic link is found in the directory and is not listed in the
-.symlinks file, it is removed.</p>
-
-<p>As a special case, if a page with the directory's name exists, and
-index.html does not exist, a link will be made from index.html to the
-main page.</p>
-
-<p>Symbolic links that point outside the web site document root are
-ignored.</p>
-
-<p>The .symlinks files obey the "ln -s" format, as described below:</p>
-
-<p>Lines starting with a sharp sign ("#") are ignored.</p>
-
-<p>Lines that do not contain two strings separated by white space are silently
-ignored.</p>
-
-<p>Symbolic links that point outside the web site document root are
-ignored.</p>
-
-<p>Here is an example of a .symlinks file:</p>
-
-<pre>
-# Make a link named l.html to a target t.html.
-# Strictly equivalent to ln -s t.html l.html:
-t.html l.html
-</pre>
-
-<p>On each line the first file name must be a relative path name to an
-existing file. The file designated by this path must not be outside the
-document root. The second file name may not contain any slash; it is the
-name of the symbolic link to be created in the present directory.</p>
-
-<p>At one time, the command used to implement this feature was
-web-symlinks, a Perl script; <a
-href="http://cvs.savannah.gnu.org/viewvc/www/symlinks/?root=www";>it can
-be found in www's sources CVS</a>.  It is completely different from the
-<a href="http://ibiblio.org/pub/linux/utils/file/";>symlinks utility</a>
-for verifying a system's symbolic links.  These days, the .symlinks
-handling happens on <tt>www.gnu.org</tt> itself and webmasters do not
-have access to it.</p>
-
-
-<h4 id="pollinking">Linking Policies</h4>
+<h4 id="pollinking">Linking policies</h4>
 
 <p>
 One of the most complex aspects of webmastering is following the linking
@@ -981,7 +921,7 @@
 possibility and be ready to handle them properly.
 </p>
 
-<h4>Handling Common Requests</h4>
+<h4>Handling common requests</h4>
 
 <p>
 There are a number of requests which recur frequently.  This section
@@ -994,7 +934,7 @@
 here.  Only requests which may require non-obvious action are listed.
 </p>
 
-<h4>Fixing Dead Links</h4>
+<h4>Fixing dead links</h4>
 
 <p>
 If a link has gone bad because a page has moved, try to find its
@@ -1014,7 +954,7 @@
 maintainer&mdash;please notify them of the problem and what you did to fix it.
 </p>
 
-<h4>Adding Links</h4>
+<h4>Adding links</h4>
 
 <p>
 We'll sometimes be asked to add links to the page; most often, this will
@@ -1045,7 +985,7 @@
 feel the link is most appropriate for our site.
 </p>
 
-<h4>Adding New Articles</h4>
+<h4>Adding new articles</h4>
 
 <p>Occasionally, RMS will mail an article, usually in plain text, to
 webmasters and ask that they put it on the site.  The text needs to be
@@ -1079,7 +1019,7 @@
 
 
 <a id="gnupackages"></a>
-<h4>Web Pages for GNU Software Packages</h4>
+<h4>Web pages for official GNU software</h4>
 
 <p>GNU software maintainers usually gain CVS write access to their
 /software subdirectory by registering their project with Savannah.  (In
@@ -1094,7 +1034,7 @@
 change.</p>
 
 
-<h4>Adding Translations</h4>
+<h4>Adding translations</h4>
 
 <p>
 Occasionally, someone will send us a translation of a single page.  You
@@ -1106,7 +1046,7 @@
 translation teams is available there as well.
 </p>
 
-<h4>Deleting Translations</h4>
+<h4>Deleting translations</h4>
 
 <p>
 Here and there you might find a translated page which is actually a copy of
@@ -1119,7 +1059,7 @@
 the page to be left alone, you can handle it as you see fit.
 </p>
 
-<h4>Adding an Event to the Events Page</h4>
+<h4>Adding an event to the events page</h4>
 
 <p>
 Sometimes we will be asked to add an event to the events page.  If the
@@ -1128,14 +1068,13 @@
 person is address@hidden; otherwise, it's the speaker themselves.
 </p>
 
-<p>
-If the request is urgent, and the request is coming from FSF staff, you can
+<p>If the request is urgent, and the request is coming from FSF staff, you can
 add the event to /events/events.input-html, above the AUTO
 section. However, if you do so, please take responsibility for the event
-and remove it when it has passed.
-</p>
+and remove it when it has passed.</p>
 
-<h4>Requests For Permission To Use An Image</h4>
+
+<h4>Requests for permission to use an image</h4>
 
 <p>When someone emails requesting permission to use an 
 image from the Art section of the site, the first thing to do is to check the
@@ -1154,6 +1093,14 @@
 should give permission for. Feel free to discuss any requests with www-discuss
 before responding to them.</p>
 
+
+<h4><a id="scripts">Scripts</a></h4>
+
+<p>A <a href="/server/source/source.html">description of scripts and
+software</a> used on www.gnu.org is available.  Please read it before
+writing any scripts, and also update it as needed.</p>
+
+
 <h4>Checking out the repository</h4>
 
 <p>To make an initial checkout of our repository, set the environment
@@ -1186,7 +1133,67 @@
 says ok.  At the very least, inform them if you make a change.</p>
 
 
-<h4>System Administrators</h4>
+<a id="symlinks"></a>
+<h4>Symbolic links</h4>
+
+<p>Since CVS is not able to handle symbolic links directly, a separate
+mechanism has been implemented to allow webmasters to maintain symbolic
+links, as follows.  (Actual symbolic links are no longer created on
+<tt>www.gnu.org</tt>; mod_rewrite rules are used instead.  But we'll
+keep this discussion talking about symlinks since it is easier to
+understand that way.)</p>
+
+<p>Special files, named .symlinks, can be committed to the CVS tree that
+are interpreted as specificiations to build symbolic links.  On commit,
+the current directory is searched recursively for .symlinks files.  Only
+directories containing a .symlinks file are handled.</p>
+
+<p>Each symbolic link specification from the .symlinks file is honored,
+i.e., the symbolic link is created if it does not exist yet. If a
+symbolic link is found in the directory and is not listed in the
+.symlinks file, it is removed.</p>
+
+<p>As a special case, if a page with the directory's name exists, and
+index.html does not exist, a link will be made from index.html to the
+main page.</p>
+
+<p>Symbolic links that point outside the web site document root are
+ignored.</p>
+
+<p>The .symlinks files obey the "ln -s" format, as described below:</p>
+
+<p>Lines starting with a sharp sign ("#") are ignored.</p>
+
+<p>Lines that do not contain two strings separated by white space are silently
+ignored.</p>
+
+<p>Symbolic links that point outside the web site document root are
+ignored.</p>
+
+<p>Here is an example of a .symlinks file:</p>
+
+<pre>
+# Make a link named l.html to a target t.html.
+# Strictly equivalent to ln -s t.html l.html:
+t.html l.html
+</pre>
+
+<p>On each line the first file name must be a relative path name to an
+existing file. The file designated by this path must not be outside the
+document root. The second file name may not contain any slash; it is the
+name of the symbolic link to be created in the present directory.</p>
+
+<p>At one time, the command used to implement this feature was
+web-symlinks, a Perl script; <a
+href="http://cvs.savannah.gnu.org/viewvc/www/symlinks/?root=www";>it can
+be found in www's sources CVS</a>.  It is completely different from the
+<a href="http://ibiblio.org/pub/linux/utils/file/";>symlinks utility</a>
+for verifying a system's symbolic links.  These days, the .symlinks
+handling happens on <tt>www.gnu.org</tt> itself and webmasters do not
+have access to it.</p>
+
+
+<h4>System administrators</h4>
 
 <p>The system administrators for GNU change from time to time.  Please
 email the sysadmin list (address@hidden) rather than an individual,
@@ -1224,7 +1231,7 @@
 
 <p>Updated:
 <!-- timestamp start -->
-$Date: 2009/11/17 17:39:26 $
+$Date: 2009/11/18 17:07:54 $
 <!-- timestamp end -->
 </p>
 </div>