#Notes Below is a default CONTRIBUTING.md file for all repositories under the Basho organization. It's best to keep the Contributing header identical - please open a PR if you think it should change!
All How-to contribute sections are recommended to be updated with the maintainer's preferred text.
##Contributing
This repo's maintainers are engineers at Basho and we welcome your contribution to the project!
Due to our obsession with stability and our rich ecosystem of users, community updates on this repo take longer to review.
The most helpful way to contribute is by reporting your experience through issues. Issues may not be updated while we review internally, but they're still incredibly appreciated.
Pull requests take multiple engineers for verification and testing. If you're passionate enough to want to learn more on how you can get hands on in this process, reach out to Matt, your developer advocate.
Thank you for being part of the community! We love you for it.
IMPORTANT: Always start by opening an issue to notify the engineers maintaining this repo. PRs that do not begin as a conversation over an issue are not as likely to be merged.
We encourages Issues and PRs to Riak from the community. Here’s how to get started.
- Fork the appropriate sub-projects that are affected by your change.
- Create a topic branch for your change and checkout that branch.
git checkout -b some-topic-branch - Make your changes and run the test suite if one is provided. (see below)
- Commit your changes and push them to your fork.
- Open pull-requests for the appropriate projects.
- Contributors will review your pull request, suggest changes, and merge it when it’s ready and/or offer feedback.
- To report a bug or issue, please open a new issue against this repository.
You can read the full guidelines for bug reporting and code contributions on the Riak Docs.
And thank you! Your contribution is incredibly important to us.