You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 )
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.
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.
Reacted by Jean Burellier, Jon Church and Sebastian Beltran
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 TC meeting (2025-05-07), with Jean, Ulises, Sebastian, and I
reaffirmed again at TC meeting (2025-06-23) with Filip, Jean, Jon, Sebastian, Wes, 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)
Activity
bjohansebas commentedon Apr 12, 2025
Should i open an issue in the CPC for the
coc-escalation@lists.openjsf.orgemail? I don't see it referenced in the COC of CPCwesleytodd commentedon Apr 14, 2025
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 commentedon Apr 28, 2025
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 commentedon Apr 29, 2025
I am in favor of using the OpenJS COC
[-]Update CoC mailing lists[/-][+]eliminate express CoC handling[/+]ctcpip commentedon May 7, 2025
this was reaffirmed at TC meeting (2025-05-07), with Jean, Ulises, Sebastian, and I
reaffirmed again at TC meeting (2025-06-23) with Filip, Jean, Jon, Sebastian, Wes, and I
so here is what we need to do to close this out:
express-coc@lists.openjsf.org) (ACTION: Chris)docs: remove express from handling the CoC
bjohansebas commentedon Jul 25, 2025
openjs-foundation/cross-project-council#1521
expressjs/.github#34
jshttp/.github#6
pillarjs/.github#4
docs: remove express from handling the CoC (#1521)
docs: remove express from handling the CoC (#1521)