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] RIPE Code of Conduct 2.0
- Previous message (by thread): [diversity] RIPE Code of Conduct 2.0
- Next message (by thread): [diversity] RIPE Code of Conduct 2.0
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Daniel Karrenberg
dfk at ripe.net
Fri Jun 14 07:09:20 CEST 2019
Mirjam, Vesna, Rob, thank you very much for picking this up. I appreciate it very much because this is something all of you did not originally sign up for. Typing 'code of conduct transparency report' into your favourite search engine will give you some examples. I liked https://symfony.com/blog/symfony-code-of-conduct-transparency-report-2018 There are quite a number from djangocon where I assume much of the text in the current draft originates. Some of these are by-the-way also quite educational about what the current draft can lead to, like: "One of the lightning talks contained unfortunate phrasing directed towards one of the attendees. Video from that lightning talk won’t be published online." No mention of who decided this and how. Was it voluntary? This is the kind of censorship that we as a community should not want. Daniel On 13/06/2019 12:00, Rob Evans wrote: > Hi all, > > Picking up on this particular point. > >> I strongly suspect that the current scope of the trusted contacts is >> lacking; so we have no disagreement there at all. However we have not >> seen any sort of 'transparency report' from the trusted contacts that >> would allow for a good analysis. We need to hear from the trusted >> contacts and base our discussion on what they have to report and what >> they might suggest. > > As Trusted Contacts, our primary responsibility is confidentiality of > the report to us. Our training was as a "vertrouwenspersoon," although > fortunately for me that was the only part of the training that took > place in Dutch. > > This makes the production of reports somewhat difficult as above all we > do not want those who have reported an issue to us to feel they could be > identified through that report -- or that in future they do not report > an issue for fear of being identified (the simple act of writing down > the report is even something to consider). > > We do report back to Hans Petter, and we are currently working on a > report but with the figures quite abstracted as a result. If others > that have been involved in similar work elsewhere have examples of the > level of public report we could be producing, they would be welcome. So > far, my suggestion is that it is no more detailed than something along > the lines of the following categories: > > - "In-meeting behaviour"; > - "Behaviour at social events"; > - "Mailing list behaviour" > > The number of reports we do receive is, as that report will show, quite low. > > > Cheers, > Rob > >
- Previous message (by thread): [diversity] RIPE Code of Conduct 2.0
- Next message (by thread): [diversity] RIPE Code of Conduct 2.0
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]