Contributing to Harp
Discussion about Harp happens on GitHub and over mailing list.
Community is critical to Harp. Contributions are welcomed!
How Can I Contribute to Harp?
You can first read the following pages to have a basic understanding of Heron:
In general, contributions that fix bugs or add features (as opposed to stylistic, refactoring, or “cleanup” changes) are preferred. Please check with mailing list if your patch involves lots of changes.
If you have any question or issues about troubleshooting, you should post on mailing list instead of opening GitHub issues.
Submitting a Patch
Read and accept the Apache License.
Discuss your plan and design, and get agreement on mailing list.
Implement proper unit tests along with your change. Verify that all tests can pass.
Submit a GitHub pull request that includes your change and test cases. Describe clearly your pull request the change.
Complete a code review by addressing reviewers’s comments.
A project committer will merge the patch to the master branch.