|
| 1 | +# Contributing Guidelines |
| 2 | + |
| 3 | +Read the following guide if you're interested in contributing to Ingress. |
| 4 | + |
| 5 | +## Contributor License Agreements |
| 6 | + |
| 7 | +We'd love to accept your patches! Before we can take them, we have to jump a couple of legal hurdles. |
| 8 | + |
| 9 | +Please fill out either the individual or corporate Contributor License Agreement (CLA). |
| 10 | + |
| 11 | + * 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). |
| 12 | + * 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). |
| 13 | + |
| 14 | +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. |
| 15 | + |
| 16 | +***NOTE***: Only original source code from you and other people that have signed the CLA can be accepted into the main repository. |
| 17 | + |
| 18 | +## Finding Things That Need Help |
| 19 | + |
| 20 | +If you're new to the project and want to help, but don't know where to start, we have a semi-curated list of issues that should not need deep knowledge of the system. [Have a look and see if anything sounds interesting](https://github.com/kubernetes/ingress/issues?utf8=%E2%9C%93&q=is%3Aopen%20is%3Aissue%20label%3Ahelp-wanted%20). Alternatively, read some of the docs on other controllers and try to write your own, file and fix any/all issues that come up, including gaps in documentation! |
| 21 | + |
| 22 | +## Contributing A Patch |
| 23 | + |
| 24 | +1. If you haven't already done so, sign a Contributor License Agreement (see details above). |
| 25 | +1. Fork the desired repo, develop and test your code changes. |
| 26 | +1. Submit a pull request. |
| 27 | + |
| 28 | +All changes must be code reviewed. Coding conventions and standards are explained in the official [developer docs](https://github.com/kubernetes/kubernetes/tree/8a2c639bfb2087a9a89c02d2dc30fcb9bd0846f6/docs/devel). Expect reviewers to request that you avoid common [go style mistakes](https://github.com/golang/go/wiki/CodeReviewComments) in your PRs. |
| 29 | + |
| 30 | +### Merge Approval |
| 31 | + |
| 32 | +Ingress collaborators may add "LGTM" (Looks Good To Me) or an equivalent comment to indicate that a PR is acceptable. Any change requires at least one LGTM. No pull requests can be merged until at least one Ingress collaborator signs off with an LGTM. |
| 33 | + |
| 34 | +## Support Channels |
| 35 | + |
| 36 | +Whether you are a user or contributor, official support channels include: |
| 37 | + |
| 38 | +- GitHub issues: https://github.com/kubenetes/ingress/issues/new |
| 39 | +- Slack: kubernetes-users room in the [Kubernetes Slack](http://slack.kubernetes.io/) |
| 40 | +- Email: [kubernetes-users](https://groups.google.com/forum/#!forum/kubernetes-users) mailing list |
| 41 | + |
| 42 | +Before opening a new issue or submitting a new pull request, it's helpful to search the project - it's likely that another user has already reported the issue you're facing, or it's a known issue that we're already aware of. |
0 commit comments