forked from LaconicNetwork/kompose
27 lines
1.4 KiB
Markdown
27 lines
1.4 KiB
Markdown
# Contributing guidelines
|
|
|
|
## 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.
|
|
|
|
Please fill out either the individual or corporate Contributor License Agreement (CLA).
|
|
|
|
* 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.
|
|
* If you work for a company that wants to allow you to contribute your work, then you'll need to sign a corporate CLA.
|
|
|
|
Contact one of the [OWNERS](OWNERS) on Slack 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.
|
|
|
|
### Contributing A Patch
|
|
|
|
1. Submit an issue describing your proposed change to the repo in question.
|
|
1. The [repo owners](OWNERS) 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.
|
|
|
|
### Adding dependencies
|
|
|
|
If your patch depends on new packages, add that package with [`glide`](https://github.com/Masterminds/glide). Follow the [instructions to add a dependency](https://github.com/kubernetes-incubator/kompose/blob/master/docs/development.md#glide-glide-vc-and-dependency-management).
|