Skip to content
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.

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

MAINT: Adopt new NiPreps' governance model #174

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

oesteban
Copy link
Member

@oesteban oesteban commented Aug 18, 2021

This is an example of what NiPreps components would need to change with the current draft of governance at https://github.com/nipreps/GOVERNANCE

It would be nice to have this merged before the upcoming roundup https://github.com/orgs/nipreps/discussions/28#discussion-5114946.

Please check where I have listed your names and suggest corrections.

cc/ @edickie @arokem @josephmje

@pep8speaks
Copy link

Hello @oesteban, thank you for submitting the Pull Request!

Line 124:24: E741 ambiguous variable name 'l'

To test for issues locally, pip install flake8 and then run flake8 dmriprep.

@arokem
Copy link
Collaborator

arokem commented Aug 20, 2021

Following conversation this morning, I believe that this PR should be significantly amended to include just a brief pointer to the centralized GOVERNANCE repo rather than including all of this text.

@arokem
Copy link
Collaborator

arokem commented Aug 20, 2021

And by "conversation this morning", I mean this: https://nipy.discourse.group/t/task-force-working-group-governance-model-documentation/42/7

@oesteban oesteban marked this pull request as ready for review April 21, 2023 14:13
@oesteban oesteban changed the title MAINT: Adopt new NiPreps' governance model [example] MAINT: Adopt new NiPreps' governance model Apr 21, 2023
@arokem
Copy link
Collaborator

arokem commented Apr 21, 2023

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants