Learn more about contributing to Harp and our contributors


Slack group

Join our slack group

Contributing to Harp

Before starting, it would be a good idea to have a basic understanding of Harp. 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 questions or issues about troubleshooting, you should post on the Google Group instead of opening GitHub issues.

Harp Installation

Learn More

Data Interfaces and Types

Learn More

Computation Models

Learn More

Submitting a Patch

  1. Read and accept the Apache License.

  2. Discuss your plan and design, and get to an agreement on the Google Group.

  3. Implement proper unit tests along with your change. Verify that all tests can pass.

  4. Submit a GitHub pull request that includes your change and test cases. In your pull request clearly describe your change.

  5. Complete a code review by addressing reviewers’ comments.

  6. A project committer will merge the patch to the master branch.