CVSROOT: /web/www
Module name: www
Changes by: Karl Berry <karl> 10/10/08 18:15:51
Modified files:
server/standards: README.webmastering.html
Log message:
web-translators gets translation-related stuff, except for FSF-related
translations
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/server/standards/README.webmastering.html?cvsroot=www&r1=1.110&r2=1.111
Patches:
Index: README.webmastering.html
===================================================================
RCS file: /web/www/www/server/standards/README.webmastering.html,v
retrieving revision 1.110
retrieving revision 1.111
diff -u -b -r1.110 -r1.111
--- README.webmastering.html 5 Oct 2010 16:00:32 -0000 1.110
+++ README.webmastering.html 8 Oct 2010 18:15:43 -0000 1.111
@@ -183,9 +183,10 @@
<ul>
<li>To see open tickets, visit <a
href="http://rt.gnu.org/";>rt.gnu.org</a> and log in with your assigned
-username/password. (If you don't have one, email www-discuss.) There
-will be a link (and lots of other things) on your RT home page. Once
-you see the list, clicking on the subject link will open the ticket.</li>
+RT username/password. (If you don't have one, email www-discuss.)
+There will be a link to the webmasters queue (among lots of other
+things) on your RT home page. Once you see the list, clicking on the
+subject link will open the ticket.</li>
<li>If the message is spam, click the ‘Mark as Spam’ link in
the top row.</li>
@@ -197,13 +198,6 @@
<li>If the message is just a thank-you to us, or something else that
doesn't require action on our part, click ‘Resolve’.</li>
-<li>If the message is about the web pages for a given software package,
-forward it to the maintainer of the package. (You can use the <a
-href="http://directory.fsf.org";>Free Software Directory</a> to find the
-maintainers.) Don't just forward the message to a public bug list,
-since the submitter may not want his/her email address to be
-exposed.</li>
-
<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, and then ‘Resolve’ it.</li>
@@ -245,9 +239,10 @@
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, move it to the corresponding queue.
-<a href="#rtmisdirected">More detailed info.</a>
+<li>If the message needs to be dealt with by another group, such as
+sysadmin or licensing, move it to the corresponding queue or otherwise
+forward it. <a href="#rtmisdirected">Specific directions for
+redirecting tickets.</a>
</ul>
@@ -403,6 +398,11 @@
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>Move tickets about a new or existing translation of a gnu.org web page
+ to web-translators. Exception: for happy-birthday-to-gnu subtitles
+ and other FSF campaigns pages on gnu.org, handle them
+ ourselves.</li>
+
<li>If the ticket is about Savannah, email the original message to
savannah-hackers-priv...@gnu.org.</li>
@@ -414,27 +414,27 @@
<a href="http://mail.gnu.org";>http://mail.gnu.org</a> should be forwarded
to <mail...@mail.gnu.org>.</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 queue.</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 queue.</li>
+
+<li>For tickets about the GNU libc web pages, point the OP to
+ http://www.gnu.org/software/libc/bugs.html. That is the best way to
+ get the glibc maintainers' attention.</li>
<li>If the ticket is about the web pages for a <a
- href="#gnupackages">specific GNU software package</a>, generally it
- is best to send it in private email to the maintainers of that
- package (they are recorded in the file
+ href="#gnupackages">specific GNU software package</a>, it is best to
+ send it in private email to the maintainers of that package (they
+ are recorded in the Free Software Directory, or look at the file
<tt>/gd/gnuorg/maintainers.bypkg</tt> on fencepost), and reply to
- the OP saying that you did so, resolving the ticket.
- Exception: for tickets about the GNU libc web pages, point the OP
- to http://www.gnu.org/software/libc/bugs.html. That is the best way
- to get the glibc maintainers' attention.</li>
+ the OP saying that you did so, resolving the ticket.</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>
+doesn't provide automatic notification. You can do this by sending mail
+to queuename-comm...@gnu.org with the original subject line. Just a
+terse message "Moved ticket 1234 to your queue" suffices.</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
@@ -1169,7 +1169,7 @@
<p>Updated:
<!-- timestamp start -->
-$Date: 2010/10/05 16:00:32 $
+$Date: 2010/10/08 18:15:43 $
<!-- timestamp end -->
</p>
</div>
