|
| 1 | +## Contributing |
| 2 | + |
| 3 | +[fork]: https://github.com/IBM/sarama/fork |
| 4 | +[pr]: https://github.com/IBM/sarama/compare |
| 5 | +[released]: https://help.github.com/articles/github-terms-of-service/#6-contributions-under-repository-license |
| 6 | + |
| 7 | +Hi there! We are thrilled that you would like to contribute to Sarama. |
| 8 | +Your help is essential for keeping it great. |
| 9 | + |
| 10 | +Contributions to this project are [released][released] to the public under the project's [opensource license](LICENSE.md). |
| 11 | +By contributing to this project you agree to the [Developer Certificate of Origin](https://developercertificate.org/) (DCO). |
| 12 | +The DCO was created by the Linux Kernel community and is a simple statement that you, as a contributor, wrote or otherwise have the legal right to contribute those changes. |
| 13 | + |
| 14 | +Contributors must _sign-off_ that they adhere to these requirements by adding a `Signed-off-by` line to all commit messages with an email address that matches the commit author: |
| 15 | + |
| 16 | +``` |
| 17 | +feat: this is my commit message |
| 18 | +
|
| 19 | +Signed-off-by: Random J Developer <[email protected]> |
| 20 | +``` |
| 21 | + |
| 22 | +Git even has a `-s` command line option to append this automatically to your commit message: |
| 23 | + |
| 24 | +``` |
| 25 | +$ git commit -s -m 'This is my commit message' |
| 26 | +``` |
| 27 | + |
| 28 | +## Submitting a pull request |
| 29 | + |
| 30 | +0. [Fork][fork] and clone the repository |
| 31 | +1. Create a new branch: `git checkout -b my-branch-name` |
| 32 | +2. Make your change, push to your fork and [submit a pull request][pr] |
| 33 | +3. Wait for your pull request to be reviewed and merged. |
| 34 | + |
| 35 | +Here are a few things you can do that will increase the likelihood of your pull request being accepted: |
| 36 | + |
| 37 | +- Keep your change as focused as possible. If there are multiple changes you would like to make that are not dependent upon each other, consider submitting them as separate pull requests. |
| 38 | +- Write a [good commit message](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html). |
| 39 | + |
| 40 | +## Further Reading |
| 41 | + |
| 42 | +- [Developer Certificate of Origin versus Contributor License Agreements](https://julien.ponge.org/blog/developer-certificate-of-origin-versus-contributor-license-agreements/) |
| 43 | +- [The most powerful contributor agreement](https://lwn.net/Articles/592503/) |
| 44 | +- [How to Contribute to Open Source](https://opensource.guide/how-to-contribute/) |
| 45 | +- [Using Pull Requests](https://help.github.com/articles/about-pull-requests/) |
| 46 | +- [GitHub Help](https://help.github.com) |
0 commit comments