[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www/server/standards README.webmastering.html
|
From: |
Pavel Kharitonov |
|
Subject: |
www/server/standards README.webmastering.html |
|
Date: |
Sat, 03 Mar 2012 06:05:01 +0000 |
CVSROOT: /web/www
Module name: www
Changes by: Pavel Kharitonov <ineiev> 12/03/03 06:05:01
Modified files:
server/standards: README.webmastering.html
Log message:
Boilerplate update; validation fixes; typo corrections.
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/server/standards/README.webmastering.html?cvsroot=www&r1=1.139&r2=1.140
Patches:
Index: README.webmastering.html
===================================================================
RCS file: /web/www/www/server/standards/README.webmastering.html,v
retrieving revision 1.139
retrieving revision 1.140
diff -u -b -r1.139 -r1.140
--- README.webmastering.html 2 Mar 2012 14:58:47 -0000 1.139
+++ README.webmastering.html 3 Mar 2012 06:04:46 -0000 1.140
@@ -1,10 +1,10 @@
<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: $Revision: 1.140 $ -->
<title>Webmastering Guidelines - GNU Project - Free Software Foundation</title>
-<meta http-equiv="content-type" content='text/html; charset=utf-8' />
-<link rel="stylesheet" type="text/css" href="/gnu.css" />
-<link rev="made" href="address@hidden" />
<!--#include virtual="/server/banner.html" -->
+<!--#set var="article_name" value="/server/standards/README.webmastering" -->
+<!--#include virtual="/server/gnun/initial-translations-list.html" -->
<h2>GNU Webmastering Guidelines</h2>
@@ -30,7 +30,7 @@
<a href="#commonreq">Handling common requests</a> -
<a href="#repo">Working with our repositories</a>.
-<p>By the way, please edit and improve this document!
+<p>By the way, please edit and improve this document!</p>
<h3 id="working">Working as a www.gnu.org webmaster</h3>
@@ -71,7 +71,9 @@
<p>As a general rule, things like this are always okay to do:</p>
<ul>
- <li>Fix typos, mis-spellings, broken links, and the like (a report of broken
links in <tt>/home/w/wwj/linc/reports</tt> on Fencepost. The reports are
separated by language code.)</li>
+ <li>Fix typos, misspellings, broken links, and the like (a report of
+ broken links in <tt>/home/w/wwj/linc/reports</tt> on Fencepost.
+ The reports are separated by language code.)</li>
<li>Requests from Richard Stallman
<a href="mailto:address@hidden";><address@hidden></a>,
John Sullivan <a
href="mailto:address@hidden";><address@hidden></a>,
@@ -90,7 +92,7 @@
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>
+not to the requestor!), and ask someone else to take it from there.</p>
<p>We do not have links to web sites of the <a
href="/distros/common-distros.html">well-known</a> GNU/Linux system
@@ -189,8 +191,7 @@
maintain, go ahead and fix it, using ‘Reply’ to tell the
submitter what you did, and then ‘Resolve’ it.</li>
-<a name="thankgnu"></a>
-<li>If the message is a ThankGNU:</li>
+<li id="thankgnu">If the message is a ThankGNU:
<ul>
<li>For an individual, add it to the appropriate
<tt>/thankgnus/YYYYsupporters.html</tt> file in the correct place.</li>
@@ -206,31 +207,32 @@
msgs has bugs. The occasional case of a person donating the same
amount twice is handled by FSF staff.</li>
</ul>
+</li>
<li>If the message is about making a link on one of our pages, see
-<a href="#pollinking">linking procedures and information</a>.
+<a href="#pollinking">linking procedures and information</a>.</li>
<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.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>.
+<a href="/fun/README">/fun/README</a>.</li>
<li>If the message is about a mirror, see <a
-href="#mirrors">mirror procedures and information</a>.
+href="#mirrors">mirror procedures and information</a>.</li>
<li>If the message opened a new ticket, but is actually a follow-up to
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.
+ticket.</li>
<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>
+redirecting tickets</a>.</li>
</ul>
@@ -371,22 +373,24 @@
<ul>
<li>Move tickets with opinions or inquiries about free software or GNU
philosophy, help using specific programs, or other such non-web
- site-specific questions, to the info queue.
+ site-specific questions, to the info queue.</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.
+ to the resources queue.</li>
<li>Move tickets that are about the actual content of fsf.org pages to
- the campaigns queue.
+ the campaigns queue.</li>
-<li>Move tickets that are about FSF memberships to the memberships queue.
+<li>Move tickets that are about FSF memberships to the memberships
+ queue.</li>
<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.
+ verify the problem and if it is real, move it to the sysadmin
+ queue.</li>
<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
@@ -550,7 +554,7 @@
<p>News items are posted by adding a new "News" entry to the
<a href="http://savannah.gnu.org/projects/www";>www project on
-Savannah</a>.
+Savannah</a>.</p>
<p>Once that is done there is no need to do anything more. The News
item will eventually appear on <a href="http://planet.gnu.org";>
@@ -703,7 +707,7 @@
<p>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
+rather than "open source." We do, however, require that they not
promote any non-free software.</p>
<p>If all this seems complicated, that's because, unfortunately, it is. Don't
@@ -750,8 +754,7 @@
additions.</p>
-<a id="usergroups"></a>
-<h4>Links to GNU & Free Software User Groups</h4>
+<h4 id="usergroups">Links to GNU & Free Software User Groups</h4>
<p>Requests for links to GNU or Free Software Users Groups can be referred
to the LibrePlanet website. Our ticket can then be resolved.</p>
@@ -765,7 +768,7 @@
<p>When we get a request to add, change, or remove a mirror of
ftp.gnu.org, first ensure the mirror meets our criteria, as described on
the above page. If in <i>any</i> doubt, check with the mailing list
-and/or address@hidden before taking any action.
+and/or address@hidden before taking any action.</p>
<p>After confirming the mirror meets our criteria for listing, edit the
file prep/FTP (in CVS); it's plain text, not HTML. Then run make in the
@@ -793,11 +796,11 @@
fencepost. and add contact information if it's not there already. We
lack information for many older mirrors.</p>
-<p><i>Ibiblio url changes:</i> if we are told or determine that the
-rsync url for ibiblio, or the <a href="/server/mirror.html">advertised
-source mirrors</a> urls, change, all mirror maintainers should be
+<p><i>Ibiblio URL changes:</i> if we are told or determine that the
+rsync URL for ibiblio, or the <a href="/server/mirror.html">advertised
+source mirrors</a> URLs, change, all mirror maintainers should be
informed. This requires hand-assembling a list of addresses from the
-<tt>FTP.contacts</tt> file based on the current mirror list.
+<tt>FTP.contacts</tt> file based on the current mirror list.</p>
<h3 id="commonreq">Handling common requests</h3>
@@ -1004,7 +1007,7 @@
<tt>www</tt> in the author, and you will get the repository
corresponding to <a
href="http://audio-video.gnu.org";>audio-video.gnu.org</a>. Discuss
-any changes to audio-video with address@hidden
+any changes to audio-video with address@hidden</p>
<p><i>Other packages:</i> Many software packages have their own projects
@@ -1037,7 +1040,7 @@
understand that way.)</p>
<p>Special files, named .symlinks, can be committed to the CVS tree that
-are interpreted as specificiations to build symbolic links. On commit,
+are interpreted as specifications to build symbolic links. On commit,
the current directory is searched recursively for .symlinks files. Only
directories containing a .symlinks file are handled.</p>
@@ -1078,7 +1081,7 @@
href="/server/fsf-html-style-sheet.html#NamingTranslations">naming
conventions</a>. As a side effect, this makes it impossible to use
symlinks to redirect to and from HTML files whose names look like
-translations, that is, <code>page.<var>LL</var>.html<code> or
+translations, that is, <code>page.<var>LL</var>.html</code> or
<code>page.<var>LL-CC</var>.html</code>, where LL and CC are two-letter
codes. When you need such redirections, use the <a
href="#htaccess">htaccess mechanism</a>.</p>
@@ -1107,13 +1110,24 @@
email the sysadmin list (address@hidden) rather than an individual,
unless you have a specific reason to do so.</p>
+<!-- If needed, change the copyright block at the bottom. In general,
+ pages on the GNU web server should be under CC BY-ND 3.0 US.
+ Please do NOT change or remove this without talking
+ with the webmasters or licensing team first.
+ Please make sure the copyright date is consistent with the document.
+ For web pages, it is ok to list just the latest year the document
+ was modified, or published.
+
+ If you wish to list earlier years, that is ok too.
+ Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
+ years, as long as each year in the range is in fact a copyrightable
+ year, i.e., a year in which the document was published (including
+ being publicly visible on the web or in a revision control system).
+
+ There is more detail about copyright years in the GNU Maintainers
+ Information document, www.gnu.org/prep/maintain. -->
+
-<!-- 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. -->
-<!-- Please make sure the copyright date is consistent with the document -->
-<!-- and that it is like this "2001, 2002" not this "2001-2002." -->
</div><!-- for id="content", starts in the include above -->
<!--#include virtual="/server/footer.html" -->
<div id="footer">
@@ -1130,43 +1144,18 @@
README</a> for information on coordinating and submitting translations
of this article.</p>
-<p>Copyright © 2011 Free Software Foundation, Inc.</p>
+<p>Copyright © 2012 Free Software Foundation, Inc.</p>
<p>This page is licensed under a <a rel="license"
href="http://creativecommons.org/licenses/by-nd/3.0/us/";>Creative
-Commons Attribution-NoDerivs 3.0 United States License</a>.
-</p>
+Commons Attribution-NoDerivs 3.0 United States License</a>.</p>
<p>Updated:
<!-- timestamp start -->
-$Date: 2012/03/02 14:58:47 $
+$Date: 2012/03/03 06:04:46 $
<!-- timestamp end -->
</p>
</div>
-
-<div id="translations">
-<h4>Translations of this page</h4>
-
-<!-- Please keep this list alphabetical by language code. -->
-<!-- Comment what the language is for each type, i.e. de is German. -->
-<!-- Write the language name in its own language (Deutsch) in the text. -->
-<!-- If you add a new language here, please -->
-<!-- advise address@hidden and add it to -->
-<!-- - /home/www/html/server/standards/README.translations.html -->
-<!-- - one of the lists under the section "Translations Underway" -->
-<!-- - if there is a translation team, you also have to add an alias -->
-<!-- to mail.gnu.org:/com/mailer/aliases -->
-<!-- Please also check you have the language code right; see: -->
-<!-- http://www.loc.gov/standards/iso639-2/php/code_list.php -->
-<!-- If the 2-letter ISO 639-1 code is not available, -->
-<!-- use the 3-letter ISO 639-2. -->
-<!-- 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>