1If you have a bugfix or new feature that you would like to contribute to 2elasticsearch-py, please find or open an issue about it first. Talk about what 3you would like to do. It may be that somebody is already working on it, or that 4there are particular issues that you should know about before implementing the 5change. 6 7We enjoy working with contributors to get their code accepted. There are many 8approaches to fixing a problem and it is important to find the best approach 9before writing too much code. 10 11The process for contributing to any of the Elasticsearch repositories is similar. 12 131. Please make sure you have signed the [Contributor License 14 Agreement](http://www.elastic.co/contributor-agreement/). We are not 15 asking you to assign copyright to us, but to give us the right to distribute 16 your code without restriction. We ask this of all contributors in order to 17 assure our users of the origin and continuing existence of the code. You only 18 need to sign the CLA once. 19 202. Run the test suite to ensure your changes do not break existing code: 21 22 ```` 23 python setup.py test 24 ```` 25 26 See the README file in `test_elasticsearch` directory for more information on 27 running the test suite. 28 293. Rebase your changes. 30 Update your local repository with the most recent code from the main 31 elasticsearch-py repository, and rebase your branch on top of the latest master 32 branch. We prefer your changes to be squashed into a single commit. 33 344. Submit a pull request. Push your local changes to your forked copy of the 35 repository and submit a pull request. In the pull request, describe what your 36 changes do and mention the number of the issue where discussion has taken 37 place, eg “Closes #123″. Please consider adding or modifying tests related to 38 your changes. 39 40Then sit back and wait. There will probably be a discussion about the pull 41request and, if any changes are needed, we would love to work with you to get 42your pull request merged into elasticsearch-py. 43 44