1# Contributing 2 3We'd love to accept your code patches! However, before we can take them, we 4have to jump a couple of legal hurdles. 5 6## Contributor License Agreements 7 8Please fill out either the individual or corporate Contributor License 9Agreement as appropriate. 10 11* If you are an individual writing original source code and you're sure you 12own the intellectual property, then sign an [individual CLA](https://developers.google.com/open-source/cla/individual). 13* If you work for a company that wants to allow you to contribute your work, 14then sign a [corporate CLA](https://developers.google.com/open-source/cla/corporate). 15 16Follow either of the two links above to access the appropriate CLA and 17instructions for how to sign and return it. 18 19## Submitting a Patch 20 211. Sign the contributors license agreement above. 222. Decide which code you want to submit. A submission should be a set of changes 23that addresses one issue in the [issue tracker](https://github.com/google/leveldb/issues). 24Please don't mix more than one logical change per submission, because it makes 25the history hard to follow. If you want to make a change 26(e.g. add a sample or feature) that doesn't have a corresponding issue in the 27issue tracker, please create one. 283. **Submitting**: When you are ready to submit, send us a Pull Request. Be 29sure to include the issue number you fixed and the name you used to sign 30the CLA. 31 32## Writing Code ## 33 34If your contribution contains code, please make sure that it follows 35[the style guide](https://google.github.io/styleguide/cppguide.html). 36Otherwise we will have to ask you to make changes, and that's no fun for anyone. 37