Define a Code of Conduct team and have a dedicated email for it

[choldgraf]

Context

As a part of #3, I noticed that in our Code of Conduct we do not list who responds to Code of Conduct reports, and who monitors the email that is listed there.

It's important to be explicit about who monitors Code of Conduct reports, so that people that might make these reports know what to expect. Moreover, it's important that the teams that monitor CoC channels have expertise in handling matters like this, as they can be quite sensitive.

Finally, I noted that the contact email there is [email protected], which is a single-user account. We could share the emails to this account between team members, but it'll be easier to make it explicit who has access to the account, and to add / remove people, if we use a Group account for this.

Note that if we successfully incorporate as a Jupyter sub-project, we'll inherit Jupyter's Code of Conduct processes, which are similar to what I've described above.

Proposal

Unless others object, I'll plan to do the following:

• Create a Google Group that is dedicated for CoC reports
• Make it possible to message the group from the outside, but messages are only visible to group members.
• Put the Sloan Project Principal Investigators as members of this group
• Re-direct our CoC guidelines to report to this group
• Add a PR to our team compass to make the CoC more visible and to make this process explicit

In the future, there are a few other things that we need to do to improve this process, but we can leave that to a follow-up:

• Define a more "formal" CoC process
• Define a team of people with formal training in how to handle these issues
• Make it possible to submit reports anonymously
• Make it possible to submit reports outside of this process, in case people don't want the readers of the account to see the report.

There are two PRs related to this one:

• Update Code of Conduct process meta#770
• Update Code of Conduct to use a dedicated email .github#29

This is also related to:

• part of [Proposal] Community Strategy for this organization meta#493

References

There's a ton of information out there about CoCs, but here are two useful ones:

• https://opensource.guide/code-of-conduct/
• https://frameshiftconsulting.com/resources/code-of-conduct-book/
• https://projectinclude.org/writing_cocs

[rowanc1]

Thanks for your work here @choldgraf, I reviewed the two PRs linked and both look great. Especially acknowledging the current state in the code of conduct, our progress towards the community goals that you have outlined, as well opening various documented community communication lines. I think it makes a lot of sense to bootstrap with the Sloan Project Principal Investigators as initial members of this group as you suggest.

[welcome]

Thanks for opening your first issue here! Engagement like this is essential for open source projects! 🤗

If you haven't done so already, check out EBP's Code of Conduct. Also, please try to follow the issue template as it helps other community members to contribute more effectively.

If your issue is a feature request, others may react to it, to raise its prominence (see Feature Voting).

Welcome to the EBP community! 🎉