Skip to content

DOC: Clarify how contributors list is updated #57

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 27, 2025
Merged

DOC: Clarify how contributors list is updated #57

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions docs/community/CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -290,6 +290,13 @@ myworkflow_rh_wf = init_workflow_wf(name='myworkflow_rh_wf')
We welcome and recognize all contributions regardless their size, content or scope:
from documentation to testing and code development.
You can see a list of current developers and contributors in our [zenodo file][link_zenodo].
Note that the `.zenodo.json` file is generated automatically, digesting data
from the `maint/MAINTAINERS.md` and `maint/CONTRIBUTORS.md` files (and from
the `maint/PIs.md` and `maint/FORMER.md` files, if applicable).
New contributors should add their names to the `maint/CONTRIBUTORS.md` file.
Contributors are promoted to the `maint/MAINTAINERS.md` list following the
*NiPreps* governance model.
Governance information can be found in the [GOVERNANCE repository][link_governance_repository].
Before every release, a new [zenodo file][link_zenodo] will be generated.
The [update script][link_update_script] will also sort creators and contributors by
the relative size of their contributions, as provided by the `git-line-summary` utility
Expand Down Expand Up @@ -344,6 +351,8 @@ You're awesome. :wave::smiley:

[link_neurostars]: https://neurostars.org/tags/fmriprep

[link_governance_repository]: https://github.com/nipreps/GOVERNANCE

[link_git]: https://git-scm.com/
[link_handbook]: https://guides.github.com/introduction/git-handbook/
[link_swc_intro]: http://swcarpentry.github.io/git-novice/
Expand Down
12 changes: 10 additions & 2 deletions docs/community/members.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,15 @@ However, because of the scientific domain of *NiPreps*, the community features s
structure from *meritocracy models* to prescribe the order in the
authors list of [new papers about these tools](CONTRIBUTING.md#publications).

## Developers
## Historical note

The sections below provide a note on how contributions to the *NiPreps*
projects were historically acknowledged.
The scheme below has been substituted by a robuster strategy
that is described in the [contributor recognition](CONTRIBUTING.md#recognizing-contributions)
section.

### Developers

Developers are members of a wonderful team _driving the project_.
Names and contacts of all developers are included in the
Expand All @@ -13,7 +21,7 @@ Examples of steering activities that _drive the project_ are: actively participa
follow-up meetings, leading documentation sprints, helping in the design of the tool and definition of the roadmap,
providing resources (in the broad sense, including funding), code-review, etc.

## Contributors
### Contributors

Contributors enlisted in the
[`.maint/contributors.json` file](https://github.com/nipreps/fmriprep/blob/master/.maint/contributors.json) of each project
Expand Down