[coc-tf] Update following today's discussion

Leo,

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...

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?

Happy to discuss this more on a future call pre-82 ofc.

Thanks,

Brian


Brian Nisbet (he/him)

Service Operations Manager

HEAnet CLG, Ireland's National Education and Research Network

1st Floor, 5 George's Dock, IFSC, Dublin D01 X8N7, Ireland

+35316609040 brian.nisbet at heanet.ie www.heanet.ie

Registered in Ireland, No. 275301. CRA No. 20036270

________________________________
From: coc-tf <coc-tf-bounces at ripe.net> on behalf of Leo Vegoda <leo at vegoda.org>
Sent: Thursday 18 March 2021 17:02
To: coc-tf at ripe.net <coc-tf at ripe.net>
Subject: [coc-tf] Update following today's discussion

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.


Hi,

We had an informal chat today instead of a formal meeting as a couple
of people were ill and others had time constraints.

We chatted about both the amount of feedback we have seen so far and
the upcoming RIPE meeting. I agreed to send a reminder to the list in
case people missed the original announcement. We also discussed
holding a BoF at RIPE 82 and thought it was a good idea. As the
closing date for submissions is tomorrow, I have made a submission
with this abstract and a very simple agenda:

CoC TF BoF at RIPE 82
This BoF aims to present the work delivered by the Code of Conduct TF,
gather input from the community on that work, and discuss the TF’s
next steps:
● Code of Conduct team selection
● Reporting and operational procedures for the Code of Conduct team

Separately, I proposed that we keep the same meeting cadence in Q2,
with adjustments for public holidays, as it didn't seem to be a bad
time for anyone.

Kind regards,

Leo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </ripe/mail/archives/coc-tf/attachments/20210322/919ebeb7/attachment-0001.html>