Skip to content

Commit 1c1f52f

Browse files
committed
Change CONTRIBUTING.md to CNCF CLA
1 parent 22f6906 commit 1c1f52f

File tree

1 file changed

+8
-10
lines changed

1 file changed

+8
-10
lines changed

CONTRIBUTING.md

Lines changed: 8 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,19 +1,17 @@
1-
# Contributing guidelines
1+
# Contributing
22

3-
We'd love to accept your patches! Before we can take them, we have to jump a couple of legal hurdles.
3+
Welcome to git-sync!
44

5-
Please fill out either the individual or corporate Contributor License Agreement (CLA).
5+
The [Kubernetes community repo](https://github.com/kubernetes/community) contains information about how to get started, how the community organizes, and more.
66

7-
* If you are an individual writing original source code and you're sure you own the intellectual property, then you'll need to sign an [individual CLA](http://code.google.com/legal/individual-cla-v1.0.html).
8-
* If you work for a company that wants to allow you to contribute your work, then you'll need to sign a [corporate CLA](http://code.google.com/legal/corporate-cla-v1.0.html).
7+
## Sign the CLA
98

10-
Follow either of the two links above to access the appropriate CLA and instructions for how to sign and return it. Once we receive it, we'll be able to accept your pull requests.
9+
We'd love to accept your patches, but before we can do that, you must sign the CNCF [Contributor License Agreement](https://git.k8s.io/community/contributors/guide/README.md#sign-the-cla).
1110

12-
***NOTE***: Only original source code from you and other people that have signed the CLA can be accepted into the main repository. This policy does not apply to [third_party](third_party/).
1311

14-
### Contributing A Patch
12+
## Contributing A Patch
1513

1614
1. Submit an issue describing your proposed change.
17-
1. If your proposed change is accepted, and you haven't already done so, sign a Contributor License Agreement (see details above).
18-
1. Fork the desired repo, develop and test your code changes.
15+
1. If your proposal is accepted, and you haven't already done so, sign the Contributor License Agreement (see details above).
16+
1. Fork the repo, develop and test your code changes. Don't forget tests!
1917
1. Submit a pull request.

0 commit comments

Comments
 (0)