<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">In principle, yes...but it's a grey
      area in terms of the RIPE Chair's scope...technically, SEE and
      ENOG and MENOG are not governed by RIPE.<br>
      <br>
      I think once we have the RIPE CoC up and running, we can then push
      the respective PCs to adopt or amend to their needs while keeping
      the spirit/key points as close to ours as possible. <br>
      <br>
      On 10/04/2019 14:59, Brian Nisbet wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:DB7PR06MB5643C725DA7D50DC67929554942E0@DB7PR06MB5643.eurprd06.prod.outlook.com">
      <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
      <style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
      <div style="font-family:Calibri,Arial,Helvetica,sans-serif;
        font-size:12pt; color:rgb(0,0,0)">
        First off, Sasha, this is great, thank you so much!</div>
      <div style="font-family:Calibri,Arial,Helvetica,sans-serif;
        font-size:12pt; color:rgb(0,0,0)">
        <br>
      </div>
      <div style="font-family:Calibri,Arial,Helvetica,sans-serif;
        font-size:12pt; color:rgb(0,0,0)">
        Secondly, I think any CoC has to apply to all RIPE Community
        events and online interactions. I don't think restricting it to
        just RIPE meetings would be a good idea. </div>
      <div style="font-family:Calibri,Arial,Helvetica,sans-serif;
        font-size:12pt; color:rgb(0,0,0)">
        <br>
      </div>
      <div style="font-family:Calibri,Arial,Helvetica,sans-serif;
        font-size:12pt; color:rgb(0,0,0)">
        Now, maybe there has to be something iterative here, but
        certainly the aim should be to have the same, or as close to the
        same, bearing in mind the diversity of the service region, CoC
        across anything RIPE is running.</div>
      <div style="font-family:Calibri,Arial,Helvetica,sans-serif;
        font-size:12pt; color:rgb(0,0,0)">
        <br>
      </div>
      <div style="font-family:Calibri,Arial,Helvetica,sans-serif;
        font-size:12pt; color:rgb(0,0,0)">
        Even if we started with the main meeting and the mailing lists,
        that would be a good thing, but I'd really like to see it spread
        further than that.</div>
      <div style="font-family:Calibri,Arial,Helvetica,sans-serif;
        font-size:12pt; color:rgb(0,0,0)">
        <br>
      </div>
      <div style="font-family:Calibri,Arial,Helvetica,sans-serif;
        font-size:12pt; color:rgb(0,0,0)">
        Thanks,</div>
      <div style="font-family:Calibri,Arial,Helvetica,sans-serif;
        font-size:12pt; color:rgb(0,0,0)">
        <br>
      </div>
      <div style="font-family:Calibri,Arial,Helvetica,sans-serif;
        font-size:12pt; color:rgb(0,0,0)">
        Brian</div>
      <div style="font-family:Calibri,Arial,Helvetica,sans-serif;
        font-size:12pt; color:rgb(0,0,0)">
        <br>
      </div>
      <div id="signature">
        <div id="divtagdefaultwrapper" dir="ltr" style="font-size:12pt;
          color:#000000; font-family:Calibri,Helvetica,sans-serif">
          <p style="margin-top: 0px; margin-bottom: 0px;margin-top:0px;
            margin-bottom:0px">
            Brian Nisbet </p>
          <p style="margin-top: 0px; margin-bottom: 0px;margin-top:0px;
            margin-bottom:0px">
            Service Operations Manager</p>
          <p style="margin-top: 0px; margin-bottom: 0px;margin-top:0px;
            margin-bottom:0px">
            HEAnet CLG, Ireland's National Education and Research
            Network</p>
          <p style="margin-top: 0px; margin-bottom: 0px;margin-top:0px;
            margin-bottom:0px">
            1st Floor, 5 George's Dock, IFSC, Dublin D01 X8N7, Ireland</p>
          <p style="margin-top: 0px; margin-bottom: 0px;margin-top:0px;
            margin-bottom:0px">
            +35316609040 <a class="moz-txt-link-abbreviated" href="mailto:brian.nisbet@heanet.ie">brian.nisbet@heanet.ie</a> <a class="moz-txt-link-abbreviated" href="http://www.heanet.ie">www.heanet.ie</a></p>
          <p style="margin-top: 0px; margin-bottom: 0px;margin-top:0px;
            margin-bottom:0px">
            Registered in Ireland, No. 275301. CRA No. 20036270 </p>
        </div>
      </div>
      <hr tabindex="-1" style="display:inline-block; width:98%">
      <div id="divRplyFwdMsg" dir="ltr"><font style="font-size:11pt"
          face="Calibri, sans-serif" color="#000000"><b>From:</b>
          diversity <a class="moz-txt-link-rfc2396E" href="mailto:diversity-bounces@ripe.net"><diversity-bounces@ripe.net></a> on behalf of
          Amanda Gowland <a class="moz-txt-link-rfc2396E" href="mailto:agowland@ripe.net"><agowland@ripe.net></a><br>
          <b>Sent:</b> Tuesday 9 April 2019 09:36<br>
          <b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:diversity@ripe.net">diversity@ripe.net</a><br>
          <b>Subject:</b> Re: [diversity] [Ext] Draft CoC and response
          guide</font>
        <div> </div>
      </div>
      <div class="BodyFragment"><font size="2"><span
            style="font-size:11pt">
            <div class="PlainText">Hi Gergana, Benno,<br>
              <br>
              Benno has it right.<br>
              <br>
              We talked about this in the last TF meeting - the minutes
              were <br>
              circulated a few weeks ago or so. If we follow the typical
              TF protocol <br>
              for work output, it's basically:<br>
              <br>
              - Present to the community<br>
              - Ask for feedback from community<br>
              - TF reiterates if needed<br>
              - RIPE Chair declares consensus<br>
              <br>
              But since there isn't the equivalent of HPH in the other
              regional <br>
              communities, I would imagine this would fall to the
              respective <br>
              PCs...well, I'm not sure but I think that sounds right?<br>
              <br>
              thx,<br>
              <br>
              Amanda<br>
              <br>
              On 08/04/2019 18:20, Benno Overeinder wrote:<br>
              > Hi Gergana and all,<br>
              ><br>
              > I think you are correct.<br>
              ><br>
              > Speaking now for myself, not the PC collective, a
              suggestion might be to ask the RIPE chair, PC and the WG
              chairs collective for a first reading and approval (not
              sure this is the right wording), and next for community
              consensus of the CoC on the RIPE mailing list (not the TF
              mailing list).<br>
              ><br>
              > But for sure, our RIPE chair knows how to proceed in
              the proper way.<br>
              ><br>
              > Best,<br>
              ><br>
              > — Benno<br>
              ><br>
              > —<br>
              > Benno J. Overeinder<br>
              > NLnet Labs<br>
              > <a href="https://www.nlnetlabs.nl/"
                moz-do-not-send="true">https://www.nlnetlabs.nl/</a><br>
              ><br>
              >> Op 8 apr. 2019 om 17:18 heeft Gergana Petrova
              <a class="moz-txt-link-rfc2396E" href="mailto:gpetrova@ripe.net"><gpetrova@ripe.net></a> het volgende geschreven:<br>
              >><br>
              >> Thanks Amanda! I can certainly bring this up with
              the relevant PCs for the regional meetings.<br>
              >><br>
              >> But, just for my info - is the RIPE PC going to
              be approving the CoC? I wasn't aware they have to. They
              are responsible for the plenary program, but not the
              meeting itself. So for example all day Wednesday and
              Thursday have nothing to do with them. Here is their
              Charter for more info: <a
                href="https://www.ripe.net/publications/docs/ripe-600"
                moz-do-not-send="true">
                https://www.ripe.net/publications/docs/ripe-600</a>).<br>
              >><br>
              >> I thought the CoC is more a question of the RIPE
              community's agreement/concensus (basically this
              taskforce's mailing list, which include the people from
              the RIPE Community interested on this topic). Similar to
              the way WGs work.<br>
              >><br>
              >> Anybody from RIPE PC can shed light on this?
              Brian? I hope I'm not creating a mess.<br>
              >><br>
              >> Cheers,<br>
              >> Gergana<br>
              >><br>
              >>> On 08/04/2019 16:35, Amanda Gowland wrote:<br>
              >>> Hi Gergana,<br>
              >>> It's a good question. But seeing as the ENOG
              and MENOG and SEE Meetings have their own PCs, I think
              it's probably something that they would need to adopt on
              their own accord. Certainly, it would be simple to just
              adapt one for the RIPE Meeting but it's not within the
              scope of the TF to do that.<br>
              >>> thx,<br>
              >>> Amanda<br>
              >>>> On 08/04/2019 16:30, Gergana Petrova
              wrote:<br>
              >>>> Hi Sasha, hi all,<br>
              >>>><br>
              >>>> Just want to join in with thanking you
              for this excellent CoC draft!<br>
              >>>><br>
              >>>> Just a general question, as I am not sure
              if the mandate of the Transforce covers this. The CoC
              mentions "Where does the Code of Conduct apply?" - RIPE
              meetings. I was wondering if we can include "RIPE meetings
              and other events organised by the RIPE NCC such as ENOG,
              MENOG, SEE and other regional meetings."<br>
              >>>><br>
              >>>> What do you think?<br>
              >>>><br>
              >>>> Cheers,<br>
              >>>> Gergana<br>
              >>>><br>
              >>>>> On 08/04/2019 10:48, Amanda Gowland
              wrote:<br>
              >>>>> Sasha,<br>
              >>>>><br>
              >>>>> THANK YOU for contributing such a
              stellar draft! I've gone through and made some edits, some
              more British spelling-isms + putting some of the goals in
              active tense. I also made the scope (in terms of who it
              applies to) a bit more explicit.<br>
              >>>>><br>
              >>>>> Warm regards,<br>
              >>>>><br>
              >>>>> Amanda<br>
              >>>>><br>
              >>>>><br>
              >>>>><br>
              >>>>>> On 08/04/2019 10:36, John
              Springer wrote:<br>
              >>>>>> I agree, excellent work!<br>
              >>>>>><br>
              >>>>>> I have suggest some minor edits
              of the Response guide.<br>
              >>>>>><br>
              >>>>>> John Springer<br>
              >>>>>> acting solely on my own behalf<br>
              >>>>>><br>
              >>>>>> On Sat, Apr 6, 2019 at 5:10 AM
              David Huberman <<a class="moz-txt-link-abbreviated" href="mailto:david.huberman@icann.org">david.huberman@icann.org</a> <<a
                href="mailto:david.huberman@icann.org"
                moz-do-not-send="true">mailto:david.huberman@icann.org</a>>>
              wrote:<br>
              >>>>>><br>
              >>>>>>      Sasha,<br>
              >>>>>><br>
              >>>>>>      The draft CoC is quite
              excellent. Nice work!  I have completed a<br>
              >>>>>>      copyediting pass in
              "suggesting" mode:<br>
              >>>>>><br>
              >>>>>>      - normalized words to
              British English spellings (3 instances of<br>
              >>>>>>      behavior were changed to
              behaviour)<br>
              >>>>>>      - removed contractions<br>
              >>>>>>      - fixed a few typos<br>
              >>>>>>      - enforced consistent
              paragraph spacing<br>
              >>>>>>      - enforced the Oxford comma<br>
              >>>>>><br>
              >>>>>>      /david<br>
              >>>>>>      writing solely on his
              personal behalf<br>
              >>>>>><br>
              >>>>>>      On 4/5/19, 7:32 AM,
              "diversity on behalf of Sasha Romijn"<br>
              >>>>>>     
              <<a class="moz-txt-link-abbreviated" href="mailto:diversity-bounces@ripe.net">diversity-bounces@ripe.net</a> <<a
                href="mailto:diversity-bounces@ripe.net"
                moz-do-not-send="true">mailto:diversity-bounces@ripe.net</a>>
              on<br>
              >>>>>>      behalf of <a class="moz-txt-link-abbreviated" href="mailto:sasha@mxsasha.eu">sasha@mxsasha.eu</a>
              <<a href="mailto:sasha@mxsasha.eu"
                moz-do-not-send="true">mailto:sasha@mxsasha.eu</a>>>
              wrote:<br>
              >>>>>><br>
              >>>>>>          Hello all,<br>
              >>>>>><br>
              >>>>>>          Closely based on the
              work I did for Write the Docs, with some<br>
              >>>>>>      adjustments to fit the RIPE
              community, I put together a draft for<br>
              >>>>>>      a CoC and for a response
              guide.<br>
              >>>>>><br>
              >>>>>>          CoC:<br>
              >>>>>> <a
href="https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_1IAJj9UjW2zroz5v6XQYgYEYotfZlV4Trk2vRdaoPaP4_edit&d=DwIGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=iTOW7nSt3tBCc5xNiHfQNhFilU9Ki9_nVAHGfa3QG5w&m=ag_h5GXVGbSsDgGW59YleMXVaOJnV4ga6CJcCIfZ38A&s=sy8t_T8v902B5ESqiOxzVnu6ezEWJaYUIsfScYJuvyY&e="
                moz-do-not-send="true">
https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_1IAJj9UjW2zroz5v6XQYgYEYotfZlV4Trk2vRdaoPaP4_edit&d=DwIGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=iTOW7nSt3tBCc5xNiHfQNhFilU9Ki9_nVAHGfa3QG5w&m=ag_h5GXVGbSsDgGW59YleMXVaOJnV4ga6CJcCIfZ38A&s=sy8t_T8v902B5ESqiOxzVnu6ezEWJaYUIsfScYJuvyY&e=</a><br>
              >>>>>><br>
              >>>>>>          Response guide:<br>
              >>>>>> <a
href="https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_1gaLo4axYDRTpQnhUJyG92EHBmEIkxSDN8Urmy-2Dzn9nQ_edit&d=DwIGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=iTOW7nSt3tBCc5xNiHfQNhFilU9Ki9_nVAHGfa3QG5w&m=ag_h5GXVGbSsDgGW59YleMXVaOJnV4ga6CJcCIfZ38A&s=tLYhKXwOC4CmhGYH2JhF4h-Qy6XZgbV4ujIJt5XPyus&e="
                moz-do-not-send="true">
https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_1gaLo4axYDRTpQnhUJyG92EHBmEIkxSDN8Urmy-2Dzn9nQ_edit&d=DwIGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=iTOW7nSt3tBCc5xNiHfQNhFilU9Ki9_nVAHGfa3QG5w&m=ag_h5GXVGbSsDgGW59YleMXVaOJnV4ga6CJcCIfZ38A&s=tLYhKXwOC4CmhGYH2JhF4h-Qy6XZgbV4ujIJt5XPyus&e=</a><br>
              >>>>>><br>
              >>>>>>          I went with Google docs
              for now, as it’s quite accessible. You<br>
              >>>>>>      can leave comments and
              suggest changes, and we can discuss broader<br>
              >>>>>>      topics on the mailing list.
              There are a few parts about structure<br>
              >>>>>>      still to be filled in, but
              let’s start here.<br>
              >>>>>>          We haven’t really spoken
              about any of the details, other than<br>
              >>>>>>      a general “this can be a
              starting point”, so I don’t know what<br>
              >>>>>>      kind of discussions other
              people would like to bring up.<br>
              >>>>>><br>
              >>>>>>          Sasha<br>
              >>>>>>         
              _______________________________________________<br>
              >>>>>>          diversity mailing list<br>
              >>>>>>      <a class="moz-txt-link-abbreviated" href="mailto:diversity@ripe.net">diversity@ripe.net</a> <<a
                href="mailto:diversity@ripe.net" moz-do-not-send="true">mailto:diversity@ripe.net</a>><br>
              >>>>>> <a
href="https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.ripe.net_mailman_listinfo_diversity&d=DwIGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=iTOW7nSt3tBCc5xNiHfQNhFilU9Ki9_nVAHGfa3QG5w&m=ag_h5GXVGbSsDgGW59YleMXVaOJnV4ga6CJcCIfZ38A&s=BARWpiMNfao6C_dqEoTNumUx0AVYtnpFY2CTnE4YmwA&e="
                moz-do-not-send="true">
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.ripe.net_mailman_listinfo_diversity&d=DwIGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=iTOW7nSt3tBCc5xNiHfQNhFilU9Ki9_nVAHGfa3QG5w&m=ag_h5GXVGbSsDgGW59YleMXVaOJnV4ga6CJcCIfZ38A&s=BARWpiMNfao6C_dqEoTNumUx0AVYtnpFY2CTnE4YmwA&e=</a><br>
              >>>>>><br>
              >>>>>>     
              _______________________________________________<br>
              >>>>>>      diversity mailing list<br>
              >>>>>>      <a class="moz-txt-link-abbreviated" href="mailto:diversity@ripe.net">diversity@ripe.net</a> <<a
                href="mailto:diversity@ripe.net" moz-do-not-send="true">mailto:diversity@ripe.net</a>><br>
              >>>>>>      <a
                href="https://mailman.ripe.net/"
                moz-do-not-send="true">https://mailman.ripe.net/</a><br>
              >>>>>><br>
              >>>>>><br>
              >>>>>><br>
              >>>>>>
              _______________________________________________<br>
              >>>>>> diversity mailing list<br>
              >>>>>> <a class="moz-txt-link-abbreviated" href="mailto:diversity@ripe.net">diversity@ripe.net</a><br>
              >>>>>> <a
                href="https://mailman.ripe.net/"
                moz-do-not-send="true">https://mailman.ripe.net/</a><br>
              >>>>><br>
              >>>>><br>
              >>>>>
              _______________________________________________<br>
              >>>>> diversity mailing list<br>
              >>>>> <a class="moz-txt-link-abbreviated" href="mailto:diversity@ripe.net">diversity@ripe.net</a><br>
              >>>>> <a
                href="https://mailman.ripe.net/"
                moz-do-not-send="true">https://mailman.ripe.net/</a><br>
              >>>>><br>
              >>>>
              _______________________________________________<br>
              >>>> diversity mailing list<br>
              >>>> <a class="moz-txt-link-abbreviated" href="mailto:diversity@ripe.net">diversity@ripe.net</a><br>
              >>>> <a
                href="https://mailman.ripe.net/"
                moz-do-not-send="true">https://mailman.ripe.net/</a><br>
              >> _______________________________________________<br>
              >> diversity mailing list<br>
              >> <a class="moz-txt-link-abbreviated" href="mailto:diversity@ripe.net">diversity@ripe.net</a><br>
              >> <a
                href="https://mailman.ripe.net/"
                moz-do-not-send="true">https://mailman.ripe.net/</a><br>
              ><br>
              > _______________________________________________<br>
              > diversity mailing list<br>
              > <a class="moz-txt-link-abbreviated" href="mailto:diversity@ripe.net">diversity@ripe.net</a><br>
              > <a
                href="https://mailman.ripe.net/"
                moz-do-not-send="true">https://mailman.ripe.net/</a><br>
              <br>
              <br>
              <br>
              _______________________________________________<br>
              diversity mailing list<br>
              <a class="moz-txt-link-abbreviated" href="mailto:diversity@ripe.net">diversity@ripe.net</a><br>
              <a
                href="https://mailman.ripe.net/"
                moz-do-not-send="true">https://mailman.ripe.net/</a><br>
            </div>
          </span></font></div>
    </blockquote>
    <p><br>
    </p>
  </body>
</html>