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/diversity@ripe.net/
[diversity] Draft CoC and response guide
- Previous message (by thread): [diversity] Draft CoC and response guide
- Next message (by thread): [diversity] Draft CoC and response guide
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Vesna Manojlovic
BECHA at ripe.net
Thu Apr 11 11:28:55 CEST 2019
Hi all, Sasha, thanks for the comprehensive drafts!! This is my input, speaking as an individual member of the community, and based on my personal experience, not as RIPE NCC staff: On 05/04/2019 13:31, Sasha Romijn wrote: > I went with Google docs for now, as it’s quite accessible. You can leave comments and suggest changes, and we can discuss broader topics on the mailing list. There are a few parts about structure still to be filled in, but let’s start here. My comments are mostly about the "ordering" of the parts of the document; so I prefer to send my suggestions to the list, rather then reshuffling the whole online document. 1. I think that the most important parts are *practical* instructions to the person who should be reporting the incident, and therefore, I would like to see that these sections are *moved up*: (just after "Principles") * What to do in case of violations? * Guidelines for reporting incidents * Other assistance * (& Reporting and contact information, which, IMO, should be folded into "Other assistance") The other sections can follow later: - Where does it apply (folding in "Sponsors, exhibitors..) - What can happen - (And special case) "reports against team member" 2. (in both documents) I believe that in the "resolutions" or "Actions" that can be taken, one is missing -- giving a warning -- and the others need to be given in a different order of importance: from the most reassuring (or frequent) to the least -- and therefore I have moved the "no action" to the bottom of the list, in the document itself. 3. The document "guidelines for response" should add: * who is in the team? how are they chosen? * the NAMING of the "team member", "contact", "staff member" etc should be consistent - it's confusing who-is-doing-what * the "sections" can use some reshuffling, e.g. "conflicts of interest" can be moved the the back of the document... 4. What is the role of, or relation to, the existing "trusted contacts"? (disclaimer - I am one of the "trusted contacts" now, and so I am directly involved in handling reports right now) I see several outcomes - that this role is considered as one of the "other assistance" options; that it disappears; or that it is included in the CoC-enforcement-Team... and I am open to all these, or any new, outcomes. 5. Finally, we will - practically - need a short version too, for the printing, one reference web page, etc -- with links to longer versions. Regards, Vesna
- Previous message (by thread): [diversity] Draft CoC and response guide
- Next message (by thread): [diversity] Draft CoC and response guide
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]