You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.rst
+14-7Lines changed: 14 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,11 @@
1
-
Hacking on ``gcloud-python``
1
+
Contributing
2
2
============================
3
3
4
+
#. **Please sign one of the contributor license agreements below.**
5
+
#. Fork the repo, develop and test your code changes, add docs.
6
+
#. Make sure that your commit messages clearly describe the changes.
7
+
#. Send a pull request.
8
+
4
9
Here are some guidelines for hacking on gcloud-python.
5
10
6
11
Using a Development Checkout
@@ -155,10 +160,12 @@ can build the docs via::
155
160
156
161
$ tox -e docs
157
162
158
-
Change Log
159
-
----------
163
+
Contributor License Agreements
164
+
------------------------------
165
+
166
+
Before we can accept your pull requests you'll need to sign a Contributor License Agreement (CLA):
167
+
168
+
- **If you are an individual writing original source code** and **you own the intellectual property**, then you'll need to sign an `individual CLA <https://developers.google.com/open-source/cla/individual>`__.
169
+
- **If you work for a company that wants to allow you to contribute your work**, then you'll need to sign a `corporate CLA <https://developers.google.com/open-source/cla/corporate>`__.
160
170
161
-
- Feature additions and bugfixes must be added to the ``CHANGES.txt``
162
-
file in the prevailing style. Changelog entries should be long and
163
-
descriptive, not cryptic. Other developers should be able to know
164
-
what your changelog entry means.
171
+
You can sign these electronically (just scroll to the bottom). After that, we'll be able to accept your pull requests.
0 commit comments