[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www/server/standards README.html
|
From: |
D E Evans |
|
Subject: |
www/server/standards README.html |
|
Date: |
Sun, 24 Feb 2008 06:02:44 +0000 |
CVSROOT: /web/www
Module name: www
Changes by: D E Evans <sinuhe> 08/02/24 06:02:44
Modified files:
server/standards: README.html
Log message:
Initial SSI template import.
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/server/standards/README.html?cvsroot=www&r1=1.51&r2=1.52
Patches:
Index: README.html
===================================================================
RCS file: /web/www/www/server/standards/README.html,v
retrieving revision 1.51
retrieving revision 1.52
diff -u -b -r1.51 -r1.52
--- README.html 31 Jan 2008 23:35:09 -0000 1.51
+++ README.html 24 Feb 2008 06:02:28 -0000 1.52
@@ -1,302 +1,376 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/html4/loose.dtd";>
-<HTML>
-<HEAD>
-<TITLE>GNU Webmaster Guidelines - GNU Project - Free Software Foundation
(FSF)</TITLE>
-<meta http-equiv="content-type" content="text/html; charset=utf-8">
-<LINK REV="made" HREF="mailto:address@hidden";>
-</HEAD>
-<BODY BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#1F00FF" ALINK="#FF0000"
VLINK="#9900DD">
-<H3>GNU Webmaster Guidelines</H3>
-<!-- When using this boilerplate, remember to replace the "???" in both places
above. -->
+<!--#include virtual="/server/header.html" -->
+<title>
+ GNU Webmaster Guidelines - GNU Project - Free Software Foundation
+</title>
+<!--#include virtual="/server/banner.html" -->
+<h2>GNU Webmaster Guidelines</h2>
<!-- when you replace this graphics, make sure you change the link
- to also point to the correct html page.
- If you make a new graphics for this page, make sure it has
- a corresponding entry in /graphics/graphics.html -->
-<A HREF="/graphics/atypinggnu.html"><IMG SRC="/graphics/gnu-type-sm.jpg"
- ALT=" [image of the typing GNU] "
- WIDTH="137" HEIGHT="114"></A>
-
-<HR>
-
-<H4>Table of Contents</H4>
-
-<UL>
-<LI><A NAME="TOC0" HREF="README.html#SEC0">Organization</A>
-<LI><A NAME="TOC00" HREF="README.html#SEC00">How to edit www.gnu.org/... ?</A>
-<LI><A NAME="TOC01" HREF="README.html#SEC01">Symbolic Links</A>
-<LI><A NAME="TOC1" HREF="README.html#SEC1">Style guidelines</A>
-<LI><A NAME="TOC2" HREF="README.html#SEC2">Webmasters</A>
-<LI><A NAME="TOC3" HREF="README.html#SEC31">CVS and timestamps</A>
-<LI><A NAME="TOC3" HREF="README.html#SEC3">.emacs and timestamps</A>
-<LI><A NAME="TOC4" HREF="README.html#SEC4">umask</A>
-<LI><A NAME="TOC5" HREF="README.html#SEC5">Using the <CODE>TAGS</CODE> file</A>
-<LI><A NAME="TOC6" HREF="README.html#SEC6">Groups on files</A>
-<LI><A NAME="TOC7" HREF="README.html#SEC7">Update the What's New page!</A>
-<LI><A NAME="TOC8" HREF="README.html#SEC8">Update the Sitemap page?</A>
-<LI><A NAME="TOC9" HREF="README.html#SEC9">Update GNUs Flashes on the home
page http://www.gnu.org/</A>
-<LI><A NAME="TOC10" HREF="README.html#SEC10">Check your HTML!</A>
-<LI><A NAME="TOC11" HREF="README.html#SEC11">More webmaster tasks</A>
-<LI><A NAME="TOC12" HREF="README.html#SEC12">Archive of
<address@hidden></A>
-<LI><A NAME="TOC13" HREF="README.html#SEC13">Scripts</A>
-<LI><A NAME="TOC14" HREF="README.html#SEC14">Cron Jobs</A>
-<LI><A NAME="TOC15" HREF="README.html#SEC15">Adding FTP mirrors</A>
-<LI><A NAME="TOC16" HREF="README.html#SEC16">Audio and video files</A>
-<LI><A NAME="TOC17" HREF="README.html#SEC17">Adding an Event</A>
-<LI><A NAME="TOC18" HREF="README.html#SEC18">Creating Pages under
www.gnu.org/software</A>
-<li><a name="TOC20" href="README.html#SEC20">Updating ThankGNU pages</a>
-</UL>
+ to also point to the correct html page. If you make a new
+ graphics for this page, make sure it has a corresponding
+ entry in /graphics/graphics.html -->
+<a href="/graphics/atypinggnu.html">
+ <img src="/graphics/gnu-type-sm.jpg"
+ alt=" [image of the typing GNU] "
+</a>
+<hr />
-<HR>
+<h3>Table of Contents</h3>
+<ul>
+<li><a id="TOC0" href="README.html#SEC0">Organization</a></li>
+<li>
+ <a id="TOC00" href="README.html#SEC00">How to edit
+ www.gnu.org/... ?</a>
+</li>
+<li><a id="TOC01" href="README.html#SEC01">Symbolic Links</a></li>
+<li><a id="TOC1" href="README.html#SEC1">Style guidelines</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>
+<li>
+ <a id="TOC8" href="README.html#SEC8">Update the Sitemap page?</a>
+</li>
+<li>
+ <a id="TOC9" href="README.html#SEC9">Update GNUs Flashes on the
+ home page http://www.gnu.org/</a>
+</li>
+<li><a id="TOC10" href="README.html#SEC10">Check your HTML!</a></li>
+<li>
+ <a id="TOC11" href="README.html#SEC11">More webmaster tasks</a>
+</li>
+<li>
+ <a id="TOC12" href="README.html#SEC12">Archive of
+ <address@hidden></a>
+</li>
+<li><a id="TOC13" href="README.html#SEC13">Scripts</a></li>
+<li><a id="TOC14" href="README.html#SEC14">Cron Jobs</a></li>
+<li><a id="TOC15" href="README.html#SEC15">Adding FTP mirrors</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>
+<li><a id="TOC18" href="README.html#SEC18">Creating Pages under
+ www.gnu.org/software</a></li>
+<li>
+ <a name="TOC20" href="README.html#SEC20">Updating ThankGNU pages</a>
+</li>
+</ul>
-Everything (well, most everything ;-)
+<hr />
+
+<p>
+Everything (well, most everything)
you always wanted to know about www.gnu.org!
-<P>
+<p>
-<H4><A NAME="SEC0" HREF="README.html#TOC0">Organization</A></H4>
+<h4><a id="SEC0" href="README.html#TOC0">Organization</a></h4>
-<p>In order to work as a webmaster for GNU you need to become a member
+<p>
+In order to work as a webmaster for GNU you need to become a member
of the <a href="http://savannah.gnu.org/projects/www/";>www</a> project
on <a href="http://savannah.gnu.org/";>savannah.gnu.org</a>.
+</p>
-<p>If you just want to edit the web pages for your particular package,
-not work as a general webmaster, then you need only become a developer
-for the corresponding project. If no savannah project exists, <a
-href="http://savannah.gnu.org/register/";>register one</a>. This will
-allow you to edit the web pages directory for the project.
-
-<p>The whole www.gnu.org web site is stored in CVS on savannah.gnu.org.
-Most webmaster tasks are performed by checking out the CVS repository on
-your local machine, modifying them, and committing the result. <a
-href="http://savannah.gnu.org/cvs/?group=www";>Instructions on how to use
-CVS</a> (you want the “Webpages repository”).
-
-<P>When a commit to CVS is done, the live www.gnu.org web site is not
-updated instantly. The cron job that does the updates currently runs at
-the :10 and :40 of each hour.</P>
+<p>
+If you just want to edit the web pages for your particular package,
+not work as a general webmaster, then you need only become a
+developer for the corresponding project. If no savannah project
+exists, <a href="http://savannah.gnu.org/register/";>register one</a>.
+This will allow you to edit the web pages directory for the project.
+</P>
+
+<p>
+The whole www.gnu.org web site is stored in CVS on savannah.gnu.org.
+Most webmaster tasks are performed by checking out the CVS repository
+on your local machine, modifying them, and committing the result.
+<a href="http://savannah.gnu.org/cvs/?group=www";>Instructions on
+how to use CVS</a> (you want the “Webpages repository”).
+</p>
<P>
-Instead of having a single group of users who have edit permissions
-over the whole www.gnu.org CVS tree, a number of groups have been
-created and only have edit permissions on a specific directory
-tree. For instance, the <a
-HREF="http://savannah.gnu.org/projects/bravegw/";>Brave GNU World</a>
-project members only have edit permissions on the <a
-HREF="http://www.gnu.org/brave-gnu-world/";>http://www.gnu.org/brave-gnu-world/</a>
+When a commit to CVS is done, the live www.gnu.org web site is not
+updated instantly. The cron job that does the updates currently
+runs at :10 and :40 past each hour.
+</p>
+
+<p>
+Instead of having a single group of users who have
+edit permissions over the whole www.gnu.org CVS tree,
+a number of groups have been created and only have edit
+permissions on a specific directory tree. For instance,
+the <a href="http://savannah.gnu.org/projects/bravegw/";>Brave
+GNU World</a> project members only have edit permissions on the
+<a href="http://www.gnu.org/brave-gnu-world/";>
+ http://www.gnu.org/brave-gnu-world/
+</a>
directory. This has a number of advantages such as easily finding out
who is in charge of which portion of the www.gnu.org web site. A
-<a HREF="www2savannah.html">www.gnu.org to Savannah projects map</a> is
-updated every day and shows which directories are handled by which projects.
+<a href="www2savannah.html">www.gnu.org to Savannah projects map</a>
+is updated every day and shows which directories are handled by
+which projects.
+</p>
-<P>
-Some parts of the www.gnu.org web site do not yet have a matching
-project on Savannah. Don't hesitate to
-<a HREF="http://savannah.gnu.org/register/";>create a project</a> for a
-given subdirectory if you plan to work on it with other
+<p>
+Some parts of the www.gnu.org web site do not yet have
+a matching project on Savannah. Don't hesitate to
+<a href="http://savannah.gnu.org/register/";>create a project</a>
+for a given subdirectory if you plan to work on it with other
webmasters. When creating the project, select the <i>website only</i>
license. The /software/<i>package</i> directories have a special
status since they must be bound to a project that have the same name
on Savannah and are associated to a source CVS repository. You should
try to get in touch with the package maintainer before creating a
project in /software/<i>package</i>.
+</p>
-<P>
+<p>
Since it would be very complicated for highly involved webmasters to become
a member of each and every projects when they want to make some global
-changes, the special project <a HREF="http://savannah.gnu.org/projects/www/";>
+changes, the special project <a href="http://savannah.gnu.org/projects/www/";>
www</a> was created. Each member of the <i>www</i> project is granted
edit permission over the whole www.gnu.org CVS repository.
+</p>
-<P>
+<p>
If you want more information about Savannah, read the
-<a HREF="README.savannah.html">Administration Guide</a>.
-
-<H4><A NAME="SEC00" HREF="README.html#TOC00">How to edit www.gnu.org/...
?</A></H4>
+<a href="README.savannah.html">Administration Guide</a>.
+</p>
-If you want to edit the pages you are responsible for or want to become
-responsible for a specific subdirectory, proceed as follows:
+<h4>
+ <a id="SEC00" href="README.html#TOC00">How to edit www.gnu.org/... ?</a>
+</h4>
-<UL>
-<LI>Go to the <a HREF="www2savannah.html">www.gnu.org projects map</a>. If
-the directory you're interested in is already listed here, contact the
-people in charge to get write access. You don't have anything else to
-do. Anyone in charge of this directory will be able to grant you write
-access to the CVS respository.
-
-<LI>If the directory you're interested in is not listed, logon <a
-href="http://savannah.gnu.org/";>Savannah</a> and register a new
-project whose purpose is simply <b>Edit the
-www.gnu.org/thedirectory/</b>. Within 24h the project will be
-validated and you'll be able to checkout this portion of the web
-read/write.
+<p>
+If you want to edit the pages you are responsible for or want to
+become responsible for a specific subdirectory, proceed as follows:
+</p>
-</UL>
+<ul>
+ <li>
+ Go to the <a href="www2savannah.html">www.gnu.org projects
+ map</a>. If the directory you're interested in is already listed
+ here, contact the people in charge to get write access. You don't
+ have anything else to do. Anyone in charge of this directory
+ will be able to grant you write access to the CVS respository.
+ </li>
+ <li>
+ If the directory you're interested in is not listed,
+ logon <a href="http://savannah.gnu.org/";>Savannah</a> and
+ register a new project whose purpose is simply <b>Edit the
+ www.gnu.org/thedirectory/</b>. Within 24h the project will be
+ validated and you'll be able to checkout this portion of the
+ web read/write.
+ </li>
+</ul>
+<p>
If you want to understand more about www.gnu.org, CVS and Savannah,
-read the <A HREF="README.html#SEC0">Organization</A> chapter and the Savannah
<A
-HREF="README.savannah.html">Administration Guide</A>.
+read the <a href="README.html#SEC0">Organization</a> chapter and
+the Savannah <a href="README.savannah.html">Administration Guide</a>.
+</p>
-<H4><A NAME="SEC01" HREF="README.html#TOC01">Symbolic Links</A></H4>
+<h4><a id="SEC01" href="README.html#TOC01">Symbolic Links</a></h4>
+<p>
Since CVS is not able to handle symbolic links, a simple mechanism has
been implemented on the machine hosting the www.gnu.org to allow
webmasters to control the symbolic link from the CVS tree.
+</p>
-<P>
+<p>
By adding special files (".symlinks") into the CVS tree that are
interpreted as specifications to build symbolic links. The
"symlinks" script can be run immediately after a "cvs update"
to fix the symbolic links according to the specifications
included in the ".symlinks" files.
+</p>
-<P>
+<p>
The current directory is searched recursively for ".symlinks" files.
Symbolic links that exist in directory where there is no
.symlinks files will be ignored. Only directories containing a
.symlinks file are handled.
+</p>
-<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>
+<p>
Special handling to comply to the GNU webmaster standard
is also applied. If a subdirectory "foo/bar" has no
"foo/bar/index.html" file and a file "foo/bar/bar.html"
exists, then a symbolic link from "index.html" to
"bar.html" is created even if it is not listed in the
.symlinks file. In short, an implicit
-
-<PRE>
+<br />
+<pre>
cd foo/bar ; ln -s bar.html index.html
-</PRE>
+</pre>
is done.
+</p>
-<P>
+<p>
Symbolic links that point outside the web site
document root are ignored.
+</p>
-<P>
+<p>
The ".symlinks" files obey to the following format.
-<P>
+</p>
+<p>
Each line starting with a sharp sign ("#") is treated as a
comment and ignored.
-<P>
+</p>
+<p>
Lines that do not contain two strings separated by white
space are silently ignored.
-<P>
+</p>
+<p>
Here is an example of .symlinks file content:
-<PRE>
+</p>
+<pre>
#
# Link foo.html to bar.html.
# Stricly equivalent to ln -s foo.html bar.html
#
foo.html bar.html
-</PRE>
+</pre>
-<P>
+<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 sym-
-bolic link to be created.
+name may not contain any slash, it is the name of the
+symbolic link to be created.
+</p>
-<P>
+<p>
The actual command used to implement this feature is symlinks(1) and
the sources can be found in
gnudist.gnu.org:/usr/local/src/symlinks-1.1.tar.gz.
+</p>
-<H4><A NAME="SEC1" HREF="README.html#TOC1">Style guidelines</A></H4>
+<h4><a id="SEC1" href="README.html#TOC1">Style guidelines</a></h4>
-Please read <a
href="/server/fsf-html-style-sheet.html">http://www.gnu.org/server/fsf-html-style-sheet.html</a>
-before writing any HTML for www.gnu.org<P>
+<p>
+Please read
+<a
href="/server/fsf-html-style-sheet.html">http://www.gnu.org/server/fsf-html-style-sheet.html</a>
+before writing any HTML for www.gnu.org
+</p>
-<H4><A NAME="SEC2" HREF="README.html#TOC2">Webmasters</A></H4>
+<h4><a id="SEC2" href="README.html#TOC2">Webmasters</a></h4>
+<p>
New webmasters should read
<a href="/server/standards/README.webmastering.html">Information
on how to be a webmaster on www.gnu.org</a>
and review the
-<A HREF="/server/standards/readme_index.html#readme">various
-Readme's</A>.<P>
-
-
+<a href="/server/standards/readme_index.html#readme">various
+Readme's</a>.
+</p>
-<H4><A NAME="SEC31" HREF="README.html#TOC31">CVS and timestamps</A></H4>
+<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>
+<pre>
Updated:
<!-- timestamp start -->
$Date:$
<!-- timestamp end -->
<HR>
-</PRE>
-
-<P>
+</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.
+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 NAME="SEC3" HREF="README.html#TOC3">.emacs and timestamps</A></H4>
+<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>
+<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—this field is the date and user name between these two
+comments lines:
+</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 - this field is
-the date and user name between these two comments lines:
-<PRE>
+<pre>
<!-- hhmts start -->
18 Apr 2000 tower
<!-- hhmts end -->
-</PRE>
+</pre>
+<p>
An easy way to use them and get future updates is to add these lines
-to your own <CODE>~/.emacs</CODE>:
-<PRE>
+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>
-<P>
+</pre>
-<H4><A NAME="SEC4" HREF="README.html#TOC4">umask</A></H4>
+<h4><a id="SEC4" href="README.html#TOC4">umask</a></h4>
-Your umask on www.gnu.org is set to 000 as default, please don't change
-this.<P>
+<p>
+Your umask on www.gnu.org is set to 000 as default, please don't
+change this.
+</p>
-<H4><A NAME="SEC5" HREF="README.html#TOC5">Using the <CODE>TAGS</CODE>
file</A></H4>
+<h4>
+<a id="SEC5" href="README.html#TOC5">Using the <code>TAGS</code>
+file</a>
+</h4>
-A file <CODE>TAGS</CODE> in directory <CODE>~www/html/</CODE> lists
+<p>
+A file <code>TAGS</code> in directory <code>~www/html/</code> lists
all the HTML files on this site. This files allow one to search
or query replace all of the HTML files.
-See <A HREF="/TAGS.readme.html">these instructions</A>
+See <a href="/TAGS.readme.html">these instructions</a>
for more information.
-<P>
+</p>
-<H4><A NAME="SEC6" HREF="README.html#TOC6">Groups on files</A></H4>
+<h4><a id="SEC6" href="README.html#TOC6">Groups on files</a></h4>
-All files in the html tree should have the group www, if a file does not
-(and is not writable by world), please ask someone to change it.
-<P>
+<p>
+All files in the html tree should have the group www, if a file does
+not (and is not writable by world), please ask someone to change it.
+</p>
-<H4><A NAME="SEC7" HREF="README.html#TOC7">Update the What's New page!</A></H4>
+<h4>
+ <a id="SEC7" href="README.html#TOC7">Update the What's New page!</a>
+</h4>
-<p>When you add something significant to www.gnu.org, please add
- an entry to the news database in the CVS file:</p>
+<p>
+ When you add something significant to www.gnu.org, please add an
+ entry to the news database in the CVS file:
+</p>
<pre>/server/whatsnew.txt</pre>
@@ -317,7 +391,8 @@
<p>For example:</p>
<pre>
-* 21 July 2004 FSF is offering <a
href="http://patron.fsf.org/sf2004seminar.html">two days of
+* 21 July 2004 FSF is offering <a
+href="http://patron.fsf.org/sf2004seminar.html">two days of
seminars at Stanford University</a> on the
<abbr>GPL</abbr> and Free Software Licensing on August 24
and 25 of 2004.
@@ -343,140 +418,170 @@
<p>Altenately, see the Makefile for convieniant targets.</p>
-<p>Entries that can, should contain a <A HREF=" to the page (or section
-of a page (<A ... NAME="...")) that has the newly added text.
-(Multiple <A HREF=" are OK, if appropriate.)</p>
-
-<p>Entries should be newest first, so repeat visitors to the page, see
-the new items first.</P>
+<p>Entries that can, should contain a <A href=" to the page (or section
+of a page (<A ... id="...")) that has the newly added text.
+(Multiple <A href=" are OK, if appropriate.)</p>
+<p>
+Entries should be newest first, so repeat visitors to the page, see
+the new items first.
+</p>
-<H4><A NAME="SEC8" HREF="README.html#TOC8">Update the Sitemap page?</A></H4>
+<h4><a id="SEC8" href="README.html#TOC8">Update the Sitemap page?</a></h4>
-When you add something <STRONG>very</STRONG> significant
+<p>
+When you add something <strong>very</strong> significant
to www.gnu.org, please add
-an entry to /home/www/html/server/sitemap.html<br>
+an entry to /home/www/html/server/sitemap.html<br />
in the right section.
+</p>
+<p>
Entries that can, should contain a <a href=" to the page (or section
of a page (<a ... id="...")) that has the newly added text.
Multiple <a href=" are OK, if appropriate (HTML 3.2 and 2
-use NAME= instead of id=).
-<P>
+use id= instead of id=).
+</p>
-<H4><A NAME="SEC9" HREF="README.html#TOC9">Update GNUs Flashes on the home
page http://www.gnu.org/</A></H4>
+<h4>
+<a id="SEC9" href="README.html#TOC9">Update GNUs Flashes on the
+home page http://www.gnu.org/</a>
+</h4>
+<p>
GNUs Flashes on the home page are controlled by the
<code>server/whatsnew.txt</code> file. You should look at the entry
for managing news in the the webmastering guidelines:
<a
href="/server/standards/README.webmastering.html#polnews">/server/standards/README.webmastering.html</a>.
-<P>
-
+</p>
-<H4><A NAME="SEC10" HREF="README.html#TOC10">Check your HTML!</A></H4>
+<h4><a id="SEC10" href="README.html#TOC10">Check your HTML!</a></h4>
-<CODE>/usr/local/bin/htmlchek</CODE>
-can and <STRONG>SHOULD</STRONG> be used to do a syntax and some
-semantic checks on HTML files.<br>
-You could also use <CODE>weblint</CODE> or other checkers
-which may or may not be better.<P>
+<p>
+<code>/usr/local/bin/htmlchek</code> can and
+<em>should</em> be used to do a syntax and some
+semantic checks on HTML files.<br />
+You could also use <code>weblint</code> or other checkers
+which may or may not be better.
+</p>
-<H4><A NAME="SEC11" HREF="README.html#TOC11">More webmaster tasks</A></H4>
+<h4>
+ <a id="SEC11" href="README.html#TOC11">More webmaster tasks</a>
+</h4>
+<p>
The file
-<A HREF="/server/tasks.html">/home/www/html/server/tasks.html</A>
-has the tasks it be good to do to our site, www.gnu.org.<BR>
+<a href="/server/tasks.html">/home/www/html/server/tasks.html</a>
+has the tasks it be good to do to our site, www.gnu.org.<br />
The file
-<A HREF="/server/BUGS.html">/home/www/html/server/BUGS.html</A>
-has a list of known bugs that should be fixed ASAP.<P>
+<a href="/server/BUGS.html">/home/www/html/server/BUGS.html</a>
+has a list of known bugs that should be fixed ASAP.
+</p>
-<H4><A NAME="SEC12" HREF="README.html#TOC12">Archive of
<address@hidden></A></H4>
+<h4>
+<a id="SEC12" href="README.html#TOC12">Archive of
+<address@hidden></a>
+</h4>
-You might want to <STRONG>review</STRONG> the archive of the mailing list
-<STRONG><address@hidden></STRONG>.
+<p>
+You might want to <strong>review</strong> the archive of the mailing list
+<strong><address@hidden></strong>.
It has discussions about the design of this site, and the
rationales for the design decisions.
It's on the gnu.org machines (for example mail.gnu.org) at UMB as
-file <CODE>/com/archive/webmaster</CODE>
-files <CODE>/com/archive/webmaster*.gz for the older messages</CODE>.
-<P>
+file <code>/com/archive/webmaster</code>
+files <code>/com/archive/webmaster*.gz for the older messages</code>.
+</p>
-If you don't have an account on those machines, and have been appointed a
-webmaster, please request an account from <address@hidden>.
-<P>
+<p>
+If you don't have an account on those machines, and have
+been appointed a webmaster, please request an account from
+<address@hidden>.
+</p>
-<H4><A NAME="SEC13" HREF="README.html#TOC13">Scripts</A></H4>
+<h4><a id="SEC13" href="README.html#TOC13">Scripts</a></h4>
-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>
+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>
-<P>
+<h4><a id="SEC14" href="README.html#TOC14">Cron Jobs</a></h4>
-<H4><A NAME="SEC14" HREF="README.html#TOC14">Cron Jobs</A></H4>
+<p>
+(This cron information is no longer especially useful, since
+webmasters no longe have shell access to www.gnu.org and so none
+of these directories or files are accessible.)
+</p>
-<P>(This cron information is no longer especially useful, since
-webmasters no longe have shell access to www.gnu.org and so none of
-these directories or files are accessible.)
-
-<P>The cron daemon as user www
-<BR>
-runs /usr/www/bin/web-backup, which sets up the file that mirror sites pick up,
-<BR>
-and also runs /home/www/bin/nightly, which (among other stuff, maybe)
-creates /home/www/html/TAGS, useful for making global changes
- to all the html files via the GNU Emacs command tags-query-replace,
- or searching all the html files via tags-search.<P>
- Also creates files /home/www/html/TAGS.LG, that list those
- translations in language LG, for the use of each
- translation team.<P>
- See <A HREF="/TAGS.readme.html">these instructions</A>
- for more information.<P>
-</P>
+<p>
+The cron daemon as user www runs /usr/www/bin/web-backup,
+which sets up the file that mirror sites pick up, and also runs
+/home/www/bin/nightly, which (among other stuff, maybe) creates
+/home/www/html/TAGS, useful for making global changes to all
+the html files via the GNU Emacs command tags-query-replace, or
+searching all the html files via tags-search.<P> Also creates files
+/home/www/html/TAGS.LG, that list those translations in language LG,
+for the use of each translation team.
+</p>
-<P>
+<p>
+See <a href="/TAGS.readme.html">these instructions</A> for more information.
+</p>
+
+<p>
The crontab file is in /home/www/crontab and you should modify that file
and install it into cron instead of modifying the system crontab.
-Use the command <CODE>crontab -u www -e</CODE> to do this.
-</P>
+Use the command <code>crontab -u www -e</code> to do this.
+</p>
-<H4><A NAME="SEC15" HREF="README.html#TOC15">Adding FTP mirrors</A></H4>
+<h4><a id="SEC15" href="README.html#TOC15">Adding FTP mirrors</a></h4>
-<P>
+<p>
To change the ftp mirror list:
-<OL>
-<LI>Update the file <CODE>prep/FTP</CODE> in your CVS checkout.
-<LI>Run <CODE>make -f Makefile</CODE>, also in prep/.
-<LI><CODE>cvs commit FTP ftp.html</CODE>
-</OL>
+</p>
-<P>
-At some later time, a cron job may do this automatically.
-</P>
+<ol>
+<li>Update the file <code>prep/FTP</code> in your CVS checkout</li>
+<li>Run <code>make -f Makefile</code>, also in prep/</li>
+<li><code>cvs commit FTP ftp.html</code>
+</ol>
-<P>
-The FTP-related files in /gd/gnuorg on fencepost.gnu.org are no longer
-current. Everything is in CVS.
-</P>
+<p>
+At some later time, a cron job may do this automatically.
+</p>
+<p>
+The FTP-related files in /gd/gnuorg on fencepost.gnu.org are no
+longer current. Everything is in CVS.
+</p>
-<H4><A NAME="SEC16" HREF="README.html#TOC16">Audio and video files</A></H4>
-<P>
+<h4>
+ <a id="SEC16" href="README.html#TOC16">Audio and video files</a>
+</h4>
-A 22Gb disk partition was allocated to audio and video files on the
-machine audio-video.gnu.org. In order to add new files in this
-repository, one should be registered as a member of the <a
-href="http://savannah.gnu.org/projects/audio-video/";>GNU and FSF audio
-video</a> project.
+<p>
+A 22Gb disk partition was allocated to audio and video files on
+the machine audio-video.gnu.org. In order to add new files in
+this repository, one should be registered as a member of the
+<a href="http://savannah.gnu.org/projects/audio-video/";>GNU and
+FSF audio video</a> project.
+</p>
-Uploading a file can be done using rsync over ssh
+<p>
+Uploading a file can be done using rsync over ssh:
+</p>
<pre>
rsync --rsh=ssh file.vob audio-video.gnu.org:/audio-video/video
</pre>
+<p>
The access methods offered to users are:
+</p>
<ul>
<li>
@@ -492,135 +597,191 @@
</pre>
</li>
</ul>
-<P>
-<H4><A NAME="SEC17" HREF="README.html#TOC17">Adding an event</A></H4>
+<h4>
+ <a id="SEC17" href="README.html#TOC17">Adding an event</a>
+</h4>
-<p>For now, edit the <a
-href="/events.tmp.html"><code>/events.tmp.html</code></a> file.
+<p>
+For now, edit the
+<a href="/events.tmp.html"><code>/events.tmp.html</code></a> file.
When replication works again, follow the instructions below.
-
-<P>
-Webmasters should not usually add and remove events to our <a
-href="/events.html">events page</a>, they should only update the
-<code>events.input-html</code> file for formatting changes, etc. The
-actual addition and removal of events is handled by
-<code>fp:/gd/gnuorg/EventAndTravelInfo/announce-events.plx</code> and
-<code>gnudist:~www/bin/auto-event-handle</code>.
+</p>
<p>
+Webmasters should not usually add and remove events to our
+<a href="/events.html">events page</a>, they should only update
+the <code>events.input-html</code> file for formatting changes,
+etc. The actual addition and removal of events is handled by
+<code>fp:/gd/gnuorg/EventAndTravelInfo/announce-events.plx</code>
+and <code>gnudist:~www/bin/auto-event-handle</code>.
+</p>
-However, from time to time, the webmasters might get an email to add an
-event in error. There are two types of events webmasters might get:
+<p>
+However, from time to time, the webmasters might get an email to
+add an event in error. There are two types of events webmasters
+might get:
+</p>
<ul>
-
-<li> Events of a type that
-<code>fp:/gd/gnuorg/EventAndTravelInfo/announce-events.plx</code> can
-already handle. Check the POD of the script itself for information on
-whom to forward messages to. The short version: you should normally
-forward a message to the person who is speaking, except in the case of
-RMS---those go to <a
-href="mailto:address@hidden";><address@hidden></a>.</li>
-
-<li> Events of a type that are not supported yet. In that case, you
-should always ask webmaster-escalate.
-
+ <li>
+ Events of a type that
+ <code>fp:/gd/gnuorg/EventAndTravelInfo/announce-events.plx</code>
+ can already handle. Check the POD of the script itself
+ for information on whom to forward messages to. The short
+ version: you should normally forward a message to the person
+ who is speaking, except in the case of RMS---those go to
+ <a href="mailto:address@hidden";><address@hidden></a>.
+ </li>
+ <li>
+ Events of a type that are not supported yet. In that case,
+ you should always ask webmaster-escalate.
+ </li>
</ul>
-In a pinch, someone from the FSF staff might ask the webmasters to add an
-event in a hurry. In these cases, you can, if you want, figure out how to
-edit the relevant file in <code>fp:/gd/gnuorg/EventAndTravelInfo/</code>.
-If you can't figure that out, you can add the event to
-<code>events.input-html</code> above the AUTO section. However, if you do
-the latter, please take responsibility for the event and remove it when it
-has passed.
-
-
-<P>
-
+<p>
+In a pinch, someone from the FSF staff might ask the
+webmasters to add an event in a hurry. In these cases, you
+can, if you want, figure out how to edit the relevant file in
+<code>fp:/gd/gnuorg/EventAndTravelInfo/</code>. If you can't figure
+that out, you can add the event to <code>events.input-html</code>
+above the AUTO section. However, if you do the latter, please take
+responsibility for the event and remove it when it has passed.
+</p>
-<H4><A NAME="SEC18" HREF="README.html#TOC18">Creating Pages under
www.gnu.org/software</A></H4>
+<h4>
+ <a id="SEC18" href="README.html#TOC18">Creating Pages under
+ www.gnu.org/software</A>
+</H4>
-<P>Usually a package's maintainer(s) take care of their own web pages.
+<p>
+Usually a package's maintainer(s) take care of their own web pages.
Here are some tips, though (maybe for maintainers themselves).
+</p>
<ul>
-<li><STRONG>Style guidelines</STRONG><br>
+ <li><strong>Style guidelines</strong><br />
Please read
- <a
href="/server/fsf-html-style-sheet.html">http://www.gnu.org/server/fsf-html-style-sheet.html</a>
- before writing any HTML for www.gnu.org<P>
-<LI><STRONG>Content</STRONG><br>
- When writing a page for a certain program, we want to
- have some basic information on such a page. See the <a
- href="boilerplate.html">boilerplate</a>.
+ <a href="/server/fsf-html-style-sheet.html">
+ http://www.gnu.org/server/fsf-html-style-sheet.html</a>
+ before writing any HTML for www.gnu.org
+ </li>
+ <li>
+ <strong>Content</strong><br /> When writing a page for a certain
+ program, we want to have some basic information on such a page.
+ See the <a href="boilerplate.html">boilerplate</a>.
<ul>
<li>A description on what the program does
<li>Where to download the program in question
- <LI>Where to report bugs
- <LI>List of FAQs and documentation if they are available
+ <li>Where to report bugs
+ <li>List of FAQs and documentation if they are available
</ul>
For example, we think the FAQ ought to be included in the web
pages for the program. Installation instructions would be nice,
though not essential. And we would like to put the program's
documentation or manual in the web pages too.
- <P>
-<li>Documentation should be available online. For info about a script to
- do generate many formats from Texinfo, and other information too, see the
+ </li>
+ <li>
+ Documentation should be available online. For
+ info about a script to do generate many formats
+ from Texinfo, and other information too, see the
<a href="http://www.gnu.org/prep/maintain/html_node/Web-Pages.html";>
maintainer information</a>.
+ </li>
</ul>
-<P>
+<h4>
+ <a id="SEC20" href="README.html#TOC20">Updating ThankGNU pages</a>
+</h4>
-<H4><A NAME="SEC20" HREF="README.html#TOC20">Updating ThankGNU pages</A></H4>
<p>
- You'll will be seeing tickets in the webmaster queue that have
`<strong>ThankGNU</strong>'
- in the title and originate from `sysadmin at gnu.org'.
+ You'll will be seeing tickets in the webmaster queue that have
+ `<strong>ThankGNU</strong>' in the title and originate from
+ `sysadmin at gnu.org'.
</p>
+
<p>
- Each ticket will have a name that needs to be added to appropriate year page
under
- <a href="http://www.gnu.org/thankgnus/";>http://www.gnu.org/thankgnus/</a>.
For e.g.
- if the ThankGNU corresponds to the year 2006, go to
+ Each ticket will have a name that needs
+ to be added to appropriate year page under
+ <a href="http://www.gnu.org/thankgnus/";>
+ http://www.gnu.org/thankgnus/
+ </a>.
+ For e.g. if the ThankGNU corresponds to the year 2006, go to
<a href="http://www.gnu.org/thankgnus/2006supporters.html";>
- http://www.gnu.org/thankgnus/2006supporters.html</a> page. Please add the
name there,
- in the appropriate place based on the amount of the contribution and in the
alphabetical
- ordering, and then resolve the ticket.
+ http://www.gnu.org/thankgnus/2006supporters.html</a> page. Please
+ add the name there, in the appropriate place based on the amount
+ of the contribution and in the alphabetical ordering, and then
+ resolve the ticket.
</p>
-<!--
- * If needed, change the copyright block at the bottom. In general, all pages
- on the GNU web server should have the section about verbatim copying.
Please
- do NOT remove this without talking with the webmasters first.
--->
-<HR>
-
-Return to <A HREF="/home.html">GNU's home page</A>.
-<P>
+</div><!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.html" -->
+<div id="footer">
-Please send FSF & GNU inquiries & questions to
+<p>
+Please send FSF & GNU inquiries to
+<a href="mailto:address@hidden";><em>address@hidden</em></a>.
+There are also <a href="/contact/">other ways to contact</a>
+the FSF.
+<br />
+Please send broken links and other corrections or suggestions to
+<!-- If you are a project maintainer or developer, please use -->
+<!-- your own email, as webmasters does not manage most -->
+<!-- project webpages (those that we do, you know who you are). -->
+<a href="mailto:address@hidden";>
+ <em>address@hidden</em>
+</a>.
+</p>
-<A HREF="mailto:address@hidden";><EM>address@hidden</EM></A>.
-There are also <A HREF="http://www.fsf.org/about/contact.html";>other ways to
-contact</A> the FSF.
-<P>
+<p>
+Please see the
+<a href="/server/standards/README.translations.html">Translations
+README</a> for information on coordinating and submitting
+translations of this article.
+</p>
-Please send comments on these web pages to
+<p>
+Copyright © 1999, 2001, 2003, 2004, 2005, 2006, 2007, 2008
+Free Software Foundation, Inc.,
+</p>
+<address>51 Franklin St, Fifth Floor, Boston, MA 02110, USA</address>
+<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>
-<A HREF="mailto:address@hidden";><EM>address@hidden</EM></A>,
-send other questions to
-<A HREF="mailto:address@hidden";><EM>address@hidden</EM></A>.
-<P>
-Copyright © 1999, 2001, 2003, 2004, 2005, 2006, 2007 Free Software
-Foundation, Inc.,
-51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA
-<P>
-Verbatim copying and distribution of this entire article is
-permitted in any medium, provided this notice is preserved.<P>
+<p>
Updated:
<!-- timestamp start -->
-$Date: 2008/01/31 23:35:09 $
+$Date: 2008/02/24 06:02:28 $ $Author: sinuhe $
<!-- timestamp end -->
-<HR>
-</BODY>
-</HTML>
+</p>
+</div>
+
+<div id="translations">
+<h4>Translations of this page</h4>
+
+<!-- Please keep this list alphabetical. -->
+<!-- Comment what the language is for each type, i.e. de is German. -->
+<!-- If you add a new language here, please -->
+<!-- advise address@hidden and add it to -->
+<!-- - /home/www/bin/nightly-vars either TAGSLANG or WEBLANG -->
+<!-- - /home/www/html/server/standards/README.translations.html -->
+<!-- - one of the lists under the section "Translations Underway" -->
+<!-- - if there is a translation team, add an alias -->
+<!-- to mail.gnu.org:/com/mailer/aliases -->
+<!-- Please check you have the 2 letter language code right, cf. -->
+<!-- <URL:http://www.w3.org/WAI/ER/IG/ert/iso639.htm> -->
+<!-- Please use W3C normative character entities. -->
+
+<ul class="translations-list">
+<!-- English -->
+<li>
+ <a href="/server/standards/boilerplate.html">English</a> [en]
+</li>
+</ul>
+</div>
+</div>
+</body>
+</html>
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- www/server/standards README.html,
D E Evans <=