We love your input! We want to make contributing to this project as easy and transparent as possible, whether it's:
- Reporting a bug
- Discussing the current state of the code
- Submitting a fix
- Proposing new features
We use github to host code, to track issues and feature requests, as well as accept pull requests.
We actively welcome your pull requests:
- Fork or clone the repo and create your branch from
main
. - If you've added code that should be tested, add tests.
- Add docstrings to facilitate our generated documentation.
- Ensure your (and our) tests pass
- Post the PR or file an issue and we will work with you
In short, when you submit code changes, your submissions are understood to be under the same BSD 3-Clause License that covers the project. Feel free to contact the maintainers if that's a concern.
Report bugs using Github's issues
We use GitHub issues to track public bugs. Report a bug by opening a new issue; it's that easy!
Great Bug Reports tend to have:
- A quick summary and/or background
- Steps to reproduce
- Be specific!
- Give sample code if you can, a minimum working example (MWE) is best but we understand MRI involves complicated and large data
- What you expected would happen
- What actually happens
- Notes (possibly including why you think this might be happening, or stuff you tried that didn't work)
People love thorough bug reports. I'm not even kidding.
- We (mostly) use Julia Blue
- It would be great if you did as well
By contributing, you agree that your contributions will be licensed under its BSD 3-Clause License.
This document was adapted from the open-source contribution guidelines for Facebook's Draft