<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <meta name="Generator" content="Microsoft Word 15 (filtered medium)"> <style></style> </head> <body bgcolor="white" lang="EN-IE" link="blue" vlink="purple"> <div class="WordSection1"> Amanda,<o:p></o:p> <o:p> </o:p> Well, it’s not just the RIPE Chair’s scope, ofc, I mean, the ideal is for this to include RIPE NCC training courses and the like.<o:p></o:p> <o:p> </o:p> But for the first phase I shall be content with RIPE Meetings and mailing lists.<o:p></o:p> <o:p> </o:p> Thanks,<o:p></o:p> <o:p> </o:p> Brian<o:p></o:p> <o:p> </o:p> <div> Brian Nisbet <o:p></o:p> Service Operations Manager<o:p></o:p> HEAnet CLG, Ireland's National Education and Research Network<o:p></o:p> 1st Floor, 5 George's Dock, IFSC, Dublin D01 X8N7, Ireland<o:p></o:p> +35316609040 brian.nisbet@heanet.ie www.heanet.ie<o:p></o:p> Registered in Ireland, No. 275301. CRA No. 20036270<o:p></o:p> </div> <o:p> </o:p> <div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt"> <div> <div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm"> From: Amanda Gowland <agowland@ripe.net> Sent: Thursday 11 April 2019 10:45 To: Brian Nisbet <brian.nisbet@heanet.ie>; diversity@ripe.net Subject: Re: [diversity] [Ext] Draft CoC and response guide<o:p></o:p> </div> </div> <o:p> </o:p> <div> In principle, yes...but it's a grey area in terms of the RIPE Chair's scope...technically, SEE and ENOG and MENOG are not governed by RIPE. I think once we have the RIPE CoC up and running, we can then push the respective PCs to adopt or amend to their needs while keeping the spirit/key points as close to ours as possible. On 10/04/2019 14:59, Brian Nisbet wrote:<o:p></o:p> </div> <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"> <div> First off, Sasha, this is great, thank you so much!<o:p></o:p> </div> <div> <o:p> </o:p> </div> <div> Secondly, I think any CoC has to apply to all RIPE Community events and online interactions. I don't think restricting it to just RIPE meetings would be a good idea. <o:p></o:p> </div> <div> <o:p> </o:p> </div> <div> Now, maybe there has to be something iterative here, but certainly the aim should be to have the same, or as close to the same, bearing in mind the diversity of the service region, CoC across anything RIPE is running.<o:p></o:p> </div> <div> <o:p> </o:p> </div> <div> Even if we started with the main meeting and the mailing lists, that would be a good thing, but I'd really like to see it spread further than that.<o:p></o:p> </div> <div> <o:p> </o:p> </div> <div> Thanks,<o:p></o:p> </div> <div> <o:p> </o:p> </div> <div> Brian<o:p></o:p> </div> <div> <o:p> </o:p> </div> <div id="signature"> <div id="divtagdefaultwrapper"> Brian Nisbet <o:p></o:p> Service Operations Manager<o:p></o:p> HEAnet CLG, Ireland's National Education and Research Network<o:p></o:p> 1st Floor, 5 George's Dock, IFSC, Dublin D01 X8N7, Ireland<o:p></o:p> +35316609040 <a href="mailto:brian.nisbet@heanet.ie"> brian.nisbet@heanet.ie</a> <a href="http://www.heanet.ie">www.heanet.ie</a><o:p></o:p> Registered in Ireland, No. 275301. CRA No. 20036270 <o:p></o:p> </div> </div> <div class="MsoNormal" align="center" style="text-align:center"> <hr size="2" width="98%" align="center"> </div> <div id="divRplyFwdMsg"> From: diversity <a href="mailto:diversity-bounces@ripe.net"> <diversity-bounces@ripe.net></a> on behalf of Amanda Gowland <a href="mailto:agowland@ripe.net"> <agowland@ripe.net></a> Sent: Tuesday 9 April 2019 09:36 To: <a href="mailto:diversity@ripe.net">diversity@ripe.net</a> Subject: Re: [diversity] [Ext] Draft CoC and response guide <o:p></o:p> <div> <o:p></o:p> </div> </div> <div> <div> Hi Gergana, Benno, Benno has it right. We talked about this in the last TF meeting - the minutes were circulated a few weeks ago or so. If we follow the typical TF protocol for work output, it's basically: - Present to the community - Ask for feedback from community - TF reiterates if needed - RIPE Chair declares consensus But since there isn't the equivalent of HPH in the other regional communities, I would imagine this would fall to the respective PCs...well, I'm not sure but I think that sounds right? thx, Amanda On 08/04/2019 18:20, Benno Overeinder wrote: > Hi Gergana and all, > > I think you are correct. > > Speaking now for myself, not the PC collective, a suggestion might be to ask the RIPE chair, PC and the WG chairs collective for a first reading and approval (not sure this is the right wording), and next for community consensus of the CoC on the RIPE mailing list (not the TF mailing list). > > But for sure, our RIPE chair knows how to proceed in the proper way. > > Best, > > — Benno > > — > Benno J. Overeinder > NLnet Labs > <a href="https://www.nlnetlabs.nl/">https://www.nlnetlabs.nl/</a> > >> Op 8 apr. 2019 om 17:18 heeft Gergana Petrova <a href="mailto:gpetrova@ripe.net"> <gpetrova@ripe.net></a> het volgende geschreven: >> >> Thanks Amanda! I can certainly bring this up with the relevant PCs for the regional meetings. >> >> But, just for my info - is the RIPE PC going to be approving the CoC? I wasn't aware they have to. They are responsible for the plenary program, but not the meeting itself. So for example all day Wednesday and Thursday have nothing to do with them. Here is their Charter for more info: <a href="https://www.ripe.net/publications/docs/ripe-600"> https://www.ripe.net/publications/docs/ripe-600</a>). >> >> I thought the CoC is more a question of the RIPE community's agreement/concensus (basically this taskforce's mailing list, which include the people from the RIPE Community interested on this topic). Similar to the way WGs work. >> >> Anybody from RIPE PC can shed light on this? Brian? I hope I'm not creating a mess. >> >> Cheers, >> Gergana >> >>> On 08/04/2019 16:35, Amanda Gowland wrote: >>> Hi Gergana, >>> It's a good question. But seeing as the ENOG and MENOG and SEE Meetings have their own PCs, I think it's probably something that they would need to adopt on their own accord. Certainly, it would be simple to just adapt one for the RIPE Meeting but it's not within the scope of the TF to do that. >>> thx, >>> Amanda >>>> On 08/04/2019 16:30, Gergana Petrova wrote: >>>> Hi Sasha, hi all, >>>> >>>> Just want to join in with thanking you for this excellent CoC draft! >>>> >>>> Just a general question, as I am not sure if the mandate of the Transforce covers this. The CoC mentions "Where does the Code of Conduct apply?" - RIPE meetings. I was wondering if we can include "RIPE meetings and other events organised by the RIPE NCC such as ENOG, MENOG, SEE and other regional meetings." >>>> >>>> What do you think? >>>> >>>> Cheers, >>>> Gergana >>>> >>>>> On 08/04/2019 10:48, Amanda Gowland wrote: >>>>> Sasha, >>>>> >>>>> THANK YOU for contributing such a stellar draft! I've gone through and made some edits, some more British spelling-isms + putting some of the goals in active tense. I also made the scope (in terms of who it applies to) a bit more explicit. >>>>> >>>>> Warm regards, >>>>> >>>>> Amanda >>>>> >>>>> >>>>> >>>>>> On 08/04/2019 10:36, John Springer wrote: >>>>>> I agree, excellent work! >>>>>> >>>>>> I have suggest some minor edits of the Response guide. >>>>>> >>>>>> John Springer >>>>>> acting solely on my own behalf >>>>>> >>>>>> On Sat, Apr 6, 2019 at 5:10 AM David Huberman <<a href="mailto:david.huberman@icann.org">david.huberman@icann.org</a> <<a href="mailto:david.huberman@icann.org">mailto:david.huberman@icann.org</a>>> wrote: >>>>>> >>>>>> Sasha, >>>>>> >>>>>> The draft CoC is quite excellent. Nice work! I have completed a >>>>>> copyediting pass in "suggesting" mode: >>>>>> >>>>>> - normalized words to British English spellings (3 instances of >>>>>> behavior were changed to behaviour) >>>>>> - removed contractions >>>>>> - fixed a few typos >>>>>> - enforced consistent paragraph spacing >>>>>> - enforced the Oxford comma >>>>>> >>>>>> /david >>>>>> writing solely on his personal behalf >>>>>> >>>>>> On 4/5/19, 7:32 AM, "diversity on behalf of Sasha Romijn" >>>>>> <<a href="mailto:diversity-bounces@ripe.net">diversity-bounces@ripe.net</a> <<a href="mailto:diversity-bounces@ripe.net">mailto:diversity-bounces@ripe.net</a>> on >>>>>> behalf of <a href="mailto:sasha@mxsasha.eu">sasha@mxsasha.eu</a> <<a href="mailto:sasha@mxsasha.eu">mailto:sasha@mxsasha.eu</a>>> wrote: >>>>>> >>>>>> Hello all, >>>>>> >>>>>> Closely based on the work I did for Write the Docs, with some >>>>>> adjustments to fit the RIPE community, I put together a draft for >>>>>> a CoC and for a response guide. >>>>>> >>>>>> CoC: >>>>>> <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_1IAJj9UjW2zroz5v6XQYgYEYotfZlV4Trk2vRdaoPaP4_edit&d=DwIGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=iTOW7nSt3tBCc5xNiHfQNhFilU9Ki9_nVAHGfa3QG5w&m=ag_h5GXVGbSsDgGW59YleMXVaOJnV4ga6CJcCIfZ38A&s=sy8t_T8v902B5ESqiOxzVnu6ezEWJaYUIsfScYJuvyY&e="> https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_1IAJj9UjW2zroz5v6XQYgYEYotfZlV4Trk2vRdaoPaP4_edit&d=DwIGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=iTOW7nSt3tBCc5xNiHfQNhFilU9Ki9_nVAHGfa3QG5w&m=ag_h5GXVGbSsDgGW59YleMXVaOJnV4ga6CJcCIfZ38A&s=sy8t_T8v902B5ESqiOxzVnu6ezEWJaYUIsfScYJuvyY&e=</a> >>>>>> >>>>>> Response guide: >>>>>> <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_1gaLo4axYDRTpQnhUJyG92EHBmEIkxSDN8Urmy-2Dzn9nQ_edit&d=DwIGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=iTOW7nSt3tBCc5xNiHfQNhFilU9Ki9_nVAHGfa3QG5w&m=ag_h5GXVGbSsDgGW59YleMXVaOJnV4ga6CJcCIfZ38A&s=tLYhKXwOC4CmhGYH2JhF4h-Qy6XZgbV4ujIJt5XPyus&e="> https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_1gaLo4axYDRTpQnhUJyG92EHBmEIkxSDN8Urmy-2Dzn9nQ_edit&d=DwIGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=iTOW7nSt3tBCc5xNiHfQNhFilU9Ki9_nVAHGfa3QG5w&m=ag_h5GXVGbSsDgGW59YleMXVaOJnV4ga6CJcCIfZ38A&s=tLYhKXwOC4CmhGYH2JhF4h-Qy6XZgbV4ujIJt5XPyus&e=</a> >>>>>> >>>>>> I went with Google docs for now, as it’s quite accessible. You >>>>>> can leave comments and suggest changes, and we can discuss broader >>>>>> topics on the mailing list. There are a few parts about structure >>>>>> still to be filled in, but let’s start here. >>>>>> We haven’t really spoken about any of the details, other than >>>>>> a general “this can be a starting point”, so I don’t know what >>>>>> kind of discussions other people would like to bring up. >>>>>> >>>>>> Sasha >>>>>> _______________________________________________ >>>>>> diversity mailing list >>>>>> <a href="mailto:diversity@ripe.net">diversity@ripe.net</a> <<a href="mailto:diversity@ripe.net">mailto:diversity@ripe.net</a>> >>>>>> <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.ripe.net_mailman_listinfo_diversity&d=DwIGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=iTOW7nSt3tBCc5xNiHfQNhFilU9Ki9_nVAHGfa3QG5w&m=ag_h5GXVGbSsDgGW59YleMXVaOJnV4ga6CJcCIfZ38A&s=BARWpiMNfao6C_dqEoTNumUx0AVYtnpFY2CTnE4YmwA&e="> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.ripe.net_mailman_listinfo_diversity&d=DwIGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=iTOW7nSt3tBCc5xNiHfQNhFilU9Ki9_nVAHGfa3QG5w&m=ag_h5GXVGbSsDgGW59YleMXVaOJnV4ga6CJcCIfZ38A&s=BARWpiMNfao6C_dqEoTNumUx0AVYtnpFY2CTnE4YmwA&e=</a> >>>>>> >>>>>> _______________________________________________ >>>>>> diversity mailing list >>>>>> <a href="mailto:diversity@ripe.net">diversity@ripe.net</a> <<a href="mailto:diversity@ripe.net">mailto:diversity@ripe.net</a>> >>>>>> <a href="https://mailman.ripe.net/">https://mailman.ripe.net/</a> >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> diversity mailing list >>>>>> <a href="mailto:diversity@ripe.net">diversity@ripe.net</a> >>>>>> <a href="https://mailman.ripe.net/">https://mailman.ripe.net/</a> >>>>> >>>>> >>>>> _______________________________________________ >>>>> diversity mailing list >>>>> <a href="mailto:diversity@ripe.net">diversity@ripe.net</a> >>>>> <a href="https://mailman.ripe.net/">https://mailman.ripe.net/</a> >>>>> >>>> _______________________________________________ >>>> diversity mailing list >>>> <a href="mailto:diversity@ripe.net">diversity@ripe.net</a> >>>> <a href="https://mailman.ripe.net/">https://mailman.ripe.net/</a> >> _______________________________________________ >> diversity mailing list >> <a href="mailto:diversity@ripe.net">diversity@ripe.net</a> >> <a href="https://mailman.ripe.net/">https://mailman.ripe.net/</a> > > _______________________________________________ > diversity mailing list > <a href="mailto:diversity@ripe.net">diversity@ripe.net</a> > <a href="https://mailman.ripe.net/">https://mailman.ripe.net/</a> _______________________________________________ diversity mailing list <a href="mailto:diversity@ripe.net">diversity@ripe.net</a> <a href="https://mailman.ripe.net/">https://mailman.ripe.net/</a><o:p></o:p> </div> </div> </blockquote> <o:p> </o:p> </div> </div> </body> </html>