- diversity - mailman.ripe.net

Fwd: [ripe-list] RIPE Code of Conduct - Call for volunteers
by Mirjam Kühne 09 Sep '20

09 Sep '20

Hi all, I am not sure this mail made it to the Diversity list yesterday. Kind regards, Mirjam > Begin forwarded message: > > From: Mirjam Kühne <mir(a)zu-hause.nl> > Subject: [ripe-list] RIPE Code of Conduct - Call for volunteers > > Date: 8 September 2020 at 14:43:29 CEST > To: <ripe-list(a)ripe.net> > Cc: "Niall O'Reilly" <niall.oreilly(a)ucd.ie>, <diversity(a)ripe.net> > Reply-To: Mirjam Kühne <mir(a)zu-hause.nl> > > Dear colleagues, > > The Diversity Task Force has put a lot of work into updating the current RIPE Code of Conduct. They put together a series of draft documents that were then reviewed by the community. The most recent version 3.0 can be found here: > https://www.ripe.net/participate/meetings/ripe-meetings/ripe-meeting-code-o… > > During the RIPE 80 community plenary, Hans Petter Holen described what he views as the best way forward to finalize the updated RIPE Code of Conduct and we would like to follow the process he laid out during his presentation. > > The main idea is to split the current draft document into three individual documents and to review each of them separately: > 1. The Code of Conduct > 2. The selection of the Trusted Contacts or Code of Conduct team > 3. Procedures for the team > > We are now looking for volunteers to finalize this set of documents. During RIPE 80 three community members already offered their help. If you are still interested, please let us know. This of course also applies to anyone who would like to help and has not yet put their name forward. Please contact us before 15 September 2020. > > ———— > More Background and current status: > > The existing RIPE Code of Conduct and the Trusted Contacts: > https://ripe81.ripe.net/attend/coc/ > > Draft 3.0 of the new RIPE Code of Conduct: > https://www.ripe.net/participate/meetings/ripe-meetings/ripe-meeting-code-o… > > During the last review round, the RIPE NCC conducted an impact analysis that can be found here: > https://www.ripe.net/participate/meetings/ripe-meetings/impact-analysis-for… > > The relevant part of Hans Petter’s presentation at RIPE 80: > https://ripe80.ripe.net/archives/video/384/ > https://ripe80.ripe.net/wp-content/uploads/presentations/58-RIPE-Code-of-Co… > > Kind regards, > Mirjam & Niall > =========== > > P.S.: I (Mirjam) used to be one of the trusted contacts together with Rob Evans and Vesna Manojlovic, but stepped down from this position when I started my new role as RIPE Chair.

1 0

WISE : gender balance in science, technology and engineering
by Vesna Manojlovic 04 Sep '20

04 Sep '20

Hi, I've just heard about the "WISE", Women into Science and Engineering, an organisation in UK: "the campaign for gender balance in science, technology and engineering, from the classroom to the boardroom" https://www.wisecampaign.org.uk/ They say: "The correlation between improved diversity and stronger business results is striking. " https://wisecampaign.scdn3.secure.raxcdn.com/wp-content/uploads/2019/09/Why… Among other things, they offer webinars. This one is for free / available to everyone: Wed, Sep 9, 2020 12:00 PM - 12:45 PM CEST "WISE Young Professionals Board, a group of diverse, relatable professionals who lead initiatives to inspire, engage & advocate for the next generation of STEM. We also support, develop and challenge the WISE Campaign. With applications for the 2021 board opening in September we wanted to introduce you to a few of us, share what we do, and answer any questions you may have. " https://register.gotowebinar.com/register/670351757158593039 And on 23rd September (only for members) : WISE’s Ten Steps programme is a cultural transformational framework created for WISE Members. The programme includes a diagnostic to establish your starting point and measure progress... Etc. Something to consider... ... if you are a company in UK, you might want to become a member ... if you are looking for new employees: https://jobs.wisecampaign.org.uk/ ... if you are a woman in STEM, profile yourself here: https://www.wisecampaign.org.uk/1ofthemillion Quite interesting read for the upcoming weekend... Ciao, Vesna

1 0

Fwd: RIPE NCC Community Projects Fund - Call for Applications 2020
by Vesna Manojlovic 28 Jul '20

28 Jul '20

FYI -------- Forwarded Message -------- Subject: [RACI-list] RIPE NCC Community Projects Fund - Call for Applications 2020 Date: Tue, 14 Jul 2020 10:54:00 +0300 From: Gergana Petrova <gpetrova(a)ripe.net> To: raci-list(a)ripe.net Dear colleagues, Are you working on or planning a non-commercial project that would benefit the Internet or the RIPE community? Apply for funding via the RIPE Community Projects Fund by 23 August: https://ripe.net/cpf For more than 25 years, the RIPE NCC has been supporting activities and projects for the “Good of the Internet”. Community-driven, non commercial work has been fundamental to the success of the Internet from its earliest days, and continues to play an important role in making the Internet resilient, secure and accessible for everyone. Under the RIPE NCC Community Projects Fund, the RIPE NCC will provide up to EUR 250,000 per year to support projects of value to the operation, sustainability and resilience of the Internet, with a focus on tools and services benefitting the technical community in the Europe, the Middle East and Central Asia. Apply now to get your project funded! If you or your organisation is working on a new or existing project that fits the criteria below, and need some financial support to get it off the ground or keep it going, we want to hear from you! Is your project of benefit to the Internet, particularly the RIPE community? Is your project non-commercial in nature? Do you have a clear project plan and timeline? A few things to keep in mind: - Funding may be used to purchase equipment, but this cannot be the sole expenditure - Funding cannot be used for humanitarian aid, donations, or to encourage political reform - Funding cannot be used to provide scholarships or cover tuition fees - Funding cannot be used to support any form of commercial activity If you have any questions about applying, write to us at cpf(a)ripe.net. Best regards, Gergana -- Gergana Petrova External Relations RIPE NCC _______________________________________________ RACI-list mailing list RACI-list(a)ripe.net https://lists.ripe.net/mailman/listinfo/raci-list

1 0

Fwd: [ripe-list] RIPE Chairs Selected
by Vesna Manojlovic 02 Jul '20

02 Jul '20

\o/ First time in history of RIPE: a woman is a Chair Person! Congrats, Mirjam!! V -------- Forwarded Message -------- Subject: [ripe-list] RIPE Chairs Selected Date: Thu, 02 Jul 2020 12:54:37 +0200 From: Daniel Karrenberg via ripe-list <ripe-list(a)ripe.net> Reply-To: Daniel Karrenberg <chair(a)ripe-nomcom.org> To: RIPE List <ripe-list(a)ripe.net> Dear colleagues, The RIPE 2020 NomCom has selected Mirjam Kühne as RIPE Chair and Niall O'Reilly as RIPE Vice Chair. After interviewing all nominees, hearing substantial input from the community and a thorough discussion during three selection meetings all voting members voted to select Mirjam as Chair and eight out of ten voting members voted to select Niall as Vice Chair. The selection was subsequently supported unanimously by all members of the committee. We closely followed the process spelled out in ripe-727 and ripe-728. We regularly paused to confirm that the whole committee was comfortable with the process and its progress. We were able to choose from a set of nominees who are all very capable and well respected in the community. We expect that the community would support any of them as their Chair. Our selection is in no way a negative statement about the nominees we did not select. We selected Mirjam because the input from the community clearly favoured her. She is very widely regarded as someone who listens carefully to everyone and who helps the community to find consensus and move forward. We selected Niall because of the positive input we received about his track record with the community. Mirjam and Niall convinced us that they would work well as a team and complement each other. The RIPE NCC board has confirmed the candidates in accordance with the process set out in ripe-727. The original time line called for a transition from Hans Petter to Mirjam and Niall during RIPE 81 in October. Hans Petter has since resigned as RIPE Chair because he accepted to be the new managing director of the RIPE NCC; he is currently also serving as RIPE Chair ad-interim. In this situation it makes little sense to stick to the original time line. Therefore we suggest that the outgoing and incoming Chairs arrange the transition among themselves as soon as practicable. We plan to publish the NomCom report about this first run of the selection process in September before our term ends at RIPE 81. We expect to make suggestions for improving the process and look forward to the community discussing and deciding the process for the next iteration. We thank everyone who supported the NomCom, especially all nominees and the many members of the community who made time to give us their input. Finally we call on the whole community to welcome and support Mirjam and Niall in their new roles! Daniel Karrenberg - Chair - RIPE 2020 Nomcom

1 0

(long) Equity & Justice, Diversity & Inclusion in the post-covid remote work & conferencing
by Vesna Manojlovic 23 Jun '20

23 Jun '20

Dear all, personally, I have been privileged to ease through this pandemic (for now) and to overcome the multiple crisis-es unfolding on all the levels: health scare, childcare during lockdown, remote work, no visits to friends & relatives... while other, less fortunate people had it worse. Since the "Diversity Task Force" aims to remove barriers that prevent participation in RIPE Community, particularly those that affect underrepresented groups, we can learn from the plenty of new sources that published either the tips & recommendations, or the analysis, or the news stories about problems/issues. I've collected many resources and I wanted to share them with you, in the hope that we can use them for our own progress. I would love to join your project, if you are working on the concrete ways to address any of these issues: please let me know how! Regards, Vesna 0. "THE TIME’S UP GUIDE TO Equity and Inclusion During Crisis" (attached) https://timesupfoundation.org/work/equity/guide-equity-inclusion-during-cri… 1. Subtle, unconscious biases that hinder inclusion & justice World Economic Forum: https://www.weforum.org/agenda/2020/04/how-to-achieve-gender-equality-after… 1. The quantity of jobs available 2. The quality of work (wages and access to social protections) 3. Outsized effects on the most vulnerable employees (namely women) https://yourstory.com/herstory/2020/04/work-home-discussions-gender-diversi… 2. Power Dynamics, Power Inequalities https://afsee.atlanticfellows.org/events/lockdown-is-a-luxury & specific tips for virtual conferences: https://wiki.techinc.nl/User:Becha/COVID-19#Virtual_Events_aka_Remote_Confe… 3. Social Gender Inequalities * 29.5. https://www.theguardian.com/global-development/2020/may/29/we-are-losers-in… * 29.4. https://us.boell.org/en/2020/04/30/invisible-coronavirus-makes-systemic-gen… * 29.3. https://theconversation.com/return-of-the-1950s-housewife-how-to-stop-coron… * 16.3. https://www.theguardian.com/us-news/2020/mar/16/womens-coronavirus-domestic… https://en.unesco.org/news/mapping-online-articles-covid-19-and-gender Pay Gap https://www.project-syndicate.org/commentary/covid19-pandemic-gender-differ… https://www.nytimes.com/2020/03/31/us/equal-pay-coronavirus-economic-impact… https://www.theatlantic.com/international/archive/2020/03/feminism-womens-r… Child-care gender gap https://www.nytimes.com/2020/05/06/upshot/pandemic-chores-homeschooling-gen… https://www.bloomberg.com/news/articles/2020-03-11/coronavirus-will-make-ge… "We need business communities and governments to respond to the crisis in a way that not only considers girls and women but that also helps to transform unequal gender relations. In the immediate term, this means ensuring girls and women have equal voice and power in planning and executing crisis response, improving pay and conditions for key workers and caregivers, expanding access to social protection and benefits including paid leave and immediate cash grants, and applying tough conditions to corporate bailouts to ensure worker benefit. It also means recognizing that different groups, including girls and women from minority backgrounds and those with disabilities, are more likely to be disadvantaged." https://www.usnews.com/news/best-countries/articles/2020-04-06/commentary-c… 4. Racial Gap All of the above inequalities are also present on the "racial" scale. https://wiki.techinc.nl/User:Becha/COVID-19#Racial_Inequality 5. Sustainability There is an "intersection" between all of these topics & climate: https://wiki.techinc.nl/User:Becha/COVID-19#Sustainability_Links 6. Working From Home In general, WFH is mentally difficult for everyone, regardless of all the other systematic inequalities I just mentioned. So we will all have to learn many new behaviors and create new habits of productivity, team-building, communication and mutual care. Here are some practical tips: https://www.vox.com/recode/2020/4/14/21211789/coronavirus-office-space-work… https://www.wsp.com/en-GB/insights/office-vs-home-working-how-we-can-save-o… https://www.theatlantic.com/ideas/archive/2020/05/never-go-back-office/6118… & more: https://wiki.techinc.nl/User:Becha/COVID-19#Working_From_Home Regards, Vesna

1 0

Invitation to N2Women event @ IEEE ICC 2020 on June 7, 2020
by Vesna Manojlovic 04 Jun '20

04 Jun '20

FYI -------- Forwarded Message -------- Subject: [n2women] Invitation to N2Women event @ IEEE ICC 2020 on June 7, 2020 Date: Wed, 3 Jun 2020 08:25:58 +0200 From: Katia Jaffrès-Runser <kjr(a)ENSEEIHT.FR> Reply-To: N2Women <n2women(a)ACM.ORG>, Katia Jaffrès-Runser <kjr(a)ENSEEIHT.FR> To: n2women(a)ACM.ORG Dear all, We are happy to invite you to an interactive panel discussion with distinguished panelists from academia and industry who will share their knowledge and valuable experiences of their research career with us. Topic - *Women in Technological Research: Winning the Uphill Battle* * *Panelists - 1. *Andrea Goldsmith*, Professor, Stanford University 2. *Muriel *Médard, Professor, MIT 3. *Jennifer Rexford*, Professor, Princeton University 4. *Ruoyi Zhou*, Director, IBM Research, Ireland 5. *Alessandra Sala*, Head, Analytics Research, Nokia Bell Labs Date: *Sunday, June 7, 2020* Time: *2:00 pm – 3:30 pm (Dublin Time)* Please find the flyer for this event *here <https://drive.google.com/file/d/1iUFbbVyuFi9isGYifuvJev8noqtJpFq8/view?usp=…>*. Everyone is welcome to join us! Please RSVP *here <https://forms.gle/jiTsryzmY6Tv5nku8>*. Event Zoom Meeting Link - https://us02web.zoom.us/j/87502114336 The event link will also be made available on the IEEE ICC 2020 virtual platform. Organized by: Aishwariya Chakraborty, PhD Scholar, IIT Kharagpur, India Faculty Mentor: Prof. Michele Nogueira, Federal University of Paraná, Brazil Please do attend! For more information, please contact aishwariyach(a)iitkgp.ac.in <mailto:aishwariyach@iitkgp.ac.in>. Thanks and regards, Aishwariya Chakraborty

2 1

RIPE 80 going virtual. testing new waters for diversity-tf?
by Ruben van Staveren 20 Mar '20

20 Mar '20

Dear all, RIPE80 going virtual was a difficult but a good choice, and allows to test new waters. I don’t know how the format is going to be, but it could attract people who normally wouldn’t go to these meetings for any reason whatever, and we might want to cater for them. For instance, getting Slido or equivalent back for questions, closed captioning, and benchmarking the online part of the CoC to name a few. This is not an extensive list but a few things that came into mind. Best Regards, and stay safe - Ruben van Staveren

1 0

Impact assesment for the code of conduct
by Hans Petter Holen 26 Feb '20

26 Feb '20

The Impact assessment from the RIPE NCC has been published as a link at the top of the page: https://www.ripe.net/participate/meetings/ripe-meetings/ripe-meeting-code-o… I would like to thank the RIPE NCC and the RIPE NCC Executive board for providing this assessment. It would be great if the chair(s) of the task force could make an action plan to address the issues raised in the impact assessment and previously on the list. I have some ideas I am happy to share with you on this. PS: apologies for losing track of who is chairing the diversity task force, but it is not listed on https://www.ripe.net/participate/ripe/tf/ripe-diversity-task-force -- Sincerely, Hans Petter Holen - hph(a)oslo.net - +47 45066054

3 3

Draft new Code of Conduct - comments, suggestions
by Gordon Lennox 02 Feb '20

02 Feb '20

There are some, quite separate, points I would like to make about the current draft Code of Conduct. Sorry it has taken me a bit of time since the last meeting. What some call “real life” sort of got in the way. But maybe this will contribute a little to some discussion before Berlin. 1) The level of churn when it comes to actual participation in RIPE meetings is significant. Around 25%, and some times more, attendees identify as first-timers. We cannot expect those people to have read any agreed CoC. We might also have reasonable doubts about regulars. Many of us have seen that people in the wider technical Internet community, while quite capable of travelling half-way round the world and even getting into the relevant WG session on time, still too often have not read the relevant Internet Drafts. So do we have to tick-a-box on registration saying we are aware of the CoC? We know it is a waste of time asking if people have actually read the CoC. Just like any license agreement. Do we need a the equivalent of the IETF ”Note well” slide that is sort of repeated during the week? I am not sure how far this has to go. But I do feel that merely having a CoC somewhere on a website may not be enough. 2) The diversity angle. I understand why this effort is coming from the Diversity TF. I have learned things from reading the mail archive. And that has also made me reevaluate incidents from the past. There were things that happened in Madrid in particular that I did not appreciate. I therefore understand the desire to have a formalised CoC. At the same time I do not see why a person needs to be associated with a “minority”, either in terms of self-identification or in terms of some community perception, so that they can be afforded the protections of such a CoC. Your ethnicity or gender or sexual orientation or whatever cannot be a necessary starting point before showing that something nasty happened. The CoC has to be inclusive. It ought not be about protecting those people on that side of the room from those on the other side of the room. There are two important paragraphs in the current draft that refer to behaviour that will not be tolerated. To be clear: the two paragraphs start with “Any behaviour or actions…”. I suggest that the order of those two paragraphs be reversed. 3) The process. A few points. ** There is mention of requiring a “public apology”. While that may be useful if the behaviour was “public” it may not always be so. An apology to the person concerned, in the presence of CoC Team members, may sometimes be more appropriate. Or even an apology in front of the group that witnessed the incident(s). ** I think the use of the word “immediately” - “Participants are expected to comply “immediately….” - may be a little excessive, too severe a constraint. By that point a conversation is underway. We should not unduly curtail that conversation. ** There is mention of contacting the CoC Team by mail and there is also mention of records being kept. None of this ought to be permanent. I am fully aware that once certain items are out there it is nigh on impossible to delete them. But NCC cannot hold records of accusations, accusations which may not even be followed-up for whatever reason, forever. Even if an incident is reported and processed and there is a satisfactory conclusion then that story has to become irrelevant at some stage. In addition maintaining a permanent record may mean a permanent liability. I would naturally initially defer to the NCC lawyers for words to deal with this. Gordon

1 0

Re: [diversity] Impact analisys of the new Code of Conduct (Sasha Romijn)
by Antony Gollan 17 Jan '20

17 Jan '20

Dear Sasha, (Replying on Athina's behalf, as she is out of the office today.) We have just about finished our analysis, though with the Christmas break next week it will likely be early in the new year that we are ready to publish. Apologies for the delay - this has been an exceptionally busy period in the office. We hope you can bear with us just a little longer. Regards Antony

3 2

Report about N² Women event on RIPE Labs
by Mirjam Kuehne 20 Dec '19

20 Dec '19

Hi, Martine Sophie Lenders published an article on RIPE Labs describing her experiences organising a Networking Networking Women (N² Women) event: https://labs.ripe.net/Members/martine_sophie_lenders/networking-networking-… Kind regards, Mirjam Kühne RIPE NCC

1 0

Fwd: Impact analisys of the new Code of Conduct
by Athina Fragkouli 16 Dec '19

16 Dec '19

Dear Hans Petter, Thank you for the request. The RIPE NCC will do a full Impact Analysis of the version 3.0 CoC including a full legal review. We expect to complete this in the coming 3-4 weeks. Comments and input on the version 2.0 were given internally in an effort to explain certain legal aspects of the draft, but this will be the first full impact analysis. To avoid us needing to do an impact analysis on a newer version, we would ask that further input and comments are incorporated into the 3.0 version after we conduct the impact analysis. This might make things easier for us and for the Task Force. Kind regards, Athina Fragkouli Chief Legal Officer RIPE NCC > > -------- Forwarded Message -------- > Subject: [diversity] Fwd: Impact analisys of the new Code of Conduct > Date: Sun, 20 Oct 2019 00:32:00 +0200 > From: Hans Petter Holen <hph(a)oslo.net> > Reply-To: hph(a)oslo.net > To: diversity(a)ripe.net <diversity(a)ripe.net> > > > > 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 <mailto:hph@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 <mailto:rna-exec@ripe.net> Mailing List > <rna-exec(a)ripe.net <mailto:rna-exec@ripe.net>> > Cc: Athina Fragkouli <athina.fragkouli(a)ripe.net > <mailto:athina.fragkouli@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 > <mailto:hph@oslo.net> | http://hph.oslo.net > -- > -- Hans Petter Holen Mobile +47 45 06 60 54 | hph(a)oslo.net > <mailto:hph@oslo.net> | http://hph.oslo.net

2 1

Towards a more inclusive community
by Job Snijders 22 Nov '19

22 Nov '19

Dear all, I've been observing various efforts towards constructing a safe and inclusive environment both at RIPE meetings and our online platforms. I appreciate these efforts, however, I have some concerns with the process and our ability to execute. A careful observer may see that the next generation of Internet engineers is not quite like the current establishment. I believe this diversity needs to be acknowledged in our policies. We owe it to them to create an environment that contributes to their comfort and well being. I recorded some thoughts on my way to RIPE - https://youtu.be/6_dLgcfv8kU Kind regards, Job

12 14

Re: [diversity] [address-policy-wg] cultural idioms in RIPE discussions
by JORDI PALET MARTINEZ 01 Nov '19

01 Nov '19

Diversity? (in copy) El 1/11/19 13:50, "address-policy-wg en nombre de Brian Nisbet" <address-policy-wg-bounces(a)ripe.net en nombre de brian.nisbet(a)heanet.ie> escribió: I'm sure it will shock absolutely nobody if I say that I think this conversation is very important. Maybe AP-WG isn't the best place, but I'm not sure where is? I think it is useful to all of us to realise that our cultural references are not everyone else's, because of language or country or age or one of many other things. We can no longer just assume a shared set of references and we should look to inform (and hopefully share the awesomeness that is Monthy Python, for instance) and expand. I mean, how long will it be before WG Chairs start to talk about yeeting proposals into or out of WGs? 😊 I'm not, for one second, suggesting people shouldn't use references, I use them all the time, but I am saying that those who use them should be understanding when others don't get them. Thanks, 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 > -----Original Message----- > From: address-policy-wg <address-policy-wg-bounces(a)ripe.net> On Behalf > Of JORDI PALET MARTINEZ via address-policy-wg > Sent: Friday 1 November 2019 12:38 > To: Jim Reid <jim(a)rfc1035.com> > Cc: RIPE Address Policy WG List <address-policy-wg(a)ripe.net> > Subject: Re: [address-policy-wg] cultural idioms in RIPE discussions > > Hi Jim, > > Despite how many years I've been participating, I still have (sometimes) > difficulties, and often talking with other non-native English speakers they tell > me the same. We know that not everybody is happy to express that in a list. > > I'm not convinced "common-sense" is such simple thing! Otherwise, either > I'm really stupid, or I should have cached the reference in a more humoristic > way. > > I don't think we can compare our technical jargon with such kind of > references, especially because not everybody (as it is my case) follows > "Monty Python, Star Wars, Star Trek, H2G2, etc.". Precisely because I often > heard those references, I decided today, to ask for a clarification! I've missed > a lot of fun, I guess! > > I didn't respond to the first email because, sometimes, when a thread is > moving fast in the list, you just respond to the last email that you read. Not > sure if that's a broken way, but I do sometimes. > > Regards, > Jordi > @jordipalet > > > > El 1/11/19 13:27, "address-policy-wg en nombre de Jim Reid" <address- > policy-wg-bounces(a)ripe.net en nombre de jim(a)rfc1035.com> escribió: > > > > > On 1 Nov 2019, at 11:14, JORDI PALET MARTINEZ via address-policy-wg > <address-policy-wg(a)ripe.net> wrote: > > > > My point was also a general observation (not something against any > specific participant, just taking advantage of this specific example, as a > mention to "Spanish inquisition" and "routing police" could be interpreted in > between lines as something different, even if not intended). > > Jordi, your comment is a reasonable one. But it misses the point. In this > case, your common sense should have told you the earlier remark wasn't a > literal reference to the Spanish Inquisition. > > The RIPE/tech community habitually uses references to a variety of idioms > from popular culture in films, TV, books and songs. Using catchphrases from > Monty Python, Star Wars, Star Trek, H2G2, etc. are very common. That's > gone on for decades. These phrases might well confuse non-native English > speakers at first. Or (say) an English speaker who haven't seen Star Wars. > However people soon pick up these references, just like we all learn the > industry jargon -- route flapping, prefix filtering, trust anchors, ROA, PI > address space, etc -- that probably doesn't translate well into other > languages. That sort of understanding becomes almost automatic for those > who have been active in these communities for a while. > > To be honest Jordi, I'm surprised you said you were confused. Since you've > been coming to RIPE/IETF/ICANN meetings for longer than I can remember, > this couldn't possibly have been the first time you've come across a Monty > Python reference. > > And if you were confused, you could have said so at the time and asked > the original poster to explain. I think that's a far better way to handle things. > It's certainly far more productive than starting this meta-discussion or telling > others how they should express themselves. > > > > > > > > > ********************************************** > IPv4 is over > Are you ready for the new Internet ? > http://www.theipv6company.com > The IPv6 Company > > This electronic message contains information which may be privileged or > confidential. The information is intended to be for the exclusive use of the > individual(s) named above and further non-explicilty authorized disclosure, > copying, distribution or use of the contents of this information, even if > partially, including attached files, is strictly prohibited and will be considered a > criminal offense. If you are not the intended recipient be aware that any > disclosure, copying, distribution or use of the contents of this information, > even if partially, including attached files, is strictly prohibited, will be > considered a criminal offense, so you must reply to the original sender to > inform about this communication and delete it. > > > > ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.

1 0

Slido discontinued?
by Ruben van Staveren 25 Oct '19

25 Oct '19

Hi, To my surprise Slido wasn’t continued from its pilot in RIPE78 Are there any plans to bring it, or equivalent, back? Regards, Ruben

1 0

Code of Conduct
by Hans Petter Holen 22 Oct '19

22 Oct '19

Thanks for the hard work with the next version of the code of conduct. Special thanks to Brian and Sahsa for presenting the work. Now the final challenge is to establish consensus. This means identifying remaining issues and address them. (This does not mean that all can be solved, but we should aim to document why they are not solved at this point.) I have done a quick analisys of the differences between the existing code of conduct and the new code of conduct. https://www.ripe.net/participate/meetings/ripe-meetings/ripe-meeting-code-o… and https://www.ripe.net/participate/meetings/ripe-meetings/ripe-meeting-code-o… The main text: « For over a quarter of a century, the RIPE community's strength comes from its breadth of experience, diversity of views, and an open, respectful exchange of ideas – values that we want all of our RIPE Meeting attendees to uphold.» Is the same in the two documents. In the old code of conduct it continues: « Please treat each other with tolerance and respect. Free speech and an open exchange of ideas are encouraged and celebrated. Demeaning, intimidating or harming anyone at the meeting is wrong. We are especially sensitive to behaviour that offends based on gender, sexual orientation, religion, race or ethnic origin, or other perceived social, cultural, or personal differences.» This has been removed from the new Coc, at least from the Intro. Is this deliberate? In the old code of conduct, there are currently 3 trusted contacts, selected by the RIPE chair without any documented process. In the new version the trusted contacts has been renamed to a CoC team of 4 to 6 and with a process on how the RIPE Chair selects the As for consequences the existing CoC only states « Please be aware that attendees violating the RIPE Meeting Code ofConduct may be asked to leave the meeting without a refund and other actions may be taken as deemed necessary.» In the new version there is a much more detailed list. It goes one step further on two areas: * Ban from future meetings is explicitly stated (which I would argue could happen under the existing CoC too) * Removing content from presentations on the meeting web. Here the PC has taken a very principal possition that the submitted presentation will be published as presented. Appeals is not at all covered in the existing CoC but is specified in the new version. While this is a very quick and high level analisys, I am thinking of publishing my thoughts on this, but would like your input before I do so. -hph -- -- Hans Petter Holen Mobile +47 45 06 60 54 | hph(a)oslo.net | http://hph.oslo.net

9 15

some thoughts on draft code of conduct 3.0
by Joe Abley 22 Oct '19

22 Oct '19

Hi all, I have read the draft code of conduct published at <https://www.ripe.net/participate/meetings/ripe-meetings/ripe-meeting-code-o…> and have written down some comments, as requested. Some context: I do not personally feel like I am in an under-represented group of any kind. Despite being a serial immigrant in an entirely technical sense, I have never felt systemically under-represented, oppressed or threatened in my life. I think this makes me fortunate, since oppression is surely not something to wish for, but also quite ignorant, which is nothing to be proud of. Anyway: The need for the code of conduct is clear to me, thanks in part to the efforts of people like the authors of this document. The principles of the draft code of conduct seem entirely reasonable to me. I could summarise them as "be kind and show respect" -- but kindness and respect have the potential to be subjective and I think the extra detail in the document is useful. The consequences of a code of conduct violation seem clear and reasonable to me, although I would add "No action (if the team has not been able to determine that a violation has occurred)", which is not the same as the final bullet and seems important to include, since life is analogue and its signal is lossy. I think the idea of having a team of trained people available to navigate the swamp of poor conduct is a good idea. I do wonder slightly what happens if due to illness, visa problems or other unexpected consequences, it is not possible for three or more team members to attend a meeting. Simply declaring a requirement isn't enough to ensure it will always happen. However unlikely, it seems sensible to think about what would happen in that case. I have one principal concern with the document, as written. The RIPE community includes people who are painfully aware of what poor conduct looks like (because they have been subject to it) and also people who have never knowingly experienced it and who hence are poorly-informed. Setting aside deliberate bad behaviour that I am certain exists and which this code of conduct properly seeks to deal with, there is still the potential for harm between people who don't realise they are being hurtful and those who are hurt as a consequence. This seems like the most difficult kind of interaction to deal with fairly as a mediator and as a community. This document puts an enormous responsibility on a small team of volunteers to provide that function, and it is not obvious to me that that is fair. This seems to me like hard and painful work; work that has the potential to cause collateral damage to the community if it ever becomes too much for a small pool of volunteers to deal with, and rife with decisions that have the potential to have great personal and professional impact to all people concerned, including the people on the team. So, I have some thoughts: 1. Perhaps the code of conduct team don't need to take ultimate responsibility for decisions; perhaps in the case where the team has decided that a member of the community has behaved badly and action should be taken, that action (and responsibility for the action) can be taken by the RIPE NCC as the organisation that coordinates the RIPE community's social infrastructure. (Perhaps this is even prudent, considering that some of the actions that the team might decide should be taken might have legal consequences; I don't think volunteers should have to take legal or other personal risk. There are many jurisdictions to consider and some of them are more litigious than others.) 2. Perhaps the kind of training that is imagined for the code of conduct team could be made available, in some form, for everybody. I would certainly appreciate being educated on the myriad problems faced by others that I am not aware of. Awareness and understanding are surely good bridges towards fostering a safer and more kind environment for everybody. (That last one in particular just seems like good engineering: you take precautions when you design networks and systems to avoid failure, but you are prepared to deal with failure in case it happens anyway. The draft arguably concentrates on the latter without paying as much attention on the former. I think both are important.) Joe

3 2

Meeting venue influences inclusivity
by Hank Nussbacher 21 Oct '19

21 Oct '19

I have read over the draft V3 CoC and notice an aspect that has bothered me and which precludes me and others from attending general RIPE meetings in certain venues. RIPE 75 took place in Dubai, UAE. Any Israeli citizen is not allowed to enter Dubai: http://www.dubaifaqs.com/israeli-stamp-passport-dubai.php "Israeli citizens are not permitted to enter the UAE on an Israeli passport or apply for a UAE visa" https://en.wikipedia.org/wiki/Israel%E2%80%93United_Arab_Emirates_relations "As the UAE does not officially recognize Israel, and does not allow Israeli citizens or those suspected of being Israeli citizens entry into the UAE, including Israeli passport holders, except for transit." If a CoC is being drafted and the intent is to be inclusive as possible and to eliminate discrimination based on nationality, I would like to suggest that it include a section that the venue of any general RIPE meeting cannot take place in a country that forbids certain people from attending. Regards, Hank

6 5

Fwd: [ripe-list] Code of Conduct 3.0
by Hans Petter Holen 20 Oct '19

20 Oct '19

Malcolm raises some issues in his email to the ripe-list. How can theese be addressed? Even under the current CoC with trusted contacts this is not defined. I personally does not have an answer to how to handle this. There was an incident in 2016 that may be used as a case study to better understand the complexity: https://omblog.icann.org/ ---------- Forwarded message --------- From: Malcolm Hutty <Malcolm(a)linx.net> Date: Wed, 16 Oct 2019 at 14:25 Subject: [ripe-list] Code of Conduct 3.0 To: ripe-list(a)ripe.net <ripe-list(a)ripe.net> Dear all, I understand that on Thursday afternoon the RIPE Plenary will be invited to adopt “Code of Conduct v3.0”. Unfortunately I must leave Rotterdam at lunchtime, so I am writing to share with you my reasons for believing it should not be approved. Code of Conduct v3.0 proposes the creation of a new entity, the “CoC Team” who will be invested with the power to hear allegations of breach of the Code of Conduct and decide what sanctions, if any, to apply to the community member in violation. Planned sanctions include, amongst other things, 1. Not allowing someone to participate further in RIPE Meetings and/or other RIPE community spaces, for a set period or an indefinite period 2. A public reprimand 3. Requiring that a public apology is made Denying someone the opportunity to participate in RIPE is clearly a serious step. Issuing a public reprimand, or requiring a public apology (i.e. admission of guilt) is potentially seriously damaging to a person’s reputation. Since a public reprimand might make reference to the purposes of the Code, including the prevention of sexual harassment and racist abuse, and assert that the person was found to have violated the Code, but not necessarily say what the individual is alleged to have actually done, a public reprimand from the CoC team could have lasting impact on a person’s career prospects. It is therefore a matter of great importance to every member of this community that if such sanctions are ever applied, the most scrupulous process is used. Unfortunately, in my view the process set out in Code of Conduct 3.0 is very far from fit for purpose. For a start, given the gravity of the intended sanctions, I am stunned to see that the Code neither requires nor suggests that the CoC Team should attempt to speak to the accused individual to get their side of the story. Indeed, there is no requirement that the accused person is even informed of the details of the allegation against them. A public reprimand could be the first the subject hears of the matter. The right to be heard before being punished is not an obscure legalistic procedural device. It is fundamental to basic fairness. Granted, a right of appeal has been added to the Code (thank you Daniel Karrenberg for your urgent intervention!), but I do not think appeal after the fact is sufficient correction to a basically abusive process. Although the most egregious, that is far from the only flaw with Code of Conduct 3.0. It positively encourages anonymous complaints. Complaints are also encouraged not only from alleged “victims”, but also from “witnesses” The Code promises that the identity of the complainant will not be disclosed to the subject of the complaint, potentially making it impossible to understand the circumstances or provide an explanation. The person submitting a complaint is not disqualified under the Code from sitting as a member of the CoC Team adjudicating the complaint. Given that the Code also invites witness reports and assures witnesses that their reports will not be viewed less favourably because they have made multiple reports, it would be entirely consistent with the Code for the CoC Team to also act as as a Code of Conduct patrol, making reports of violations and then sitting in judgement on their own allegations. Thanks to anonymity, nobody outside the CoC team would even know if this were occurring. There are other problems, but this message is already too long. Throughout the Code, the emphasis is consistently on the CoC Team’s responsibility to the reporter. There is no such recognition of a responsibility to the person ‘under investigation’ – by which I mean, the person who is the subject of the complaint; there is actually no expectation set in the Code that the CoC Team would actually conduct an investigation, rather than proceeding directly to judgement on the basis solely of the information contained in the allegation. I have described some serious flaws, but in my view, it is not worth trying to rescue this proposal with patches to each of them. The document as a whole is riddled with bias, and should be abandoned. The Diversity Taskforce has demonstrated that it is not an appropriate body to be undertaking this work. Any serious attempt to create a process for enforcement of a Code of Conduct should be predicated on the basis that a grievance and disciplinary process (which is what this is) owes a serious duty of fairness to all parties, not only to one side. Malcolm. -- Malcolm Hutty | tel: +44 20 7645 3523 Head of Public Affairs | web: www.linx.net London Internet Exchange | London Internet Exchange Ltd Monument Place, 24 Monument Street London EC3R 8AJ <https://www.google.com/maps/search/Monument+Place,+24+Monument+Street+Londo…> Company Registered in England No. 3137929 Trinity Court, Trinity Street, Peterborough PE1 1DA -- -- Hans Petter Holen Mobile +47 45 06 60 54 | hph(a)oslo.net | http://hph.oslo.net

3 2

Re: [diversity] [comms-circle] [ripe-list] Towards a more inclusive community
by Julia Freeman 17 Oct '19

17 Oct '19

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, Oct 17, 2019 at 06:12:09PM +0300, Hank Nussbacher wrote: > On 17/10/2019 17:32, Julia Freeman wrote: > > Julie, at no time did I say it is not happening. I just said that > *I *am clueless about it since I didn't see it or hear about it. > Now that you have come forward as well as Jordi, hopefully people > will be kinder and more importantly, if you see such behavior being > imposed on someone else, and you are a bystander, then you should > say something - not only the victim. Yes, people witnessing things should be doing more. The whole issue of the bystander effect could fill whole dissertations. Not every CoC violation is easily witnessed. The problem is, everytime someone says "I've not seen it", it is interpreted by people as "it's not happening". We shouldn't have to go into detail of what happened for people to believe us that harrasssment and CoC violations are happening. And my name is Julia not Julie. J -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFdqIfe42M0lILkmGIRAtBoAJ9y+A9gespRoD4ux5djECc69AnziwCgto5Y 2cOtLUfVKwDFziaS5k2+vIg= =KIuK -----END PGP SIGNATURE-----

1 0

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. 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

6 8

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