eliminate express CoC handling

[UlisesGascon]

As discussed (ref) we need to ensure that the emails (coc-escalation@lists.openjsf.org and express-coc@lists.openjsf.org) are updated (cc: @wesleytodd )

[bjohansebas]

Should i open an issue in the CPC for the coc-escalation@lists.openjsf.org email? I don't see it referenced in the COC of CPC

[wesleytodd]

I can do the admin work on these, I think the missing piece here is deciding how we want to manage the membership. Do we need to have a team on them? Is it the TC? Do we need to do something about the spam? That sort of stuff.

[wesleytodd]

We are still waiting on a few things, namely if we want to remove our COC reporting for us at all. The proposal would be to rely fully on the OpenJS COC and follow their process without any additional process on our end. The folks on today's TC meeting were in support on this. If folks who were not able to attend are in support we can take next steps.

[bjohansebas]

I am in favor of using the OpenJS COC

[ctcpip]

The proposal would be to rely fully on the OpenJS COC and follow their process without any additional process on our end. The folks on today's TC meeting were in support on this.

this was reaffirmed at today's meeting, with Jean, Ulises, Sebastian, and I

so here is what we need to do to close this out:

• PR to remove express from CoC policy doc(s) in openjs CPC repo (ACTION: Chris)
• PRs to update our CoC (ACTION: Chris)
  • express org
  • pillarjs org (currently missing)
  • jshttp org (currently missing)
• ask Ben to delete the express CoC email list (express-coc@lists.openjsf.org) (ACTION: Chris)