aboutsummaryrefslogtreecommitdiff
path: root/content/organizing-go-code.article
diff options
context:
space:
mode:
authorChris Broadfoot <cbro@golang.org>2017-02-03 12:06:31 -0800
committerChris Broadfoot <cbro@golang.org>2017-02-03 20:09:42 +0000
commitb3c50d1de11cd2caa3aa9ac81bb19502879a81e9 (patch)
tree339a0633086711461c8c0d125d47749995fbfd3b /content/organizing-go-code.article
parent788e27859f0b885bb2ee9b907e66571f6dd8b3d3 (diff)
content: fix links to code.google.com
Some minor fixes and clean up to articles that referred to code.google.com (now defunct). This cleans up all of the top 30 articles (not much point in cleaning up the articles that are less viewed). Fixes golang/go#18907. Change-Id: I38a22f57e1effa8a545b429dface088042df0f91 Reviewed-on: https://go-review.googlesource.com/36311 Reviewed-by: Russ Cox <rsc@golang.org>
Diffstat (limited to 'content/organizing-go-code.article')
-rw-r--r--content/organizing-go-code.article2
1 files changed, 1 insertions, 1 deletions
diff --git a/content/organizing-go-code.article b/content/organizing-go-code.article
index 17e8831..147bee2 100644
--- a/content/organizing-go-code.article
+++ b/content/organizing-go-code.article
@@ -22,7 +22,7 @@ A good name is the most important part of a software interface: the name is the
An import path is the string with which users import a package. It specifies the directory (relative to `$GOROOT/src/pkg` or `$GOPATH/src`) in which the package's source code resides.
-Import paths should be globally unique, so use the path of your source repository as its base. For instance, the `websocket` package from the `go.net` sub-repository has an import path of `"golang.org/x/net/websocket"`. The Go project owns the path `"code.google.com/p/go"`, so that path cannot be used by another author for a different package. Because the repository URL and import path are one and the same, the `go`get` command can fetch and install the package automatically.
+Import paths should be globally unique, so use the path of your source repository as its base. For instance, the `websocket` package from the `go.net` sub-repository has an import path of `"golang.org/x/net/websocket"`. The Go project owns the path `"github.com/golang"`, so that path cannot be used by another author for a different package. Because the repository URL and import path are one and the same, the `go`get` command can fetch and install the package automatically.
If you don't use a hosted source repository, choose some unique prefix such as a domain, company, or project name. As an example, the import path of all Google's internal Go code starts with the string `"google"`.