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] NVC online course : Social Change: Supporting Diversity, Equity, and Inclusion
- Next message (by thread): [diversity] Draft CoC and response guide
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sasha Romijn
sasha at mxsasha.eu
Thu May 9 14:22:18 CEST 2019
Hi all, I merged all suggestions made in Google Docs, with some text tweaks where needed to make everything fit. For comments made on the list here, see below - I merged most of them. Thanks for all the feedback! As far as I’m concerned, the document is now ready to be presented to others, unless any other members would like to comment. Sasha > One question about reporting. I have read of several cases where after > reporting an incident, event organizers had the reporter meet with the > people they are reporting about. Entirely agree. There was something in there about this, but I clarified it. > 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”) Agreed and done. Folded Reporting and Contact information into the Guidelines for reporting, because it only had a single paragraph now. > 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. Agreed, already merged. > 3. The document "guidelines for response" should add: > > * who is in the team? how are they chosen? This is a discussion we still need to have, I think, as noted in my other mail. > * the NAMING of the "team member", "contact", "staff member" etc should > be consistent - it's confusing who-is-doing-what Agreed, I think this is sufficiently clarified now. > * the "sections" can use some reshuffling, e.g. "conflicts of interest" > can be moved the the back of the document… I kind of like it where it is, as it is an important step in the process. Unresolved conflicts of interest can erode trust in the process. > In the beginning listing > "... moderators, organisers, and volunteers." is there a reason it > doesnt end in an "open ended": moderators, organisers, volunteers, and > others. I think that looks a bit strange grammatically, in the context of that paragraph. I did change “including” to “including, but not limited to” - I think that covers it. > So I suggest changing "Be welcoming" to "Be welcoming and patient” We seem to have it in the first bullet point of that part already. Not sure when we added that, but it’s in there now. Sasha
- Previous message (by thread): [diversity] NVC online course : Social Change: Supporting Diversity, Equity, and Inclusion
- Next message (by thread): [diversity] Draft CoC and response guide
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]