<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Leo,</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Great stuff, thank you!</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
The data protection piece is fair, albeit I'd love to expand that to 18 and 36 months to guarantee it covering 3 meetings to more easily spot patterns, but Athina is the expert here.</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Under 4 we still say: "In all cases, the RIPE Chair Team and the RIPE NCC will be informed of a decision by the CoC Team before it is implemented." Is it intended to change that language to reflect only major (you said significant, but if we're using minor/major
language elsewhere, I'm assuming significant = major) breaches will be informed prior to implementation?</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
My biggest concern is that we now have to create broad classifications of what a minor or major breach is, which I'll admit I'd been hoping we could avoid.</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Brian</div>
<div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div id="Signature">
<div>
<div></div>
<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">Brian Nisbet (he/him)</p>
<p style="margin-top:0px; margin-bottom:0px">Service Operations Manager</p>
<p style="margin-top:0px; margin-bottom:0px">HEAnet CLG, Ireland's National Education and Research Network</p>
<p style="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">+35316609040 brian.nisbet@heanet.ie www.heanet.ie</p>
<p style="margin-top:0px; margin-bottom:0px">Registered in Ireland, No. 275301. CRA No. 20036270 </p>
</div>
</div>
</div>
</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> coc-tf <coc-tf-bounces@ripe.net> on behalf of Leo Vegoda <leo@vegoda.org><br>
<b>Sent:</b> Thursday 31 March 2022 16:48<br>
<b>To:</b> coc-tf@ripe.net <coc-tf@ripe.net><br>
<b>Cc:</b> chair-team@ripe.net <chair-team@ripe.net><br>
<b>Subject:</b> [coc-tf] CoC Process and Next Steps</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">CAUTION[External]: This email originated from outside of the organisation. Do not click on links or open the attachments unless you recognise the sender and know the content is safe.<br>
<br>
<br>
Hi,<br>
<br>
Antony, Kjerstin, and I met earlier today. These are some lightweight<br>
notes. Kjerstin will provide proper minutes later.<br>
<br>
We reviewed the updated draft process. The key change in this is that<br>
only significant breaches of the Code of Conduct will be reported to<br>
the RIPE Chair Team and the RIPE NCC before actions are taken.<br>
<br>
We made some changes to the section dealing with data during the<br>
meeting. We were advised that we cannot just make a statement that the<br>
record system will comply with the law. We need to state how long the<br>
RIPE NCC will keep records for. The update we made recognises minor<br>
and major breaches of the Code of Conduct.<br>
<br>
The records system will always keep data that does not identify<br>
individuals to allow trend analysis. It will keep information<br>
identifying an individual for a minor breach for 12 months. It will<br>
keep information identifying an individual for a major breach for 24<br>
months. If a person is permanently barred from attending RIPE events<br>
or posting to RIPE lists, it will need to keep information on them<br>
indefinitely. Otherwise, that action could not be implemented.<br>
<br>
We intend to publish the updated draft as soon as possible. We would<br>
like the RIPE NCC's legal team to review it before publishing but if<br>
that is not possible, we plan to publish next week.<br>
<br>
We have a blog post drafted. It presents a fairly concise summary,<br>
asks two questions, and asks the community to provide any feedback<br>
they have. We'd like to have a three week comment period on the draft.<br>
<br>
We agreed that it made sense to propose a Code of Conduct BoF for RIPE<br>
84. The focus in the proposal to the RIPE Programme Committee will be:<br>
1. Present the proposed Code of Conduct Team recruitment process,<br>
based on the one used for the Arbiters<br>
2. Present the Code of Conduct Team training plans and estimated time commitment<br>
3. Discussion - which could include discussion on the process document<br>
if significant issues are raised on the RIPE Discussion List<br>
<br>
I will draft a proposal for the BoF and circulate it.<br>
<br>
Kind regards,<br>
<br>
Leo<br>
<br>
--<br>
coc-tf mailing list<br>
coc-tf@ripe.net<br>
<a href="https://lists.ripe.net/mailman/listinfo/coc-tf">https://lists.ripe.net/mailman/listinfo/coc-tf</a><br>
</div>
</span></font></div>
</body>
</html>