This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[diversity] [Ext] Re: *draft* CoC Team doc
- Previous message (by thread): [diversity] [Ext] Re: *draft* CoC Team doc
- Next message (by thread): [diversity] *draft* CoC Team doc -> training & workshops
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Rob Evans
Rob.Evans at jisc.ac.uk
Fri Aug 30 16:45:28 CEST 2019
Hi, >> Perhaps it is of value to run a simulate instance of violation (as a >> CoC training game) and try to handle the situation or even try to >> enforce CoC to identify areas of possible improvement. In a few cases >> I've noticed [in small conferences] that the lack of experience from the >> organizers, even with a CoC in hand, it was hard to handle such >> incidents. And some times aggression can escalate conflict instead of >> reduce it. > This is a really good idea. I think we should also ensure that when we communicate this document again, we make it clear that this is a *new* process and we will need to be mindful of feedback and tweak the process once its being used should something not be working as it should. Just to add to this, I would say it is essential. The RIPE NCC arranged training for the Trusted Contacts, whose role is far less “hands on,” and part of that was going through reporting scenarios with an actor. It was, in my mind, a critical part of training. Cheers, Rob
- Previous message (by thread): [diversity] [Ext] Re: *draft* CoC Team doc
- Next message (by thread): [diversity] *draft* CoC Team doc -> training & workshops
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]