<div dir="ltr"><div class="gmail-moz-cite-prefix">Alex, <br>
<br>
While I'm happy to see that the CoC is receiving more input, perhaps you
are not aware that this whole process has been going on for over a
year, discussed transparently on the list with updates at the subsequent
RIPE Meetings. The statistics on the process, edits, participation are
in the slide deck that the TF presented on Thursday. <br>
<br>
The community HAS come up with a CoC, we've been working on it for
awhile. We are not asking for the entire thing to be scrapped - that
would be a huge setback to the community - and I think it's becoming
more evident that we need a strong mechanism in place to protect people
*now*. <br>
<br>
Did you watch the TF update at RIPE 78? Did you see the statistic about
how many people reported being harassed - 38% - that's almost 4 in 10
people. A handful of people have been brave enough to come forward with
their stories - which is absolutely terrifying to do, I may add - but
then think about how many people haven't come forward. <br>
<br>
The CoC is not set in stone. We have repeatedly said this - this is new
for the community and it is likely that we will discover that some
things need to be tweaked. <br>
<br>
The last version of the document was already heavily reviewed by RIPE
NCC Legal (see my previous messages on the diversity TF for that) - but
there was confusion on the process because this document is different
than anything that's come before and so we sought clarity from Hans
Petter before moving forward. <br>
<br>
You are essentially making suggestions for things that we have already been doing. <br>
<br>
I believe - and many others have already voiced this - that there is
strong support for this CoC. Sure, finessing and clarifying parts here
and there, but I strongly disagree with your suggestions below. <br>
<br>
Amanda <br>
<br>
On 20/10/2019 22:31, Alex de Joode wrote:<br>
</div>
<blockquote type="cite">
<br>
<div class="gmail-x-axi-signature"><br><div class="gmail-x-axi-signature" style="font-size:10pt">-- <div>IDGARA | Alex de Joode | +31651108221</div></div></div>
<br>
<div><hr><b>Subject:</b> Re: [ripe-list] CoC and the PDP<br><b>From:</b> Alex de Joode <<a href="mailto:adejoode@idgara.nl">adejoode@idgara.nl</a>><br><b>Date:</b> Sun, 20-10-2019 22h 29min<br><b>To:</b> Erik Bais <<a href="mailto:ebais@a2b-internet.com">ebais@a2b-internet.com</a>><br><b>Cc:</b> Leslie <<a href="mailto:geekgirl@gmail.com">geekgirl@gmail.com</a>>, "Sascha Luck [ml]" <<a href="mailto:lists-ripe@c4inet.net">lists-ripe@c4inet.net</a>>, RIPE List <<a href="mailto:ripe-list@ripe.net">ripe-list@ripe.net</a>><br><br><div><div style="font-family:"Source Sans Pro",sans-serif;font-size:10pt">On Sun, 20-10-2019 19h 05min, Erik Bais <<a href="mailto:ebais@a2b-internet.com">ebais@a2b-internet.com</a>> wrote:<br><blockquote style="border-left:1px solid rgb(204,204,204);margin-left:10px;padding-left:10px"><div size="">Hi,<br><br>I've been in the RIPE community and in the Dutch NOG community for quite a long time ... <br>[..]<br>On the topic back to the CoC ... I understand the requirement and urge us to proceed with clear version to move forwards. <br><br>One
of the items I would like to address is that we have in our community
quite some people that may be on the autism spectrum or on the edge of
it .. <br>They might have some issues with deciding on what is socially
acceptable or what the consequences are of certain text in the CoC .. <br>They might not be able to decide, based on the text what is acceptable behaviour .. but not on a predatory way .. <br><br>I
would strongly suggest that we try to include them as much in these
discussions and perhaps even better, ask some if they would be willing
to proof read the document and provide feedback on what they think based
on the CoC. <br><br>If their reaction is going to be, I don’t
understand the consequences of the document and I will just not give a
hand or speak to someone when I'm at the RIPE meeting, or not come at
all, we may need to look at the wording. <br><br>On the topic of this
should go through the PDP ? ... I think that the RIPE NCC should have a
strong CoC ( that should also include the trainings and member lunches
btw, not only the meetings.. )<br>The community can provide input, but
as the official organiser, the NCC MUST (in my opinion) take a legal
liability point here and draw the line of what is acceptable behaviour
.. <br><br>I think the NCC MUST take a lead here, with the input from
the community and have the final say here and implement the new CoC
asap. <br><br>Regards,<br>Erik Bais <br></div></blockquote><div size=""><br></div><div size="">I
know from stories of (former) co-workers who attended the same event(s)
as I did, they did not feel comfortable and left the venue early. (me
wondering where they were). This makes they were not particularly
thrilled to join the next venue. So this issue is real issue, and it
needs resolving.</div><div size=""><br></div><div size="">Question is, how do we solve it, or better how do we approach this as a problem.</div><div size=""><br></div><div size="">A
good Code of Conduct clearly spells out what behaviour is
(un)acceptable, and also gives clear guidelines on how to report a
(percieved) incident. The current CoC lacks this. It's reads more as an
activist pamphlet and an instruction guide to the "enforcement team". It
also totally fails to protect the rights of the 'accused' (yes they
have rights) and does not at all provide for 'due process'.</div><div size=""><br></div><div size="">Given
the a-typical nature of tech conferences with, as Erik already pointed
out, an over-representation of people who boarder in the spectrum, I
feel only a CoC will not do.</div><div size=""><span style="font-size:10pt"><br></span></div><div size=""><span style="font-size:10pt">Therefor I suggest the following:</span></div><div size=""><ol id="ext-gen7110" start="1"><li><span style="font-size:10pt">The community should come up with a specification for a CoC (what needs to be in it)</span></li><li><span style="font-size:10pt">RIPE NCC come up with a text</span></li><li>The
community and RIPE NCC come up with mitigating actions (akin to
'security by design'), are there ways to organise RIPE meeting this
abuse/behaviour cannot happen.</li><li>Maybe investigate into introducing an 'Ombudsman'-like function.</li></ol></div><div size=""><div class="gmail-x-axi-signature" style="font-size:13.3333px"><div class="gmail-x-axi-signature" style="font-size:10pt">-- <div>IDGARA | Alex de Joode | +31651108221</div></div></div></div></div></div></div>
</blockquote>
<p><br>
</p></div>