First off, hey Olaf, thanks for agreeing to do this!

Leo, I like that message, sets out the questions we have quite clearly. Of course we know our community, people will still try to talk about the things they want to talk about, but I'm confident that the discussion can be steered in the right direction.

It strikes me that one question that might be raised, which isn't in scope, but even so, is "Why are we taking so long?" This hasn't been raised by email, which means either people aren't as worried as I think they might be, they just aren't engaging, or they don't want to use email as a medium, but it might come up in conversation.

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@heanet.ie www.heanet.ie

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

From: coc-tf <coc-tf-bounces@ripe.net> on behalf of Leo Vegoda <leo@vegoda.org>
Sent: Tuesday 11 May 2021 21:20
To: Olaf Kolkman <kolkman@isoc.org>; coc-tf@ripe.net <coc-tf@ripe.net>
Subject: [coc-tf] RIPE 82 Code of Conduct TF BoF
 
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,

Earlier today, Olaf and Denesh spoke. Olaf has agreed to chair the
BoF, which is great news.

We can use the BoF as a way to gather input from the community on the
next steps of the CoC TF's work. We also need to let people know that
the draft document we published is being updated and a new version
will be shared soon.

I have drafted the message below. I'd like to send a message along
these lines to the RIPE Discussion List by Thursday. It does several
things:

1. Lets people know when we plan to share the next version of the
draft CoC document
2. Lets people know who will make the decision on consensus
3. Sets out the questions we'll be asking at the BoF and guides them
to the slides

I'd appreciate thoughts on the draft.

Thanks,

Leo


To: RIPE Discussion List
Subject: Questions to discuss at RIPE 82 Code of Conduct BoF

Dear RIPE community,

I'd like to thank everyone who contributed to our recent discussion on
the draft RIPE Code of Conduct (CoC). We are using the input to update
the draft. We plan to publish an updated version by the end of June.
The RIPE Chair will decide if there is a consensus on that version.

At next week's BoF, to be chaired by Olaf Kolkman, we want to gather
your input on the other two items in our charter. We want your input
on three key questions:

- What kind of team is needed?
- How should we balance process and speed?
- What kind of process will be required to update the CoC or its processes?

You can see the full set of questions in our slide deck:

https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fripe82.ripe.net%2Fwp-content%2Fuploads%2Fpresentations%2F3-Code-of-Conduct-TF-RIPE-82-BoF.pdf&amp;data=04%7C01%7C%7C021fff549e6f485850c608d914ba5393%7Ccd9e8269dfb648e082538b7baf8d3391%7C0%7C0%7C637563613218911666%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=B229oCegrTbT0uNplsqK6vkgBsxEVEB%2Fvik4LD8nsl4%3D&amp;reserved=0

Please give these issues some thought ahead of time, as we only have
an hour and want to cover a lot of ground.

Many thanks,

Leo Vegoda
on behalf of the Code of Conduct TF

--
coc-tf mailing list
coc-tf@ripe.net
https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ripe.net%2Fmailman%2Flistinfo%2Fcoc-tf&amp;data=04%7C01%7C%7C021fff549e6f485850c608d914ba5393%7Ccd9e8269dfb648e082538b7baf8d3391%7C0%7C0%7C637563613218911666%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=M3zACSfgGgyIFHIWozW6liwhwkPK0d9XGwKFKiG6L6U%3D&amp;reserved=0