- diversity - mailman.ripe.net

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