Skip to content

Latest commit

 

History

History
25 lines (15 loc) · 2.03 KB

CONTRIBUTING.md

File metadata and controls

25 lines (15 loc) · 2.03 KB

Contributing

  1. Fork it!
  2. Create your feature branch: git checkout -b my-new-feature (try to follow this convention)
  3. Commit your changes: git commit -am 'Add some feature'
  4. Push to the branch: git push origin my-new-feature
  5. Fill out the appropriate Contributor License Agreement (CLA) as explained below.
  6. Submit a pull request :D

Look at open issues on github. If you submit an issue, try to label it with the appropriate piece of the code it refers to, e.g. frontend, backend, android app, quality control or no label if none of the previous apply.

Look at DEVELOPER.md for much more detailed info on how the software operates.

Contributor License Agreements

Before we can use your code, you must sign a Contributor License Agreement (CLA). The CLA is necessary mainly because you own the copyright to your changes, even after your contribution becomes part of our codebase, so we need your permission to use and distribute your code. We also need to be sure of various other things — for instance that you'll tell us if you know that your code infringes on other people's patents. You don't have to sign the CLA until after you've submitted your pull request, but you must do it before we can put your code into our codebase.

Please fill out either the individual or corporate Contributor License Agreement:

  • If you are an individual writing original source code and you're sure you own the intellectual property, then you'll need to sign an individual CLA.

  • If you work for a company that wants to allow you to contribute your work, then you'll need to sign a corporate CLA.

Follow either of the two links above to access the appropriate CLA and instructions for how to sign and submit it. Once we receive it, we'll be able to accept your pull requests.