use https on links to build/dev.clojure.org

puredanger · puredanger · commit 3a7d19b8bd67 · 2017-04-20T11:13:59.000-05:00
diff --git a/content/community/contributing.adoc b/content/community/contributing.adoc
@@ -19,9 +19,9 @@ The CA does not change the rights or responsibilities of the Clojure community u
 
 == Making a contribution
 
-Before you invest time working on a change, discuss what you're trying to do with others on the https://groups.google.com/group/clojure-dev[Clojure Dev Google group]. They're likely to be able to offer comments and suggestions that will result in a higher-quality change and a smoother submission process. Announcing that you're working on a particular item can also help to avoid wasted effort in case someone else is already working on it. Once you've submitted the CA, you can http://dev.clojure.org/jira/browse/CLJ[submit patches via JIRA]. Frequent and trusted contributors of more substantial libraries may be granted committer membership in the Clojure contrib projects.
+Before you invest time working on a change, discuss what you're trying to do with others on the https://groups.google.com/group/clojure-dev[Clojure Dev Google group]. They're likely to be able to offer comments and suggestions that will result in a higher-quality change and a smoother submission process. Announcing that you're working on a particular item can also help to avoid wasted effort in case someone else is already working on it. Once you've submitted the CA, you can https://dev.clojure.org/jira/browse/CLJ[submit patches via JIRA]. Frequent and trusted contributors of more substantial libraries may be granted committer membership in the Clojure contrib projects.
 
-Please see the http://dev.clojure.org/display/community/Contributing[Contributing] wiki for a collection of resources on tickets, builds, patches, source, and more. If you'd like to submit a patch, please follow these guidelines on the http://dev.clojure.org/display/community/JIRA+workflow[preferred process for submitting].
+Please see the https://dev.clojure.org/display/community/Contributing[Contributing] wiki for a collection of resources on tickets, builds, patches, source, and more. If you'd like to submit a patch, please follow these guidelines on the https://dev.clojure.org/display/community/JIRA+workflow[preferred process for submitting].
 
 [[contributors]]
 == Contributors
diff --git a/content/community/downloads.adoc b/content/community/downloads.adoc
@@ -21,7 +21,7 @@ ifdef::env-github,env-browser[:outfilesuffix: .adoc]
 
 == Clojure Source
 
-Clojure source code is hosted at https://github.com/clojure/clojure[github.com/clojure/clojure]. Builds of the very latest version of Clojure's master branch are available at https://oss.sonatype.org/content/repositories/snapshots/org/clojure/clojure/1.9.0-master-SNAPSHOT/[build.clojure.org].
+Clojure source code is hosted at https://github.com/clojure/clojure[github.com/clojure/clojure]. Builds of the very latest version of Clojure's master branch are available at https://oss.sonatype.org/content/repositories/snapshots/org/clojure/clojure/1.9.0-master-SNAPSHOT/[oss.sonatype.org].
 
 == Get Clojure via Leiningen
 
@@ -34,6 +34,6 @@ Modify the dependencies and repositories sections of your https://leiningen.org/
 ----
 == Where did Clojure Contrib go?
 
-If you are migrating from a pre-1.3 version of Clojure, please see http://dev.clojure.org/display/community/Where+Did+Clojure.Contrib+Go[this page] for migration help regarding old contrib libraries.
+If you are migrating from a pre-1.3 version of Clojure, please see https://dev.clojure.org/display/community/Where+Did+Clojure.Contrib+Go[this page] for migration help regarding old contrib libraries.
 
 == <<downloads_older#,Older Releases>>
diff --git a/content/community/libraries.adoc b/content/community/libraries.adoc
@@ -11,17 +11,17 @@ ifdef::env-github,env-browser[:outfilesuffix: .adoc]
 
 Clojure Contrib is a collection of libraries managed with the same Contributor Agreement, license, and development workflow as Clojure itself. Code in Clojure Contrib can be considered for inclusion in newer versions of Clojure.
 
-Clojure Contrib library code is hosted on https://github.com/clojure[Github]. Design and issue tracking are via http://dev.clojure.org/display/doc/Clojure+Contrib[Confluence] and JIRA.
+Clojure Contrib library code is hosted on https://github.com/clojure[Github]. Design and issue tracking are via https://dev.clojure.org/display/doc/Clojure+Contrib[Confluence] and JIRA.
 
-Prior to Clojure 1.3, Contrib was packaged as a single monolithic JAR. If you are migrating from a pre-1.3 version of Clojure, please see http://dev.clojure.org/display/community/Where+Did+Clojure.Contrib+Go[this page] for migration help regarding old contrib libraries.
+Prior to Clojure 1.3, Contrib was packaged as a single monolithic JAR. If you are migrating from a pre-1.3 version of Clojure, please see https://dev.clojure.org/display/community/Where+Did+Clojure.Contrib+Go[this page] for migration help regarding old contrib libraries.
 
 == Leiningen
 
 The vast majority of Clojure developers use https://github.com/technomancy/leiningen[Leiningen] to create and manage Clojure projects.
 
 == IDEs and Developer Tools
 
-Community volunteers maintain http://dev.clojure.org/display/doc/getting+started[Getting Started] documentation for a number of different developer tools.
+Community volunteers maintain https://dev.clojure.org/display/doc/getting+started[Getting Started] documentation for a number of different developer tools.
 
 == Finding Libraries
 
diff --git a/content/community/resources.adoc b/content/community/resources.adoc
@@ -12,11 +12,11 @@ ifdef::env-github,env-browser[:outfilesuffix: .adoc]
 * https://groups.google.com/group/clojure[Clojure Google Group]
 * #clojure IRC channel on https://freenode.net[freenode.net]
 * http://clojurians.net[Clojurians Slack Chat]
-* http://dev.clojure.org/display/community/Clojure+User+Groups[Clojure User Groups]
+* https://dev.clojure.org/display/community/Clojure+User+Groups[Clojure User Groups]
 * http://planet.clojure.in/[Planet Clojure] blog aggregator
-* http://dev.clojure.org/display/community/Home[Community Wiki]
-* http://dev.clojure.org/display/doc/Home[Documentation Wiki]
-* http://dev.clojure.org/display/design/Home[Design Wiki]
+* https://dev.clojure.org/display/community/Home[Community Wiki]
+* https://dev.clojure.org/display/doc/Home[Documentation Wiki]
+* https://dev.clojure.org/display/design/Home[Design Wiki]
 
 == Tutorials and Learning Materials
 
@@ -27,7 +27,7 @@ Official:
 * <<xref/../../reference/documentation#,Clojure Reference Docs>> - official reference information
 * <<xref/../../api/cheatsheet#,Clojure Cheatsheet>> - helpful categorization of most core functions
 * Source - https://github.com/clojure/clojure[Clojure], https://github.com/clojure/clojurescript[ClojureScript], https://github.com/clojure/clojure-clr[ClojureCLR]
-* Issues - http://dev.clojure.org/jira/browse/CLJ[Clojure], http://dev.clojure.org/jira/browse/CLJS[ClojureScript], http://dev.clojure.org/jira/browse/CLJCLR[ClojureCLR]
+* Issues - https://dev.clojure.org/jira/browse/CLJ[Clojure], https://dev.clojure.org/jira/browse/CLJS[ClojureScript], https://dev.clojure.org/jira/browse/CLJCLR[ClojureCLR]
 
 Community:
 
@@ -76,7 +76,7 @@ Video training (commercial):
 
 == Clojure Tools
 
-Community volunteers maintain http://dev.clojure.org/display/doc/getting+started[Getting Started] documentation for a number of different tools and approaches. Some of the most commonly used tools include:
+Community volunteers maintain https://dev.clojure.org/display/doc/getting+started[Getting Started] documentation for a number of different tools and approaches. Some of the most commonly used tools include:
 
 * https://leiningen.org/[Leiningen] - an extensible build tool that provides dependency management, REPL support, testing, packaging, deployment, and many other capabilities.
 * http://boot-clj.com/[Boot] - build tooling for Clojure: instead of a special-purpose DSL, Boot supplies abstractions and libraries you can use to automate nearly any build scenario with the full power of the Clojure language
diff --git a/content/news/2011/07/22/introducing-clojurescript.adoc b/content/news/2011/07/22/introducing-clojurescript.adoc
@@ -45,7 +45,7 @@ Some parts of the Clojure language have no direct analog in ClojureScript, in pa
 
 Obviously, any code making interop calls to Java, as most existing Clojure libraries do, will not work in ClojureScript. Code written in pure Clojure will **probably** work in ClojureScript with minor adjustments. For example, https://github.com/clojure/clojure/blob/master/src/clj/clojure/zip.clj[clojure.zip in Clojure] and https://github.com/clojure/clojurescript/blob/master/src/cljs/clojure/zip.cljs[clojure.zip in ClojureScript] are nearly identical. With a little effort, purely algorithmic code can be made portable between implementations. However, trying to abstract over all the differences among host platforms has never been a goal of Clojure, nor will it be a goal of ClojureScript.
 
-We have a http://dev.clojure.org/jira/browse/CLJS[ClojureScript JIRA instance] set up to track bugs. As with Clojure itself, submitting patches requires signing the <<xref/../../../../../community/contributing#,Clojure Contributor Agreement>>. We can only accept patches through JIRA, not GitHub pull requests.
+We have a https://dev.clojure.org/jira/browse/CLJS[ClojureScript JIRA instance] set up to track bugs. As with Clojure itself, submitting patches requires signing the <<xref/../../../../../community/contributing#,Clojure Contributor Agreement>>. We can only accept patches through JIRA, not GitHub pull requests.
 
 == The Relationship to Google Closure
 
diff --git a/content/news/2012/02/17/clojure-governance.adoc b/content/news/2012/02/17/clojure-governance.adoc
@@ -43,7 +43,7 @@ The first big issue Clojure/core had to confront was the distribution of clojure
 
 My attempts at https://github.com/clojure/clojure-contrib/commit/a6a92b9b3d2bfd9a56e1e5e9cfba706d1aeeaae5[modularizing clojure-contrib within a single Git repository] failed to improve the situation. Eventually, we settled on the solution of separate Git repositories for each library. This was a huge amount of work: dozens of repositories to create and hundreds of files to move. Many of the contrib libraries were stagnant, their original authors lacking time to continue working on them.
 
-Finally, almost a year later, the situation has stabilized: http://dev.clojure.org/display/doc/Clojure%2BContrib[28 libraries], each with its own Git repository, test suite, http://build.clojure.org/[continuous integration], and independent release cycle. The overall code quality is higher and development is moving forward again.
+Finally, almost a year later, the situation has stabilized: https://dev.clojure.org/display/doc/Clojure%2BContrib[28 libraries], each with its own Git repository, test suite, https://build.clojure.org/[continuous integration], and independent release cycle. The overall code quality is higher and development is moving forward again.
 
 It was a painful transition for everyone, not least for those of us trying to manage it all and bear the brunt of the inevitable carping. On top of everything else, the whole process overlapped with the release of Clojure 1.3, the first release to break backwards-compatibility in noticeable ways (non-dynamic Vars as a default, long/double as default numeric types).
 
@@ -64,11 +64,11 @@ Conversely, the decision to move some libraries into the language, notably my te
 
 If there was one mistake that I personally made during the 1.3 migration, it was speaking as if Clojure/core *owned* Clojure and clojure-contrib. We don't: Clojure is owned by Rich Hickey, and clojure-contrib is owned jointly by Rich Hickey and contributors. But we *are* the appointed stewards (and Stuarts!) of the open-source Clojure ecosystem. In that role, we have to make decisions about what we choose to invest time in supporting. Given limited time, and following Rich's conservative position on new features, that decision is usually "no."
 
-It's a difficult position to be in. Most of Clojure/core's members come from the free-wheeling, fast-paced open-source world of Ruby on Rails. We really don't enjoy saying "no" all the time. But a conservative attitude toward new features is exactly the reason Clojure is so stable. Patches don't get into the language until they have been http://dev.clojure.org/display/design/JIRA%2Bworkflow[reviewed by at least three people], one of them Rich Hickey. New libraries don't get added to http://dev.clojure.org/display/design/Clojure%2BContrib[clojure-contrib] without multiple mailing-list discussions. None of the new contrib libraries has reached the http://dev.clojure.org/display/design/Contrib%2B1.0.0%2BReleases[1.0.0 milestone], and probably won't for some time. These hurdles are not arbitrary; they are an attempt to guarantee that new additions to Clojure reflect the same consideration and careful design that Rich invested in the original implementation.
+It's a difficult position to be in. Most of Clojure/core's members come from the free-wheeling, fast-paced open-source world of Ruby on Rails. We really don't enjoy saying "no" all the time. But a conservative attitude toward new features is exactly the reason Clojure is so stable. Patches don't get into the language until they have been https://dev.clojure.org/display/design/JIRA%2Bworkflow[reviewed by at least three people], one of them Rich Hickey. New libraries don't get added to https://dev.clojure.org/display/design/Clojure%2BContrib[clojure-contrib] without multiple mailing-list discussions. None of the new contrib libraries has reached the https://dev.clojure.org/display/design/Contrib%2B1.0.0%2BReleases[1.0.0 milestone], and probably won't for some time. These hurdles are not arbitrary; they are an attempt to guarantee that new additions to Clojure reflect the same consideration and careful design that Rich invested in the original implementation.
 
 So what is clojure-contrib today? It's a curated set of libraries whose ownership and licensing is governed by the Clojure Contributor Agreement. It could also serve as a proving ground for new features in the language, but this does not imply that every contrib library will eventually make it into the language.
 
-With the expansion of contrib, we've given name to another layer of organization: *Clojure/dev*. Clojure/dev is the set of all people who have signed the Clojure Contributor Agreement. This entitles them to participate in discussions on the http://groups.google.com/group/clojure-dev[clojure-dev mailing list], submit patches on http://dev.clojure.org/jira[JIRA], and become committers on contrib libraries. Within Clojure/dev is the smaller set of people who have been tasked with screening Clojure language tickets. Clojure/core overlaps with both groups.
+With the expansion of contrib, we've given name to another layer of organization: *Clojure/dev*. Clojure/dev is the set of all people who have signed the Clojure Contributor Agreement. This entitles them to participate in discussions on the http://groups.google.com/group/clojure-dev[clojure-dev mailing list], submit patches on https://dev.clojure.org/jira[JIRA], and become committers on contrib libraries. Within Clojure/dev is the smaller set of people who have been tasked with screening Clojure language tickets. Clojure/core overlaps with both groups.
 
 image::/images/content/news/2012-02-17/clojure-community-layers.png[Diagram showing layers of the Clojure community]
 
diff --git a/content/reference/repl_and_main.adoc b/content/reference/repl_and_main.adoc
@@ -153,8 +153,8 @@ Connection closed by foreign host.
 
 Also see:
 
-* http://dev.clojure.org/jira/browse/CLJ-1671[CLJ-1671]
-* http://dev.clojure.org/display/design/Socket+Server+REPL[Socket REPL design page]
+* https://dev.clojure.org/jira/browse/CLJ-1671[CLJ-1671]
+* https://dev.clojure.org/display/design/Socket+Server+REPL[Socket REPL design page]
 
 == Related functions
 
