2016-04-25 17:42:07 +00:00
|
|
|
# Contributing guidelines
|
|
|
|
|
|
|
|
|
|
## Filing issues
|
|
|
|
|
|
|
|
|
|
File issues using the standard Github issue tracker for the repo.
|
|
|
|
|
|
|
|
|
|
## How to become a contributor and submit your own code
|
|
|
|
|
|
|
|
|
|
### Contributor License Agreements
|
|
|
|
|
|
|
|
|
|
We'd love to accept your patches! Before we can take them, we have to jump a couple of legal hurdles.
|
|
|
|
|
|
2018-01-02 06:04:49 +00:00
|
|
|
[Please fill out either the individual or corporate Contributor License Agreement (CLA)](http://git.k8s.io/community/CLA.md)
|
2016-04-25 17:42:07 +00:00
|
|
|
|
|
|
|
|
### Contributing A Patch
|
|
|
|
|
|
|
|
|
|
1. Submit an issue describing your proposed change to the repo in question.
|
|
|
|
|
1. The repo owner will respond to your issue promptly.
|
|
|
|
|
1. If your proposed change is accepted, and you haven't already done so, sign a Contributor License Agreement (see details above).
|
|
|
|
|
1. Fork the desired repo, develop and test your code changes.
|
|
|
|
|
1. Submit a pull request.
|
