[coc-tf] Status update: blog post and socialising the draft CoC with ENOG, MENOG and SEE

Hi Brian,

Leo asked me to jump in here: As far as I understand, it's the
communities as a whole (not the programme committees) who will have a
say in whether they want to adopt this specific code of conduct. That's
why I suggested to reach out to the ENOG, MENOG and SEE lists now to
encourage them to review the code of conduct and the RIPE Labs article.

As organiser of the events, the RIPE NCC might actually insist that
there is some kind of a code in place. And I am hoping that the regional
communities will appreciate all the work the TF has done and will adopt
the RIPE Code of Conduct.

Kind regards,
Mirjam

On 16/04/2021 10:40, Brian Nisbet wrote:
> Thanks Leo.
>
> It's interesting, one of the questions I've seen most often about the
> CoC is why the various Programme Committees have any say in whether
> it's applied to their events. I think we definitely need feedback from
> a wider pool here, but I think that's going to be something we need
> RIPE Chair Team support to explain.
>
> 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 15 April 2021 20:07
> *To:* coc-tf at ripe.net <coc-tf at ripe.net>
> *Subject:* [coc-tf] Status update: blog post and socialising the draft
> CoC with ENOG, MENOG and SEE
>  
> 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,
>
> A quick update to let you know that after a discussion with Mirjam, we
> have published the blog post earlier than previously planned and it is
> now at the top of
> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flabs.ripe.net%2F&data=04%7C01%7C%7Cb2a68f7582e443e5727808d90041b816%7Ccd9e8269dfb648e082538b7baf8d3391%7C0%7C0%7C637541104999057977%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=mBpGSKfmcLf7i92cQELyP7Mb6zSGFe8C4qUK3YR7FJU%3D&reserved=0
> <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flabs.ripe.net%2F&data=04%7C01%7C%7Cb2a68f7582e443e5727808d90041b816%7Ccd9e8269dfb648e082538b7baf8d3391%7C0%7C0%7C637541104999057977%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=mBpGSKfmcLf7i92cQELyP7Mb6zSGFe8C4qUK3YR7FJU%3D&reserved=0>.
>
> Mirjam will make sure that ENOG, MENOG, and SEE are alerted to the
> blog post so that they can decide whether they want to adopt the CoC
> when it is finalised.
>
> Kind regards,
>
> Leo
>
> --
> coc-tf mailing list
> coc-tf at ripe.net
> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ripe.net%2Fmailman%2Flistinfo%2Fcoc-tf&data=04%7C01%7C%7Cb2a68f7582e443e5727808d90041b816%7Ccd9e8269dfb648e082538b7baf8d3391%7C0%7C0%7C637541104999057977%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=K1%2FUJLTFMIfKIXxBQhksBCJIBGwQVnW0MCyqksv6DO8%3D&reserved=0
> <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ripe.net%2Fmailman%2Flistinfo%2Fcoc-tf&data=04%7C01%7C%7Cb2a68f7582e443e5727808d90041b816%7Ccd9e8269dfb648e082538b7baf8d3391%7C0%7C0%7C637541104999057977%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=K1%2FUJLTFMIfKIXxBQhksBCJIBGwQVnW0MCyqksv6DO8%3D&reserved=0>