How to become a contributor and submit patchesContributor License AgreementsWe'd love to accept your code patches! However, 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. - 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 to Google Data Python Client Library, then you'll need to sign a corporate CLA.
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 add you to the official list of contributors and be able to accept your patches. Submitting Patches- Join Google Data Python Client Library Contributors discussion group.
- Decide which code you want to submit. A submission should be a set of changes that addresses one issue in the Google Data Python Client Library issue tracker. Please don't mix more than one logical change per submittal, because it makes the history hard to follow. If you want to make a change that doesn't have a corresponding issue in the issue tracker, please create one.
- Also, coordinate with team members that are listed on the issue in question. This ensures that work isn't being duplicated and communicating your plan early also generally leads to better patches.
- Ensure that your code adheres to the Google Data Python source code style.
- Ensure that there are unit tests for your code. For templates to help you get started with new unit tests, see the CodeTemplates page.
- Sign a Contributor License Agreement.
- Attach the code (including unit tests) to the issue it addresses. For brand new files, attach the whole file. For patches to existing files, attach a Subversion diff (that is, svn diff).
|
