Change from Google CLA to DCO in CONTRIBUTING.md. (#1702)
Signed-off-by: Wolfgang Hess <whess@lyft.com>master
parent
b38b1cefa0
commit
10e57b0a27
|
@ -1,27 +1,30 @@
|
||||||
Want to contribute? Great! First, read this page (including the small print at the end).
|
Want to contribute? Great! First, read this page.
|
||||||
|
|
||||||
### Before you contribute
|
### Before you contribute
|
||||||
Before we can use your code, you must sign the
|
|
||||||
[Google Individual Contributor License Agreement]
|
Any contribution that you make to this repository will
|
||||||
(https://cla.developers.google.com/about/google-individual)
|
be under the Apache 2 License, as dictated by that
|
||||||
(CLA), which you can do online. The CLA is necessary mainly because you own the
|
[license](http://www.apache.org/licenses/LICENSE-2.0):
|
||||||
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
|
5. Submission of Contributions. Unless You explicitly state otherwise,
|
||||||
know that your code infringes on other people's patents. You don't have to sign
|
any Contribution intentionally submitted for inclusion in the Work
|
||||||
the CLA until after you've submitted your code for review and a member has
|
by You to the Licensor shall be under the terms and conditions of
|
||||||
approved it, but you must do it before we can put your code into our codebase.
|
this License, without any additional terms or conditions.
|
||||||
Before you start working on a larger contribution, you should get in touch with
|
Notwithstanding the above, nothing herein shall supersede or modify
|
||||||
us first through the issue tracker with your idea so that we can help out and
|
the terms of any separate license agreement you may have executed
|
||||||
possibly guide you. Coordinating up front makes it much easier to avoid
|
with Licensor regarding such Contributions.
|
||||||
frustration later on.
|
```
|
||||||
|
|
||||||
|
### Developer Certificate of Origin
|
||||||
|
|
||||||
|
Contributors must sign-off each commit by adding a `Signed-off-by: ...`
|
||||||
|
line to commit messages to certify that they have the right to submit
|
||||||
|
the code they are contributing to the project according to the
|
||||||
|
[Developer Certificate of Origin (DCO)](https://developercertificate.org/).
|
||||||
|
You can sign-off a commit via `git commit -s`.
|
||||||
|
|
||||||
### Code reviews
|
### Code reviews
|
||||||
All submissions, including submissions by project members, require review. We
|
|
||||||
use Github pull requests for this purpose.
|
|
||||||
|
|
||||||
### The small print
|
All submissions, including submissions by project members, require review.
|
||||||
Contributions made by corporations are covered by a different agreement than
|
We use GitHub pull requests for this purpose.
|
||||||
the one above, the
|
|
||||||
[Software Grant and Corporate Contributor License Agreement]
|
|
||||||
(https://cla.developers.google.com/about/google-corporate).
|
|
||||||
|
|
Loading…
Reference in New Issue