|
| 1 | +<!-- |
| 2 | +Text in these brackets are comments, and won't be visible when you submit your pull request. |
| 3 | +If this is your first contribution, please take the time to read these, in particular the comment |
| 4 | +beginning "Welcome, new contributors!". |
| 5 | +--> |
| 6 | + |
| 7 | +## Changes proposed in this pull request |
| 8 | + |
| 9 | +<!-- |
| 10 | +Please describe here the main features / changes proposed for review and integration in fMRIPost-AROMA |
| 11 | +If this PR addresses some existing problem, please use GitHub's citing tools |
| 12 | +(eg. ref #, closes # or fixes #). |
| 13 | +If there is not an existing issue open describing the problem, please consider opening a new |
| 14 | +issue first and then link it from here (so the *fMRIPost-AROMA* community has a better understanding |
| 15 | +of ongoing development efforts and possible overlaps between contributions). |
| 16 | +--> |
| 17 | + |
| 18 | + |
| 19 | +## Documentation that should be reviewed |
| 20 | +<!-- |
| 21 | +Please summarize here the main changes to the documentation that the reviewers should be aware of. |
| 22 | +--> |
| 23 | + |
| 24 | + |
| 25 | + |
| 26 | +<!-- |
| 27 | +Welcome, new contributors! |
| 28 | +
|
| 29 | +We ask you to read through the Contributing Guide: |
| 30 | +https://github.com/nipreps/fmripost-aroma/blob/master/CONTRIBUTING.md |
| 31 | +
|
| 32 | +These are guidelines intended to make communication easier by describing a consistent process, but |
| 33 | +don't worry if you don't get it everything exactly "right" on the first try. |
| 34 | +
|
| 35 | +To boil it down, here are some highlights: |
| 36 | +
|
| 37 | +1) Consider starting a conversation in the issues list before submitting a pull request. The discussion might save you a |
| 38 | + lot of time coding. |
| 39 | +2) Please use descriptive prefixes in your pull request title, such as "ENH:" for an enhancement or "FIX:" for a bug fix. |
| 40 | + (See the Contributing guide for the full set.) And consider adding a "WIP" tag for works-in-progress. |
| 41 | +3) Any code you submit will be licensed under the same terms (Apache License 2.0) as the rest of fMRIPost-AROMA. |
| 42 | +4) We invite every contributor to add themselves to the `.zenodo.json` file |
| 43 | + (https://github.com/nipreps/fmripost-aroma/blob/master/.zenodo.json), which will result in your being listed as an author |
| 44 | + at the next release. Please add yourself as the next-to-last entry, just above Russ. |
| 45 | +
|
| 46 | +A pull request is a conversation. We may ask you to make some changes before accepting your PR, |
| 47 | +and likewise, you should feel free to ask us any questions you have. |
| 48 | +
|
| 49 | +--> |
0 commit comments