<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">Hi Hans Petter, <br>
      <br>
      On 19/10/2019 23:50, Hans Petter Holen wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAJPAtr0s0s-EefiPJiL5GtZo-JX3oE_GqBDY7stvqdf94VG_sQ@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=utf-8">
      <div dir="auto">Thanks for the hard work with the next version of
        the code of conduct. Special thanks to Brian and Sahsa for
        presenting the work.</div>
      <div dir="auto"><br>
      </div>
      <div dir="auto">Now the final challenge is to establish consensus.
        This means identifying remaining issues and address them. (This
        does not mean that all can be solved, but we should aim to
        document why they are not solved at this point.)</div>
      <div dir="auto"><br>
      </div>
      <div dir="auto">I have done a quick analisys of the differences
        between the existing code of conduct and the new code of
        conduct.</div>
      <div dir="auto">
        <div><a
href="https://www.ripe.net/participate/meetings/ripe-meetings/ripe-meeting-code-of-conduct"
            moz-do-not-send="true">https://www.ripe.net/participate/meetings/ripe-meetings/ripe-meeting-code-of-conduct</a></div>
      </div>
      <div dir="auto">and </div>
      <div dir="auto">
        <div><a
href="https://www.ripe.net/participate/meetings/ripe-meetings/ripe-meeting-code-of-conduct-3-0-draft"
            moz-do-not-send="true">https://www.ripe.net/participate/meetings/ripe-meetings/ripe-meeting-code-of-conduct-3-0-draft</a></div>
        <br>
      </div>
      <div dir="auto">The main text: «<span
          style="color:rgb(51,51,51);font-family:"Open
Sans",Helvetica,Arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)"> For
          over a quarter </span><span class="highlightedSearchTerm"
style="box-sizing:border-box;background-color:rgb(255,255,170);color:rgb(51,51,51);font-family:"Open
          Sans",Helvetica,Arial,sans-serif;font-size:13px">of</span><span
          style="color:rgb(51,51,51);font-family:"Open
Sans",Helvetica,Arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)"> a
          century, the </span><span class="ripe-glossary-popover"
          title=""
style="box-sizing:border-box;border-bottom-width:1px;border-bottom-style:dotted;border-bottom-color:rgb(204,204,204);color:rgb(51,51,51);font-family:"Open
          Sans",Helvetica,Arial,sans-serif;font-size:13px">RIPE
          community</span><span
          style="color:rgb(51,51,51);font-family:"Open
Sans",Helvetica,Arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">'s
          strength comes from its breadth </span><span
          class="highlightedSearchTerm"
style="box-sizing:border-box;background-color:rgb(255,255,170);color:rgb(51,51,51);font-family:"Open
          Sans",Helvetica,Arial,sans-serif;font-size:13px">of</span><span
          style="color:rgb(51,51,51);font-family:"Open
Sans",Helvetica,Arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)"> experience,
          diversity </span><span class="highlightedSearchTerm"
style="box-sizing:border-box;background-color:rgb(255,255,170);color:rgb(51,51,51);font-family:"Open
          Sans",Helvetica,Arial,sans-serif;font-size:13px">of</span><span
          style="color:rgb(51,51,51);font-family:"Open
Sans",Helvetica,Arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)"> views,
          and an open, respectful exchange </span><span
          class="highlightedSearchTerm"
style="box-sizing:border-box;background-color:rgb(255,255,170);color:rgb(51,51,51);font-family:"Open
          Sans",Helvetica,Arial,sans-serif;font-size:13px">of</span><span
          style="color:rgb(51,51,51);font-family:"Open
Sans",Helvetica,Arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)"> ideas
          – values that we want all </span><span
          class="highlightedSearchTerm"
style="box-sizing:border-box;background-color:rgb(255,255,170);color:rgb(51,51,51);font-family:"Open
          Sans",Helvetica,Arial,sans-serif;font-size:13px">of</span><span
          style="color:rgb(51,51,51);font-family:"Open
Sans",Helvetica,Arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)"> our
          RIPE Meeting attendees to uphold.»</span></div>
      <div dir="auto"><br>
      </div>
      <div dir="auto">Is the same in the two documents.</div>
      <div dir="auto"><br>
      </div>
      <div dir="auto">In the old code of conduct it continues: «<span
          style="color:rgb(51,51,51);font-family:"Open
Sans",Helvetica,Arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)"> Please
          treat each other with tolerance and respect. Free speech and
          an open exchange </span><span class="highlightedSearchTerm"
style="box-sizing:border-box;background-color:rgb(255,255,170);color:rgb(51,51,51);font-family:"Open
          Sans",Helvetica,Arial,sans-serif;font-size:13px">of</span><span
          style="color:rgb(51,51,51);font-family:"Open
Sans",Helvetica,Arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)"> ideas
          are encouraged and celebrated. Demeaning, intimidating or
          harming anyone at the meeting is wrong. We are especially
          sensitive to behaviour that </span><span
          class="highlightedSearchTerm"
style="box-sizing:border-box;background-color:rgb(255,255,170);color:rgb(51,51,51);font-family:"Open
          Sans",Helvetica,Arial,sans-serif;font-size:13px">of</span><span
          style="color:rgb(51,51,51);font-family:"Open
Sans",Helvetica,Arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">fends
          based on gender, sexual orientation, religion, race or ethnic
          origin, or other perceived social, cultural, or personal
          differences.»</span></div>
      <div dir="auto"><br>
      </div>
      <div dir="auto">This has been removed from the new Coc, at least
        from the Intro. Is this deliberate?</div>
    </blockquote>
    No, it wasn't deliberate - the text is just so explicit later in the
    document on this but we can add it back it in, no problem. <br>
    <blockquote type="cite"
cite="mid:CAJPAtr0s0s-EefiPJiL5GtZo-JX3oE_GqBDY7stvqdf94VG_sQ@mail.gmail.com">
      <div dir="auto"><br>
      </div>
      <div dir="auto">In the old code of conduct, there are currently 3
        trusted contacts, selected by the RIPE chair without any
        documented process. In the new version the trusted contacts has
        been renamed to a CoC team of 4 to 6 and with a process on how
        the RIPE Chair selects the </div>
      <div dir="auto"><br>
      </div>
      <div dir="auto"><br>
      </div>
      <div dir="auto">As for consequences the existing CoC only states «<span
          style="color:rgb(51,51,51);font-family:"Open
Sans",Helvetica,Arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)"> Please
          be aware that attendees violating the RIPE Meeting </span><span
          class="highlightedSearchTerm"
style="box-sizing:border-box;background-color:rgb(255,255,170);color:rgb(51,51,51);font-family:"Open
          Sans",Helvetica,Arial,sans-serif;font-size:13px">Code</span><span
          style="color:rgb(51,51,51);font-family:"Open
Sans",Helvetica,Arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)"> </span><span
          class="highlightedSearchTerm"
style="box-sizing:border-box;background-color:rgb(255,255,170);color:rgb(51,51,51);font-family:"Open
          Sans",Helvetica,Arial,sans-serif;font-size:13px">of</span><span
          style="color:rgb(51,51,51);font-family:"Open
Sans",Helvetica,Arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)"></span><span
          class="highlightedSearchTerm"
style="box-sizing:border-box;background-color:rgb(255,255,170);color:rgb(51,51,51);font-family:"Open
          Sans",Helvetica,Arial,sans-serif;font-size:13px">Conduct</span><span
          style="color:rgb(51,51,51);font-family:"Open
Sans",Helvetica,Arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)"> may
          be asked to leave the meeting without a refund and other
          actions may be taken as deemed necessary.» </span></div>
      <div dir="auto"><br>
      </div>
      <div dir="auto">In the new version there is a much more detailed
        list.</div>
      <div dir="auto">It goes one step further on two areas:</div>
      <div dir="auto">* Ban from future meetings is explicitly stated
        (which I would argue could happen under the existing CoC too)</div>
      <div dir="auto">* Removing content from presentations on the
        meeting web. Here the PC has taken a very principal possition
        that the submitted presentation will be published as presented. </div>
      <div dir="auto"><br>
      </div>
      <div dir="auto">Appeals is not at all covered in the existing CoC
        but is specified in the new version.</div>
      <div dir="auto"><br>
      </div>
      <div dir="auto">While this is a very quick and high level
        analisys, I am thinking of publishing my thoughts on this, but
        would like your input before I do so.</div>
    </blockquote>
    Just to clarify - the intention with the CoC Team wasn't to replace
    the Trusted Contacts necessarily. But yeah, I think that if we have
    a CoC Team, then it's probably not necessary and if the existing TC
    members were to receive the additional training that the CoC Team
    would get, they could easily nominate themselves to be on the team.
    Having two bodies around this may be confusing and we definitely do
    not want that. <br>
    <br>
    As per the concerns raised earlier by Daniel and the discussion I
    had with you, we added the appeals process (two parts - for
    appealing a potential member of the CoC Team and for appealing a
    decision from the CoC Team on an investigation). Before sending it
    to the list, I spoke about this in detail with legal and
    incorporated their feedback into the 3.0 version. <br>
    <blockquote type="cite"
cite="mid:CAJPAtr0s0s-EefiPJiL5GtZo-JX3oE_GqBDY7stvqdf94VG_sQ@mail.gmail.com">
      <div dir="auto"><br>
      </div>
      <div dir="auto">-hph</div>
    </blockquote>
    Amanda<br>
    <blockquote type="cite"
cite="mid:CAJPAtr0s0s-EefiPJiL5GtZo-JX3oE_GqBDY7stvqdf94VG_sQ@mail.gmail.com">
      <div dir="auto"><br>
      </div>
      -- <br>
      <div dir="ltr" class="gmail_signature"
        data-smartmail="gmail_signature">
        -- Hans Petter Holen Mobile +47 45 06 60 54 | <a
          href="mailto:hph@oslo.net" moz-do-not-send="true">hph@oslo.net</a>
        | <a href="http://hph.oslo.net" moz-do-not-send="true">http://hph.oslo.net</a>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
diversity mailing list
<a class="moz-txt-link-abbreviated" href="mailto:diversity@ripe.net">diversity@ripe.net</a>
<a class="moz-txt-link-freetext" href="https://mailman.ripe.net/">https://mailman.ripe.net/</a>
</pre>
    </blockquote>
    <p><br>
    </p>
  </body>
</html>