| Trevor Johns | e904b62 | 2014-08-27 18:30:35 -0700 | [diff] [blame] | 1 | # How to become a contributor and submit your own code |
| 2 | |
| 3 | ## Contributor License Agreements |
| 4 | |
| 5 | We'd love to accept your sample apps and patches! Before we can take them, we |
| 6 | have to jump a couple of legal hurdles. |
| 7 | |
| 8 | Please fill out either the individual or corporate Contributor License Agreement (CLA). |
| 9 | |
| 10 | * If you are an individual writing original source code and you're sure you |
| 11 | own the intellectual property, then you'll need to sign an [individual CLA] |
| 12 | (https://developers.google.com/open-source/cla/individual). |
| 13 | * If you work for a company that wants to allow you to contribute your work, |
| 14 | then you'll need to sign a [corporate CLA] |
| 15 | (https://developers.google.com/open-source/cla/corporate). |
| 16 | |
| 17 | Follow either of the two links above to access the appropriate CLA and |
| 18 | instructions for how to sign and return it. Once we receive it, we'll be able to |
| 19 | accept your pull requests. |
| 20 | |
| 21 | ## Contributing A Patch |
| 22 | |
| 23 | 1. Submit an issue describing your proposed change to the repo in question. |
| 24 | 1. The repo owner will respond to your issue promptly. |
| 25 | 1. If your proposed change is accepted, and you haven't already done so, sign a |
| 26 | Contributor License Agreement (see details above). |
| 27 | 1. Fork the desired repo, develop and test your code changes. |
| 28 | 1. Ensure that your code adheres to the existing style in the sample to which |
| 29 | you are contributing. Refer to the |
| 30 | [Android Code Style Guide] |
| 31 | (https://source.android.com/source/code-style.html) for the |
| 32 | recommended coding standards for this organization. |
| 33 | 1. Ensure that your code has an appropriate set of unit tests which all pass. |
| 34 | 1. Submit a pull request. |
| 35 | |
