October 2019 - diversity - mailman.ripe.net

Suscribe
by laura kaplan 17 Oct '19

17 Oct '19

Hello I would like to be suscribe to this list please. Thank you Laura

3 2

Community Plenary Presentation
by Brian Nisbet 17 Oct '19

17 Oct '19

Folks, Amanda, Denesh, Sasha and I have put this presentation together for the community plenary this afternoon. It is forthright, but we definitely feel that it needs to be so. I tried to send it to the list earlier, but it was caught in moderation, so you can see it here: https://ripe79.ripe.net/programme/meeting-plan/ripe-community/ We are going to make it clear that we're still accepting comments on v3.0, but also still looking at having this in place for RIPE 80 if at all possible. I know I and others present in Rotterdam have got some really good further feedback. And, of course, as with all things, whatever CoC we have is never set in stone, it's always changeable as situations change. Thanks for everyone's input on this so far! Brian Brian Nisbet 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(a)heanet.ie www.heanet.ie Registered in Ireland, No. 275301. CRA No. 20036270

1 0

Re: [diversity] CoC Impact assessment
by Hans Petter Holen 16 Oct '19

16 Oct '19

Julia, & task force memebers. On Mon, 14 Oct 2019 at 07:21, Julia Freeman <ripe-diversity(a)quixotic.eu> wrote: > I am writing on behalf of the diversity task force regarding the proposed > improvements to the Ripe Code Of Conduct. There has been some confusion as > to the next steps we need to take, and were hoping you could provide > guidance on what should happen next. Strictly speaking we do not have a process for adopting RIPE Community governance documents. Lacking this I try to follow the PDP where relevant. If there is consensus in the Task force on the latest version I think you should publish the version so it can be moved from discussion phase to review phase. When all concerns has been addressed in the review phase, a call for consensus can be made. > We have a draft version 3.0 of the CoC, based on feedback from various > parties to a version 2.0 that was sent to ripe mailing lists in May. This > version is below. > > > https://docs.google.com/document/d/1yqOUPR02SONuSt812cuOBkk_xnhjYzjdk9qmsJk… Great. Has this updated draft been published yet? Is there consensus in the task force? <https://docs.google.com/document/d/1yqOUPR02SONuSt812cuOBkk_xnhjYzjdk9qmsJk…> > It has been suggested that perhaps we should have RIPE NCC legal do an > Impact Analysis on the code of conduct before it's fully adopted, but we > are unclear the exact process required. In the PDP there is a step for the RIPE NCC to do an impact asessment at the end of the discussion phase before moving to the review phase. > > Please can you advise, and if appropriate, request RIPE NCC Legal do an > impact analysis on our proposed code of conduct. I am happy to do so if you can confirm that there is consensus in the task force on the document, and the latest draft has been published. Hans Petter > > -- -- Hans Petter Holen Mobile +47 45 06 60 54 | hph(a)oslo.net | http://hph.oslo.net

2 2

RIPE Community plenary - Presentation of the latest version of the code of conduct
by Hans Petter Holen 16 Oct '19

16 Oct '19

Hi, I have put Code of Conduct on the agenda for discussion in the Community plenary tomorrow. It would be great if the chair, or a task force representative could present the latest published version of the code of conduct. Please let me know who will present and upload your presentation into the presentation system. Hans Petter -- -- Hans Petter Holen Mobile +47 45 06 60 54 | hph(a)oslo.net | http://hph.oslo.net

3 2

CoC v3.0 and RIPE List Email
by Brian Nisbet 16 Oct '19

16 Oct '19

Malcolm, In regard to the email you've just sent to the RIPE List, honestly, I'm gobsmacked. I see Hans Petter has also clarified on the list, but I think we need more than that. You are on the Diversity TF, you have the ability to interact with the conversation around the CoC and you will have seen that Julia has been talking to HPH about how best to proceed. There is, as you should be aware, zero intention of asking the Plenary to approve the CoC tomorrow. We absolutely need to circulate v3.0 for discussion and, as referenced, speak to the NCC about an Impact Analysis. I'm not even going to get into my frustrations around this whole process, because that's not the point of this email. I believe you need to immediately reply to your own mail and say that you were mistaken and that the new version CoC will be presented to the Community by the Diversity TF, a version that has taken into account the feedback received both within and without the TF. We will then be speaking to the NCC about an IA and will take that into account as well. Currently you are spreading fear and trying to undermine the TF, which is not what I would have ever expected from you. Brian Brian Nisbet 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(a)heanet.ie www.heanet.ie Registered in Ireland, No. 275301. CRA No. 20036270

1 0

Clarification re: RIPE NCC & survey
by Amanda Gowland 14 Oct '19

14 Oct '19

Hi list, To clarify on the one-question survey that Denesh emailed to the list earlier this week: The RIPE NCC has no involvement in this survey - including collecting or analysing the survey data or presenting the results. Thanks, Amanda (sent as a woman at the RIPE Meeting and member of the Diversity TF only)

1 0

[FWD: CoC Impact assessment]
by Julia Freeman 14 Oct '19

14 Oct '19

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Forgot to cc the mailing list when I sent this to HPH. I only had one reply to my draft from Job, folded in their feedback, and sent the email. I will forward HPH's response when I get it. Thanks Julia - ----- Forwarded message ----- From: Julia Freeman <> To: <hph> Subject: CoC Impact assessment Dear Hans Peiter, I am writing on behalf of the diversity task force regarding the proposed improvements to the Ripe Code Of Conduct. There has been some confusion as to the next steps we need to take, and were hoping you could provide guidance on what should happen next. We have a draft version 3.0 of the CoC, based on feedback from various parties to a version 2.0 that was sent to ripe mailing lists in May. This version is below. https://docs.google.com/document/d/1yqOUPR02SONuSt812cuOBkk_xnhjYzjdk9qmsJk… It has been suggested that perhaps we should have RIPE NCC legal do an Impact Analysis on the code of conduct before it's fully adopted, but we are unclear the exact process required. Please can you advise, and if appropriate, request RIPE NCC Legal do an impact analysis on our proposed code of conduct. Yours Sinceerly Julia Freeman (On behalf of the Ripe Diversity Task Force) - ----- End forwarded message ----- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFdpAZh42M0lILkmGIRAvZ+AJ9YsTAHiIixOn2Hb8/5W3Fw90c7fACgm/rw /9FlobSIFhzmWbKfezyVops= =9udy -----END PGP SIGNATURE-----

1 0

Email to HPH
by Julia Freeman 09 Oct '19

09 Oct '19

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 At risk of writing an email by commmittee, below is my first draft of the email for HPH. I just wanna double check I've fully understood all the points we're asking before I hit send. Is the below what people had in mind that we should be asking? - ------ Dear Hans Peiter, I am writing on behalf of the diversity task force regarding the proposed improvements to the Ripe Code Of Conduct. There has been some confusion as to the next steps we need to take, and were hoping you could provide guidance on what should happen next. We have a draft version 3.0 of the CoC, based on feedback from various parties to a version 2.0 that was sent to ripe mailing lists in May. This version is below. https://docs.google.com/document/d/1yqOUPR02SONuSt812cuOBkk_xnhjYzjdk9qmsJk… It has been suggested that perhaps we should have ripe legal do an Impact Analysis on the CoC of conduct before it's fully adopted, but we are unclear the exact process required. Please can you advise. Julia Freeman (On behalf of the Ripe Diversity Task Force) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFdnbL342M0lILkmGIRAkYmAJwN7sL5JJCrgRqn6nMSebwIfacRugCfSakO 5+ZhyefOoVuIdaR6X97Ntlc= =WFrz -----END PGP SIGNATURE-----

2 1

Survey - "Have you ever experienced or witnessed harrassment, intimidation or any other unwanted behaviour while at a RIPE Meeting?"
by Denesh Bhabuta 08 Oct '19

08 Oct '19

Hi all Gearing up to the discussions we will be having around the new CoC draft (and the CoC Team), we would like to get an idea about the climate of unwanted behaviours our attendees have experienced or witnessed over the years. We have heard a lot of stories from people...but as we've never had a proper reporting channel to investigate/handle reports, it's hard to imagine the scope of the problem. We've also heard many people say "there is no problem." The intention for this survey is to illustrate why this work on the CoC is so important - to make the meetings safer. This is not a reporting tool - we are specifically asking people not to divulge any identifying remarks. Here is the link for the survey (anyone on the TF who would like to share their story may also do so): <https://www.surveymonkey.com/r/N6S5SJ3> Regards Denesh

8 10

Re: [diversity] Requesting Impact Analysis + Legal Review from the RIPE NCC on CoC 2.0
by Amanda Gowland 08 Oct '19

08 Oct '19

Oh dear Julia, that is awful!! Sorry to hear that. I will send you Hans Petter's email directly. Amanda On 08/10/2019 14:50, Julia Freeman wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Tue, Oct 08, 2019 at 09:04:24AM +0200, Amanda Gowland wrote: >> Hi Julia, >> >> Are you alright to email HPH on the question(s) about how to proceed? > Yes. I'll send a draft to the mailing list in the next few hours, then if > people are ok with it send it on to HPH. Can you confirm HPH's email > address so I know I'm sending it to the right place? > > I meant to do this yesterday, but crashed my bike on Saturday and spent > yesterday trying not to move. > > J > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.4 (GNU/Linux) > > iD8DBQFdnIYA42M0lILkmGIRAgXoAKC3p0qSx+bSopaC8GrAaq1dZRPk1QCeJgrF > 4Kgf9/ymCinS74BjpNgv+zo= > =MD5I > -----END PGP SIGNATURE----- >

1 0