<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=Windows-1252"> <meta name="Generator" content="Microsoft Exchange Server"> <style></style> </head> <body> <div> <div dir="ltr"> <div dir="ltr" style="color:rgb(33,33,33); background-color:rgb(255,255,255); text-align:left"> Mirjam,</div> <div dir="ltr" style="color:rgb(33,33,33); background-color:rgb(255,255,255); text-align:left"> <br> </div> <div dir="ltr" style="color:rgb(33,33,33); background-color:rgb(255,255,255); text-align:left"> Ok, so, then there is confusion, and, if you could help, what can they do?</div> <div dir="ltr" style="color:rgb(33,33,33); background-color:rgb(255,255,255); text-align:left"> <br> </div> <div dir="ltr" style="color:rgb(33,33,33); background-color:rgb(255,255,255); text-align:left"> I can edit and re-upload.</div> <div dir="ltr" style="color:rgb(33,33,33); background-color:rgb(255,255,255); text-align:left"> <br> </div> <div dir="ltr" style="color:rgb(33,33,33); background-color:rgb(255,255,255); text-align:left"> Brian</div> <div id="x_ms-outlook-mobile-signature"> <div><br> </div> Brian Nisbet,<br> Service Operations Manager, HEAnet</div> </div> <hr tabindex="-1" style="display:inline-block; width:98%"> <div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> Mirjam Kuehne <mir@ripe.net><br> <b>Sent:</b> Thursday, October 17, 2019 3:22:58 PM<br> <b>To:</b> Brian Nisbet <brian.nisbet@heanet.ie>; diversity@ripe.net <diversity@ripe.net><br> <b>Subject:</b> Re: [diversity] Community Plenary Presentation</font> <div> </div> </div> </div> <font size="2"><span style="font-size:11pt;"> <div class="PlainText"><br> Hi,<br> <br> On slides 5 in the speaker notes (which I assume will be published?) it<br> says:<br> <br> ""Trusted contacts will emotionally support you, but absolutely can not<br> take any other action. Effectively, our CoC creates a false sense of<br> security. So our community’s current status is: if you get severely<br> harassed at the party, which is a thing that happens, we can say how<br> sorry we are for you, and tomorrow and next year your assailant will be<br> sitting next to you. There is a CoC, but there is no accountability or<br> consequences.”"<br> <br> This is not true and as I pointed out earlier on this list the Trusted<br> contacts (and the RIPE Chair) have taken action in the past. I agree<br> that the responsibilities of the Trusted Contacts may not be well<br> understood or documented, but stating it like in the text above is wrong.<br> <br> Mirjam<br> <br> <br> On 17/10/2019 14:58, Brian Nisbet wrote:<br> > Folks,<br> > <br> > 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.<br> > <br> > 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.<br> > <br> > I know I and others present in Rotterdam have got some really good further feedback.<br> > <br> > And, of course, as with all things, whatever CoC we have is never set in stone, it's always changeable as situations change.<br> > <br> > Thanks for everyone's input on this so far!<br> > <br> > Brian<br> > <br> > Brian Nisbet<br> > Service Operations Manager<br> > HEAnet CLG, Ireland's National Education and Research Network<br> > 1st Floor, 5 George's Dock, IFSC, Dublin D01 X8N7, Ireland<br> > +35316609040 brian.nisbet@heanet.ie <a href="http://www.heanet.ie">www.heanet.ie</a><br> > Registered in Ireland, No. 275301. CRA No. 20036270<br> > <br> > <br> > _______________________________________________<br> > diversity mailing list<br> > diversity@ripe.net<br> > <a href="https://mailman.ripe.net/">https://mailman.ripe.net/</a><br> > <br> <br> </div> </span></font> </body> </html>