Create a merged contributor file for the organisation

[RayStick]

References #59

Draft python code in this branch - I will get feedback on how useful this is before proceeding. Some initial thoughts below:

• We need a non-manual way to keep this file up to date: docs/community/team.md. This is what the Python code in this branch aims to do
• Even better would be to make a workflow that triggers the running of this python code every time a contributor file changes in any repo of the organisation. But I don't know how workflows work across repos, only within
• Also consider a merged Zenodo file (e.g. one for phys2bids)?

Proposed Changes

Change Type

• bugfix
• refactoring
• infrastructure
• documentation
• other

Checklist before review

• I added everything I wanted to add to this PR.
• [Documentation only] I built the docs locally.
• My contribution is harmonious with the rest of the code: I'm not introducing repetitions.
• My code respects the adopted style, especially linting conventions.
• The title of this PR is explanatory on its own, enough to be understood as part of a changelog.
• I added or indicated the right labels.

• I added information regarding the timeline of completion for this PR.

• Please, comment on my PR while it's a draft and give me feedback on the development!

[smoia]

THIS!

Yes, please, automation is what we need.

I'm thinking convoluted bad ideas: we could think about using the way of the submodules, checking if there are any workflows to keep an eye on changes in submodules repos, and if there are, add all the other repos as submodules and trigger actions in that way.
Another alternative is checking if all-contributor can cross-post across different repos

[RayStick]

we could think about using the way of the submodules, checking if there are any workflows to keep an eye on changes in submodules repos, and if there are, add all the other repos as submodules and trigger actions in that way.

hmm git submodules could be a solution, but I worry a bit overkill? I have no experience with them though, so might be worth a look

Another alternative is checking if all-contributor can cross-post across different repos

I don't think it can, with how it works now.
Seems like a common issue: all-contributors/all-contributors#416
Found this: https://github.com/marketplace/actions/merge-all-contributors (not that supported though, so we might want to just use for inspiration?)