- diversity - mailman.ripe.net

Call for Papers: Workshop on Analyzing IETF Data (AID), 2021
by Vesna Manojlovic 08 Sep '21

08 Sep '21

FYI -------- Forwarded Message -------- Subject: [RACI-list] Call for Papers: Workshop on Analyzing IETF Data (AID), 2021 Date: Wed, 8 Sep 2021 17:18:36 +0300 From: Lars Eggert <lars(a)eggert.org> Reply-To: aid-workshop-pc(a)iab.org To: raci-list(a)ripe.net

1 0

Fwd: Code of Conduct Task Force Session - 1 September
by Vesna Manojlovic 26 Aug '21

26 Aug '21

FYI Topic: Code of Conduct TF Time: Sep 1, 2021 16:00 Amsterdam Join Zoom Meeting https://ripe.zoom.us/j/91503459567?pwd=U0I0MHhLREhzNVp6MTdTVzBRalNrQT09 Vesna -------- Forwarded Message -------- Subject: [ripe-list] Code of Conduct Task Force Session - 1 September Date: Wed, 25 Aug 2021 15:45:25 +0200 From: Antony Gollan <agollan(a)ripe.net> To: ripe-list(a)ripe.net Dear colleagues, The Code of Conduct Task Force will hold a virtual session to get input from the RIPE community on its updated draft RIPE Code of Conduct on 1 September 2021 at 16:00 (UTC+2). You are invited to join this session and share your thoughts. The updated draft Code of Conduct is published here: https://www.ripe.net/publications/docs/ripe-documents/other-documents/ripe-… Information on the task force is available here: https://www.ripe.net/participate/ripe/tf/code-of-conduct-task-force The Zoom details for this session are below. Kind regards Antony Gollan Communications Team Manager RIPE NCC ======== Topic: Code of Conduct TF Time: Sep 1, 2021 16:00 Amsterdam Join Zoom Meeting https://ripe.zoom.us/j/91503459567?pwd=U0I0MHhLREhzNVp6MTdTVzBRalNrQT09 Meeting ID: 915 0345 9567 Passcode: 516980 Join by SIP 91503459567(a)zoomcrc.com Join by H.323 162.255.37.11 (US West) 162.255.36.11 (US East) 221.122.88.195 (China) 115.114.131.7 (India Mumbai) 115.114.115.7 (India Hyderabad) 213.19.144.110 (Amsterdam Netherlands) 213.244.140.110 (Germany) 103.122.166.55 (Australia Sydney) 103.122.167.55 (Australia Melbourne) 209.9.211.110 (Hong Kong SAR) 64.211.144.160 (Brazil) 69.174.57.160 (Canada Toronto) 65.39.152.160 (Canada Vancouver) 207.226.132.110 (Japan Tokyo) 149.137.24.110 (Japan Osaka) Meeting ID: 915 0345 9567 Passcode: 516980

1 0

Today: join "Open House" on Community Resilience: 14. July, 12AM CEST
by Vesna Manojlovic 14 Jul '21

14 Jul '21

Dear colleagues, we are inviting you to join a session about wellbeing, mental health, resilience and community care. We have all experienced the impact of COVID-19 on our social connections and with our mental health. Let's connect with each other, exchange experiences and tips, ask for help or offer a helping hand. The session will take place on 14 July 2021 at 12:00 - 13:30 CEST. Please register here: https://www.ripe.net/participate/meetings/open-house/ripe-ncc-open-house-ri… Kind regards, Vesna Manojlovic Community Builder RIPE NCC

1 0

Updated Draft Code of Conduct Published for Review
by Leo Vegoda 07 Jul '21

07 Jul '21

Dear RIPE community, As promised at RIPE 82, we have published an updated draft RIPE Code of Conduct. A clean text version of the document and a redline version, showing all the changes from the version published in March, can be found at: https://www.ripe.net/publications/docs/ripe-documents/other-documents/copy_… Please send comments in support of this draft, or asking for specific changes, to the RIPE Discussion List by 17 September 2021. The RIPE Chair will evaluate the community’s consensus based on comments made. Some of the key changes in this draft: - We have numbered the major sections and simplified some of the language - We have expanded the introduction to provide background on the discussion that led to the development of this document - We have added a new “Call to Action” section - We have clarified the language in the “Scope” section and removed the bulleted lists there - We simplified the subsection on law - We added a new subsection on aggressive behaviour in the “Behaviour” section - We added a section noting that reports that are not made in good faith, such as in retaliation for another report, can be rejected We have also published a RIPE Labs article about why we made the changes you’ll see in the new draft. https://labs.ripe.net/author/leo_vegoda/updated-draft-ripe-code-of-conduct/ We will hold a session with the community to discuss the changes, which has been scheduled for 1 September 2021. We recognise that it will not be possible for everyone to attend this webinar so it will be recorded and published, and we will release more information about the session nearer the time. Kind regards, Leo Vegoda for the Code of Conduct TF

1 0

Some examples from other communities about the procedures of the CoC-Teams
by Vesna Manojlovic 01 Jun '21

01 Jun '21

Here are some examples: Cultural Catalyst Lab (attached) TechInc hackerspace https://wiki.techinc.nl/Dispute_Procedure IETF (please find a link yourself) CCC (please find a link yourself) Another kind of example: Debian https://people.debian.org/~enrico/dcg/ch04s07.html#meta-links-cr And let's look at all the examples provided on this list, mostly by Sasha Romijn. Vesna

2 2

"Gender, Diversity and Inclusion in Open Source Communities"
by Vesna Manojlovic 25 May '21

25 May '21

Interesting article: *** Gender, Diversity and Inclusion in Open Source Communities *** Open source hides social hierarchies. There is no equal participation for all in reality. Women, people of diverse gender, racialised people and people with disabilities do not have the same opportunities to participate, although there are no formal barriers that explicitly deny them participation. https://www.genderit.org/feminist-talk/gender-diversity-and-inclusion-open-… (forwarded from another list: Digital Rights Community)

1 0

Re: [diversity] [ripe-list] Updated Draft RIPE Code of Conduct Published for Community Review
by Daniel Karrenberg 21 Apr '21

21 Apr '21

On 21 Apr 2021, at 12:57, Hans Petter Holen wrote: > my naïve view is that, if the ncc is an organiser, then the coc MUST > apply. > > > We strongly believe that all RIPE NCC-organised events should follow > the > same CoC, and we think this is something the community should be able > to > agree on. …. The RIPE NCC is of course free to make rules within its area of responsibility. I expect that this will happen in the RIPE tradition by consulting the communities along the lines Mirjam and Niall are setting out within this discussion and not by unilateral action on the part of the RIPE NCC. I hope that the RIPE NCC will be able to keep facilitating local and regional communities while respecting the local codes and customs. Very probably this discussion is another symptom of how the pandemic influences our discourse by preventing face to face, informal and group interactions. I apologise for my part in this. We may very well all pretty much agree. ;-) Daniel

1 0

Re: [diversity] [ripe-list] Updated Draft RIPE Code of Conduct Published for Community Review
by Daniel Karrenberg 21 Apr '21

21 Apr '21

That works forme. For the reasoning see my other message in this thread on the RIPE list. Daniel PS: In my reality the PC does not organise a meeting of its own and therefore has no role in determining things like which CoC applies. The PC has the responsibility for the program of *part of* the RIPE meeting which is organised by RIPE and chaired by our RIPE Chair. On 19 Apr 2021, at 18:50, Niall O'Reilly wrote: > Perhaps the following text would suit: > >> The RIPE NCC regularly organizes events for communities which are >> distinct from RIPE. When preparing for such an event, the RIPE NCC >> will ascertain whether the respective community has adopted the >> RIPE Code of Conduct and, if not, also ascertain which Code must >> be applied.

1 0

FYI: Research Paper: Representation is Not Sufficient for Selecting Gender Diversity
by Mirjam Kuehne 07 Apr '21

07 Apr '21

Hi all, You might find this research paper interesting. Kind regards, Mirjam *Representation is Not Sufficient for Selecting Gender Diversity* Representation of women and minorities in a “selectorate”—the group that chooses an organization's leaders—is a key mechanism for promoting diversity. We show that representation, on its own, is not sufficient for selecting gender diversity: a supportive organizational culture is also required. In the case of the Internet Engineering Task Force, a random increase in female representation in its selection committee caused an increase in female appointments only after cultural norms supporting diversity and inclusion became more salient. <https://www.nber.org/papers/w28649 <https://www.nber.org/papers/w28649>>

1 0

Updated Draft RIPE Code of Conduct Published for Community Review
by Leo Vegoda 02 Apr '21

02 Apr '21

Dear RIPE community, An updated draft RIPE Code of Conduct (CoC) is now published for your review. As this is intended to cover all participation within RIPE, it applies to interactions over the Internet, mailing lists, as well as in-person at RIPE Meetings. You can find the document here: https://www.ripe.net/publications/docs/ripe-documents/other-documents/ripe-… This draft keeps most of the text in v3.0[1], which was developed by the RIPE Diversity TF. It also draws from CoCs that are in use in other communities, including the Python CoC[2]. The biggest change is that the updated draft covers scope and behaviour only. It doesn’t touch on process or the CoC Team – these aspects will be addressed in two separate documents that are still to come. Please review the draft and share any comments on the RIPE Discussion List by Friday, 2 April 2021. We welcome suggested changes, but if you don’t see problems with the draft then statements of support are also helpful. The RIPE Chair Team will evaluate your comments and determine whether there is consensus on this draft or additional work is needed. While we would prefer comments to be shared on the RIPE Discussion List, we recognise that some people might have feedback that they would like to share in private. If you want to provide feedback in private you can contact members of the CoC TF or the RIPE Chair Team directly. Some key changes in this version: - The goal of “a neutral, transparent and open framework for report handling” has been removed and will be covered in the upcoming document that describes process. - The scope is defined as “all participation in RIPE.” - Groups and events with separate governance from RIPE may adopt this CoC but will need to manage their own implementation. - A new section covers how the CoC relates to national law. - A new section lists desired behaviours along with an updated list of unacceptable behaviours. - Both lists are arranged alphabetically, to avoid suggesting a hierarchy. We look forward to reading your thoughts on the current draft. Kind regards, Leo Vegoda On behalf of the RIPE Code of Conduct TF [1] RIPE Meeting Code of Conduct 3.0 - Draft https://www.ripe.net/participate/meetings/ripe-meetings/ripe-meeting-code-o… [2] Python Community Code of Conduct https://www.python.org/psf/conduct/

7 12