[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: |
Sun, 01 Feb 2009 19:54:32 +0000 |
CVSROOT: /web/www
Module name: www
Changes by: Karl Berry <karl> 09/02/01 19:54:32
Modified files:
server/standards: README.webmastering.html
Log message:
more about different queues, from johns
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/server/standards/README.webmastering.html?cvsroot=www&r1=1.80&r2=1.81
Patches:
Index: README.webmastering.html
===================================================================
RCS file: /web/www/www/server/standards/README.webmastering.html,v
retrieving revision 1.80
retrieving revision 1.81
diff -u -b -r1.80 -r1.81
--- README.webmastering.html 14 Jan 2009 22:53:15 -0000 1.80
+++ README.webmastering.html 1 Feb 2009 19:53:55 -0000 1.81
@@ -268,11 +268,11 @@
<a name="rtguide"></a>
<h4>RT - Quick Guide</h4>
-<p>Of course, first and foremost is to use your judgment, rather than
-blindly following procedures. If the action on a particular ticket is
-in question for any reason, write www-discuss or use the
-‘Comment’ link on the ticket. That said, most tickets fall
-into one of a few categories, so here's a how-to guide.</p>
+<p>First and foremost: use your judgment, rather than blindly following
+procedures. If the action on a particular ticket seems questionable to
+you for any reason, email www-discuss or use the ‘Comment’
+link on the ticket. That said, most tickets fall into one of a few
+categories, so we try to enumerate the common cases here.</p>
<ul>
<li>To see open tickets, visit <a
@@ -300,7 +300,7 @@
<li>If the message is a simple typo or other buglet on a page we
maintain, go ahead and fix it, using ‘Reply’ to tell the
-submitter what you did.</li>
+submitter what you did, and then ‘Resolve’ it.</li>
<li>If the message is a ThankGNU:</li>
<ul>
@@ -321,7 +321,7 @@
<li>If the message is about adding a graphic or a joke, be sure to get
the explicit ok for it to be released under a free
-license—GPLv3-or-later and FDLv1.2-or-later is good. Then make a
+license—GPLv3-or-later and FDLv1.3-or-later is good. Then make a
new page under <tt>/graphics</tt> resp. <tt>/fun</tt> and add it to the
index page. rms' requirements for adding items to <tt>/fun</tt> is in
<a href="/fun/README">/fun/README</a>.
@@ -330,14 +330,15 @@
href="#mirrors">mirror procedures and information</a>.
<li>If the message opened a new ticket, but is actually a follow-up to
-an existing ticket, you can use the ‘Links’ feature of RT to
-combine them. This happens when the original submitter cc'd the message
-to other recipients, and one of the other recipients replies including
-us—their message will start a new ticket.
+an existing ticket, use the ‘Links’ feature of RT to combine
+them. This happens when the original submitter cc'd the message to
+other recipients, and one of the other recipients sends a reply that
+includes us—each such reply will (unfortunately) start a new
+ticket.
<li>If the message needs to be dealt with by another group, most often
-sysadmin, licensing, or directory, add a comment to that effect and move
-it to the corresponding queue. <a href="">More info.</a>
+sysadmin, licensing, or directory, move it to the corresponding queue.
+<a href="#rtmisdirected">More detailed info.</a>
</ul>
@@ -493,71 +494,77 @@
<a name="rtmisdirected"></a>
<h4>RT - Misdirected Tickets</h4>
-<p>
-Sometimes people send mail to webmasters which should've gone elsewhere.
-When this happens, you can do one of two things: redirect the ticket
-within RT, or forward it in regular email.
-</p>
+<p>Sometimes people send mail to webmasters which is best handled
+elsewhere. When this happens, you can do one of two things: redirect
+the ticket within RT, or forward it in regular email.</p>
-<p>
-If there's an RT queue which is appropriate for the ticket, move it
-there. The ticket's queue can be changed
-under the ‘Basics’ menu item.
-</p>
+<p>If there's an RT queue which is appropriate for the ticket, move it
+there. The ticket's queue can be changed under the ‘Basics’
+menu item.</p>
<ul>
-<li>Bug reports and similar items about the Free Software Directory should go
- to the directory queue (see the the form link from /directory).</li>
-<li>Mail about accounts should go to the accounts queue.</li>
-<li>Tickets about system problems (e.g. a web page is not replicating,
- or a symlinks file is creating the symbolic link), can be put into the
- sysadmin queue. If the ticket is about Savannah, send the original mail to
- address@hidden</li>
+<li>Move bug reports and other items about the Free Software Directory
+ to the directory queue.</li>
+
+<li>Move bug reports about fsf.org pages (broken links, typos, layout)
+ to the resources queue.
+
+<li>Move tickets that are about the actual content of fsf.org pages to
+ the campaigns queue.
+
+<li>For tickets about system problems with www.gnu.org (e.g., system
+ down, a .symlinks file not creating the symbolic link), try to
+ verify the problem and if it is real, move it to the sysadmin queue.
+
+<li>If the ticket is about Savannah, email the original message to
+ address@hidden</li>
+
+<li>Move tickets about accounts to the accounts queue.</li>
+
<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
- info or gnu queue.</li>
+ info queue.</li>
</ul>
-<p>
-It's nice to notify a queue's watchers when a ticket is moved; RT doesn't
- provide automatic notification. You can determine who watches a queue by
- going to "Configuration," choosing "Queues," selecting the desired queue,
- and choosing "Watchers." Just a brief mail to them saying "I moved
- ticket 1234 to your queue" will suffice.
-</p>
+<p>It's nice to notify a queue's watchers when a ticket is moved; RT
+doesn't provide automatic notification. You can determine who watches a
+queue by going to "Configuration," choosing "Queues," selecting the
+desired queue, and choosing "Watchers." Just a brief mail to them
+saying "I moved ticket 1234 to your queue" will suffice.</p>
<p>If there isn't an appropriate RT queue, forward the mail to the
- appropriate party, and make a comment indicating that you did so. (You
- can send the forward itself as a comment to the ticket if you like. See
- the instructions in "Coordination with others," above, for more
- information about doing this.)</p>
+appropriate party, and make a comment indicating that you did so
+(perhaps resolving it, if appropriate). It is usually best not to do
+this via the RT cc mechanism. Instead, forward the message in normal
+email.</p>
<h4>RT - Spam Quarantine</h4>
-<p>When time has elapsed, a ticket will be automatically sent to the
-webmaster's queue to remind them to clean out the mail quarantine. The
-quarantine is a collection of mails to address@hidden that are
-caught by our spam filter, and should be checked occasionally for false
-positives.</p>
-
-<p>To do so, use your RT username and password to log in to the
-quarantine manager (available at <a
-href="http://rt.gnu.org/qmanager/webmasters";>http://rt.gnu.org/qmanager/webmasters</a>).
The
+<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
+false positives.</p>
+
+<p>To do this, use your RT username and password to log in to the <a
+href="http://rt.gnu.org/qmanager/webmasters";>quarantine manager</a>. The
background of the page is color coded from blue (least likely to be
-spam) to red (most likely to be spam). To read an email, click on it's
+spam) to red (most likely to be spam). To read an email, click on its
subject. If you find a false positive then click the "Send to RT" button
at the top of the page. When you are satisfied that all of the emails on
-the index page are spam, you can delete them using the "Delete All
-Message On This Page" button at the bottom of the index page.</p>
+the index page are spam, delete them using the "Delete All Message On
+This Page" button at the bottom of the index page.</p>
-<p>When done you should resolve the ticket.</p>
+<p>If the quarantine is not checked for several days, RT will synthesize
+a ticket in our queue. When the above is done you should resolve such a
+ticket. It is best not to wait around for the ticket, though, because
+webmasters get several hundred spams every day.</p>
-<!-- Some of this information is redundant. If you find it above -->
+<!-- Some of the following information is redundant. If you find it above -->
<!-- or in the style guidelines, feel free to edit out the -->
<!-- appropriate portion, or combine it with the guidelines section. -->
@@ -1227,7 +1234,7 @@
<p>Updated:
<!-- timestamp start -->
- $Date: 2009/01/14 22:53:15 $
+ $Date: 2009/02/01 19:53:55 $
<!-- timestamp end -->
</p>
</div>
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- www/server/standards README.webmastering.html,
Karl Berry <=