Add Code of Conduct #1
Conversation
| ## Our Pledge | ||
|
|
||
| In the interest of fostering an open and welcoming environment, we as | ||
| contributors and maintainers pledge to making participation in our projects and |
There was a problem hiding this comment.
Pluralized projects.
|
|
||
| Instances of abusive, harassing, or otherwise unacceptable behavior may be | ||
| reported by contacting the maintainer of the relevant project, or members of the | ||
| project team designated in a project-level code of conduct. |
There was a problem hiding this comment.
In other projects, this sentence lists specific points of contact. I don't know if we want to establish a lab-wide ombud, or require each project to specifically designate a person.
I personally would prefer that there always be a backup. On fMRIPrep, we have both Oscar and me, which means that each of us can serve as a contact if someone believes the other has violated the CoC. For projects like FitLins which are mostly one person (me), it's not clear what the check on their (my) abuses would be.
There was a problem hiding this comment.
I can offer to be a contact where is it appropriate. The most relevant to me (if we are splitting up by project) would be BIDS and OpenNeuro. I can take on the responsibility of other projects.
This is directly lifted from fMRIPrep, with changes I will note below. If there is another preferred source, I can adapt that, too.
The justification for fMRIPrep is that, as our project that has engaged the most outside contributions, including from several people who have thought significantly about CoCs and contributing guides, this will have received more scrutiny than the others.
cc @poldrack @poldracklab/owners