April 2021 - diversity - mailman.ripe.net

Fwd: Impact analisys of the new Code of Conduct
by Hans Petter Holen 01 May '24

01 May '24

I have requested an impact analisys from the RIPE NCC as requested by the task force. -hph ---------- Forwarded message --------- From: Hans Petter Holen <hph(a)oslo.net> Date: Sun, 20 Oct 2019 at 00:31 Subject: Impact analisys of the new Code of Conduct To: rna-exec(a)ripe.net Mailing List <rna-exec(a)ripe.net> Cc: Athina Fragkouli <athina.fragkouli(a)ripe.net> The diversity task force has published a draft of a new code of conduct (CoC). Before moving this forward I would like to request an impact assesment from the RIPE NCC for the community to understand if there is an impact on the RIPE NCC and if this impact can be accepted. https://www.ripe.net/participate/meetings/ripe-meetings/ripe-meeting-code-o… For the record, I would also like to point out that there is an existing code of conduct in place: https://www.ripe.net/participate/meetings/ripe-meetings/ripe-meeting-code-o… The new code of conduct does however specify how the Trusted Contacts (now Code of Conduct team) is appointed and outlines in more details what actions can be taken. It can be argued that all theese actions can be taken allready, by the Trusted Contacts, RIPE Chair, PC and RIPE NCC meeting organisers today, but the new CoC makes this explicit. Yours sincerely, Hans Petter Holen RIPE Chair -- -- Hans Petter Holen Mobile +47 45 06 60 54 | hph(a)oslo.net | http://hph.oslo.net -- -- Hans Petter Holen Mobile +47 45 06 60 54 | hph(a)oslo.net | http://hph.oslo.net

3 2

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