forked from kubernetes-retired/contrib
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
link to the official CONTRIBUTING.md doc
- Loading branch information
1 parent
e055bc0
commit ce3a60a
Showing
1 changed file
with
1 addition
and
32 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,34 +1,3 @@ | ||
| # 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](http://code.google.com/legal/individual-cla-v1.0.html). | ||
| * 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). | ||
|
|
||
| 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. | ||
|
|
||
| ***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](https://github.com/GoogleCloudPlatform/kubernetes/tree/master/third_party). | ||
|
|
||
| ## 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. | ||
|
|
||
| ## Protocols for Collaborative Development | ||
|
|
||
| Please read [this doc](docs/devel/collab.md) for information on how we're running development for the project. | ||
| Also take a look at the [development guide](docs/devel/development.md) for information on how to set up your environment, run tests, manage dependencies, etc. | ||
|
|
||
| ## Adding dependencies | ||
|
|
||
| If your patch depends on new packages, add that package with [`godep`](https://github.com/tools/godep). Follow the [instructions to add a dependency](docs/devel/development.md#godep-and-dependency-management). | ||
|
|
||
|
|
||
| []() | ||
| For instructions on how to contribute to the Kubernetes project please refer to the official [contributing guide](https://releases.k8s.io/HEAD/CONTRIBUTING.md) |