We love pull requests from everyone! We follow the standard Git workflow of fork -> change -> pull request -> merge -> update fork -> change ... (repeat forever). If you are new to open source, we recommend GitHub's excellent guide on "How to Contribute to Open Source". In addition, please feel free to reach out to any of the maintainers or other community members if you are struggling; we are here to help you learn!
Before getting started, please make sure you've read the README to get a primer on our project. Augur's documentation can be found at: https://oss-augur.readthedocs.io/en/master
If you're experience an issue with Augur or have a question you'd like help answering, please feel free to open an issue. To help us prevent duplicates, we kindly ask that you briefly search for your problem or question in our issues before opening a new one.
Please note that if you open a bug report and your issue does not follow our template, we cannot help you until you have provided us all the relevant information in that format. Respectfully, we do not have the time to try and recreate an error given with on minimal or no context, so by providing this information you are helping us help you! You will see this template when you open an issue; click on "Bug Report" and it will be populated with descriptions of what to put in each section. Replace the descriptions with your comments to the best of your ability, and please include screenshots and error logs if applicable.
- Fork this repo, and then clone it:
$ git clone github.com:your-username/augur.git
$ cd augur/-
Follow the development installation instructions.
-
Make your change(s).
-
Push to your fork.
-
Then, submit a pull request.
At this point you're waiting on us. We like to at least comment on pull requests within three business days (and, typically, one business day). Once one of our maintainers has had a chance to review your PR, we will either mark it as "needs review" and provide specific feedback on your changes, or we will go ahead and complete the pull request.
We require all commits to be signed off with a Developer Certificate of Origin in accordance with the CHAOSS charter. This can be easily done by using the -s flag when using git commit. For example: git commit -s -m "Update README.md". Any pull requests containing commits that are not signed off will not be eligible for merge until the commits have been signed off.
- Stable documentation (
masterbranch) - Nightly/developer build documentation (
devbranch) (warning: this is should be considered an unstable branch and should not be used for production) - Live Augur demo
- Website
- Get Involved
- Metrics
- Evolution Metrics Working Group
- Common Metrics Working Group
- Risk Metrics Working Group
- Value Metrics Working Group
- Diversity & Inclusion Metrics Working Group
- How to contribute to Open Source
- GitHub's Git Handbook
- GitHub's "Hello World" tutorial
- Understanding the GitHub Flow
- Commit message style guidelines
- No-nonsense Git reference (best to have a cursory understanding of Git before hand)