- diversity - mailman.ripe.net

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

Requesting Impact Analysis + Legal Review from the RIPE NCC on CoC 2.0
by Amanda Gowland 04 Oct '19

04 Oct '19

Hi all, So, an update... After speaking with RIPE NCC's legal team on next steps for the CoC, they advise that the Chair of this TF (which we don't have afaik) request an impact analysis and legal review of the RIPE CoC 2.0, which Brian shared on the ripe-list last May for comment: https://www.ripe.net/participate/meetings/ripe-meetings/ripe-meeting-code-o… Could someone (Brian, Shane or Denesh) email legal(a)ripe.net with the link above to request this and cc the TF? Now, prior to this info, I had been working (a lot) on adapting the 2.0 text to address the comments received here. I also felt that there was a lot of overlap between the CoC text and the CoC Team doc, so I merged them for clarity: https://docs.google.com/document/d/1yqOUPR02SONuSt812cuOBkk_xnhjYzjdk9qmsJk… This is a version I'd like you to comment on, hopefully we can move forward...I hope we've addressed the concerns about appeals. Happy for your feedback. Kind regards, Amanda

7 16

Relevant reading: The resignation of MIT's Richard Stallman and the danger of not speaking up
by Amanda Gowland 19 Sep '19

19 Sep '19

Hi all, In light of our discussions around the CoC and the Response Team doc (which is being checked by our legal team and I'll have their input by tomorrow FYI), I'd like to share this article that was forwarded to me today...about the resignation of Richard Stallman from CSAIL at MIT: <https://medium.com/@thomas.bushnell/a-reflection-on-the-departure-of-rms-18…> One line from the author really stood out for me:    "But at the time I didn’t put that together with what it would be like for women who were weirded out or alienated, who felt threatened, etc." ...and I would like to ask that everyone in this community and on this list think on that for a moment. If we don't insist on a safe and inclusive space for *everyone* at RIPE Meetings, we can't have a safe space for *anyone*.   The article references the original 'whistle blowing' article: <  https://medium.com/@selamie/remove-richard-stallman-fec6ec210794> Amanda

1 0

*draft* CoC Team doc
by Amanda Gowland 02 Sep '19

02 Sep '19

Hi all, Please find attached a draft proposal for the CoC Team: https://docs.google.com/document/d/1yqOUPR02SONuSt812cuOBkk_xnhjYzjdk9qmsJk… I used Sasha's draft as the framework for the doc, just adding/editing where necessary. There are some to-be-determined factors, mainly: - How long should a term be for volunteers? - How many people (minimum, maximum) should we aim for? - What is the time-frame for response (e.g. how long would a reporter need to wait for a confirmation of receipt from the team?) Please add your comments. Kind regards, Amanda

12 24

RIPE Code of Conduct 2.0
by Daniel Karrenberg 29 Jul '19

29 Jul '19

Summary: - It is good that the draft gives examples of unacceptable behavior. - It is a real bad idea to create a special enforcement committee. - The draft should encourage anyone in the community to actively intervene when they observe unacceptable behavior. - It would be better to continue the current system of trusted contacts and empower them more. -------- Full disclosure: I have participated in RIPE for 30 years and attended 76 RIPE meetings as well as numerous other meetings organised by our community. During these 30 years there were some times when I have not behaved in an exemplary manner; a few of those times I would have run afoul of this draft code of conduct. With the help of people from this community I have been able to realise my behavior was not appropriate, to apologise and to make amends. Despite these missteps I feel that I have contributed positively to the development and success of the RIPE community. I have also experienced some inappropriate behavior towards myself over the years and dealt with it appropriately, again with the help of people from this community. I welcome the part of this draft that describes examples of inappropriate behavior and states clearly that we as a community do not tolerate it. This is an improvement over the current code. I am very deeply concerned about the part of this draft that creates a very vaguely described 'enforcement committee' without any responsibility to anyone and without any process whatsoever. Adopting this part of the code would be a disaster for the credibility and standing of RIPE all by itself but even more so by inviting our antagonists to use it as a vehicle to harm us. RIPE is not a conference but a community that with a significant governance aspect. We argue in favor of our self governance by pointing to RIPE, its openness and its low threshold to participation. This requires that anyone interested can participate meaningfully in RIPE. Excluding people from RIPE will be very bad; doing so without a clear process and a hearing will be a disaster! We should remove this language from the draft completely. Instead, I suggest to a call on everyone in the community to actively intervene when they observe inappropriate behavior and to help all parties concerned to resolve the situation. The language should make it clear that such interventions are positive and welcomed by the RIPE community. I realise that it requires courage to act. We should encourage people and not give them further excuse to look away by putting emphasis only on a specific formal mechanism. I suggest to maintain the current system of trusted contacts for reporting violations and add that staff and volunteers such as chairs and PC are also available. Where, by the way, is the evidence that this is not sufficient? Maybe the trusted contacts can provide some sort of transparency report to us? Further I recommend to develop a response plan that defines who is responsible to take action in cases where individuals do not stop inappropriate behavior once it is pointed out to them. These responsibilities do exist today within our governance structure. They are shared between RIPE, RIPE NCC and third parties such as the owners/operators of our venues. Maybe this needs to be clarified and we may need to establish roles within these structures that are responsible to follow up on any actions. But let us not create a new committee whose sole purpose is to sanction community members without any process! Before we know it this will lead its own life. We should also make it clear that we do not tolerate any abuse of the code of conduct itself. I realise that can be interpreted as off-putting. However it is an essential part of such a code. In case the TF wishes to act on my suggestions regarding the draft, I am very much willing to help with creating new text. Sincerely! Daniel

7 14

Fwd: [systers] IETF 105 Female Attendance
by Mirjam Kuehne 26 Jul '19

26 Jul '19

Hi, FYI some numbers from the IETF meeting this week. Mirjam -------- Forwarded Message -------- Subject: [systers] IETF 105 Female Attendance Date: Fri, 26 Jul 2019 09:49:58 -0400 From: Jasmine Magallanes <jmagallanes(a)amsl.com> To: systers(a)ietf.org Hello Systers, As requested, please see the female to male ratio below for IETF 105. Please note that not everyone fills out the gender field on their registration. Here is the best information we have to date. Female onsite attendance: 125 Male onsite attendance: 864 Overall, about 11% of our community identified as female this meeting. Thank you! Regards, Jasmine Magallanes Project Coordinator Direct +1 510-492-4086 Fax +1 510 492-4001 --------- Association Management Solutions Forum Management, Meeting and Event Planning Website: http://www.amsl.com _______________________________________________ systers mailing list systers(a)ietf.org https://www.ietf.org/mailman/listinfo/systers

1 0

Article on RIPE Labs re: Neurodiversity (and Slido)
by Amanda Gowland 26 Jun '19

26 Jun '19

Hi all, I wanted to share some background behind our motivation to pilot Slido at RIPE 78: https://labs.ripe.net/Members/agowland/the-microphone-is-the-devil-some-kno… And also, if you appreciated/support that we continue to use such a tool, now is the last chance to submit feedback on the RIPE 78 Feedback Survey: https://ripe78.ripe.net/feedback/ Many thanks, Amanda

5 5

Article on "Trying to be a better man"
by Mirjam Kuehne 25 Jun '19

25 Jun '19

Hi, I came across this article: https://medium.com/@rafi0t/on-trying-to-be-better-men-227d2aad6670 It's already from 2017, but still quite timely. FYI, here is the code of conduct of a security conference I attended last week: https://www.first.org/about/policies/code-of-conduct I don't think they have a team to enforce this. It's done by the FIRST board. Mirjam

1 0

Exposing the Bias Embedded in Tech - NYTimes
by Amanda Gowland 18 Jun '19

18 Jun '19

Hi all, There was a great article in the NYTimes yesterday and this quote pretty much sums up why we're doing what we're doing: “But what I always think the way to turn anything around is to shine a light on it. You keep the light on there until the data surfaces, and then you have to find a way to fix it. It’s not a ‘check the box and move on, everyone take unconscious bias training and we’re all good now.’ You have to keep at it, keep at it, keep at it.” https://www.nytimes.com/2019/06/17/business/artificial-intelligence-bias-te… <https://www.nytimes.com/2019/06/17/business/artificial-intelligence-bias-te…>

1 0