[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www/server/standards README.webmastering.html
From: |
Dora Scilipoti |
Subject: |
www/server/standards README.webmastering.html |
Date: |
Sat, 17 Jan 2015 14:27:31 +0000 |
CVSROOT: /web/www
Module name: www
Changes by: Dora Scilipoti <dora> 15/01/17 14:27:31
Modified files:
server/standards: README.webmastering.html
Log message:
More under 'mirrors'.
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/server/standards/README.webmastering.html?cvsroot=www&r1=1.178&r2=1.179
Patches:
Index: README.webmastering.html
===================================================================
RCS file: /web/www/www/server/standards/README.webmastering.html,v
retrieving revision 1.178
retrieving revision 1.179
diff -u -b -r1.178 -r1.179
--- README.webmastering.html 6 Jan 2015 07:20:17 -0000 1.178
+++ README.webmastering.html 17 Jan 2015 14:27:30 -0000 1.179
@@ -750,57 +750,76 @@
<h3 id="mirrors">Mirrors</h3>
-<p><i>ftp mirrors:</i> we have <a href="/server/mirror.html">advice for
-mirrors</a> that explains what we ask mirror volunteers to provide.</p>
+<h4>GNU mirrors</h4>
-<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.</p>
+<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
+<a href="/server/mirror.html">advice for mirrors</a>; that page explains
+what we ask mirror volunteers to provide. If in <i>any</i> doubt, comment
+on the same ticket to ask other webmasters' opinion, or check with the
+webmasters mailing list and/or address@hidden before taking any
+action.</p>
<p>After confirming the mirror meets our criteria for listing, do this:</p>
<ol>
- <li>Edit the file prep/FTP (in CVS); it's plain text, not HTML.</li>
+ <li>Edit the file /prep/FTP (in CVS); it's plain text, not HTML.</li>
<li>Run <code>make</code> in the <tt>prep/</tt> subdirectory.</li>
- <li>cvs commit both of the files FTP and ftp.html. In the commit log message,
- include the name of the mirror and its location, and the RT number if there
- is one.</li>
+ <li>cvs commit both files FTP and ftp.html. In the commit log message,
+ include the name of the mirror and its location, and the RT number if
+ there is one.</li>
<li>Update the file <tt>/gd/gnuorg/web/FTP.contacts</tt> on Fencepost,
keeping the pattern as explained at the beginning of the file.</li>
+ <li>See next entry about the status of mirrors.</li>
</ol>
+<h5>Checking the Status of Mirrors</h5>
+
+<p>Mirrors are useful as long as they are kept up-to-date. Outdated mirrors
+can even be harmful, since downloading old versions of software may involve
+security risks for users. Checking the status of mirrors is therefore an
+essential part of the process of adding/modifying mirrors.</p>
+
<p>A <a href="http://download.savannah.gnu.org/mirmon/allgnu/">mirmon page</a>
-tracker shows how up-to-date each mirror is (maintained by savannah). when a
-mirror has gotten more than a week or two out of date, it is good to contact
-its maintainers and let them know about the problem so that they can fix it.
-If a mirror needs to be removed, please check to see if it is referenced
+tracker (maintained by savannah) shows how up-to-date each mirror is. When
+a mirror has gotten more than a few days out of date, it is necessary to
+contact its maintainers and let them know about the problem so that they
+can fix it. For examples on how to do this, search the RT system for
+tickets with subjects containing “[Mirror Status]”.</p>
+
+<p>If a mirror needs to be removed, please check to see if it is referenced
on <tt>/server/mirror.html</tt> and remove that entry as well.</p>
<p>The address <tt>http://ftpmirror.gnu.org/PKG</tt> (also maintained by
savannah) multiplexes between the mirrors, trying to choose one that is
nearby and up to date.</p>
-<p><i>nongnu mirrors:</i> when we get a request to add, change, or
-remove a nongnu savannah mirror, email address@hidden
-with the information. The reason to use -private is to avoid the
-contact address from becoming public. If the email address of a mirror
-admin is not involved or there are no other privacy issues, it's better to
-use address@hidden</p>
-
-<p><i>www mirrors:</i> we no longer recommend or list mirrors of
-www.gnu.org.</p>
-
-<p><i>Mirror contact information:</i> when we get a request relating to
-a mirror, please check the file <tt>/gd/gnuorg/web/FTP.contacts</tt> on
-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
-informed. This requires hand-assembling a list of addresses from the
-<tt>FTP.contacts</tt> file based on the current mirror list.</p>
+<h4>nongnu mirrors</h4>
+
+<p>When we get a request to add, change, or remove a nongnu savannah mirror,
+email address@hidden with the information. The reason to
+use -private is to avoid the contact address from becoming public. If the
+email address of a mirror admin is not involved or there are no other
+privacy issues, it's better to use address@hidden</p>
+
+<h4>www mirrors</h4>
+
+<p>We no longer recommend or list mirrors of www.gnu.org.</p>
+
+<p><b>Mirror contact information</b></p>
+
+<p>When we get a request relating to a mirror, please check the file
+<tt>/gd/gnuorg/web/FTP.contacts</tt> on Fencepost and add contact
+information if it's not there already, or update it, if necessary. We lack
+information for many older mirrors, or the data we have is not up to date.</p>
+
+<p><b>Ibiblio URL changes</b></p>
+
+<p>If we are told or determine that there is a change in the rsync URL or
+the <a href="/server/mirror.html">advertised source mirror</a> URLs for
+ibiblio, 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.</p>
<h3 id="thankgnu">ThankGNU/ThankCRM</h3>
@@ -1251,7 +1270,7 @@
<p class="unprintable">Updated:
<!-- timestamp start -->
-$Date: 2015/01/06 07:20:17 $
+$Date: 2015/01/17 14:27:30 $
<!-- timestamp end -->
</p>
</div>
- www/server/standards README.webmastering.html, Dora Scilipoti, 2015/01/01
- www/server/standards README.webmastering.html, Dora Scilipoti, 2015/01/01
- www/server/standards README.webmastering.html, Dora Scilipoti, 2015/01/03
- www/server/standards README.webmastering.html, Quentin Pradet, 2015/01/06
- www/server/standards README.webmastering.html,
Dora Scilipoti <=
- www/server/standards README.webmastering.html, Quentin Pradet, 2015/01/26
- www/server/standards README.webmastering.html, Quentin Pradet, 2015/01/27