www/server/standards README.html README.webmast...

[Karl Berry]

CVSROOT:        /web/www
Module name:    www
Changes by:     Karl Berry <karl>       09/11/11 19:41:01

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

Log message:
        merge timestamp info

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/server/standards/README.html?cvsroot=www&r1=1.56&r2=1.57
http://web.cvs.savannah.gnu.org/viewcvs/www/server/standards/README.webmastering.html?cvsroot=www&r1=1.89&r2=1.90

Patches:
Index: README.html
===================================================================
RCS file: /web/www/www/server/standards/README.html,v
retrieving revision 1.56
retrieving revision 1.57
diff -u -b -r1.56 -r1.57
--- README.html 10 Nov 2009 18:55:39 -0000      1.56
+++ README.html 11 Nov 2009 19:40:20 -0000      1.57
@@ -28,14 +28,6 @@
   www.gnu.org/... ?</a>
 </li>
 <li><a id="TOC2" href="README.html#SEC2">Webmasters</a></li>
-<li><a id="TOC3" href="README.html#SEC31">CVS and timestamps</a></li>
-<li><a id="TOC3" href="README.html#SEC3">.emacs and timestamps</a></li>
-<li><a id="TOC4" href="README.html#SEC4">umask</a></li>
-<li>
-  <a id="TOC5" href="README.html#SEC5">Using the
-   <code>TAGS</code> file</a>
-</li>
-<li><a id="TOC6" href="README.html#SEC6">Groups on files</a></li>
 <li>
   <a id="TOC7" href="README.html#SEC7">Update the What's New page!</a>
 </li>
@@ -175,61 +167,6 @@
 </p>
 
 <h4>
-  <a id="SEC31" href="README.html#TOC31">CVS and timestamps</a>
-</h4>
-
-<p>
-Each HTML file should contain a timestamp.  Because we only recently
-switched to CVS, there are still two ways that timestamps are done.  The
-preferred way is via CVS:
-</p>
-
-<pre>
-Updated:
-&lt;!-- timestamp start --&gt;
-&#36;Date:&#36;
-&lt;!-- timestamp end --&gt;
-&lt;HR&gt;
-</pre>
-
-<p>
-If you are working in a file that is stored by CVS, and such a timestamp
-entry isn't in the file, please add it.  If a file under CVS that you are
-working in still uses the <pre>hhmts</pre> method for updates described
-below, please switch it to the <pre>timestamp</pre> method.
-</p>
-
-<h4><a id="SEC3" href="README.html#TOC3">.emacs and timestamps</a></h4>
-
-<p>
-If the web directory you are working in isn't in CVS, please use this
-method, via your .emacs, to update the timestamp.
-</p>
-
-<p>
-The file <code>~www/.emacs</code> contains some suggestions for your
-own <code>~/.emacs</code>.  In particular, what we want is numbered
-backups and the "Last updated" field changed automatically on file
-write&mdash;this field is the date and user name between these two
-comments lines:
-</p>
-
-<pre>
-&lt;!-- hhmts start --&gt;
-18 Apr 2000 tower
-&lt;!-- hhmts end --&gt;
-</pre>
-<p>
-An easy way to use them and get future updates is to add these lines
-to your own <code>~/.emacs</code>:
-</p>
-<pre>
-(let ((www-emacs-file (expand-file-name "~www/.emacs")))
-(if (file-exists-p www-emacs-file)
-(load-file www-emacs-file)))
-</pre>
-
-<h4>
   <a id="SEC7" href="README.html#TOC7">Update the What's New page!</a>
 </h4>
 
@@ -555,7 +492,7 @@
 <p>
 Updated:
 <!-- timestamp start -->
-$Date: 2009/11/10 18:55:39 $
+$Date: 2009/11/11 19:40:20 $
 <!-- timestamp end -->
 </p>
 </div>

Index: README.webmastering.html
===================================================================
RCS file: /web/www/www/server/standards/README.webmastering.html,v
retrieving revision 1.89
retrieving revision 1.90
diff -u -b -r1.89 -r1.90
--- README.webmastering.html    10 Nov 2009 18:55:41 -0000      1.89
+++ README.webmastering.html    11 Nov 2009 19:40:22 -0000      1.90
@@ -115,31 +115,25 @@
 
 <h3>Handling Press Releases</h3>
 
-<p>
-Occasionally, the webmasters are asked to handle press releases.  These
+<p>Occasionally, the webmasters are asked to handle press releases.  These
 are in the <a href="/press">/press</a> directory.  You should always make
 both a text and HTML version, and follow the format used for other press
 releases.  (Some do have PDF and Postscript, but webmasters need not worry
-about that at the moment).
-</p>
+about that at the moment).</p>
 
-<p>
-Currently, it is often <a href="mailto:address@hidden";>johns</a> who
-handles the text version of a press release.
-He will normally commit the <acronym title="American Standard Code for 
Information Interchange">ASCII</acronym> version, and then tell webmasters to 
do the "rest" or "DTRT" (do
-the right thing) with it.</p>
-<p>(Although sometimes the file will be emailed to webmasters instead.)  You 
will also be given a date and time when the press release should be up.
-</p>
+<p>Currently, it is often <a href="mailto:address@hidden";>johns</a> who
+handles the text version of a press release.  He will normally commit
+the <acronym title="American Standard Code for Information
+Interchange">ASCII</acronym> version, and then tell webmasters to do the
+"rest" or "DTRT" (do the right thing) with it.  
+Sometimes the file will be emailed to webmasters instead.  You will
+also be given a date and time when the press release should be up.</p>
 
-<p>
-For the time being, always check with johns before posting any press
+<p>At present, always check with johns before posting any press
 releases sent in by other parties, and note that johns will always
-GPG-sign his messages about press releases.
-</p>
+GPG-sign his messages about press releases.</p>
 
-<p>
-To handle one of these requests, here is what you should do:
-</p>
+<p>To handle one of these requests, here is what you should do:</p>
 
 <ul>
 <li>Make an HTML version of the ASCII file, following the
@@ -232,15 +226,14 @@
 us know when you want to move on: please don't simply disappear.
 </p>
 
-<p>
-When you sign up to be a webmaster, you commit to a certain number of
-hours a week of volunteer work.  If you need to drop below that level for
-more than a few weeks, or want to stop being a webmaster entirely, please
-inform <a href="mailto:address@hidden";>
+<p>When you sign up to be a webmaster, you commit to a certain number of
+hours a week of volunteer work.  If you need to drop below that level
+for more than a few weeks, or want to stop being a webmaster entirely,
+please inform <a href="mailto:address@hidden";>
 &lt;address@hidden&gt;</a> and <a
-href="mailto:address@hidden";> &lt;address@hidden&gt;</a>
-as soon as your situation changes.
-</p>
+href="mailto:address@hidden";>
+&lt;address@hidden&gt;</a> as soon as your situation
+changes.</p>
 
 
 
@@ -627,13 +620,11 @@
 by adding an entry to the /server/whatsnew.txt file (see <a href="#polnews" 
>Adding news</a>)
 </p>
 
-<p>
-If you're adding a new page, add a link to the directory's main page.  For
-example, if you've created a new page with more GNU history,
-/gnu/more-history.html, add a link to it from /gnu/gnu.html.  If the page
-is particularly useful, consider adding a link on /server/sitemap.html as
-well.
-</p>
+<p>If you're adding a new page, add a link to the directory's main page.
+For example, if you've created a new page with more GNU history,
+/gnu/more-history.html, add a link to it from /gnu/gnu.html.  If the
+page is particularly useful, consider adding a link on
+/server/sitemap.html as well.</p>
 
 <p>
 If the page discusses an important issue, consider adding a notice about it
@@ -719,10 +710,11 @@
 <p>ftp mirrors: when we get a request to add, change, or remove an ftp
 mirror, edit the file prep/FTP (in CVS); it's just text, not HTML.  Then
 make (in the prep/ subdirectory).  Then cvs commit both FTP and
-ftp.html, and updated /gd/gnuorg/web/FTP.contacts on fencepost.  A <a
-href="http://gnu-mirmon.basemirror.de";>mirmon page</a> tracks how
-up-to-date each mirror is; it is good to write a mirror contact when it
-has gotten more than a week or two out of date.</p>
+ftp.html, and update /gd/gnuorg/web/FTP.contacts on fencepost, following
+the pattern.  A <a href="http://gnu-mirmon.basemirror.de";>mirmon
+page</a> tracks how up-to-date each mirror is; it is good to write a
+mirror contact when it has gotten more than a week or two out of
+date.</p>
 
 <p>nongnu mirrors: when we get a request to add, change, or remove a
 nongnu savannah mirror, email address@hidden with the
@@ -1057,33 +1049,34 @@
 
 <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 converted to
-the HTML and put into our standard boilerplate; you can use
-/boilerplate.html to provide a template for the header and footer, or base
-your page from another article.  There are some things which you should
-look out for when doing the conversion:
-</p>
+<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
+converted to the HTML and put into our standard boilerplate; you can use
+/boilerplate.html to provide a template for the header and footer, or
+base your page from another article.  There are some things which you
+should look out for when doing the conversion:</p>
 
 <ul>
-<li>Remember to make sure translation links actually use the page's given
-  name, rather than a boilerplate one</li>
-<li>Make sure the article's title is put in both locations, in the 
&lt;title&gt;
-  tag and in the &lt;h2&gt; text at the top of the page</li>
-<li>Put the author of the article in the page's header as well</li>
-<li>Provide a link back to the directory's main page (if it is a
-  speech or an interview, please state briefly the topic)</li>
+<li>Ensure that translation links use the page's given
+  name, rather than a boilerplate one.</li>
+<li>Ensure that the article's title is put in both the
+  &lt;title&gt; tag and in the &lt;h2&gt; text at the top of the page.</li>
+<li>Put the author of the article in the page's header as well.</li>
+<li>Provide a link back to the directory's main page.  If it is a
+   speech or an interview, briefly state the topic.</li>
+<li>New pages (and existing pages) should have a timestamp at the bottom.
+   See the <a href="boilerplate.html">boilerplate</a> file for the precise
+   location and format.</li>
 </ul>
 
-<p>
-There are also some things you should remember when uploading the page:
-</p>
+<p>There are also some things you should remember when uploading the
+page:</p>
 
 <ul>
-<li>Add a link on the directory's main page to the article</li>
+<li>Add a link on the directory's main page to the article.</li>
 <li>Add an entry about the addition to /server/whatsnew.html by
-    adding an entry to the /server/whatsnew.txt file (see <a href="#polnews" 
>Adding news</a>)</li>
+    adding an entry to the /server/whatsnew.txt file (see <a
+    href="#polnews" >Adding news</a>).</li>
 </ul>
 
 
@@ -1092,14 +1085,15 @@
 
 <p>GNU software maintainers usually gain CVS write access to their
 /software subdirectory by registering their project with Savannah.  (In
-the past, they provide webmasters with pages about their project to
-upload to the site.)</p>
+the past, they provided webmasters with pages for us to install
+on the site, but that is no longer the best procedure.)</p>
 
-<p>In general, package maintainer are responsible for their own
-content.  In general, webmasters should not make changes to
-package-specific web pages unless we're asked to.  We do have the
-technical permission to check out any GNU (or non-GNU) web repository
-from savannah and commit changes.</p>
+<p>In general, package maintainers are responsible for their own
+content, and thus webmasters should not make changes to package-specific
+web pages unless we're asked to.  We do have the technical permission to
+check out any GNU (or non-GNU) web repository from savannah and commit
+changes, if a maintainer asks us to, or confirms a particular
+change.</p>
 
 
 <h4>Adding Translations</h4>
@@ -1232,7 +1226,7 @@
 
 <p>Updated:
 <!-- timestamp start -->
-$Date: 2009/11/10 18:55:41 $
+$Date: 2009/11/11 19:40:22 $
 <!-- timestamp end -->
 </p>
 </div>