[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www/server/standards README.webmastering.html
From: |
Karl Berry |
Subject: |
www/server/standards README.webmastering.html |
Date: |
Mon, 11 Feb 2008 00:44:16 +0000 |
CVSROOT: /web/www
Module name: www
Changes by: Karl Berry <karl> 08/02/11 00:44:16
Modified files:
server/standards: README.webmastering.html
Log message:
minor wording and formatting
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/server/standards/README.webmastering.html?cvsroot=www&r1=1.63&r2=1.64
Patches:
Index: README.webmastering.html
===================================================================
RCS file: /web/www/www/server/standards/README.webmastering.html,v
retrieving revision 1.63
retrieving revision 1.64
diff -u -b -r1.63 -r1.64
--- README.webmastering.html 4 Jan 2008 13:07:43 -0000 1.63
+++ README.webmastering.html 11 Feb 2008 00:44:02 -0000 1.64
@@ -11,12 +11,15 @@
<h3>Information on How to be a Webmaster at www.gnu.org</h3>
<p>
-All webmasters should normally have <a href="http://rt.gnu.org/">RT</a> access
to
+All webmasters should normally have access to <a
+href="http://rt.gnu.org/">webmasters RT queue</a>
+that corresponds to
<a href="mailto:address@hidden"><address@hidden></a>.
-When you take care of something sent to this list, please steal
-the ticket and reply to the message and let the sender know that
-whatever he or she asked for has been done. Please see the RT
-guidelines below.
+When you take care of something sent to this list, please take
+the ticket, reply to the message letting the sender know that
+whatever he or she asked for has been done, and resolve the ticket.
+Please see <a href="#rt">RT
+guidelines</a> below.
</p>
<p>(<em>Note that <address@hidden> forwards to
<address@hidden>.</em>)</p>
@@ -29,9 +32,9 @@
<p>
If you find a message to address@hidden that you don't know
-how to handle, it's probably best that you ignore the message unless
-you are the assigned owner. However, if you noticed that something
-has been pending for a long time, it is good to ask the
+how to handle, it's probably best to ignore the message for
+a while. However, if you noticed that something
+has been pending for more than a few days, it is good to ask the
www-discuss list: "Can someone teach me how to handle messages like this?"
</p>
@@ -40,14 +43,13 @@
</p>
<ul>
- <li>Fix typos, mis-spellings, broken links, and the like</li>
- <li>Add Table of Contents to pages</li>
+ <li>Fix typos, mis-spellings, broken links, and the like.</li>
<li>Requests from Richard Stallman
<a href="mailto:address@hidden"><address@hidden></a>,
- Peter Brown<a href="mailto:address@hidden"><address@hidden></a>,
- John Sullivan<a href="mailto:address@hidden"><address@hidden></a>,
+ Peter Brown <a href="mailto:address@hidden"><address@hidden></a>,
+ John Sullivan <a
href="mailto:address@hidden"><address@hidden></a>,
Jonas Oberg <a href="mailto:address@hidden"><address@hidden></a>
- or anyone else at the FSF Distribution Office</li>
+ or anyone else at the FSF Distribution Office.</li>
<li>Requests from one of the maintainers of a software package to change
something on web pages about that software package, if it does not
seem to conflict with any other webmastering policies.</li>
@@ -101,11 +103,6 @@
please read the <a href="/fun/README">README</a> file under
<a href="/fun/">/fun</a> first.</p>
-<p>
-Since the <address@hidden> address is advertised quite a lot on
-our web pages it happens quite often that we receive spam to that
-address. Please mark these tickets as spam and deleted.
-</p>
<h3>Handling Press Releases</h3>
@@ -172,7 +169,6 @@
<h3>Webmaster Organization</h3>
-
<p>
The following organizational rules are not rigid; they are designed to
serve us and assign responsibility so that things don't fall through the
@@ -221,7 +217,6 @@
<h3>Leaving Webmasters</h3>
-
<p>
We realize that people's lives change, and we know that you may not want
to be an FSF/GNU webmaster for the rest of your life. We ask that you let
@@ -240,6 +235,7 @@
+<a name="rt"></a>
<h3>Using RT</h3>
<h4>RT Conventions</h4>
@@ -249,7 +245,7 @@
RT. This system keeps all correspondence about a given issue
together, makes sure that no requests are lost, and so on. It works
most effectively if people working with each other use roughly the
-same conventions, and this sections looks to document the conventions
+same conventions, and so this section documents the conventions
used by the GNU webmasters.
</p>
@@ -322,9 +318,9 @@
<p>
You will often need to ask other people for more information about how to
handle a ticket. If we don't mind showing them a few internals about how
-we do things -- in other words, if they're friends of the GNU project --
-the best way to do this is to mail them, and make that mail a comment to
-the ticket as well.
+we do things—in other words, if they're friends of the GNU
+project—the best way to do this is to mail them, and make that
+mail a comment to the ticket as well.
</p>
<p>
@@ -471,8 +467,8 @@
<li>Requests to remove messages from mailing list archives (accessible via
<a href="http://mail.gnu.org">http://mail.gnu.org</a> should be forwarded
to <address@hidden>.</li>
-<li>Anything else not related to webmastering -- including questions about
- FSF opinions, requests for support, and the like -- can be moved to the
+<li>Anything else not related to webmastering—including questions about
+ FSF opinions, requests for support, and the like—can be moved to the
info or gnu queue.</li>
</ul>
@@ -502,8 +498,8 @@
<!-- or in the style guidelines, feel free to edit out the -->
<!-- appropriate portion, or combine it with the guidelines section. -->
-<h3>Other Webmastering Procedures and Policies to Consider</h3>
+<h3>Other Webmastering Procedures and Policies to Consider</h3>
<p>
There are certain procedures and policies which take hold over the entire
@@ -514,7 +510,7 @@
<h4>Inter-site Structure and Navigation</h4>
<p>
-The site is divided up into directories by topic -- there's a directory for
+The site is divided up into directories by topic—there's a directory for
GNU project information and history, a directory for our licenses, and so
on. Each of these directories has a page sharing the same name; for
example, the /philosophy directory has a page, philosophy.html. This page
@@ -733,8 +729,8 @@
</p>
<p>
-We strive to ensure that all pages we promote -- all pages which are given
-links on our site -- are friendly to the free software movement. Some
+We strive to ensure that all pages we promote—all pages which are given
+links on our site—are friendly to the free software movement. Some
pages will obviously not meet such standards; if the site flames the Free
Software Foundation, or has no apparent relation to free software and
surrounding issues, the link shouldn't be made. Beyond that, however,
@@ -751,8 +747,8 @@
The link's purpose on our site will play a role in determining how
strongly it should be judged against the other criteria. Pages
hosting GNU projects will be held to the highest standards. Pages
-about other free software and given high promotion -- for example,
-included in a GNUs Flash on the main page -- are a close second.
+about other free software and given high promotion—for example,
+included in a GNUs Flash on the main page—are a close second.
Links on the philosophy page may be given more leeway in talking
about proprietary software; GNU/Linux user group pages should call
the system GNU/Linux almost always but are hardly checked on other
@@ -815,8 +811,8 @@
GNU software project pages feel the full force of this policy.
Proprietary software should only be mentioned when the software
provides support for it, or to compare it against the features of
-well-known proprietary software. For example, the following text
--- and not much else -- would be acceptable:
+well-known proprietary software. For example, the following
+text—and not much else—would be acceptable:
</p>
<p>
@@ -839,8 +835,8 @@
<p>
Almost all pages which have links on our site should, at the very
least, treat free software and open source equally. Failure to do
-so -- whether it be by omitting free software or by implying that
-open source is superior -- is usually unacceptable. GNU software
+so—whether it be by omitting free software or by implying that
+open source is superior—is usually unacceptable. GNU software
project pages should have little mention of open source. The GNOME
page provides a good example of a way to do it tactfully:-</p>
@@ -891,7 +887,7 @@
</p>
<p>
-As a final explanation ( coming from RMS ):
+As a final explanation (coming from RMS):
Even for making links from www.gnu.org, we do not *require* that
people call the system GNU/Linux or use the term "free software"
rather than "open source". We do, however, require that they not
@@ -916,8 +912,8 @@
</p>
<p>
-Those requests which are extremely straightforward -- for example, fixing
-typographical errors, or problems in HTML formatting -- are not documented
+Those requests which are extremely straightforward—for example, fixing
+typographical errors, or problems in HTML formatting—are not documented
here. Only requests which may require non-obvious action are listed.
</p>
@@ -927,7 +923,7 @@
If a link has gone bad because a page has moved, try to find its
replacement. If you are successful, re-check the page to ensure that it
meets our linking criteria, and if so, add it. If you do not find a
-replacement, remove the link -- if it's central to the page, you may need
+replacement, remove the link—if it's central to the page, you may need
to make a note explaining that the resource is no longer available. If the
page no longer meets our linking criteria, you'll have to make a judgment
call, and weigh the value of the link against its problems'; you may want
@@ -936,9 +932,9 @@
</p>
<p>
-If you do remove a link from a page that we don't maintain -- for instance,
-the page for a piece of software which is kept up-to-date by the maintainer
--- it's nice to notify them of the problem and what you did to fix it.
+If you do remove a link from a page that we don't maintain—for instance,
+the page for a piece of software which is kept up-to-date by the
+maintainer—please notify them of the problem and what you did to fix it.
</p>
<h4>Adding Links</h4>
@@ -963,7 +959,7 @@
to the appropriate party. If the link would be part of the main GNU site,
that would be someone who can speak for the GNU project, such as RMS. If
the link would be part of a software page, direct it to the person
-responsible for the program's site -- if no other contact is given, that
+responsible for the program's site—if no other contact is given, that
would be the maintainers themselves. If you're told that adding the link
is acceptable, do so. If the link fails to meet the linking criteria,
thank the original requestor for their suggestion and explain that we don't
@@ -1150,7 +1146,7 @@
<p>Updated:
<!-- timestamp start -->
- $Date: 2008/01/04 13:07:43 $
+ $Date: 2008/02/11 00:44:02 $
<!-- timestamp end -->
</p>
</div>
- www/server/standards README.webmastering.html,
Karl Berry <=