<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">edit - shared BY Brian (on the ripe
list...;)<br>
<br>
On 16/10/2019 15:10, Amanda Gowland wrote:<br>
</div>
<blockquote type="cite"
cite="mid:3999c4d0-3442-0c39-f613-cce9eff05b49@ripe.net">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<div class="moz-cite-prefix">All, <br>
<br>
I've created a page on the website with CoC 3.0:<br>
<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><br>
<br>
This draft incorporates the many comments and feedback we've
received on 2.0, which was shared with Brian in May after RIPE
78. <br>
<br>
After sitting with Legal, they advised me to combine the CoC 2.0
draft with the draft CoC Team document, which is reflected in
3.0. <br>
<br>
Amanda <br>
<br>
On 16/10/2019 14:50, Hans Petter Holen wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAJPAtr3VbbJN7de8gr=g19g1EjXfgn8rRUYTZ-PT53zjYZF1TA@mail.gmail.com">
<meta http-equiv="content-type" content="text/html;
charset=utf-8">
<div dir="auto">Julia, & task force memebers.</div>
<div dir="auto"><br>
</div>
<div>On Mon, 14 Oct 2019 at 07:21, Julia Freeman <<a
href="mailto:ripe-diversity@quixotic.eu"
moz-do-not-send="true">ripe-diversity@quixotic.eu</a>>
wrote:<br>
</div>
<div>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">I am
writing on behalf of the diversity task force regarding
the proposed<br>
improvements to the Ripe Code Of Conduct. There has been
some confusion as<br>
to the next steps we need to take, and were hoping you
could provide<br>
guidance on what should happen next.</blockquote>
<div dir="auto"><br>
</div>
<div dir="auto">Strictly speaking we do not have a process
for adopting RIPE Community governance documents. Lacking
this I try to follow the PDP where relevant.</div>
<div dir="auto"><br>
</div>
<div dir="auto">If there is consensus in the Task force on
the latest version I think you should publish the version
so it can be moved from discussion phase to review phase.</div>
<div dir="auto"><br>
</div>
<div dir="auto">When all concerns has been addressed in the
review phase, a call for consensus can be made.</div>
<div dir="auto"><br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
We have a draft version 3.0 of the CoC, based on feedback
from various<br>
parties to a version 2.0 that was sent to ripe mailing
lists in May. This<br>
version is below.<br>
<br>
<a
href="https://docs.google.com/document/d/1yqOUPR02SONuSt812cuOBkk_xnhjYzjdk9qmsJkcDdQ/"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://docs.google.com/document/d/1yqOUPR02SONuSt812cuOBkk_xnhjYzjdk9qmsJkcDdQ/</a></blockquote>
<div dir="auto"><br>
</div>
<div dir="auto">Great. Has this updated draft been published
yet?</div>
<div dir="auto">Is there consensus in the task force?</div>
<div dir="auto"><br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
It has been suggested that perhaps we should have RIPE NCC
legal do an<br>
Impact Analysis on the code of conduct before it's fully
adopted, but we<br>
are unclear the exact process required.</blockquote>
<div dir="auto"><br>
</div>
<div dir="auto">In the PDP there is a step for the RIPE NCC
to do an impact asessment at the end of the discussion
phase before moving to the review phase.</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Please can you advise, and if appropriate, request RIPE
NCC Legal do an<br>
impact analysis on our proposed code of conduct. </blockquote>
<div dir="auto"><br>
</div>
<div dir="auto">I am happy to do so if you can confirm that
there is consensus in the task force on the document, and
the latest draft has been published.</div>
<div dir="auto"><br>
</div>
<div dir="auto">Hans Petter</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
</blockquote>
</div>
</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" moz-do-not-send="true">diversity@ripe.net</a>
<a class="moz-txt-link-freetext" href="https://mailman.ripe.net/" moz-do-not-send="true">https://mailman.ripe.net/</a>
</pre>
</blockquote>
<p><br>
</p>
<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>