<html><head><style id="axi-htmleditor-style" type="text/css">p { margin: 0px; }</style></head><body dir="" style="font-size: 10pt; font-family: "Source Sans Pro", sans-serif; background-image: none; background-repeat: repeat; background-attachment: fixed;"><br><div class="x-axi-signature"><br><div class="x-axi-signature" style="; font-size: 10pt; font-family: " source="" sans="" pro",="" sans-serif;"="">-- <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 <adejoode@idgara.nl><br><b>Date:</b> Sun, 20-10-2019 22h 29min<br><b>To:</b> Erik Bais <ebais@a2b-internet.com><br><b>Cc:</b> Leslie <geekgirl@gmail.com>, "Sascha Luck [ml]" <lists-ripe@c4inet.net>, RIPE List <ripe-list@ripe.net><br><br><div><div style="font-family: 'Source Sans Pro', sans-serif; font-size: 10pt;"><style id="axi-htmleditor-style" type="text/css">p { margin: 0px; }</style>On Sun, 20-10-2019 19h 05min, Erik Bais <ebais@a2b-internet.com> wrote:<br><blockquote style="border-left: 1px solid rgb(204, 204, 204); margin-left: 10px; padding-left: 10px;"><div style="font-family: " source="" sans="" pro="" serif="" font="font" size="" pt="">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 style="font-family: " source="" sans="" pro="" serif="" font="font" size="" pt=""><br></div><div style="font-family: " source="" sans="" pro="" serif="" font="font" size="" pt="">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 style="font-family: " source="" sans="" pro="" serif="" font="font" size="" pt=""><br></div><div style="font-family: " source="" sans="" pro="" serif="" font="font" size="" pt="">Question is, how do we solve it, or better how do we approach this as a problem.</div><div style="font-family: " source="" sans="" pro="" serif="" font="font" size="" pt=""><br></div><div style="font-family: " source="" sans="" pro="" serif="" font="font" size="" pt="">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 style="font-family: " source="" sans="" pro="" serif="" font="font" size="" pt=""><br></div><div style="font-family: " source="" sans="" pro="" serif="" font="font" size="" pt="">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 style="font-family: " source="" sans="" pro="" serif="" font="font" size="" pt=""><span style="font-size: 10pt;"><br></span></div><div style="font-family: " source="" sans="" pro="" serif="" font="font" size="" pt=""><span style="font-size: 10pt;">Therefor I suggest the following:</span></div><div style="font-family: " source="" sans="" pro="" serif="" font="font" size="" pt=""><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 style="font-family: " source="" sans="" pro="" serif="" font="font" size="" pt=""><div class="x-axi-signature" style="font-size: 13.3333px;"><div class="x-axi-signature" source="" sans="" pro="" serif="" style="font-size: 10pt;">-- <div>IDGARA | Alex de Joode | +31651108221</div></div></div></div></div></div></div></body></html>