<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr"><br class=""></div><div dir="ltr" class="gmail_attr">On Mon, 19 Apr 2021 at 19:12, Randy Bush <<a href="mailto:randy@psg.com" class="">randy@psg.com</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">>> The RIPE NCC regularly organizes events for communities which are<br class="">
>> distinct from RIPE. When preparing for such an event, the RIPE NCC<br class="">
>> will ascertain whether the respective community has adopted the<br class="">
>> RIPE Code of Conduct and, if not, also ascertain which Code must<br class="">
>> be applied.<br class="">
<br class="">
my naïve view is that, if the ncc is an organiser, then the coc MUST<br class="">
apply. </blockquote><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><br class=""></blockquote></div><br clear="all" class=""><div class=""></div><div class=""><div class="">We strongly believe that all RIPE NCC-organised events should follow the </div><div class="">same CoC, and we think this is something the community should be able to </div><div class="">agree on.</div><div class=""><br class=""></div><div class="">The updated draft provides for this. We understand that it will apply to all RIPE</div><div class="">NCC-organised events - including RIPE, MENOG, ENOG, and SEE meetings,</div><div class="">as well as things like the Roundtable Meetings, Member Lunches and RIPE</div><div class="">NCC Regional Meetings that we organise. Perhaps the CoC TF can look at</div><div class="">whether this needs to be made clearer in its draft.</div><div class=""><br class=""></div><div class="">Once the community agrees on an updated CoC, the TF will then work to </div><div class="">define procedures and how a future CoC Team will handle reports and be </div><div class="">constituted. This is where unexpected details or regional differences could </div><div class="">become relevant. For example, will members of the CoC Team need to attend </div><div class="">every Member Lunch and Regional Meeting, or will an email contact be </div><div class="">enough in some cases? Should there be one CoC Team, or would it be better </div><div class="">for MENOG, ENOG and SEE to have their own teams with more </div><div class="">understanding of local contexts?</div><div class=""><br class=""></div><div class="">My understanding is that it was an awareness of these factors that led the TF </div><div class="">to include this provision, as well as respecting the autonomy of these </div><div class="">communities, as Niall points out. </div><div class=""><br class=""></div><div class="">It is my hope and expectation that the outcome of this process should be a </div><div class="">single code of conduct that is applied in a more or less uniform way across all </div><div class="">of the events that we organise.</div><div class=""><br class=""></div><div class="">Regards</div><div class=""><br class=""></div><div class="">Hans Petter Holen</div><div class="">Managing Director</div><div class="">RIPE NCC</div></div></body></html>