Create guidelines for CoC responsibilities for in-person OpenJS Foundation events

[hackygolucky]

Following up to expand the scope here in OpenJS from @benjamingr in Issue 367 from the Node.js repos

It is currently unclear who is supposed to enforce the Code of Conduct in OpenJS summits.

The moderation team is not empowered to enforce the CoC in summits. When we receive reports to [email protected] in the summit we work with summit organizers to resolve the issue.

So, let's reconcile this.

I have run quite a few conferences over the years, and executing on the Code of Conduct of any community is especially interesting and challenging when it comes to IRL events.

• You need a team of organizers and volunteers who are on the same page as to what to do in a scenario
• You need everyone attending, whether sponsors, organizers, or attendees, to agree to abiding by the CoC as part of the registration/RSVP process
• You need signage onsite and organizers bringing to attention the various ways that a person needing to report has the ability to do so and trust it will be handled responsibly.

The premise here that I've left implicit until now: when the LF Events team organizes, the LF Events team is responsible and does enforcement. When another part is organizing, those organizers are responsible.

In-person enforcement is especially tricky and can absolutely require police intervention unlike most of our online community management, which is why I am not recommending our Moderation Team members be responsible alone or be required to be at these events.

Recommended actions

• Meet with the LF Events team on recommendations and guidance for how their team handles reporting and resolution of reports, including handling legal enforcement.
• Document the 'teeth' of our Code of Conduct, which is the reporting handling(relevant parties notified when appropriate) as well as actually addressing the safety and management of the report parties through completion in a timely fashion.
• Post-report handling so Moderation at the CPC level has record of said reports for future consideration.
• Consider potential training for those who will be responsible for handling this at sanctioned Foundation events when LF Events is not onsite and coordinating.

[mcollina]

+1 to all. We should document all of this somewhere. Il giorno gio 6 giu 2019 alle 16:14 Tracy <[email protected]> ha scritto:

…

Following up to expand the scope here in OpenJS from @benjamingr <https://github.com/benjamingr> in Issue 367 from the Node.js repos <nodejs/admin#367> It is currently unclear who is supposed to enforce the Code of Conduct in OpenJS summits. The moderation team is not empowered to enforce the CoC in summits. When we receive reports to ***@***.*** in the summit we work with summit organizers to resolve the issue. So, let's reconcile this. I have run quite a few conferences over the years, and executing on the Code of Conduct of any community is especially interesting and challenging when it comes to IRL events. - You need a team of organizers and volunteers who are on the same page as to what to do in a scenario - You need everyone attending, whether sponsors, organizers, or attendees, to agree to abiding by the CoC as part of the registration/RSVP process - You need signage onsite and organizers bringing to attention the various ways that a person needing to report has the ability to do so and trust it will be handled responsibly. The premise here that I've left implicit until now: when the LF Events team organizes, the LF Events team is responsible and does enforcement. When another part is organizing, those organizers are responsible. In-person enforcement is especially tricky and can absolutely require police intervention unlike most of our online community management, which is why I am not recommending our Moderation Team members be responsible alone or be required to be at these events. Recommended actions - Meet with the LF Events team on recommendations and guidance for how their team handles reporting and resolution of reports, including handling legal enforcement. - Document the 'teeth' of our Code of Conduct, which is the reporting handling(relevant parties notified when appropriate) as well as actually addressing the safety and management of the report parties through completion in a timely fashion. - Post-report handling so Moderation at the CPC level has record of said reports for future consideration. - Consider potential training for those who will be responsible for handling this at sanctioned Foundation events when LF Events is not onsite and coordinating. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <https://github.com/openjs-foundation/cross-project-council/issues/196?email_source=notifications&email_token=AAAMXY5NVT6ZJFU3KKAXU33PZELSRA5CNFSM4HVCNFU2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GYBCNHA>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAAMXY2WD6XYWQUKURCK34LPZELSRANCNFSM4HVCNFUQ> .

[jorydotcom]

transferring this to the /code-of-conduct repo per the CPC meeting on 12 May