<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-2022-jp">
<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);">
Thanks for this. I note, from reading Anthony's excellent minutes, that my initial thinking on any interactions during RIPE 82 should be in the vein of presenting work as done, not as something to be further discussed, and I know I went back a little on that
on Thursday, however...</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);">
I would still prefer us to present it as done (unless there is significant pushback on the mailing list) but to emphasise that CoCs should be living documents and certainly listening if people do have feedback, if that makes sense?</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);">
Happy to discuss this more on a future call pre-82 ofc.</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);">
Thanks,</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 18 March 2021 17:02<br>
<b>To:</b> coc-tf@ripe.net <coc-tf@ripe.net><br>
<b>Subject:</b> [coc-tf] Update following today's discussion</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>
We had an informal chat today instead of a formal meeting as a couple<br>
of people were ill and others had time constraints.<br>
<br>
We chatted about both the amount of feedback we have seen so far and<br>
the upcoming RIPE meeting. I agreed to send a reminder to the list in<br>
case people missed the original announcement. We also discussed<br>
holding a BoF at RIPE 82 and thought it was a good idea. As the<br>
closing date for submissions is tomorrow, I have made a submission<br>
with this abstract and a very simple agenda:<br>
<br>
CoC TF BoF at RIPE 82<br>
This BoF aims to present the work delivered by the Code of Conduct TF,<br>
gather input from the community on that work, and discuss the TF’s<br>
next steps:<br>
● Code of Conduct team selection<br>
● Reporting and operational procedures for the Code of Conduct team<br>
<br>
Separately, I proposed that we keep the same meeting cadence in Q2,<br>
with adjustments for public holidays, as it didn't seem to be a bad<br>
time for anyone.<br>
<br>
Kind regards,<br>
<br>
Leo<br>
</div>
</span></font></div>
</body>
</html>