IoTex Contributor Guide

First off, thank you for considering contributing to IoTeX. It's people like you that make IoTeX chain great.

Following these guidelines helps to communicate that you respect the time of the developers managing and developing this open source project. In return, they should reciprocate that respect in addressing your issue, assessing changes, and helping you finalize your pull requests.

iotex-core is an open source project and we love to receive contributions from our community — you! There are many ways to contribute, from writing tutorials or blog posts, improving the documentation, submitting bug reports and feature requests or writing code which can be incorporated into iotex-core itself.

Please, don't use the issue tracker for support questions. Check gitter to ask your question.

Responsibilities

• Create issues for any major changes and enhancements that you wish to make. Discuss things transparently and get community feedback.
• Each pull request should implement ONE feature or bugfix. If you want to add or fix more than one thing, submit more than one pull request.
• Do not commit changes to files that are irrelevant to your feature or bugfix.
• Be willing to accept criticism and work on improving your code.
• Be aware that the pull request review process is not immediate, and is generally proportional to the size of the pull request.