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.

1 files changed, 13 insertions, 13 deletions

diff --git a/CONTRIBUTE b/CONTRIBUTE
index 9b5fb090e77..90c6a86b123 100644
--- a/CONTRIBUTE
+++ b/CONTRIBUTE
@@ -1,7 +1,7 @@
 * How developers contribute to GNU Emacs
 
 Here is how software developers can contribute to Emacs.  (Non-developers: see
-http://www.gnu.org/software/emacs/manual/html_node/emacs/Contributing.html
+https://www.gnu.org/software/emacs/manual/html_node/emacs/Contributing.html
 or run the shell command 'info "(emacs)Contributing"'.)
 
 ** The Emacs repository
@@ -38,12 +38,12 @@ there.
 
 Bug reports and fixes, feature requests and patches/implementations
 should be sent to bug-gnu-emacs@gnu.org, the bug/feature list.  This
-is coupled to the http://debbugs.gnu.org tracker.  It is best to use
+is coupled to the https://debbugs.gnu.org tracker.  It is best to use
 the command 'M-x report-emacs-bug RET' to report issues to the tracker
 (described below).  Be prepared to receive comments and requests for
 changes in your patches, following your submission.
 
-The Savannah info page http://savannah.gnu.org/mail/?group=emacs
+The Savannah info page https://savannah.gnu.org/mail/?group=emacs
 describes how to subscribe to the mailing lists, or see the list
 archives.
 
@@ -55,7 +55,7 @@ such patch without additional remarks, you can use a command like
 
 ** Issue tracker (a.k.a. "bug tracker")
 
-The Emacs issue tracker at http://debbugs.gnu.org lets you view bug
+The Emacs issue tracker at https://debbugs.gnu.org lets you view bug
 reports and search the database for bugs matching several criteria.
 Messages posted to the bug-gnu-emacs@gnu.org mailing list, mentioned
 above, are recorded by the tracker with the corresponding bugs/issues.
@@ -89,11 +89,11 @@ If your change requires updating the manuals to document new
 functions/commands/variables/faces, then use the proper Texinfo
 command to index them; for instance, use @vindex for variables and
 @findex for functions/commands.  For the full list of predefine indices, see
-http://www.gnu.org/software/texinfo/manual/texinfo/html_node/Predefined-Indices.html
+https://www.gnu.org/software/texinfo/manual/texinfo/html_node/Predefined-Indices.html
 or run the shell command 'info "(texinfo)Predefined Indices"'.
 
 For more specific tips on Emacs's doc style, see
-http://www.gnu.org/software/emacs/manual/html_node/elisp/Documentation-Tips.html
+https://www.gnu.org/software/emacs/manual/html_node/elisp/Documentation-Tips.html
 Use 'checkdoc' to check for documentation errors before submitting a patch.
 
 ** Testing your changes
@@ -104,7 +104,7 @@ functionality you commit (of course, some changes cannot be easily
 tested).
 
 Emacs uses ERT, Emacs Lisp Regression Testing, for testing.  See
-http://www.gnu.org/software/emacs/manual/html_node/ert/
+https://www.gnu.org/software/emacs/manual/html_node/ert/
 or run 'info "(ert)"' for for more information on writing and running
 tests.
 
@@ -184,7 +184,7 @@ them right the first time, so here are guidelines for formatting them:
   between the summary line and the file entries.
 
 - Emacs generally follows the GNU coding standards for ChangeLogs: see
-  http://www.gnu.org/prep/standards/html_node/Change-Logs.html
+  https://www.gnu.org/prep/standards/html_node/Change-Logs.html
   or run 'info "(standards)Change Logs"'.  One exception is that
   commits still sometimes quote `like-this' (as the standards used to
   recommend) rather than 'like-this' or ‘like this’ (as they do now),
@@ -194,7 +194,7 @@ them right the first time, so here are guidelines for formatting them:
   to ChangeLog entries: they must be in English, and be complete
   sentences starting with a capital and ending with a period (except
   the summary line should not end in a period).  See
-  http://www.gnu.org/prep/standards/html_node/Comments.html
+  https://www.gnu.org/prep/standards/html_node/Comments.html
   or run 'info "(standards)Comments"'.
 
   They are preserved indefinitely, and have a reasonable chance of
@@ -234,7 +234,7 @@ them right the first time, so here are guidelines for formatting them:
 ** Generating ChangeLog entries
 
 - You can use Emacs functions to write ChangeLog entries; see
-  http://www.gnu.org/software/emacs/manual/html_node/emacs/Change-Log-Commands.html
+  https://www.gnu.org/software/emacs/manual/html_node/emacs/Change-Log-Commands.html
   or run 'info "(emacs)Change Log Commands"'.
 
 - If you use Emacs VC, one way to format ChangeLog entries is to create
@@ -305,8 +305,8 @@ The best way to understand Emacs internals is to read the code.  Some
 source files, such as xdisp.c, have extensive comments describing the
 design and implementation.  The following resources may also help:
 
-http://www.gnu.org/software/emacs/manual/html_node/elisp/Tips.html
-http://www.gnu.org/software/emacs/manual/html_node/elisp/GNU-Emacs-Internals.html
+https://www.gnu.org/software/emacs/manual/html_node/elisp/Tips.html
+https://www.gnu.org/software/emacs/manual/html_node/elisp/GNU-Emacs-Internals.html
 
 or run 'info "(elisp)Tips"' or 'info "(elisp)GNU Emacs Internals"'.
 
@@ -365,7 +365,7 @@ 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/>.
 
 Local variables:
 mode: outline