summaryrefslogtreecommitdiffhomepage
path: root/CONTRIBUTING.md
diff options
context:
space:
mode:
authorNicolas Lacasse <nlacasse@google.com>2018-05-02 03:00:01 -0700
committerShentubot <shentubot@google.com>2018-05-02 03:00:53 -0700
commit7e901480b4a91536e984c1150369864fafef367f (patch)
tree10af1d924740b0cffbef5b741a1bd0cd5776b9a2 /CONTRIBUTING.md
parenteb5414ee29f20b1805345820e6174afff84276c2 (diff)
Fix links in README and CONTRIBUTING.
PiperOrigin-RevId: 195068006 Change-Id: I2d04a0c600b3850321f845fbdc0b6104dd178b3f
Diffstat (limited to 'CONTRIBUTING.md')
-rw-r--r--CONTRIBUTING.md25
1 files changed, 12 insertions, 13 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 152bb318c..3f3ab4d5f 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -3,19 +3,17 @@ Want to contribute? Great! First, read this page.
### Before you contribute
Before we can use your code, you must sign the
-[Google Individual Contributor License Agreement]
-(https://cla.developers.google.com/about/google-individual)
-(CLA), which you can do online. The CLA is necessary mainly because you own the
-copyright to your changes, even after your contribution becomes part of our
-codebase, so we need your permission to use and distribute your code. We also
-need to be sure of various other things—for instance that you'll tell us if you
-know that your code infringes on other people's patents. You don't have to sign
-the CLA until after you've submitted your code for review and a member has
-approved it, but you must do it before we can put your code into our codebase.
-Before you start working on a larger contribution, you should get in touch with
-us first through the issue tracker with your idea so that we can help out and
-possibly guide you. Coordinating up front makes it much easier to avoid
-frustration later on.
+[Google Individual Contributor License Agreement][gcla] (CLA), which you can do
+online. The CLA is necessary mainly because you own the copyright to your
+changes, even after your contribution becomes part of our codebase, so we need
+your permission to use and distribute your code. We also need to be sure of
+various other things—for instance that you'll tell us if you know that your
+code infringes on other people's patents. You don't have to sign the CLA until
+after you've submitted your code for review and a member has approved it, but
+you must do it before we can put your code into our codebase. Before you start
+working on a larger contribution, you should get in touch with us first through
+the issue tracker with your idea so that we can help out and possibly guide you.
+Coordinating up front makes it much easier to avoid frustration later on.
### Coding Guidelines
All code should conform to the [Go style guidelines][gostyle].
@@ -70,4 +68,5 @@ the one above, the
[Software Grant and Corporate Contributor License Agreement]
(https://cla.developers.google.com/about/google-corporate).
+[gcla]: https://cla.developers.google.com/about/google-individual
[gostyle]: https://github.com/golang/go/wiki/CodeReviewComments