[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www/prep/maintain maintain.html
|
From: |
Ted Teah |
|
Subject: |
www/prep/maintain maintain.html |
|
Date: |
Thu, 14 Sep 2017 13:31:31 -0400 (EDT) |
CVSROOT: /web/www
Module name: www
Changes by: Ted Teah <tedt> 17/09/14 13:31:31
Modified files:
prep/maintain : maintain.html
Log message:
changed http to https and change ppump to the current status page
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/prep/maintain/maintain.html?cvsroot=www&r1=1.106&r2=1.107
Patches:
Index: maintain.html
===================================================================
RCS file: /web/www/www/prep/maintain/maintain.html,v
retrieving revision 1.106
retrieving revision 1.107
diff -u -b -r1.106 -r1.107
--- maintain.html 4 Nov 2016 03:09:49 -0000 1.106
+++ maintain.html 14 Sep 2017 17:31:31 -0000 1.107
@@ -253,13 +253,13 @@
the Texinfo source, but if that’s difficult for you, you can make a
diff for some other version of this document, or propose it in any way
that makes it clear. The source repository for this document can be
-found at <a
href="http://savannah.gnu.org/projects/gnustandards";>http://savannah.gnu.org/projects/gnustandards</a>.
+found at <a
href="https://savannah.gnu.org/projects/gnustandards";>https://savannah.gnu.org/projects/gnustandards</a>.
</p>
<a name="index-gnustandards_002dcommit_0040gnu_002eorg-mailing-list"></a>
<p>If you want to receive diffs for every change to these GNU documents,
join the mailing list <code>address@hidden</code>, for
instance via the web interface at
-<a
href="http://lists.gnu.org/mailman/listinfo/gnustandards-commit";>http://lists.gnu.org/mailman/listinfo/gnustandards-commit</a>.
+<a
href="https://lists.gnu.org/mailman/listinfo/gnustandards-commit";>https://lists.gnu.org/mailman/listinfo/gnustandards-commit</a>.
Archives are also available there.
</p>
<a name="index-Piercy_002c-Marge"></a>
@@ -298,7 +298,7 @@
project on behalf of RMS (Richard Stallman, the Chief GNUisance). If
you have any organizational questions or concerns you can contact the
committee at <a href="mailto:address@hidden";>address@hidden</a>. See
-<a
href="http://www.gnu.org/contact/gnu-advisory.html";>http://www.gnu.org/contact/gnu-advisory.html</a>
for the current
+<a
href="https://www.gnu.org/contact/gnu-advisory.html";>https://www.gnu.org/contact/gnu-advisory.html</a>
for the current
committee members. Additional information is in
<samp>/gd/gnuorg/advisory</samp>.
</p>
@@ -308,7 +308,7 @@
<p>If you find that any GNU computer systems (<code>fencepost.gnu.org</code>,
<code>ftp.gnu.org</code>, <code>www.gnu.org</code>,
<code>savannah.gnu.org</code>,
…) seem to be down, you can check the current status at
-<a href="http://pumprock.net/fsfstatus";>http://pumprock.net/fsfstatus</a>.
Most likely the problem, if
+<a href="https://quitter.se/fsfstatus";>https://quitter.se/fsfstatus</a>. Most
likely the problem, if
it can be alleviated at the FSF end, is already being worked on.
</p>
<a name="index-sysadmin_002c-FSF"></a>
@@ -337,13 +337,13 @@
available on the general GNU server, currently
<code>fencepost.gnu.org</code>. If you are the maintainer of a GNU package,
you should have an account there. If you don’t have one already, see
-<a
href="http://www.gnu.org/software/README.accounts.html";>http://www.gnu.org/software/README.accounts.html</a>.
You can also
+<a
href="https://www.gnu.org/software/README.accounts.html";>https://www.gnu.org/software/README.accounts.html</a>.
You can also
ask for accounts for people who significantly help you in working on
the package. Such GNU login accounts include email
-(see <a
href="http://www.fsf.org/about/systems/sending-mail-via-fencepost";>http://www.fsf.org/about/systems/sending-mail-via-fencepost</a>).
+(see <a
href="https://www.fsf.org/about/systems/sending-mail-via-fencepost";>https://www.fsf.org/about/systems/sending-mail-via-fencepost</a>).
</p>
<p>Other resources available to GNU maintainers are described at
-<a
href="http://www.gnu.org/software/devel.html";>http://www.gnu.org/software/devel.html</a>,
as well as throughout
+<a
href="https://www.gnu.org/software/devel.html";>https://www.gnu.org/software/devel.html</a>,
as well as throughout
this document. In brief:
</p>
<ul>
@@ -434,7 +434,7 @@
<a href="mailto:address@hidden";>address@hidden</a>.
</p>
<p>We’re happy to acknowledge all major contributors to GNU packages on
-the <a
href="http://www.gnu.org/people/people.html";>http://www.gnu.org/people/people.html</a>
web page. Please send
+the <a
href="https://www.gnu.org/people/people.html";>https://www.gnu.org/people/people.html</a>
web page. Please send
an entry for yourself to <a href="mailto:address@hidden";>address@hidden</a>,
and feel free to
suggest it to other significant developers on your package.
</p>
@@ -522,10 +522,10 @@
available on the general GNU server, currently
<code>fencepost.gnu.org</code>. If you are the maintainer of a GNU package,
you should have an account there. If you don’t have one already, see
-<a
href="http://www.gnu.org/software/README.accounts.html";>http://www.gnu.org/software/README.accounts.html</a>.
You can also
+<a
href="https://www.gnu.org/software/README.accounts.html";>https://www.gnu.org/software/README.accounts.html</a>.
You can also
ask for accounts for people who significantly help you in working on
the package. Such GNU login accounts include email
-(see <a
href="http://www.fsf.org/about/systems/sending-mail-via-fencepost";>http://www.fsf.org/about/systems/sending-mail-via-fencepost</a>).
+(see <a
href="https://www.fsf.org/about/systems/sending-mail-via-fencepost";>https://www.fsf.org/about/systems/sending-mail-via-fencepost</a>).
</p>
<p>In order for the contributor to know person should sign papers, you need
to ask per for the necessary papers. If you don’t know per well, and you
@@ -553,7 +553,7 @@
more details, you should send one of the templates that are found in
the directory <samp>/gd/gnuorg/Copyright/</samp>; they are also available
from the <samp>doc/Copyright/</samp> directory of the <code>gnulib</code>
project
-at <a
href="http://savannah.gnu.org/projects/gnulib";>http://savannah.gnu.org/projects/gnulib</a>.
This section
+at <a
href="https://savannah.gnu.org/projects/gnulib";>https://savannah.gnu.org/projects/gnulib</a>.
This section
explains which templates you should use in which circumstances.
<strong>Please don’t use any of the templates except for those listed
here, and please don’t change the wording.</strong>
@@ -619,9 +619,9 @@
For a translation of a manual, use <samp>assign.translation.manual</samp>.
</p>
<p>For translations of program strings (as used by GNU Gettext, for
-example; see <a
href="http://www.gnu.org/prep/standards/standards.html#Internationalization";>Internationalization</a>
in <cite>GNU Coding
+example; see <a
href="https://www.gnu.org/prep/standards/standards.html#Internationalization";>Internationalization</a>
in <cite>GNU Coding
Standards</cite>), use <samp>disclaim.translation</samp>. If you make use of
the
-Translation Project (<a
href="http://translationproject.org";>http://translationproject.org</a>)
facilities,
+Translation Project (<a
href="https://translationproject.org";>https://translationproject.org</a>)
facilities,
please check with the TP coordinators that they have sent the
contributor the papers; if they haven’t, then you should send the
papers. In any case, you should wait for the confirmation from the
@@ -1041,7 +1041,7 @@
Lesser GPL should be used (again, for the notice wording,
see <a href="#License-Notices-for-Code">License Notices for Code</a>). If a
GNU library provides unique
functionality, however, the GNU GPL should be used.
-<a
href="http://www.gnu.org/licenses/why-not-lgpl.html";>http://www.gnu.org/licenses/why-not-lgpl.html</a>
discusses this
+<a
href="https://www.gnu.org/licenses/why-not-lgpl.html";>https://www.gnu.org/licenses/why-not-lgpl.html</a>
discusses this
strategic choice.
</p>
<p>Some of these libraries need to work with programs released under
@@ -1076,7 +1076,7 @@
You should have received copies of the GNU General Public License and
the GNU Lesser General Public License along with this program. If
-not, see <a
href="http://www.gnu.org/licenses/";>http://www.gnu.org/licenses/</a>.
+not, see <a
href="https://www.gnu.org/licenses/";>https://www.gnu.org/licenses/</a>.
</pre></div>
<p>For small packages, you can use “This program” instead of
“GNU
@@ -1096,17 +1096,17 @@
You can use whichever is the most convenient for you.
</p>
<ul>
-<li> <a href="http://www.gnu.org/licenses/";>http://www.gnu.org/licenses/</a>.
+<li> <a href="https://www.gnu.org/licenses/";>https://www.gnu.org/licenses/</a>.
</li><li> The <code>gnulib</code> project on <code>savannah.gnu.org</code>,
which you
can access via anonymous Git or CVS. See
-<a
href="http://savannah.gnu.org/projects/gnulib";>http://savannah.gnu.org/projects/gnulib</a>.
+<a
href="https://savannah.gnu.org/projects/gnulib";>https://savannah.gnu.org/projects/gnulib</a>.
</li></ul>
<p>The official Texinfo sources for the licenses are also available in
those same places, so you can include them in your documentation. A
-GFDL-covered manual should include the GFDL in this way. See <a
href="http://www.gnu.org/software/texinfo/manual/texinfo/texinfo.html#GNU-Sample-Texts";>GNU
+GFDL-covered manual should include the GFDL in this way. See <a
href="https://www.gnu.org/software/texinfo/manual/texinfo/texinfo.html#GNU-Sample-Texts";>GNU
Sample Texts</a> in <cite>Texinfo</cite>, for a full example in a Texinfo
manual.
</p>
@@ -1137,7 +1137,7 @@
GNU General Public License for more details.
</p>
<p>You should have received a copy of the GNU General Public License
-along with this program. If not, see <a
href="http://www.gnu.org/licenses/";>http://www.gnu.org/licenses/</a>.
+along with this program. If not, see <a
href="https://www.gnu.org/licenses/";>https://www.gnu.org/licenses/</a>.
</p></blockquote>
<p>But in a small program which is just a few files, you can use
@@ -1155,13 +1155,13 @@
GNU General Public License for more details.
</p>
<p>You should have received a copy of the GNU General Public License
-along with this program. If not, see <a
href="http://www.gnu.org/licenses/";>http://www.gnu.org/licenses/</a>.
+along with this program. If not, see <a
href="https://www.gnu.org/licenses/";>https://www.gnu.org/licenses/</a>.
</p></blockquote>
<p>In either case, for those few packages which use the Lesser GPL
(see <a href="#Licensing-of-GNU-Packages">Licensing of GNU Packages</a>),
insert the word “Lesser” before
“General” in <em>all three</em> places.
-<a
href="http://www.gnu.org/licenses/gpl-howto.html";>http://www.gnu.org/licenses/gpl-howto.html</a>
discusses application
+<a
href="https://www.gnu.org/licenses/gpl-howto.html";>https://www.gnu.org/licenses/gpl-howto.html</a>
discusses application
the GPL in more detail.
</p>
@@ -1204,9 +1204,9 @@
can omit both cover texts. However, if it is copyright FSF, always
ask the FSF what to do.
</p>
-<p>See <a
href="http://www.gnu.org/software/texinfo/manual/texinfo/texinfo.html#GNU-Sample-Texts";>GNU
Sample Texts</a> in <cite>Texinfo</cite>, for a full example in a
+<p>See <a
href="https://www.gnu.org/software/texinfo/manual/texinfo/texinfo.html#GNU-Sample-Texts";>GNU
Sample Texts</a> in <cite>Texinfo</cite>, for a full example in a
Texinfo manual, and see
-<a
href="http://www.gnu.org/licenses/fdl-howto.html";>http://www.gnu.org/licenses/fdl-howto.html</a>
for more advice about
+<a
href="https://www.gnu.org/licenses/fdl-howto.html";>https://www.gnu.org/licenses/fdl-howto.html</a>
for more advice about
how to use the GNU FDL.
</p>
<p>If you write a manual that people might want to buy on paper, please
@@ -1373,10 +1373,10 @@
important one, important enough to be worth the work of cleaning it up.
</p>
<p>The GNU Coding Standards are a good thing to send people when you ask
-them to clean up changes (see <a
href="http://www.gnu.org/prep/standards/standards.html#Top";>Contents</a> in
<cite>GNU Coding
+them to clean up changes (see <a
href="https://www.gnu.org/prep/standards/standards.html#Top";>Contents</a> in
<cite>GNU Coding
Standards</cite>). The Emacs Lisp manual contains an appendix that gives
coding standards for Emacs Lisp programs; it is good to urge Lisp authors to
-read it (see <a
href="http://www.gnu.org/software/emacs/manual/html_mono/elisp.html#Tips";>Tips
and Conventions</a> in <cite>The GNU Emacs Lisp
+read it (see <a
href="https://www.gnu.org/software/emacs/manual/html_mono/elisp.html#Tips";>Tips
and Conventions</a> in <cite>The GNU Emacs Lisp
Reference Manual</cite>).
</p>
<hr>
@@ -1419,7 +1419,7 @@
because these are the most important platforms for a GNU package. If
you don’t have access to one of these platforms, as a GNU maintainer
you can get access to the general GNU login machine; see
-<a
href="http://www.gnu.org/software/README.accounts.html";>http://www.gnu.org/software/README.accounts.html</a>.
+<a
href="https://www.gnu.org/software/README.accounts.html";>https://www.gnu.org/software/README.accounts.html</a>.
</p>
<p>Supporting other platforms is optional—we do it when that seems like
a good idea, but we don’t consider it obligatory. If the users
don’t
@@ -1530,7 +1530,7 @@
<p>To create and maintain simple aliases and unmanaged lists, you can
edit <samp>/com/mailer/aliases</samp> on the main GNU server. If you
don’t
have an account there, please read
-<a
href="http://www.gnu.org/software/README.accounts.html";>http://www.gnu.org/software/README.accounts.html</a>
(see <a href="#GNU-Accounts-and-Resources">GNU Accounts and Resources</a>).
+<a
href="https://www.gnu.org/software/README.accounts.html";>https://www.gnu.org/software/README.accounts.html</a>
(see <a href="#GNU-Accounts-and-Resources">GNU Accounts and Resources</a>).
</p>
<p>But if you don’t want to learn how to do those things, you can ask
<a href="mailto:address@hidden";>address@hidden</a> to help you.
@@ -1603,7 +1603,7 @@
<a name="index-bug-reports_002c-email-tracker-for"></a>
<a name="index-bug-reports_002c-web-tracker-for"></a>
<p>If you would like to use an email-based bug tracking system, see
-<a href="http://bugs.gnu.org";>http://bugs.gnu.org</a>; this can be connected
with the regular
+<a href="https://bugs.gnu.org";>https://bugs.gnu.org</a>; this can be connected
with the regular
bug-reporting address. Alternatively, if you would like to use a
web-based bug tracking system, Savannah supports this (see <a
href="#Old-Versions">Old Versions</a>), but please don’t fail to accept
bugs by regular email as
well—we don’t want to put up unnecessary barriers against users
@@ -1624,7 +1624,7 @@
You can do this using a source control system (such as Bazaar, RCS,
CVS, Git, Subversion, …) if you like. An easy way to use
many such systems is via the Version Control library in Emacs
-(see <a
href="http://www.gnu.org/software/emacs/manual/html_mono/emacs.html#Introduction-to-VC";>Introduction
to Version Control</a> in <cite>The GNU Emacs Manual</cite>).
+(see <a
href="https://www.gnu.org/software/emacs/manual/html_mono/emacs.html#Introduction-to-VC";>Introduction
to Version Control</a> in <cite>The GNU Emacs Manual</cite>).
</p>
<p>The history of previous revisions and log entries is very important for
future maintainers of the package, so even if you do not make it
@@ -1637,7 +1637,7 @@
for source control and other package needs: <code>savannah.gnu.org</code>.
Savannah is managed by <a href="mailto:address@hidden";>address@hidden</a>.
For more
details on using and contributing to Savannah, see
-<a
href="http://savannah.gnu.org/maintenance";>http://savannah.gnu.org/maintenance</a>.
+<a
href="https://savannah.gnu.org/maintenance";>https://savannah.gnu.org/maintenance</a>.
</p>
<p>It’s not an absolute requirement, but all GNU maintainers are strongly
encouraged to take advantage of Savannah, as sharing such a central
@@ -1649,7 +1649,7 @@
<a name="index-savannah_002dannounce_0040gnu_002eorg-mailing-list"></a>
<p>If you do use Savannah, please subscribe to the
<a href="mailto:address@hidden";>address@hidden</a> mailing list
-(<a
href="http://lists.gnu.org/mailman/listinfo/savannah-announce";>http://lists.gnu.org/mailman/listinfo/savannah-announce</a>).
This
+(<a
href="https://lists.gnu.org/mailman/listinfo/savannah-announce";>https://lists.gnu.org/mailman/listinfo/savannah-announce</a>).
This
is a very low-volume list to keep Savannah users informed of system
upgrades, problems, and the like.
</p>
@@ -1802,7 +1802,7 @@
<p>If you distribute them, please inform their users prominently that
those non-free platforms trample their freedom. It is useful to refer
them to
-<a
href="http://www.gnu.org/philosophy/free-software-even-more-important.html";>http://www.gnu.org/philosophy/free-software-even-more-important.html</a>.
+<a
href="https://www.gnu.org/philosophy/free-software-even-more-important.html";>https://www.gnu.org/philosophy/free-software-even-more-important.html</a>.
You can say, “This program respects your freedom, but Windows does
not. To have freedom, you need to stop using Windows and other
software that denies your freedom.”
@@ -1938,9 +1938,9 @@
for your GNU package:
</p>
<ol>
-<li> Create an account for yourself at <a
href="http://savannah.gnu.org";>http://savannah.gnu.org</a>, if
+<li> Create an account for yourself at <a
href="https://savannah.gnu.org";>https://savannah.gnu.org</a>, if
you don’t already have one. By the way, this is also needed to
-maintain the web pages at <a href="http://www.gnu.org";>http://www.gnu.org</a>
for your project
+maintain the web pages at <a
href="https://www.gnu.org";>https://www.gnu.org</a> for your project
(see <a href="#Web-Pages">Web Pages</a>).
</li><li> In the ‘<samp>My Account Conf</samp>’ page on
<code>savannah</code>, upload the GPG
@@ -1954,7 +1954,7 @@
<code>gpg --keyserver keys.gnupg.net --send-keys <var>keyid</var></code>, where
<var>keyid</var> is the eight hex digits reported by <code>gpg
--list-public-keys</code> on the <code>pub</code> line before the date. For
full
-information about GPG, see <a
href="http://www.gnu.org/software/gpg";>http://www.gnu.org/software/gpg</a>.
+information about GPG, see <a
href="https://www.gnu.org/software/gpg";>https://www.gnu.org/software/gpg</a>.
</p>
</li><li> Compose a message with the following items in some
<var>msgfile</var>.
Then GPG-sign it by running <code>gpg --clearsign <var>msgfile</var></code>,
and
@@ -2029,7 +2029,7 @@
<p>One programmatic way to create and transfer the necessary files is to
use the <code>gnupload</code> script, which is available from the
<samp>build-aux/</samp> directory of the <code>gnulib</code> project at
-<a
href="http://savannah.gnu.org/projects/gnulib";>http://savannah.gnu.org/projects/gnulib</a>.
Run
+<a
href="https://savannah.gnu.org/projects/gnulib";>https://savannah.gnu.org/projects/gnulib</a>.
Run
<code>gnupload --help</code> for a description and examples. (With
<code>gnupload</code>, you specify a destination such as
‘<samp>ftp.gnu.org:</samp>’<var>pkgname</var> rather than using the
@@ -2165,9 +2165,9 @@
<samp>foo-1.0.tar.gz</samp> and <samp>foo-1.0.tar.gz.sig</samp> are placed in
the directory <samp>gnu/foo/</samp> on <code>ftp.gnu.org</code>. That is,
we’ll
have made our release available at
-‘<code>http://ftp.gnu.org/gnu/foo/foo-1.0.tar.gz</code>’ (and then
from
+‘<code>https://ftp.gnu.org/gnu/foo/foo-1.0.tar.gz</code>’ (and
then from
our many mirrors via
-‘<code>http://ftpmirror.gnu.org/foo/foo-1.0.tar.gz</code>’). Whew.
+‘<code>https://ftpmirror.gnu.org/foo/foo-1.0.tar.gz</code>’).
Whew.
</p>
<p>A common reason for the upload not succeeding is your GPG signature
not being registered with the upload system. There is nothing that
@@ -2346,7 +2346,7 @@
</p>
<p>If all you want to do is reduce how much stuff is in your release
directory, an alternative is to email <a
href="mailto:address@hidden";>address@hidden</a> and
-ask them to move old items to the <samp>http://ftp.gnu.org/old-gnu/</samp>
+ask them to move old items to the <samp>https://ftp.gnu.org/old-gnu/</samp>
directory; then they will still be available. In general, however, we
recommend leaving all official releases in the main release directory.
</p>
@@ -2426,7 +2426,7 @@
Savannah project site. Here, it is fine to also write news entries
for test releases and any other newsworthy events. The news feeds
from all GNU projects at savannah are aggregated at
-<a href="http://planet.gnu.org";>http://planet.gnu.org</a> (GNU Planet), unless
the text of the entry
+<a href="https://planet.gnu.org";>https://planet.gnu.org</a> (GNU Planet),
unless the text of the entry
contains the string ‘<samp>::noplanet::</samp>’. You can also
post items
directly, or arrange for feeds from other locations; see information
on the GNU Planet web page.
@@ -2446,23 +2446,23 @@
purpose of your package.
</li><li> Your package’s web page (normally
-‘<code>http://www.gnu.org/software/<var>package</var>/</code>’).
+‘<code>https://www.gnu.org/software/<var>package</var>/</code>’).
</li><li> Your package’s download location (normally
-‘<code>http://ftp.gnu.org/gnu/<var>package</var>/</code>’). It is
also
+‘<code>https://ftp.gnu.org/gnu/<var>package</var>/</code>’). It
is also
useful to mention the mirror list at
-<a
href="http://www.gnu.org/order/ftp.html";>http://www.gnu.org/order/ftp.html</a>,
and that
-‘<code>http://ftpmirror.gnu.org/<var>package/</var></code>’ will
automatically
+<a
href="https://www.gnu.org/order/ftp.html";>https://www.gnu.org/order/ftp.html</a>,
and that
+‘<code>https://ftpmirror.gnu.org/<var>package/</var></code>’ will
automatically
redirect to a nearby mirror.
-</li><li> The <tt>NEWS</tt> (see <a
href="http://www.gnu.org/prep/standards/standards.html#NEWS-File";>NEWS File</a>
in <cite>GNU Coding Standards</cite>) for
+</li><li> The <tt>NEWS</tt> (see <a
href="https://www.gnu.org/prep/standards/standards.html#NEWS-File";>NEWS
File</a> in <cite>GNU Coding Standards</cite>) for
the present release.
</li></ul>
<p>You may find the <samp>announce-gen</samp> script useful for creating
announcements, which is available from the <samp>build-aux/</samp> directory
of the <code>gnulib</code> project at
-<a
href="http://savannah.gnu.org/projects/gnulib";>http://savannah.gnu.org/projects/gnulib</a>.
+<a
href="https://savannah.gnu.org/projects/gnulib";>https://savannah.gnu.org/projects/gnulib</a>.
</p>
<hr>
@@ -2477,14 +2477,14 @@
<p>Please write web pages about your package, and install them on
<code>www.gnu.org</code>. They should follow our usual standards for web
-pages (see <a
href="http://www.gnu.org/server/fsf-html-style-sheet.html";>http://www.gnu.org/server/fsf-html-style-sheet.html</a>).
+pages (see <a
href="https://www.gnu.org/server/fsf-html-style-sheet.html";>https://www.gnu.org/server/fsf-html-style-sheet.html</a>).
The overall goals are to support a wide variety of browsers, to focus
on information rather than flashy eye candy, and to keep the site
simple and uniform.
</p>
<p>We encourage you to use the standard <code>www.gnu.org</code> template as
the basis for your pages:
-<a
href="http://www.gnu.org/server/standards/boilerplate-source.html";>http://www.gnu.org/server/standards/boilerplate-source.html</a>.
+<a
href="https://www.gnu.org/server/standards/boilerplate-source.html";>https://www.gnu.org/server/standards/boilerplate-source.html</a>.
</p>
<p>Some GNU packages have just simple web pages, but the more information
you provide, the better. So please write as much as you usefully can,
@@ -2494,7 +2494,7 @@
on <code>www.gnu.org</code> link to that site.
</p>
<p>Please follow the best practices of accessibility in your web pages
-(see <a
href="http://www.gnu.org/accessibility/accessibility.html";>http://www.gnu.org/accessibility/accessibility.html</a>).
+(see <a
href="https://www.gnu.org/accessibility/accessibility.html";>https://www.gnu.org/accessibility/accessibility.html</a>).
</p>
<table class="menu" border="0" cellspacing="0">
<tr><td align="left" valign="top">• <a href="#Hosting-for-Web-Pages"
accesskey="1">Hosting for Web Pages</a>:</td><td> </td><td
align="left" valign="top">
@@ -2521,7 +2521,7 @@
the project on <code>savannah.gnu.org</code>. Then you can edit the pages
using CVS, using the separate “web pages repository” available on
Savannah, which corresponds to
-‘<code>http://www.gnu.org/software/<var>package</var>/</code>’.
You can
+‘<code>https://www.gnu.org/software/<var>package</var>/</code>’.
You can
keep your source files there too (using any of a variety of version
control systems), but you can use <code>savannah.gnu.org</code> only for
your gnu.org web pages if you wish; simply register a “web-only”
@@ -2535,7 +2535,7 @@
<p>If you use Savannah, you can use a special file named <samp>.symlinks</samp>
in order to create symbolic links, which are not supported in CVS.
For details, see
-<a
href="http://www.gnu.org/server/standards/README.webmastering.html#symlinks";>http://www.gnu.org/server/standards/README.webmastering.html#symlinks</a>.
+<a
href="https://www.gnu.org/server/standards/README.webmastering.html#symlinks";>https://www.gnu.org/server/standards/README.webmastering.html#symlinks</a>.
</p>
<hr>
@@ -2564,11 +2564,11 @@
<p>Historically, web pages for GNU packages did not include GIF images,
because of patent problems (see <a
href="#Ethical-and-Philosophical-Consideration">Ethical and Philosophical
Consideration</a>). Although the GIF patents expired in 2006, using GIF
images is still not recommended, as the PNG and JPEG formats are
-generally superior. See <a
href="http://www.gnu.org/philosophy/gif.html";>http://www.gnu.org/philosophy/gif.html</a>.
+generally superior. See <a
href="https://www.gnu.org/philosophy/gif.html";>https://www.gnu.org/philosophy/gif.html</a>.
</p>
<p>Please make sure that any Javascript code in your web pages is covered
by a free license, and has its license indicated in a way LibreJS can
-recognize. See <a
href="http://gnu.org/philosophy/javascript-trap.html";>http://gnu.org/philosophy/javascript-trap.html</a>.
+recognize. See <a
href="https://gnu.org/philosophy/javascript-trap.html";>https://gnu.org/philosophy/javascript-trap.html</a>.
If the Javascript in the page is minified, or for any other reason is
not the source code, it must point to its source code as described
there.
@@ -2603,7 +2603,7 @@
creating all these different formats and index pages easier.
</p>
<p>We would like to list all GNU manuals on the page
-<a href="http://www.gnu.org/manual";>http://www.gnu.org/manual</a>, so if yours
isn’t there, please send
+<a href="https://www.gnu.org/manual";>https://www.gnu.org/manual</a>, so if
yours isn’t there, please send
mail to <code>address@hidden</code>, asking them to add yours, and they
will do so based on the contents of your <samp>manual</samp> directory.
</p>
@@ -2632,14 +2632,14 @@
development:
</p>
<div class="smallformat">
-<pre class="smallformat"><a
href="http://git.savannah.gnu.org/cgit/gnulib.git/tree/build-aux/gendocs.sh";>http://git.savannah.gnu.org/cgit/gnulib.git/tree/build-aux/gendocs.sh</a>
-<a
href="http://git.savannah.gnu.org/cgit/gnulib.git/tree/doc/gendocs_template";>http://git.savannah.gnu.org/cgit/gnulib.git/tree/doc/gendocs_template</a>
+<pre class="smallformat"><a
href="https://git.savannah.gnu.org/cgit/gnulib.git/tree/build-aux/gendocs.sh";>https://git.savannah.gnu.org/cgit/gnulib.git/tree/build-aux/gendocs.sh</a>
+<a
href="https://git.savannah.gnu.org/cgit/gnulib.git/tree/doc/gendocs_template";>https://git.savannah.gnu.org/cgit/gnulib.git/tree/doc/gendocs_template</a>
</pre></div>
<p>There is also a minimalistic template, available from:
</p>
<div class="smallformat">
-<pre class="smallformat"><a
href="http://git.savannah.gnu.org/cgit/gnulib.git/tree/doc/gendocs_template_min";>http://git.savannah.gnu.org/cgit/gnulib.git/tree/doc/gendocs_template_min</a>
+<pre class="smallformat"><a
href="https://git.savannah.gnu.org/cgit/gnulib.git/tree/doc/gendocs_template_min";>https://git.savannah.gnu.org/cgit/gnulib.git/tree/doc/gendocs_template_min</a>
</pre></div>
<p>Invoke the script like this, in the directory containing the Texinfo
@@ -2747,7 +2747,7 @@
</pre></div>
<p>See the “Keyword Substitution” section in the CVS manual,
available
-from <a href="http://cvs.nongnu.org";>http://cvs.nongnu.org</a>.
+from <a href="https://cvs.nongnu.org";>https://cvs.nongnu.org</a>.
</p>
<p>In Texinfo source, the recommended way to literally specify a
“dollar” keyword is:
@@ -2812,7 +2812,7 @@
JavaScript-based editing tools. Instead, a service without any
ethical concerns should be used, such as GNU’s Pootle instance
(<a
href="https://chapters.gnu.org/pootle";>https://chapters.gnu.org/pootle</a>) or
The Translation Project
-(<a href="http://translationproject.org";>http://translationproject.org</a>).
+(<a href="https://translationproject.org";>https://translationproject.org</a>).
</p>
<p>A GNU package should not refer the user to any non-free documentation
for free software. The need for free documentation to come with free
@@ -2880,7 +2880,7 @@
makes for a good society. The term open source, initiated in 1998, is
associated with a philosophy which studiously avoids such questions.
For a detailed explanation, see
-<a
href="http://www.gnu.org/philosophy/open-source-misses-the-point.html";>http://www.gnu.org/philosophy/open-source-misses-the-point.html</a>.
+<a
href="https://www.gnu.org/philosophy/open-source-misses-the-point.html";>https://www.gnu.org/philosophy/open-source-misses-the-point.html</a>.
</p>
<p>The GNU Project is aligned with the free software movement. This
doesn’t mean that all GNU contributors and maintainers have to agree;
@@ -2930,7 +2930,7 @@
documentation, and announcements and articles that you publish in your
role as the maintainer of a GNU package. If you want to explain the
terminology and its reasons, you can refer to the URL
-<a
href="http://www.gnu.org/gnu/linux-and-gnu.html";>http://www.gnu.org/gnu/linux-and-gnu.html</a>.
+<a
href="https://www.gnu.org/gnu/linux-and-gnu.html";>https://www.gnu.org/gnu/linux-and-gnu.html</a>.
</p>
<p>To make it clear that Linux is a kernel, not an operating system,
please take care to avoid using the term “Linux system” in those
@@ -2953,7 +2953,7 @@
Note that this uses a space, not a slash.
</p>
<p>For more about this point, see
-<a
href="http://www.gnu.org/gnu/gnu-linux-faq.html";>http://www.gnu.org/gnu/gnu-linux-faq.html</a>.
+<a
href="https://www.gnu.org/gnu/gnu-linux-faq.html";>https://www.gnu.org/gnu/gnu-linux-faq.html</a>.
</p>
<hr>
<a name="Interviews-and-Speeches"></a>
@@ -2969,7 +2969,7 @@
free software movement. Please avoid saying “open source” and
avoid
calling the GNU system “Linux”, just as you would in the package
itself (see <a href="#Terminology">Terminology</a>). Likewise, avoid
promoting nonfree
-programs (see <a
href="http://www.gnu.org/prep/standards/standards.html#References";>References</a>
in <cite>GNU Coding
+programs (see <a
href="https://www.gnu.org/prep/standards/standards.html#References";>References</a>
in <cite>GNU Coding
Standards</cite>) as you would in the package itself.
</p>
<p>Many GNU users have erroneous ideas about GNU. Outside of our
@@ -2979,14 +2979,14 @@
</p>
<ul>
<li> What GNU is (an operating system developed to be Unix-like and totally
-free software). It is good to mention <a
href="http://www.gnu.org";>http://www.gnu.org</a>.
+free software). It is good to mention <a
href="https://www.gnu.org";>https://www.gnu.org</a>.
</li><li> What free software is (the users control it, so it doesn’t
control
them). It is good to state the four freedoms and/or refer to
-<a
href="http://www.gnu.org/philosophy/free-sw.html";>http://www.gnu.org/philosophy/free-sw.html</a>.
+<a
href="https://www.gnu.org/philosophy/free-sw.html";>https://www.gnu.org/philosophy/free-sw.html</a>.
</li><li> What GNU/Linux is (Linux filled the last gap in GNU). It is useful
to
-refer to <a
href="http://www.gnu.org/gnu/linux-and-gnu.html";>http://www.gnu.org/gnu/linux-and-gnu.html</a>.
+refer to <a
href="https://www.gnu.org/gnu/linux-and-gnu.html";>https://www.gnu.org/gnu/linux-and-gnu.html</a>.
</li><li> What the GNU Project is (the project to develop GNU).
@@ -3061,10 +3061,10 @@
of the GNU Project, not products of <company name>. We call them
"free software" because you are free to copy and redistribute them,
following the rules stated in the license of each package. For more
-information, see http://www.gnu.org/philosophy/free-sw.html.
+information, see https://www.gnu.org/philosophy/free-sw.html.
If you are looking for service or support for GNU software, see
-http://www.gnu.org/gethelp/ for suggestions of where to ask.
+https://www.gnu.org/gethelp/ for suggestions of where to ask.
If you would like to contribute to the development of one of these
packages, contact the package maintainer or the bug-reporting address
@@ -3132,7 +3132,7 @@
spending of these funds.
</p>
<p>Of course, it is also good to encourage people to join the FSF
-(<a href="http://www.fsf.org";>http://www.fsf.org</a>) or make a general
donation, either instead
+(<a href="https://www.fsf.org";>https://www.fsf.org</a>) or make a general
donation, either instead
of or as well as package-specific donations.
</p>
@@ -3150,7 +3150,7 @@
<p>The Free Software Directory aims to be a complete list of free
software packages, within certain criteria. Every GNU package should
be listed there, so please see
-<a
href="http://www.gnu.org/help/directory.html#adding-entries";>http://www.gnu.org/help/directory.html#adding-entries</a>
for
+<a
href="https://www.gnu.org/help/directory.html#adding-entries";>https://www.gnu.org/help/directory.html#adding-entries</a>
for
information on how to write an entry for your package. Contact
<a href="mailto:address@hidden";>address@hidden</a> with any questions or
suggestions for
the Free Software Directory.
@@ -3232,7 +3232,7 @@
<div class="display">
<pre class="display">Copyright © 2000, 2001, 2002, 2007, 2008 Free
Software Foundation, Inc.
-<a href="http://fsf.org/";>http://fsf.org/</a>
+<a href="https://fsf.org/";>https://fsf.org/</a>
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
@@ -3614,7 +3614,7 @@
of the GNU Free Documentation License from time to time. Such new
versions will be similar in spirit to the present version, but may
differ in detail to address new problems or concerns. See
-<a href="http://www.gnu.org/copyleft/";>http://www.gnu.org/copyleft/</a>.
+<a href="https://www.gnu.org/copyleft/";>https://www.gnu.org/copyleft/</a>.
</p>
<p>Each version of the License is given a distinguishing version number.
If the Document specifies that a particular numbered version of this
@@ -3834,9 +3834,9 @@
<tr><td></td><td valign="top"><a href="#index-help_002c-getting">help,
getting</a>:</td><td> </td><td valign="top"><a
href="#Getting-Help">Getting Help</a></td></tr>
<tr><td></td><td valign="top"><a
href="#index-hierarchy_002c-under-ftp-upload-directory">hierarchy, under ftp
upload directory</a>:</td><td> </td><td valign="top"><a
href="#FTP-Upload-Directory-Trees">FTP Upload Directory Trees</a></td></tr>
<tr><td></td><td valign="top"><a
href="#index-hosting">hosting</a>:</td><td> </td><td valign="top"><a
href="#Hosting">Hosting</a></td></tr>
-<tr><td></td><td valign="top"><a
href="#index-http_003a_002f_002fbugs_002egnu_002eorg"><a
href="http://bugs.gnu.org";>http://bugs.gnu.org</a></a>:</td><td> </td><td
valign="top"><a href="#Replying-to-Mail">Replying to Mail</a></td></tr>
-<tr><td></td><td valign="top"><a
href="#index-http_003a_002f_002fplanet_002egnu_002eorg"><a
href="http://planet.gnu.org";>http://planet.gnu.org</a></a>:</td><td> </td><td
valign="top"><a href="#Announcements">Announcements</a></td></tr>
-<tr><td></td><td valign="top"><a
href="#index-https_003a_002f_002fpumprock_002enet_002ffsfstatus"><a
href="https://pumprock.net/fsfstatus";>https://pumprock.net/fsfstatus</a></a>:</td><td> </td><td
valign="top"><a href="#Getting-Help">Getting Help</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-http_003a_002f_002fbugs_002egnu_002eorg"><a
href="https://bugs.gnu.org";>https://bugs.gnu.org</a></a>:</td><td> </td><td
valign="top"><a href="#Replying-to-Mail">Replying to Mail</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-http_003a_002f_002fplanet_002egnu_002eorg"><a
href="https://planet.gnu.org";>https://planet.gnu.org</a></a>:</td><td> </td><td
valign="top"><a href="#Announcements">Announcements</a></td></tr>
+<tr><td></td><td valign="top"><a
href="#index-https_003a_002f_002fpumprock_002enet_002ffsfstatus"><a
href="https://quitter.se/fsfstatus";>https://quitter.se/fsfstatus</a></a>:</td><td> </td><td
valign="top"><a href="#Getting-Help">Getting Help</a></td></tr>
<tr><td></td><td valign="top"><a
href="#index-Hydra">Hydra</a>:</td><td> </td><td valign="top"><a
href="#GNU-Accounts-and-Resources">GNU Accounts and Resources</a></td></tr>
<tr><td colspan="4"> <hr></td></tr>
<tr><th><a name="Index_cp_letter-I">I</a></th><td></td><td></td></tr>
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- www/prep/maintain maintain.html,
Ted Teah <=