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

[joss] add code of conduct #315

Closed
jdkent opened this issue Dec 7, 2019 · 6 comments
Closed

[joss] add code of conduct #315

jdkent opened this issue Dec 7, 2019 · 6 comments

Comments

@jdkent
Copy link

jdkent commented Dec 7, 2019

Here are a couple examples for a code of conduct

@sappelhoff
Copy link
Member

Thanks @jdkent

I think we could use the CoC of MNE-Python (see here) ... WDYT @jasmainak @agramfort ?

Perhaps we can do it using the GitHub organization feature? That way, a single CoC file would be shared for all MNE repositories. cc @larsoner

You can add default community health files for your organization to the root of a public repository called .github that is owned by the organization. GitHub will use and display default files for any public repository in the organization that does not have its own file of that type in any of the following places ...

see here:

https://help.github.com/en/github/building-a-strong-community/creating-a-default-community-health-file-for-your-organization

@agramfort
Copy link
Member

agramfort commented Dec 7, 2019 via email

@larsoner
Copy link
Member

larsoner commented Dec 7, 2019

I like the organization-wide one. I think we should check that the MNE-CPP folks are okay with ours. Can you open an issue on their GitHub repo to ask?

@sappelhoff
Copy link
Member

@larsoner we got approval from the MNE-CPP folks in mne-tools/mne-cpp#418 (comment).

Could you open the new .github repo and put the MNE-Python Code of Conduct there, please? I don't think I have the required rights for this.

@larsoner
Copy link
Member

larsoner commented Dec 9, 2019

@sappelhoff
Copy link
Member

awesome, thanks a lot @larsoner and @jdkent for bringing up this point.

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

No branches or pull requests

4 participants