Welcome! We're excited you're here and want to contribute.
These guidelines are designed to make it as easy as possible to get involved. If you have any questions that aren't discussed below, please let us know by opening an issue!
Before you start you'll need to set up a free GitHub account and sign in. Here are some instructions.
We want to make our resources accessible to and engaging for as many researchers as possible. We therefore require that all contributions adhere to our Code of Conduct.
Wiki: Coming soon.
Code: This repository is under development, and should contain the first steps of prepocessing fetal functional MRI data (Bash, AFNI, FSL,, Python...)
The list of labels for current include:
-
These issues contain a task that a member of the team has determined we need additional help with.
If you feel that you can contribute to one of these issues, we especially encourage you to do so!
-
These issues are asking for new features to be added to the project.
Please try to make sure that your requested feature is distinct from any others that have already been requested or implemented. If you find one that's similar but there are subtle differences please reference the other request in your issue.
We appreciate all contributions, but those accepted fastest will follow a workflow similar to the following:
1. Comment on an existing issue or open a new issue referencing your addition.
This allows other members of the development team to confirm that you aren't overlapping with work that's currently underway and that everyone is on the same page with the goal of the work you're going to carry out.
This blog is a nice explanation of why putting this work in up front is so useful to everyone involved.
2. Fork the fetal-code repository to your profile.
This is now your own unique copy of the fetal-fMRI repo. Changes here won't affect anyone else's work, so it's a safe space to explore edits to the code!
Make sure to keep your fork up to date with the master repository.
3. Make the changes you've discussed.
Try to keep the changes focused. If you feel tempted to "branch out" then please make a new branch.
4. Submit a pull request.
A member of the development team will review your changes to confirm that they can be merged into the main codebase.
We follow the all-contributors specification, so we welcome and recognize all contributions from documentation to testing to code development.)
You're awesome. 👋😃
— Based on contributing guidelines from the STEMMRoleModels project.