Prefer HTTPS to FTP and HTTP in documentation

Most of this change is to boilerplate commentary such as license URLs.
This change was prompted by ftp://ftp.gnu.org's going-away party,
planned for November.  Change these FTP URLs to https://ftp.gnu.org
instead.  Make similar changes for URLs to other organizations moving
away from FTP.  Also, change HTTP to HTTPS for URLs to gnu.org and
fsf.org when this works, as this will further help defend against
man-in-the-middle attacks (for this part I omitted the MS-DOS and
MS-Windows sources and the test tarballs to keep the workload down).
HTTPS is not fully working to lists.gnu.org so I left those URLs alone
for now.

8 files changed, 26 insertions, 26 deletions

diff --git a/admin/notes/bugtracker b/admin/notes/bugtracker
index 3d6df03d5e7..6d0fe50ae53 100644
--- a/admin/notes/bugtracker
+++ b/admin/notes/bugtracker
@@ -1,6 +1,6 @@
 NOTES ON THE EMACS BUG TRACKER   -*- outline -*-
 
-The Emacs Bug Tracker can be found at http://debbugs.gnu.org/
+The Emacs Bug Tracker can be found at https://debbugs.gnu.org/
 
 * Quick-start guide
 
@@ -33,14 +33,14 @@ tags 123 moreinfo|unreproducible|wontfix|patch
 
 * More detailed information
 
-For a list of all bugs, see http://debbugs.gnu.org/db/pa/lemacs.html
+For a list of all bugs, see https://debbugs.gnu.org/db/pa/lemacs.html
 This is a static page, updated once a day.  There is also a dynamic
 list, generated on request. This accepts various options, eg to see
 the most recent bugs:
 
-http://debbugs.gnu.org/cgi/pkgreport.cgi?newest=100
+https://debbugs.gnu.org/cgi/pkgreport.cgi?newest=100
 
-Or follow the links on the front page http://debbugs.gnu.org .
+Or follow the links on the front page https://debbugs.gnu.org .
 
 ** How do I report a bug in Emacs now?
 The same way as you always did.  Send mail to bug-gnu-emacs@gnu.org,
@@ -73,7 +73,7 @@ cc everyone on replies.)
 (Many people think the submitter SHOULD be automatically subscribed
 to subsequent discussion, but this does not seem to be implemented.
 See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=37078
-See also http://debbugs.gnu.org/5439 )
+See also https://debbugs.gnu.org/5439 )
 
 Do NOT send a separate copy to the bug list address, since this may
 generate a new report.  The only time to send mail to the bug list
@@ -246,7 +246,7 @@ reopen 123
 *** Bugs can be tagged in various ways (eg wontfix, patch, etc).
 The available tags are:
 patch wontfix moreinfo unreproducible fixed notabug
-See http://debbugs.gnu.org/Developer#tags
+See https://debbugs.gnu.org/Developer#tags
 The list of tags can be prefixed with +, - or =, meaning to add (the
 default), remove, or reset the tags. E.g.:
 
@@ -254,7 +254,7 @@ tags 123 + wontfix
 
 ** URL shortcuts
 
-http://debbugs.gnu.org/...
+https://debbugs.gnu.org/...
 
 123             # given bug number
 123;mbox=yes    # mbox version of given bug
@@ -314,11 +314,11 @@ search box.  The only piece you really need to add is the "users"
 portion, the rest has the same syntax as normal.
 
 **** To browse bugs by usertag:
-http://debbugs.gnu.org/cgi/pkgindex.cgi?indexon=users
+https://debbugs.gnu.org/cgi/pkgindex.cgi?indexon=users
 
 **** To find all bugs usertagged by a given email address:
 
-http://debbugs.gnu.org/cgi/pkgreport.cgi?users=emacs
+https://debbugs.gnu.org/cgi/pkgreport.cgi?users=emacs
 
 (Supposedly, the "users" field can be a comma-separated list of more
 than one email address, but it does not seem to work for me.)
@@ -328,7 +328,7 @@ than one email address, but it does not seem to work for me.)
 This works just like a normal tags search, but with the addition of a
 "users" field.  Eg:
 
-http://debbugs.gnu.org/cgi/pkgreport.cgi?users=emacs;tag=calendar
+https://debbugs.gnu.org/cgi/pkgreport.cgi?users=emacs;tag=calendar
 
 *** To merge bugs:
 Eg when bad replies create a bunch of new bugs for the same report.
@@ -377,7 +377,7 @@ You must unmerge, clone, then re-merge.
 *** To set severity:
 severity 123 critical|grave|serious|important|normal|minor|wishlist
 
-See http://debbugs.gnu.org/Developer#severities for the meanings.
+See https://debbugs.gnu.org/Developer#severities for the meanings.
 
 *** To set the owner of a bug:
 owner 123 A Hacker <none@example.com>
@@ -435,10 +435,10 @@ The bug will be re-archived after the next 28 day period of no activity.
 
 It's a function of the number of displayed bugs.  You can speed things
 up by only looking at the newest 100 bugs:
-http://debbugs.gnu.org/cgi-bin/pkgreport.cgi?newest=100;package=emacs
+https://debbugs.gnu.org/cgi-bin/pkgreport.cgi?newest=100;package=emacs
 
 Or use the static index:
-http://debbugs.gnu.org/db/ix/full.html
+https://debbugs.gnu.org/db/ix/full.html
 
 ** What are those "mbox folder" links on the bug report pages?
 
@@ -484,7 +484,7 @@ the bug web-pages.
 
 *** Debian stuff
 
-http://lists.gnu.org/archive/html/emacs-devel/2009-11/msg00440.html
+https://lists.gnu.org/archive/html/emacs-devel/2009-11/msg00440.html
 
 ** Gnus-specific voodoo
 
@@ -493,7 +493,7 @@ http://lists.gnu.org/archive/html/emacs-devel/2009-11/msg00440.html
 *** If the above is not available:
 (add-hook 'gnus-article-mode-hook
           (lambda ()
-             (setq bug-reference-url-format "http://debbugs.gnu.org/%s")
+             (setq bug-reference-url-format "https://debbugs.gnu.org/%s")
               (bug-reference-mode 1)))
 
 and you can click on the bug number in the subject header.
@@ -507,8 +507,8 @@ reference, you don't need to read these as a user of the system.
 Getting mail from the Emacs bug list into the tracker requires the
 assistance of sysadmin at gnu.org.  The test tracker set-up was, I
 think, [gnu.org #359140]:
-http://lists.gnu.org/archive/html/savannah-hackers/2008-03/msg00074.html
-http://lists.gnu.org/archive/html/savannah-hackers/2008-04/msg00034.html
+https://lists.gnu.org/archive/html/savannah-hackers/2008-03/msg00074.html
+https://lists.gnu.org/archive/html/savannah-hackers/2008-04/msg00034.html
 
 ** The debbugs.gnu.org setup was handled in [gnu.org #510605].
 There are two pieces (replace AT with @ in the following):
@@ -548,7 +548,7 @@ It does basic spam processing on the moderator requests and
 automatically rejects the obviously bogus ones.  Someone still has to
 accept the good ones though.  The advantage of this would not be having
 to run and tune our own spam filter.  See
-http://savannah.nongnu.org/projects/listhelper
+https://savannah.nongnu.org/projects/listhelper
 
 An "X-Debbugs-Envelope-To" header is used to keep track of where the
 mail was actually bound for:
diff --git a/admin/notes/copyright b/admin/notes/copyright
index 9b614221caf..8345646b977 100644
--- a/admin/notes/copyright
+++ b/admin/notes/copyright
@@ -511,7 +511,7 @@ etc/TUTORIAL* (translations)
   rms: "We can leave the TUTORIAL translations alone until their
   maintainers update them."
   Can adapt short license text from end of GPL translations at:
-  http://www.gnu.org/licenses/translations.html
+  https://www.gnu.org/licenses/translations.html
   Only a few sentences around the license notice need changing from
   previous version.
 Done: TUTORIAL.eo
@@ -594,4 +594,4 @@ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
 GNU General Public License for more details.
 
 You should have received a copy of the GNU General Public License
-along with GNU Emacs.  If not, see <http://www.gnu.org/licenses/>.
+along with GNU Emacs.  If not, see <https://www.gnu.org/licenses/>.
diff --git a/admin/notes/elpa b/admin/notes/elpa
index 4c0f1980def..ea6c132fe19 100644
--- a/admin/notes/elpa
+++ b/admin/notes/elpa
@@ -10,7 +10,7 @@ repository named "elpa", hosted on Savannah.  To check it out:
 
 Changes to this branch propagate to elpa.gnu.org via a "deployment" script run
 daily.  This script (which is kept in elpa/admin/update-archive.sh) generates
-the content visible at http://elpa.gnu.org/packages.
+the content visible at https://elpa.gnu.org/packages.
 
 A new package is released as soon as the "version number" of that package is
 changed.  So you can use 'elpa' to work on a package without fear of releasing
diff --git a/admin/notes/font-backend b/admin/notes/font-backend
index 2418966c93d..65c37a483bc 100644
--- a/admin/notes/font-backend
+++ b/admin/notes/font-backend
@@ -66,4 +66,4 @@ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
 GNU General Public License for more details.
 
 You should have received a copy of the GNU General Public License
-along with GNU Emacs.  If not, see <http://www.gnu.org/licenses/>.
+along with GNU Emacs.  If not, see <https://www.gnu.org/licenses/>.
diff --git a/admin/notes/hydra b/admin/notes/hydra
index 4c1944a57da..a0c46df08e4 100644
--- a/admin/notes/hydra
+++ b/admin/notes/hydra
@@ -68,4 +68,4 @@ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
 GNU General Public License for more details.
 
 You should have received a copy of the GNU General Public License
-along with GNU Emacs.  If not, see <http://www.gnu.org/licenses/>.
+along with GNU Emacs.  If not, see <https://www.gnu.org/licenses/>.
diff --git a/admin/notes/multi-tty b/admin/notes/multi-tty
index d0096adc6d2..0969daf9d07 100644
--- a/admin/notes/multi-tty
+++ b/admin/notes/multi-tty
@@ -1296,4 +1296,4 @@ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
 GNU General Public License for more details.
 
 You should have received a copy of the GNU General Public License
-along with GNU Emacs.  If not, see <http://www.gnu.org/licenses/>.
+along with GNU Emacs.  If not, see <https://www.gnu.org/licenses/>.
diff --git a/admin/notes/unicode b/admin/notes/unicode
index 8284e1b44cf..bc7279150a9 100644
--- a/admin/notes/unicode
+++ b/admin/notes/unicode
@@ -306,4 +306,4 @@ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
 GNU General Public License for more details.
 
 You should have received a copy of the GNU General Public License
-along with GNU Emacs.  If not, see <http://www.gnu.org/licenses/>.
+along with GNU Emacs.  If not, see <https://www.gnu.org/licenses/>.
diff --git a/admin/notes/www b/admin/notes/www
index 8e911a44d50..8e5bfb68d7a 100644
--- a/admin/notes/www
+++ b/admin/notes/www
@@ -79,4 +79,4 @@ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
 GNU General Public License for more details.
 
 You should have received a copy of the GNU General Public License
-along with GNU Emacs.  If not, see <http://www.gnu.org/licenses/>.
+along with GNU Emacs.  If not, see <https://www.gnu.org/licenses/>.