This content is based upon a pre-established standard that developers in this project adhere to.
We're excited to hear and learn from you.
We've put together the following guidelines to help you figure out where you can best be helpful.
- Types of contributions we're looking for
- Ground rules & expectations
- How to contribute
- Style guide
- Setting up your environment
- Contribution review process
- Community
There are many ways you can directly contribute to the guides (in descending order of need):
- maintance of scraping code.
- science writing
- machine learning and analysis
- integration between science writing and analysis
Interested in making a contribution? Read on!
Before we get started, here are a few things we expect from you (and that you should expect from others):
- Anyone who makes constructive contributions, big or small, deserves credit. It is helpful, but not necessary if they can initiate self stating of affiliations in code files, and documents, were appropriate.
- Be kind and thoughtful in your conversations around this project. We all come from different backgrounds and projects, which means we likely have different perspectives on "how open source is done." Try to listen to others rather than convince them that your way is correct.
- Open Source Guides are released with a Contributor Code of Conduct. By participating in this project, you agree to abide by its terms.
- If you open a pull request, please ensure that your contribution passes all tests. If there are test failures, you will need to address them before we can merge your contribution.
- When adding content, please consider if it is widely valuable. Please don't add references or links to things you or your employer have created as others will do so if they appreciate it.
If you'd like to contribute, start by searching through the issues and pull requests to see whether someone else has raised a similar idea or question.
If you don't see your idea listed, and you think it fits into the goals of this guide, do one of the following:
- If your contribution is minor, such as a typo fix, open a pull request.
- If your contribution is major, such as a new guide, start by opening an issue first. That way, other people can weigh in on the discussion before you do any work.
If you're writing content, see the style guide to help your prose match the rest of the Guides.
Try to build within the Docker container, hyperlinked in the README.md
Although public conversation is good as it means everybody can benefit and learn from the conversation. All communication is merited, including private communication.
References: This project is built on top of heaps of FOS Software.