Community leaders (project stewards) and updating our Code of Conduct

[martinvonz]

Hi,

Our current code of conduct was part of the boilerplate I got from Google's Open-Source Programs Office. As you can see, I still haven't filled in names and emails for project stewards, since we simply don't have any project stewards yet. Since the community is getting larger, we should fix that.

Also, our code of conduct is based on Contributor Covenant Code of Conduct 1.4. There's now a version 2.1 of it. Assuming that there were good reasons for the changes made between those two versions, I'm leaning towards updating to the new version. Does that sound good? Any objections?

Does anyone volunteer to be a community leader (seems to be what's called a project steward in the 1.4 version)? I suspect we should ideally have at least two community leaders, so community members who have any issue with one of the community leaders can reach out to the other community leader. We also have the fallback of contacting [email protected], so maybe one is enough? I'm happy to hear thoughts from people who have more experience with this kind of stuff.

Thanks

[jaraco]

I'm willing to serve, but also happy to defer to anyone else interested. Presumably you'll be one of the leaders, Martin?

Who else is interested in being a project steward?

[avamsi]

Sounds good, feel free to consider me in that case (like Jason, I'm also happy to defer to someone else more active / interested).

[martinvonz]

@jaraco and @avamsi, it sounds like it would be you two who would be community leaders then. I just want to confirm that you're both okay with that. I'm not sure what the next step is other than adding your email addresses where the placeholder currently is.

[jaraco]

SGTM. I'll plan to draft a PR but feel free to beat me to it.

[arxanas]

If we need another person, I can volunteer; like @avamsi, I tend to do my GitHub (and email) management in batches, but maybe two people is still better than one?

[martinvonz]

Thanks! Yes, it just seems better to have more people (except for the usual "shared responsibility is no responsibility" problem, but I'm not concerned about that yet). I'll let @jaraco draft the PR.

[jaraco]

I'm working on this today, and I'm thinking it would be best to have a mailing list (google group) for the updated CoC. I've created [email protected]. I considered also creating a channel in Discord through which people could report concerns, but I'm unaware of a way to do that where only the community leaders and the reporter are privileged to the conversation.

[martinvonz]

Thanks!

I considered also creating a channel in Discord through which people could report concerns, but I'm unaware of a way to do that where only the community leaders and the reporter are privileged to the conversation.

Yes, I would think that it's not possible to create a channel that the admins (currently @spectral54 and I) could not spy on. So just a mailing list sounds good.

[jaraco]

PR at #2387.