ソースを参照

HTTPS urls for ./project

Signed-off-by: Eric Windisch <eric@windisch.us>
Eric Windisch 10 年 前
コミット
5dc83233bc
4 ファイル変更8 行追加8 行削除
  1. 1 1
      project/GOVERNANCE.md
  2. 3 3
      project/PACKAGERS.md
  3. 2 2
      project/RELEASE-CHECKLIST.md
  4. 2 2
      project/TOOLS.md

+ 1 - 1
project/GOVERNANCE.md

@@ -4,7 +4,7 @@ In the spirit of openness, Docker created a Governance Advisory Board, and commi
 All output from the meetings should be considered proposals only, and are subject to the review and approval of the community and the project leadership.
 
 The materials from the first Docker Governance Advisory Board meeting, held on October 28, 2014, are available at 
-[Google Docs Folder](http://goo.gl/Alfj8r)
+[Google Docs Folder](https://goo.gl/Alfj8r)
 
 These include:
 

+ 3 - 3
project/PACKAGERS.md

@@ -47,7 +47,7 @@ To build Docker, you will need the following:
 * A recent version of Git and Mercurial
 * Go version 1.3 or later
 * A clean checkout of the source added to a valid [Go
-  workspace](http://golang.org/doc/code.html#Workspaces) under the path
+  workspace](https://golang.org/doc/code.html#Workspaces) under the path
   *src/github.com/docker/docker* (unless you plan to use `AUTO_GOPATH`,
   explained in more detail below)
 
@@ -237,9 +237,9 @@ are as follows (in order):
   installed at "/usr/bin/docker", then "/usr/bin/dockerinit" will be the first
   place this file is searched for)
 * "/usr/libexec/docker/dockerinit" or "/usr/local/libexec/docker/dockerinit"
-  ([FHS 3.0 Draft](http://www.linuxbase.org/betaspecs/fhs/fhs.html#usrlibexec))
+  ([FHS 3.0 Draft](https://www.linuxbase.org/betaspecs/fhs/fhs.html#usrlibexec))
 * "/usr/lib/docker/dockerinit" or "/usr/local/lib/docker/dockerinit" ([FHS
-  2.3](http://refspecs.linuxfoundation.org/FHS_2.3/fhs-2.3.html#USRLIBLIBRARIESFORPROGRAMMINGANDPA))
+  2.3](https://refspecs.linuxfoundation.org/FHS_2.3/fhs-2.3.html#USRLIBLIBRARIESFORPROGRAMMINGANDPA))
 
 If (and please, only if) one of the paths above is insufficient due to distro
 policy or similar issues, you may use the `DOCKER_INITPATH` environment variable

+ 2 - 2
project/RELEASE-CHECKLIST.md

@@ -145,7 +145,7 @@ To test locally:
 make docs
 ```
 
-To make a shared test at http://beta-docs.docker.io:
+To make a shared test at https://beta-docs.docker.io:
 
 (You will need the `awsconfig` file added to the `docs/` dir)
 
@@ -341,7 +341,7 @@ git push -f origin docs
 make AWS_S3_BUCKET=docs.docker.com BUILD_ROOT=yes DISTRIBUTION_ID=C2K6......FL2F docs-release
 ```
 
-The docs will appear on http://docs.docker.com/ (though there may be cached
+The docs will appear on https://docs.docker.com/ (though there may be cached
 versions, so its worth checking http://docs.docker.com.s3-website-us-east-1.amazonaws.com/).
 For more information about documentation releases, see `docs/README.md`.
 

+ 2 - 2
project/TOOLS.md

@@ -14,11 +14,11 @@ we run Docker in Docker to test.
 
 Leeroy is a Go application which integrates Jenkins with 
 GitHub pull requests. Leeroy uses 
-[GitHub hooks](http://developer.github.com/v3/repos/hooks/) 
+[GitHub hooks](https://developer.github.com/v3/repos/hooks/) 
 to listen for pull request notifications and starts jobs on your Jenkins 
 server.  Using the Jenkins [notification plugin][jnp], Leeroy updates the 
 pull request using GitHub's 
-[status API](http://developer.github.com/v3/repos/statuses/)
+[status API](https://developer.github.com/v3/repos/statuses/)
 with pending, success, failure, or error statuses.
 
 The leeroy repository is maintained at