Node.js is adopting an official Discord server for the Community - CoC review is needed

ovflowd commented 1 month ago

Hey folks 👋 the Node.js project has been in talks about creating an official Discord community by repurposing an existing Discord community (details here: https://github.com/nodejs/admin/issues/872);

This issue requests that the Foundation review its CoC to verify that it follows its requirements. Since it will become an official space for an official OpenJS project, it is essential that their CoC fulfills our requirements.

Their current CoC also follows the Contributor Covenant 2.0 (based on Node.js's CoC but adapted for use on the Discord platform; since Discord is a communication app/platform, it is very different from GitHub.

Here is the diff: https://github.com/nodeiflux/documents/commit/a976e0836d337d53c8d64be9e9e7f42de6983675#diff-13936941ef00c85a7f555aa9ec176552f9965f0d2eeadd5ea95c541d5cd09bfb

I've requested @vcarl (the owner of said Discord community) to, if possible:

Update the report email address to report@nodejs.org
Update the base version of their Contributor Covenant to Contributor Covenant 2.1

I'd also like the CPC to review their CoC to ensure everything is good. Thank you!

ljharb commented 1 month ago

why are the changes needed? both the node slack and IRC have used node's code of conduct verbatim for many years without any issue.

ovflowd commented 1 month ago

why are the changes needed? both the node slack and IRC have used node's code of conduct verbatim for many years without any issue.

They are already using this CoC -- I want to retify that this CoC is also OK for us. It has also been working fine for them for a long period of years.

mhdawson commented 1 month ago

@ovflowd my understanding was that the existing moderation team was going to continue to moderate the Discord server with the Node.js moderation team being added for visibility.

In that context would it make sense to have a different report email alias (maybe report-discord@nodejs.org) that would include the discord moderation team members as well as the Node.js moderation team ?

ovflowd commented 1 month ago

@ovflowd my understanding was that the existing moderation team was going to continue to moderate the Discord server with the Node.js moderation team being added for visibility.

In that context would it make sense to have a different report email alias (maybe report-discord@nodejs.org) that would include the discord moderation team members as well as the Node.js moderation team ?

Yup, that's the idea. I already opened a PR on nodejs/email for that, if you'd like to check that 👀

PaulaPaul commented 3 weeks ago

No concerns - (this was discussed at the CPC call on 20 Aug) just wanted to share that it may be helpful to include the new Discord on the Node.js website and potentially the OpenJS Foundation website to help connet with the community.

tobie commented 3 weeks ago

Discussed in the CPC today. Waiting for follow-up from @ovflowd on the pending questions raised by the CPC in our last call:

What is the rationale for not using the foundation's CoC?
How official will this server be? If this is a verified server it implies that it is tied to the foundation and hence will need to adopt the foundation's CoC verbatim.

vcarl commented 3 weeks ago

What is the rationale for not using the foundation's CoC?

We are an independent moderation team that has demonstrated an ability to safely operate an online community space since 2018, we have not been asked to substantively alter our moderation processes. I found that the existing Node.js Code of Conduct was mostly in line with how we've been operating, but felt that our own CoC was important to distinguish that we are independently operated (though ultimately accountable to the foundation).

The changes I've made are:

changed the report email (I need to update this, this change sparked a conversation about what email to use)
elaborated on expectations for changes to behavior requested by moderators over time.
changed "temporary ban" to "timeout", as that's the name of a Discord feature for limiting participation
changed 'serious violation' to 'violation' in describing when a timeout may be used
changed 'permanent ban' to 'ban' in the Discord, which reflects the process we've used for appealing a ban historically
added details about who is eligible to appeal a ban
credited Node.js and Reactiflux as inspiration for the CoC

ljharb commented 3 weeks ago

@vcarl "permanent" doesn't mean "can't be appealed", it means "has no automatic expiry"

ovflowd commented 3 weeks ago

No concerns - (this was discussed at the CPC call on 20 Aug) just wanted to share that it may be helpful to include the new Discord on the Node.js website and potentially the OpenJS Foundation website to help connet with the community.

It will be done at the moment we release it!

PaulaPaul commented 1 week ago

@joesepi will reach out to @ovflowd to chat (Paula to sit in for education/help if appropriate)

tobie commented 1 week ago

CPC call update: discussed this today. Want to find a pathway forward. @joesepi to follow-up with @ovflowd.

openjs-foundation / cross-project-council

Node.js is adopting an official Discord server for the Community - CoC review is needed #1347