Contributions are welcome, and they are greatly appreciated! Every little bit helps, and credit will always be given. You can contribute in the ways listed below.
Report bugs using GitHub issues.
If you are reporting a bug, please include:
- Your operating system name and version.
- Any details about your local setup that might be helpful in troubleshooting.
- Detailed steps to reproduce the bug.
Look through the GitHub issues for bugs. Anything tagged with "bug" and "help wanted" is open to whoever wants to implement it.
Look through the GitHub issues for features. Anything tagged with "enhancement" and "help wanted" is open to whoever wants to implement it.
FAIR4RS could always use more documentation, whether as part of the official FAIR4RS docs, in docstrings, or even on the web in blog posts, articles, and such.
The best way to send feedback is to file an issue on GitHub.
If you are proposing a feature:
- Explain in detail how it would work.
- Keep the scope as narrow as possible, to make it easier to implement.
- Remember that this is a volunteer-driven project, and that contributions are welcome :)
Ready to contribute? Here's how to set up FAIR4RS
for local development.
- Fork the repo on GitHub.
- Clone your fork locally.
- Install your local copy into a virtualenv, e.g., using
conda
. - Create a branch for local development and make changes locally.
- Commit your changes and push your branch to GitHub.
- Submit a pull request through the GitHub website.
Please note that the FAIR4RS project is released with a Contributor Code of Conduct. By contributing to this project you agree to abide by its terms.