@@ -71,21 +71,35 @@ Also as a great rule of thumb:
71
71
72
72
** If you get help, help others. Good karma rulez!**
73
73
74
- ### Submitting a Pull Request
74
+ ## Before you Contribute
75
+
76
+ ### Sign our Contributor License Agreement
77
+
78
+ Contributions to this project must be accompanied by a
79
+ [ Contributor License Agreement] ( https://cla.developers.google.com/about ) (CLA).
80
+ You (or your employer) retain the copyright to your contribution; this simply
81
+ gives us permission to use and redistribute your contributions as part of the
82
+ project.
83
+
84
+ If you or your current employer have already signed the Google CLA (even if it
85
+ was for a different project), you probably don't need to do it again.
75
86
76
- #### Before you contribute
87
+ Visit < https://cla.developers.google.com/ > to see your current agreements or to
88
+ sign a new one.
89
+
90
+ ### Review our community guidelines
91
+
92
+ This project follows
93
+ [ Google's Open Source Community Guidelines] ( https://opensource.google/conduct/ ) .
94
+
95
+ ### Submitting a Pull Request
77
96
78
- Before we can use your code, you must sign the
79
- [ Google Individual Contributor License Agreement] [ google-cla ] (CLA), which you can do online. The
80
- CLA is necessary mainly because you own the copyright to your changes, even after your contribution
81
- becomes part of our codebase, so we need your permission to use and distribute your code. We also
82
- need to be sure of various other things, for instance, that you'll tell us if you know that your
83
- code infringes on other people's patents. You don't have to sign the CLA until after you've
84
- submitted your code for review and a member has approved it, but you must do it before we can put
85
- your code into our codebase. There is also a nifty CLA bot that will guide you through this process
86
- if you are going through it for the first time.
97
+ All submissions, including submissions by project members, require review. We use GitHub pull
98
+ requests for this purpose. Consult
99
+ [ GitHub Help] ( https://help.github.com/articles/about-pull-requests/ ) for more information on using
100
+ pull requests.
87
101
88
- Before you start working on a larger contribution, you should get in touch with us first through the
102
+ If you plan to work on a larger contribution, you should get in touch with us first through the
89
103
issue tracker with your idea so that we can help out and possibly guide you. Coordinating up front
90
104
makes it much easier to avoid frustration later on. Some pull requests (large contributions, API
91
105
additions/changes, etc) may be subject to additional internal review, we appreciate your patience as
0 commit comments