[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[GNU-traductores] old-gnudist:/home/www/html/server/standards/README.web
|
From: |
old-gnudist's file diff daemon |
|
Subject: |
[GNU-traductores] old-gnudist:/home/www/html/server/standards/README.webmastering.html -- New file |
|
Date: |
Tue, 15 Jan 2002 06:29:20 -0800 (PST) |
This is an automated report from old-gnudist.
This appears to be a new file or has only recently been added to
the list of monitored files:
14 -rw-rw-r-- 1 webcvs www 12848 Dec 20 02:18
/home/www/html/server/standards/README.webmastering.html
Contents:
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
<TITLE>Webmastering Guidelines - GNU Project - Free Software Foundation
(FSF)</TITLE>
<LINK REV="made" HREF="mailto:address@hidden";>
</HEAD>
<BODY BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#1F00FF" ALINK="#FF0000"
VLINK="#9900DD">
<H3>Webmastering Guidelines</H3>
<A HREF="/graphics/atypinggnu.html"><IMG SRC="/graphics/gnu-type-sm.jpg"
ALT=" [image of the typing GNU] "
WIDTH="137" HEIGHT="114"></A>
[
<!-- Please keep this list alphabetical -->
<!-- PLEASE UPDATE THE LIST AT THE BOTTOM (OR TOP) OF THE PAGE TOO! -->
<A HREF="README.webmastering.html">English</A>
<!-- | A HREF="boilerplate.LG.html" LANGUAGE /A -->
<!-- Please keep this list alphabetical -->
<!-- PLEASE UPDATE THE LIST AT THE BOTTOM (OR TOP) OF THE PAGE TOO! -->
]
<P>
<HR>
<P>
<H4>Table of Contents</H4>
<UL>
<LI>Information on <A HREF="#guidelines" NAME="TOCguidelines">how to be a
webmaster</A> at www.gnu.org.
<LI><A HREF="#press" NAME="TOCpress">Handling Press Releases</A>
<LI><A HREF="#organization" NAME="TOCorganization">Webmaster Organization</A>
<LI><A HREF="#leaving" NAME="TOCleaving">Leaving webmasters</A>
</UL>
<P>
<HR>
<P>
<h4><a href="#TOCguidelines" name="guidelines">Information on how to be a
webmaster on www.gnu.org</a></h4>
<p> All webmasters should normally be on the mailing list <a
href="mailto:address@hidden";><address@hidden></a>. When you
take care of something sent to this list, please reply to the message and
let the sender know that whatever he or she asked for has been done. Also,
please Cc: such messages to <a
href="mailto:address@hidden";><address@hidden></a>, so that
others can see that it has been done.
<P>
You might find it helpful to also set your Reply-To: header to <a
href="mailto:address@hidden";><address@hidden></a>. That way,
your personal incoming mailbox will less likely be crowded with webmasters
discussions. And, it will allow discussion about a webmaster issue to
continue on the webmasters list.
<p>
Note that <address@hidden>
forwards to <address@hidden>.
<p>
There are <A HREF="readme_index.html">several guides</A>
for webmasters, one of the most important ones is the
<a href="/server/fsf-html-style-sheet.html">FSF HTML Style Sheet Guidelines</a>
which is in http://www.gnu.org/server/fsf-html-style-sheet.html.
<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. However, if
you noticed that something has been pending for a long time, It might
be useful to ask the list: "Can someone teach me how to handle
messages like this?"
<P>
As a new webmaster for GNU, there is not a whole lot you can do until
you see how we want things done. But as a general rule, things like this
are always okay to do:
<ul>
<li>Fix typos, mis-spellings, broken links, and the like.
<li>Add Table of Contents to pages.
<li>Requests from Richard Stallman
<a href="mailto:address@hidden";><address@hidden></a>,
Bradley M. Kuhn <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 (this includes
<a href="mailto:address@hidden";><address@hidden></a> and
<a href="mailto:address@hidden";><address@hidden></a>).
<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>Take on one of the <A HREF="/server/tasks.html">jobs</A> we need
done for this <A HREF="/server/server.html">web server</A>.
(Please inform <a
href="mailto:address@hidden";><address@hidden></a> if
you take a task.</li>
</ul>
<P>
Sometimes people will send us pages about software that they want us to
install. Before doing so, you should make sure that the page doesn't make
any references to non-free software and is consistent with our
<a href="/server/fsf-html-style-sheet.html">HTML style sheet</a>. If you
find discrepancies, please politely point the maintainer to our policies and
ask them to make the changes. When making such a request, do so in private
email, not on the webmasters list.
<P>
People will often send mails asking us to make links to different software
packages. Before making such links, it's important to check the page that
the link points to and make sure that it does not make any references to
non-free software. When in doubt, it is best to post a summary of what you
found on the page back to the webmasters list (but not to the requester!),
and ask someone else to take it from there.
<P>
Sometimes you might be tempted to rearrange pages in some drastic way to
make certain things stand out more or to format the layout in some other
way. Before doing so you should consult <A
HREF="mailto:address@hidden";><address@hidden></A>. It's often
the case that web pages are constructed one way for a special reason.
<P>
All the www.gnu.org web site is managed with CVS. As a webmaster you
should first <a href="https://savannah.gnu.org/account/register.php";>register
on Savannah</a>. Then find out which group of people is maintaining the
part of www.gnu.org web site you plan to edit using the
<a href="www2savannah.html">www.gnu.org to Savannah projects map</a>.
Get in touch with one of the project maintainer to get write access to
this directory.
<P>
If you plan to modify a lot of files everywhere in www.gnu.org on a regular
basis, you should join the <a href="http://savannah.gnu.org/projects/www/";>
www</a> project in order to edit the whole tree.
<P>
If you update or create any pages under <A HREF="/fun/">/fun</A>,
please read the <A HREF="/fun/README">README</A> file under
<A HREF="/fun/">/fun</A>, before you do so.
<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. It's best to simply ignore such messages.
<h4><a href="#TOCpress" name="press">Handling Press Releases</a></h4>
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>
Currently, it is often <a href="mailto:address@hidden";>bkuhn</a> who
handles the text version of a press release (although will hopefully
change sometime in 2002). He will normally commit the <code>.txt</code>
file version, and then tell webmasters to do the "rest" or "DTRT" with it.
(Although sometimes the <code>.txt</code> will be emailed to webmasters
instead). You will also be given a date and time when the press release
should be up.
<p>
For the time being, always check with bkuhn before posting any press
releases sent in by other parties, and note that bkuhn will always
GPG-sign his messages about press releases.
<p>
To handle one of these requests, here is what you should do:
<ul>
<li>Make an HTML version of the <code>.txt</code> file, following the
format used for other press releases. Be sure to change the
<code>META</code> tags for <code>Keywords</code> and
<code>Description</code> to reflect the new press release. Also, make
any URLs in the press release into actual links.
</li><p>
<li>Make an entry at the top of the list on <a
href="/press/press.html">/press/press.html</a> for the press
release.</li><p>
<li>Add an entry for it on <a
href="/server/whatsnew.html">/server/whatsnew.html</a>. <p></li>
<li>Add an entry for it on the GNU's Flashes of <a
href="/home.html">/home.html</a>, unless the request to post the
release specifically says <em>not</em> to put a note there.</li><p>
<li> A release date and time "window" will be included in the request to
post it. The <code>cvs commit</code> should <strong>only be
done</strong> in that window. If you won't be able to do it then,
use the <code>makepatch</code> command (it's in the makepatch
package of Debian) to send a patch back to bkuhn, and put URGENT in
the subject line.</li><p>
<li> The final step is submitting it as a story to as many news sites as
possible (linuxtoday.com, slashdot.org, and newsforge.com should
definitely be done). This can be done later in the same day as
when the release goes up, but should also be done the same
day.</li><p>
</ul>
<p>
<h4><a href="#TOCorganization" name="organization">Webmaster
Organization</a></h4>
The following organizational rules are not rigid; they are designed to
serve us and assign responsibility so that things don't fall through the
cracks. Thus, the policies and escalation procedures need not be followed
to the letter, but if you aren't sure what to do, it's best to follow
these policies.
<p>
The GNU Webmaster Group is led by the Chief Webmaster <a
href="mailto:address@hidden";><address@hidden></A>.
You can always find out the identity of the Chief Webmaster by looking at
the aliases file on the GNU mail server.
<p>
The Chief Webmaster is responsible for making sure that every message sent
to the webmasters gets handled <a
href="mailto:address@hidden";><address@hidden></A>
eventually. The Chief Webmaster isn't responsible for handling ever
message; just making sure that someone handles them in a timely manner.
The Chief Webmaster is also responsible for training new webmasters, and
doing her best to correct mishandled webmaster email, when necessary.
<p>
If it isn't clear to the webmasters how the handle a particular issue, the
message should be sent to <a href="mailto:address@hidden";>
<address@hidden></a>. Replies from
<address@hidden> are typically sent back to the whole
<address@hidden> list, so that all the webmasters can learn how
to handle those issues in the future. It's also useful to cc the whole
webmasters list on message to <address@hidden>, so the
other webmasters know the message has been escalated and that they should
wait for a response.
<p>
Mail to <address@hidden> is usually answered in a week
or so, at worst. If anyone notices a message sent there has been pending
for longer, please do send a message to <address@hidden>
checking on the status.
<p>
<h4><a href="#TOCleaving" name="leaving">Leaving webmasters</a></h4>
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
us know when you want to move on: please don't simply disappear.
<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 few weeks, or want to stop being a webmaster entirely, please
inform <a href="mailto:address@hidden";>
<address@hidden></a> and <a
href="mailto:address@hidden";> <address@hidden></a>
as soon as your situation changes.
<!--
* 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>
[
<!-- Please keep this list alphabetical -->
<!-- PLEASE UPDATE THE LIST AT THE BOTTOM (OR TOP) OF THE PAGE TOO! -->
<A HREF="README.webmastering.html">English</A>
<!-- | A HREF="boilerplate.LG.html" LANGUAGE /A -->
<!-- Please keep this list alphabetical -->
<!-- PLEASE UPDATE THE LIST AT THE BOTTOM (OR TOP) OF THE PAGE TOO! -->
]
<P>
Return to <A HREF="/home.html">GNU's home page</A>.
<P>
Please send FSF & GNU inquiries & questions to
<A HREF="mailto:address@hidden";><EM>address@hidden</EM></A>.
There are also <A HREF="/home.html#ContactInfo">other ways to
contact</A> the FSF.
<P>
Please send comments on these web pages to
<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 (C) 1999, 2001 Free Software Foundation, Inc.,
59 Temple Place - Suite 330, Boston, MA 02111, USA
<P>
Verbatim copying and distribution of this entire article is
permitted in any medium, provided this notice is preserved.<P>
Updated:
<!-- timestamp start -->
$Date: 2001/12/20 10:18:10 $ $Author: mohit $
<!-- timestamp end -->
<HR>
</BODY>
</HTML>
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- [GNU-traductores] old-gnudist:/home/www/html/server/standards/README.webmastering.html -- New file,
old-gnudist's file diff daemon <=