Contributor Policy

At HASH, our mission is to eliminate information failure. Amongst other things, that means being clear upfront about expectations.

We care about the long-term sustainability, growth, and legal footing of HASH’s open-source mission and free-to-access services. Because our work largely takes place in open codebases, and we accept code contributions from the general public, it's important we're able to guarantee that the code which is contributed is done so free from additional limitations or any risk of permissions being withdrawn in the future. We also seek to ensure that contributions are produced in a way that is consistent with our community guidelines. Finally, good Contributor Agreements protect contributors, lifting them of support duties or warranties which might exist in certain jurisdictions or circumstances.

We require everybody submitting code to HASH's public codebase on GitHub to sign a Contributor Agreement. Such as agreements are widely accepted and commonplace within open-source, with virtually all big projects maintained by companies requiring contributors sign an agreement. Our own is designed to be as close as possible to that of Google, who have grown spectacularly successful open-source projects under such terms (including operating systems like Android, and fundamental web technologies like Chromium).

You can view the terms of our Contributor Agreements below (links open in new tabs):

• →

  Individual Contributor Agreement

• →

  Organizational Contributor Agreement

You can sign up to our Contributor Agreement by opening a Pull Request on our public repositories and following the CLA Assistant bot's instructions. If you are part of an organization for which you do not ordinarily have legal signing authority, you must obtain consent from somebody who does. We look forward to welcoming you to the contributor community!