<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hey Ruben, <br>
<br>
I've incorporated changes suggested by you and Keith here: <br>
<a class="moz-txt-link-freetext" href="https://docs.google.com/document/d/1yqOUPR02SONuSt812cuOBkk_xnhjYzjdk9qmsJkcDdQ/edit?usp=sharing">https://docs.google.com/document/d/1yqOUPR02SONuSt812cuOBkk_xnhjYzjdk9qmsJkcDdQ/edit?usp=sharing</a><br>
<br>
I added a section about how the team is to be selected, modelling
it loosely on the Arbiter's panel selection procedure (instead of
the RIPE NCC Executive Board though, the interest is submitted to
the RIPE Chair and it is the RIPE Chair who makes the selection).
<br>
<br>
Are we ready to: <br>
<br>
a) Share the draft CoC Team doc with the wider community so that<br>
b) We can ask HPH to declare consensus + open the call for
volunteers<br>
<br>
Kind regards, <br>
<br>
Amanda <br>
<br>
On 23/08/2019 19:29, Ruben van Staveren wrote:<br>
</div>
<blockquote type="cite"
cite="mid:1E711326-A484-4C5E-8540-EE43D226E9A1@verweg.com">
<pre wrap="">Hi,
Given it is a bit quiet here, probably also due to the holidays, I thought I might give it a little swing.
With RIPE79 just over 51 days away, would it be possible to either refurbish the RIPE NCC Arbiters’ panel. or finalise the CoC draft and get a response team ready?
I do not have experience with either, but we could make an effort to see how Sasha’s draft and Keith’s proposal might come together.
Best Regards,
Ruben
</pre>
<blockquote type="cite">
<pre wrap="">On 6 Aug 2019, at 17:11, Keith Mitchell <a class="moz-txt-link-rfc2396E" href="mailto:keith@smoti.org"><keith@smoti.org></a> wrote:
The function is very different, but the concept of a neutral, stable,
respected panel of volunteers serving the community's interests is not
so different from the existing arrangements for the RIPE NCC Arbiters'
panel. It might be worth a look at the relevant documents in case
there's anything in there that could be incorporated to save effort
defining processes/structure, to make the CoC Team parameters more
"RIPE-like", and/or that might otherwise be overlooked.
Keith
On 8/5/19 8:15 AM, Amanda Gowland wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Please find attached a draft proposal for the CoC Team:
<a class="moz-txt-link-freetext" href="https://docs.google.com/document/d/1yqOUPR02SONuSt812cuOBkk_xnhjYzjdk9qmsJkcDdQ/edit?usp=sharing">https://docs.google.com/document/d/1yqOUPR02SONuSt812cuOBkk_xnhjYzjdk9qmsJkcDdQ/edit?usp=sharing</a>
I used Sasha's draft as the framework for the doc, just
adding/editing where necessary.
There are some to-be-determined factors, mainly:
- How long should a term be for volunteers?> - How many people (minimum, maximum) should we aim for?> - What is the
</pre>
</blockquote>
<pre wrap="">time-frame for response (e.g. how long would a reporter need to wait for a
</pre>
<blockquote type="cite">
<pre wrap="">confirmation of receipt from the team?)
Please add your comments.
Kind regards,
Amanda
</pre>
</blockquote>
<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>
<pre wrap="">
</pre>
<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>