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. "On 17/10/2019 15:33, Sasha Romijn wrote:
I am definitely confused, because the text as written in the notes is precisely how I heard it multiple times from at least one of the other trusted contacts.
SashaMirjam,
Ok, so, then there is confusion, and, if you could help, what can they do?
I can edit and re-upload.
BrianBrian Nisbet,
Service Operations Manager, HEAnet
From: Mirjam Kuehne <mir@ripe.net>
Sent: Thursday, October 17, 2019 3:22:58 PM
To: Brian Nisbet <brian.nisbet@heanet.ie>; diversity@ripe.net <diversity@ripe.net>
Subject: Re: [diversity] Community Plenary Presentation
Hi,
On slides 5 in the speaker notes (which I assume will be published?) it
says:
""Trusted contacts will emotionally support you, but absolutely can not
take any other action. Effectively, our CoC creates a false sense of
security. So our community’s current status is: if you get severely
harassed at the party, which is a thing that happens, we can say how
sorry we are for you, and tomorrow and next year your assailant will be
sitting next to you. There is a CoC, but there is no accountability or
consequences.”"
This is not true and as I pointed out earlier on this list the Trusted
contacts (and the RIPE Chair) have taken action in the past. I agree
that the responsibilities of the Trusted Contacts may not be well
understood or documented, but stating it like in the text above is wrong.
Mirjam
On 17/10/2019 14:58, Brian Nisbet wrote:
> Folks,
>
> Amanda, Denesh, Sasha and I have put this presentation together for the community plenary this afternoon. It is forthright, but we definitely feel that it needs to be so.
>
> We are going to make it clear that we're still accepting comments on v3.0, but also still looking at having this in place for RIPE 80 if at all possible.
>
> I know I and others present in Rotterdam have got some really good further feedback.
>
> And, of course, as with all things, whatever CoC we have is never set in stone, it's always changeable as situations change.
>
> Thanks for everyone's input on this so far!
>
> Brian
>
> Brian Nisbet
> Service Operations Manager
> HEAnet CLG, Ireland's National Education and Research Network
> 1st Floor, 5 George's Dock, IFSC, Dublin D01 X8N7, Ireland
> +35316609040 brian.nisbet@heanet.ie www.heanet.ie
> Registered in Ireland, No. 275301. CRA No. 20036270
>
>
> _______________________________________________
> diversity mailing list
> diversity@ripe.net
> https://lists.ripe.net/mailman/listinfo/diversity
>
_______________________________________________
diversity mailing list
diversity@ripe.net
https://lists.ripe.net/mailman/listinfo/diversity
_______________________________________________ diversity mailing list diversity@ripe.net https://lists.ripe.net/mailman/listinfo/diversity