- diversity - mailman.ripe.net

NVC online course : Social Change: Supporting Diversity, Equity, and Inclusion
by Vesna Manojlovic 08 May '19

08 May '19

Hi all, I am following a "mediator" course in Non-Violent Communication, and this "advertisement" caught my attention: if you know someone who would benefit from such an education, please suggest it to them: http://nvctraining.com/media/_2019/ML-RM/social-change/index.html "Avoiding conversations about domination, power, race, gender, or sexual orientation is no longer an option. Why? Because the pain engendered by avoiding difficult conversations shows up in your classes, your meetings, your workplaces, and your relationships. But HOW do you hold such a conversation? How do you address power differences, unearned advantages, or racial oppression? How do you open a conversation about race, gender, or sexual orientation? And how do you embrace people from all walks of life and facilitate groups so everyone feels fully heard, valued for their contribution, and acknowledged for their unique experiences?" Thanks, Vesna -------- Forwarded Message -------- From: NVC Academy <training(a)nvctraining.com> Responding to the Call of Our Times: A Leadership Coaching Program *Join us if you're weary of walking on eggshells and are ready for change!* If you're weary of walking on eggshells... tired of feeling afraid you might say the wrong thing... and you're ready for CHANGE... you're invited to join Roxy Manning and Martha Lasley for *Social Change: Supporting Diversity, Equity, and Inclusion* http://nvctraining.com/media/_2019/ML-RM/social-change/index.html Mondays, July 8th - September 2nd 12:00-2:00pm Pacific (California) Time The consciousness of Nonviolent Communication can give us the courage we need to address some of the most challenging issues of our time. During this series we'll explore highly effective ways of responding to bias, slights, stereotypes, domination, and oppression – an intense and deeply rewarding experience. *Join us. It's time to ask – and answer – difficult questions.*

1 0

Great read on sexual harassment in the workplace on HBR
by Amanda Gowland 24 Apr '19

24 Apr '19

https://hbr.org/2019/04/ending-harassment-at-work-requires-an-intersectiona… This was an interesting read on sexual harassment in the workplace, breaking down the assumption that perpetrator is often a senior male and victims often a junior woman.

1 0

RIPE Diversity TF Meeting - 5 March 2019 - draft minutes
by Amanda Gowland 05 Apr '19

05 Apr '19

Hi all, Please find below the draft minutes from our last meeting. Shane, you were cutting out a bit when you were updating on the gender metrics...so I have a feeling you'll need to maybe have a look at that part. If there's anything I didn't capture correctly, please let me know. Warm regards, Amanda --- RIPE Diversity Task Force - Meeting Minutes, 5 March 2019 Participants: Amanda Gowland, Mirjam Kühne, Brian Nisbet, J, Sasha Romijn, Vesna Manojlovic, Bijal Sanghani, Shane Kerr, Malcolm Hutty Agenda - Code of Conduct - Updates for RIPE 78 The main discussion for the day's meeting focused on the need to improve the RIPE Meeting Code of Conduct, specifically: - The text itself - The lack of processes around violations, reporting - The role that WG Chairs play in upholding the CoC - The timing and practical aspects of moving forward Amanda asked Sasha if she could brief the TF on what she shared on the mailing list given her experience working on Django's CoC and Write the Docs (WtD). Sasha said that the RIPE Meeting's CoC essentially says "don't be an asshole", but there's no documented mechanism for reporting violations or a team of people equipped to enforce it. She said that dealing with CoC violations/reporting requires resources and expressed doubt that the RIPE Chair had the time/resources for this. She said that for Write the Docs, they have a CoC Response Guide, which is a structured plan that stipulates who you involve when, how you deal with conflicts of interest and more specific information on what kinds of things are and are not acceptable. Amanda asked if the TF should propose a Code of Conduct Team, since the scope of the RIPE Meeting Trusted Contacts was not meant to tackle reporting and enforcing consequences of CoC violations. She asked Sasha if she'd be willing to help with this since she's the most experienced. Sasha said she would be happy to draw on the text from WtD. Amanda asked the TF what they thought about getting this in place for RIPE 78? Brian said he'd be weary of having something for the next meeting, only because registration is already open and people have to agree to the CoC during the registration process. It was too short to have a new proposal to the community. J asked if there was anything that could be done to improve the CoC for RIPE 78 without touching upon the text, like improving the process or the implementation. Code of Conduct Team? Sasha said that the current text is weak, so changes will need to happen there but in the meantime other things can be improved to help things progress. Brian agreed that the TF could look at the process and how that works. Amanda asked how the CoC Team should be selected - are people asked, is there a nomination process, etc? Sasha said it depends, in her experience it's a team of volunteers that ideally have experience and who meet some specific criteria (like having no record of CoC violations). Amanda mentioned that the RIPE NCC was in discussion with Hans Petter Holen (HPH) about having training for the WG Chairs so they are able to better uphold the CoC. Mirjam updated the TF that this is something that HPH is really supportive of and has given the go-ahead for us to organise this in Reykjavik for RIPE 78. He would like to do it at the WG Chair Lunch to ensure full participation. As an aside, Mir informed the group that she submitted a BoF for HPH about "RIPE and the Bigger Picture" - looking at the societal obligations of the RIPE community. Axel has also expressed a desired to have a bigger focus on this. Amanda asked what the next steps should be for drafting a new CoC and its related processes. Malcolm said that he would like to contribute. Sasha said she would also like to work on this. J asked what the process was for a new document, what process does it need to follow to be approved? Malcome said that for the Accountability TF, they just submitted their report. The process they were instructed to follow was that they share their report with the community for comment, there's a consultation period, the TF worked on the contributions and made amendments where applicable. A revised draft is then reported back to the community and it is up to HPH to declare consensus. Brian added that if they can get text together in the next 4-6 weeks, a draft could be ideally shared or presented at RIPE 78. He felt there would likely be pushback on any sort of stronger document. He said there was a difference with this and what the Accountability TF is doing - the issue with the CoC is that we don't want to have to go through 18 iterations. Malcolm replied that he hoped there wouldn't be multiple rounds of iterations and pointed out that this is a TF and not a WG. Although consultation is expected, it is up to the TF to decide what to do with the contributions from the community to the draft. But it is not for the TF to go from draft to execution, it is HPH to declare consensus and move forward. RIPE 78 Updates Amanda gave an update on the WiT session for RIPE 78 - we were moving it into the Side Room, taking place from 13:00-14:00. She has been working with the Icelandic WiT group and they were enthusiastic on helping build the programme. She said that she was disappointed with how few registered attendees have volunteered to be a mentor for RIPE 78, but that maybe it was a case of it just building up slowly. She also said that there were no organisations signing up as Diversity Ticket sponsors, so they will monitor this for a couple meetings and have to consider whether they still facilitate it going forward. Shane said he didn't really have much of an update for the gender metric gathering. He was playing around with a way to create visualisations. He updates the graphs for every meeting but they didn't look great in terms of % of women. He will work on an update before RIPE 78. Bijal added that it was the first time she has taken part in the TF, she missed the discussion about the CoC but will catch up on it. She said she was surprised there weren't more people signing up to be mentors and she will put her name forward. J asked about the mechanism to draft the CoC to ensure version control, bug trackers, etc., and if we were using something already for this? Amanda said that Google Docs seemed to be the easiest way to work on it to ensure changes are tracked, etc. J suggested GitHub. There were no further comments. Amanda thanked everyone for their feedback and closed the meeting.

3 2

WebEx details for today's Diversity Task Force Meeting - 15:00 CET/14:00 GMT
by Amanda Gowland 05 Mar '19

05 Mar '19

Hi all, Please find below the WebEx details for our meeting today at 15:00. The main agenda is the RIPE Meeting Code of Conduct. Warm regards, Amanda -------- Forwarded Message -------- Subject: Webex meeting invitation: Diversity TF Meeting Date: Tue, 5 Mar 2019 09:51:26 +0000 (GMT) From: Daniella Coutinho <messenger(a)webex.com> Reply-To: dcoutinh(a)ripe.net To: agowland(a)ripe.net Hi, AmandaGowland, Daniella Coutinho invites you to join this Webex meeting. *Diversity TF Meeting* Tuesday, March 5, 2019 3:00 pm | Europe Time (Amsterdam, GMT+01:00) | 1 hr Meeting number (access code): 700 432 508 Meeting password: hMtuPSED Add to Calendar <https://ripencc.webex.com/ripencc/j.php?MTID=m0810bc8a2ce9a095b6a6c40d3db53…> When it's time, join the meeting <https://ripencc.webex.com/ripencc/j.php?MTID=mbb87ab95c245c6da499852cf7bdb1…>. *Join by phone* *0800-051-3810 <tel:0800-051-3810,,*01*700432508%23%23*01*>* United Kingdom toll-free *+44-203-478-5289 <tel:%2B44-203-478-5289,,*01*700432508%23%23*01*>* United Kingdom toll Global call-in numbers <https://ripencc.webex.com/ripencc/globalcallin.php?serviceType=MC&ED=768011…> | Toll-free calling restrictions <https://www.webex.com/pdf/tollfree_restrictions.pdf> Can't join the meeting? <https://collaborationhelp.cisco.com/article/WBX000029055> IMPORTANT NOTICE: Please note that this Webex service allows audio and other information sent during the session to be recorded, which may be discoverable in a legal matter. By joining this session, you automatically consent to such recordings. If you do not consent to being recorded, discuss your concerns with the host or do not join the session.

3 2

On the RIPE community CoC
by Sasha Romijn 19 Feb '19

19 Feb '19

Hello all, At the last RIPE meeting, we talked about our Code of Conduct. I offered to send a good example. I’ve since also actually reported a CoC incident in the RIPE community, and want to share some thoughts on that experience. Sending a CoC example took some time, as I’ve been refactoring and improving the CoC for the Write the Docs community. Our new CoC is: http://www.writethedocs.org/code-of-conduct/ http://www.writethedocs.org/code-of-conduct-response/ And these are the most significant changes: http://www.writethedocs.org/blog/new-community-coc-2019/ I’m happy to further explain the decisions behind it, if you have any questions. I will not share the full details of the incident I reported in the RIPE community, because I prefer not to be identified as the reporter. About four months have passed since my report, and I have not received any reply from the wg chairs or the RIPE chair, who are the designated contacts, other than two notes that it was being worked on. I initially reported to the relevant working group chairs, and then escalated to the RIPE chair, as documented in the RIPE community CoC. To my knowledge, no action has been taken. My general impression is that none of the people listed as CoC contacts in any part of the RIPE community are able to effectively take action on a CoC incident. Either because this is explicitly not part of their task (trusted contacts) or, I suspect, they lack any kind of resources or possibly time to handle an incident. That is *not* a failure on the part of any of these people individually, but rather caused by a flawed and mostly absent process and mandate to act. In addition, confidentiality of CoC reports is violated in every single report. Both wg chair mailing lists and the trusted contacts address are moderated by NCC staff, which means an unknown person(s) can also see the report, and reporters are not made aware of this in advance. This can have severe consequences, and makes reporting unsafe. The RIPE chair doesn’t seem to have any publicly listed contact address at all. Personally I feel that the ability of the RIPE community to handle a CoC incident is so abysmal, that we would be better off not publishing one at all, as we are now creating a false sense of security. I should also note that this was a fairly minor incident, pretty much the most trivial kind of incident a CoC contact has to deal with. The consequences of the lack of ability to respond properly could be very severe in case of a more serious incident - which have taken place in the RIPE community as well. The updated Code of Conduct for Write the Docs, along with our response guide, handles many of these concerns specifically, so I suggest you have a look at it, and see how it can be adopted for the RIPE community. However, in order to have an effective CoC process, it will also require setting up one or more response teams, which can be contacted privately, with publicly listed membership, and most importantly, a mandate to act. Including, if needed, immediate removal of a community member, including those in a position of power. From my personal experience, this is a quite rare measure, but it needs to be on the table for the CoC to be effective. I’m not sure what the process would be to continue with this, or how others feel - I’m curious to hear your ideas. But the apparent fact that the RIPE community is currently unable to handle even the most trivial CoC reports, makes it inherently unsafe. Sasha

5 6

Doodle Poll for next meeting
by Amanda Gowland 13 Feb '19

13 Feb '19

Hi TF members, I've created a Doodle Poll with some timeslots for the next couple weeks - I purposely didn't have 20 options to avoid vote splitting :) https://doodle.com/poll/ruvk9uviear6i3xg Hopefully there's something in there that we can all fit into our calendars. Please fill it in by Monday, 18th. Many thanks, Amanda On behalf of the Diversity TF

3 6

Vismas focus on diversty
by Hans Petter Holen 11 Feb '19

11 Feb '19

I am not personally involved in this, but it may be of interest to some of you: https://www.visma.com/shesgotthis/ -- Sincerely, Hans Petter Holen - hph(a)oslo.net - +47 45066054

2 1

RIPE 78 is now on diversitytickets.org!
by Amanda Gowland 29 Jan '19

29 Jan '19

Hi everyone, I'm *thrilled* to finally announce that RIPE 78 is now listed on diversitytickets.org and we now have it listed as an official sponsorship package for RIPE Meetings! Organisations (or individuals) can send up to three attendees from underrepresented parts of the tech community to a meeting. The selection is done by diversitytickets.org and the RIPE NCC will assist with visa invitation letters as needed. Please spread the word far and wide! Tickets will be added to the event as sponsorship funds are allocated. More info on RIPE Labs: https://labs.ripe.net/Members/agowland/do-good-at-ripe-78-sponsor-a-diversi… More info about becoming a Diversity Ticket Sponsor (or On-Site Childcare!): https://ripe78.ripe.net/sponsors/become-a-sponsor/ Oh, and we now have a dedicated section for Diversity on the meeting website: https://ripe78.ripe.net/diversity/ If you have any questions, please let me know. Warm regards, Amanda

4 4

Diversity Tickets and RIPE Meetings
by Amanda Gowland 10 Dec '18

10 Dec '18

Hi all, We would like to include an option under our Diversity Sponsor category for organisations or individuals to fund Diversity Tickets. The number of tickets available will depend on the number of sponsors and the amount they fund. The selection is done by diversitytickets.org based on the following criteria they use: "This diversity program is aimed to help underrepresented groups in tech to attend and lowering the barriers for them. This includes but isn’t limited to: women, people of color, LGBTQIA+ people, and disabled people. Your privacy, details and answers will only be shared with the organizers of RIPE 78. We will not share any data with those who sponsor these tickets." We will cover the cost of the ticket and reimburse them EUR 650 to help with their travel/accommodation costs. I am asking the organisers if we can amend the criteria text above to say "This includes but isn't limited to women, people of colour, LGBTQIA+ people, disabled people and people coming from countries underrepresented at RIPE Meetings." If anyone has any feedback, please let me know (sooner rather than later). Warm regards, Amanda

2 1

Re: [diversity] Feedback, including a piece of friendly and hopefully constructive criticism
by Amanda Gowland 22 Oct '18

22 Oct '18

Hi Theresa, Thank you for your feedback - I am, above all, really happy that we are finally starting to see some engagement at the RIPE Meetings on our D&I efforts (both from the Diversity TF and also the RIPE NCC). I am really happy to also see people active in the D&I circles coming to the meetings! I'm replying here as myself and not a TF member. It can be a bit of a gray area, since I'm involved in the TF initiatives too. The WiT Lunch is not a TF initiative, just to clarify. It was initially proposed by our board member, Salam Yamout (who is the woman that you mentioned from Lebanon that spoke at the mic after my presentation). Replying inline now... On 21/10/2018 11:27, Theresa Enghardt wrote: > Dear Diversity Taskforce, > > thank you so much for your work. > > RIPE 77 was my first RIPE meeting and I really enjoyed it. It feels nice > to come into a community and see that the diversity work is already > being done, so I don't have to be the one to do the heavy lifting. > (A bit of personal context: I do diversity-related work in other > communities, e.g., at the Chaos Communcation Congress.) > > Thank you in particular for the amazing presentation at the plenary on > Friday. > > That said, I would like to provide some friendly and hopefully > constructive criticsm in the following, rather long, e-mail. > This is NOT a call-out of any individual person, but rather something > I'm asking you as a group to consider. > Feel free to pass it on to people not on your mailing list, but then > without my name, please. > > > > 1.) Please do not issue a general invitation for people to talk to women > about their experience at RIPE. > > I was at RIPE to talk about technology, about my work, not about feminism. > Being asked about feminism in a work context generates a lot of stress > for me (details on that below, if you are interested). > I would rather have people talk to me about my work. I assume this is > true for many other women as well. When I said "talk to women about their experiences", my intention was not that it be about their experiences with being othered, but just to speak to them about their experiences period. About their work, yes. About their aspirations in their career, about the projects they're excited about. But also about the barriers they face that their male colleagues may not have any understanding of. It was certainly not meant as an open invitation for men to ask women about how they're being harrassed or discriminated against. It was related to my previous slides of what it means to be a male ally, and that the first step to advocacy is awareness. I want men to start recognising and advocating for the work that their non-male colleagues are doing so that hopefully we see more representation at the meetings, on the stage, etc. > > If you want to encourage people to learn more about women's experiences > in tech, how about "Consider reading up on this, here's some links, and > here are some people who volunteered to answer questions"? > > If you must invite people to talk to women they know about their > personal experience, please at least include a very prominent reminder > that not every woman may be comfortable to talk about her experiences > for many very valid reasons. > > Some details about my own reasons, just to illustrate: > I personally did not have any experience of harassment or discrimination > at RIPE that I recall. I'm sure this is the case for a number of other > women as well. Hearing "talk to a woman about her experience here", for > me, implies that you expect that everyone has experienced discrimination > AND is comfortable to talk about it. It also feels a little bit > infantilizing to me, like, "You poor women have it so bad here". This is > simply not true. > I know that there's still lots of problems, so I could talk about other > women's experiences, or about feminism in general. However, I have been > "the angry feminist" in a work context before. Even with coworkers that > I really like, if I disagree with them on some feminist topic, it can > create a lot of stress and a feeling of alienation on both sides. In > addition, I fear that having a public stance on feminism could damage my > future career. I don't feel like it's on me to "get over this", but for > the culture to change. > Your work is an important part of that change, and I appreciate it. > > > > 2.) Please do not misuse the term "intersectionality". > > (Relevant context for the following section: I'm white. Please consider > reading the writings by black feminists on this topic.) > If I recall correctly, in the plenary the term was used to mean "we do > things for women and then other minorities / everyone benefits from it". > This is not what intersectionality means. In fact, it's literally the > opposite. In our first diversity workshop before the TF was formed, we understood the phrase to mean how the struggle to combat sexism and racism (and other forms of discrimination) intersect. Yes, Crenshaw's original definition of the phrase has taken on ambiguous meaning over the years and I should have chosen a better phrase there. However, her original intention of the word to frame the struggle that someone belonging to more than one marginalised group faces is still relevant for our diversity efforts I think. > > The term "intersectionality" was created by Black feminists Kimberlé Crenshaw > to mean that > black women are discriminated in different ways than white women. They > experience racism AND sexism, so their experience of racism is different > from the racism black men experience, and their experience of sexism is > different from the sexism that white women experience. > This means that if you just "do things for women" without looking at > other forms of discrimination, you end up doing things that mostly > support white women, and leave other women behind. > Similar points apply to trans women (who also experience transmisogyny), > disabled women (who also experience ableism), and so on. I agree that we need to tackle diversity from every angle and I know that we will get there. We are working within an almost 30yo community built on 'legacy' and achieving the change I believe we need to see means building the foundation for inclusiveness of women, period. Once we do that, then I hope that it'll be easier (and quicker) to improve the meeting and community experience for all under-represented groups. > > I think that the remark at the mic by the woman from the middle-east, > whose name I sadly don't recall, Salam Yamout > was exactly spot on. > Different discriminations exist, they are sometimes combined, and > working against them does not have to be mutually exclusive. > > Do not assume that all women need or want the same. Do not assume that > there is a universal female experience or perspective. There is not. The > "universal" female perspective is usually the white, cis, non-disabled > female perspective. (Such as my own, technically and ironically, as I > have all those privileges.) I fully agree here. And while we don't aim to speak on behalf of all women, I also don't feel comfortable speaking on behalf of another group. Making our meetings more inclusive for women will (I hope) make it also more inclusive for non-white/cis/non-disabled women. We have to start somewhere. > It's not a bad thing to have privilege, but one should be aware of it, > one should question it, and one should actively give space to others who > do not have this privilege. > In that sense, I try my best to be a cis ally to trans* people, a white > ally to non-white people, and a non-disabled ally to disabled people. > > In summary, it's fine you focus on women, but please be aware that > there's different kinds of women. > It's fine if you pick your battles. It's fine that you cannot do > everything at once. > I'm simply asking you to read up on the term "intersectionality" and to > not misuse it. > > > > 3.) Please try to avoid gender binarism. > > I heard gender-binarist language (e.g., "both men and women" used to > mean everyone) a lot this week. > I don't know if there's any openly non-binary people in the community, > but given that your registration form includes a non-binary option, > perhaps there's a way to find out if anybody was brave enough to out > themself on that form. Anyway, I'm pretty sure they exist. There was one person that identified themselves as non-binary. > > You don't necessarily have to educate everyone about this stuff, at > least not for me. To me, just being conscious of your language, like > saying "Dear gentlepeople" instead of "Dear ladies and gentlemen", makes > a big difference. Also, consider having T-shirts in "fitted" and > "unisex" cut instead of "woman's" and "man's" cut. > Having some gender-neutral bathrooms in addition to gendered bathrooms > might also help to make the space more inclusive to non-binary people, > and maybe also to binary trans* people. Funny about the t-shirts, we have had the opposite feedback from women in the community. For this meeting, we had unisex t-shirts, but previous meetings we've had different cuts for m/f (which was requested from our female attendees). We can certainly be more inclusive in how we label the shirts at the table though (although, annoyingly for this meeting we had two colours of unisex shirts and some people were still referring to the burgundy shirts as the "girl" shirts :/). For the bathrooms, I will certainly pass this feedback back to our meeting organisation team. Not sure what is/isn't possible given that the meetings are always in hotels. > > > Finally, a but of positive feedback again: > > I think the discussion on (male) allies is a really good and important > one, I was really pleased to see it. > I've met lots of male allies at RIPE, even those who aren't active > advocates and don't call themselves feminist (yet?), but who encourage > me in my work and mentor me. > If some of these men become more feminist, that's really awesome, and > thank you for working on that. Thank you Theresa for your valuable feedback and for engaging in the diversity discussions! > > Hope to see you at a RIPE meeting next year! > > Best, > Theresa >

4 6

Feedback, including a piece of friendly and hopefully constructive criticism
by Theresa Enghardt 22 Oct '18

22 Oct '18

Dear Diversity Taskforce, thank you so much for your work. RIPE 77 was my first RIPE meeting and I really enjoyed it. It feels nice to come into a community and see that the diversity work is already being done, so I don't have to be the one to do the heavy lifting. (A bit of personal context: I do diversity-related work in other communities, e.g., at the Chaos Communcation Congress.) Thank you in particular for the amazing presentation at the plenary on Friday. That said, I would like to provide some friendly and hopefully constructive criticsm in the following, rather long, e-mail. This is NOT a call-out of any individual person, but rather something I'm asking you as a group to consider. Feel free to pass it on to people not on your mailing list, but then without my name, please. 1.) Please do not issue a general invitation for people to talk to women about their experience at RIPE. I was at RIPE to talk about technology, about my work, not about feminism. Being asked about feminism in a work context generates a lot of stress for me (details on that below, if you are interested). I would rather have people talk to me about my work. I assume this is true for many other women as well. If you want to encourage people to learn more about women's experiences in tech, how about "Consider reading up on this, here's some links, and here are some people who volunteered to answer questions"? If you must invite people to talk to women they know about their personal experience, please at least include a very prominent reminder that not every woman may be comfortable to talk about her experiences for many very valid reasons. Some details about my own reasons, just to illustrate: I personally did not have any experience of harassment or discrimination at RIPE that I recall. I'm sure this is the case for a number of other women as well. Hearing "talk to a woman about her experience here", for me, implies that you expect that everyone has experienced discrimination AND is comfortable to talk about it. It also feels a little bit infantilizing to me, like, "You poor women have it so bad here". This is simply not true. I know that there's still lots of problems, so I could talk about other women's experiences, or about feminism in general. However, I have been "the angry feminist" in a work context before. Even with coworkers that I really like, if I disagree with them on some feminist topic, it can create a lot of stress and a feeling of alienation on both sides. In addition, I fear that having a public stance on feminism could damage my future career. I don't feel like it's on me to "get over this", but for the culture to change. Your work is an important part of that change, and I appreciate it. 2.) Please do not misuse the term "intersectionality". (Relevant context for the following section: I'm white. Please consider reading the writings by black feminists on this topic.) If I recall correctly, in the plenary the term was used to mean "we do things for women and then other minorities / everyone benefits from it". This is not what intersectionality means. In fact, it's literally the opposite. The term "intersectionality" was created by Black feminists to mean that black women are discriminated in different ways than white women. They experience racism AND sexism, so their experience of racism is different from the racism black men experience, and their experience of sexism is different from the sexism that white women experience. This means that if you just "do things for women" without looking at other forms of discrimination, you end up doing things that mostly support white women, and leave other women behind. Similar points apply to trans women (who also experience transmisogyny), disabled women (who also experience ableism), and so on. I think that the remark at the mic by the woman from the middle-east, whose name I sadly don't recall, was exactly spot on. Different discriminations exist, they are sometimes combined, and working against them does not have to be mutually exclusive. Do not assume that all women need or want the same. Do not assume that there is a universal female experience or perspective. There is not. The "universal" female perspective is usually the white, cis, non-disabled female perspective. (Such as my own, technically and ironically, as I have all those privileges.) It's not a bad thing to have privilege, but one should be aware of it, one should question it, and one should actively give space to others who do not have this privilege. In that sense, I try my best to be a cis ally to trans* people, a white ally to non-white people, and a non-disabled ally to disabled people. In summary, it's fine you focus on women, but please be aware that there's different kinds of women. It's fine if you pick your battles. It's fine that you cannot do everything at once. I'm simply asking you to read up on the term "intersectionality" and to not misuse it. 3.) Please try to avoid gender binarism. I heard gender-binarist language (e.g., "both men and women" used to mean everyone) a lot this week. I don't know if there's any openly non-binary people in the community, but given that your registration form includes a non-binary option, perhaps there's a way to find out if anybody was brave enough to out themself on that form. Anyway, I'm pretty sure they exist. You don't necessarily have to educate everyone about this stuff, at least not for me. To me, just being conscious of your language, like saying "Dear gentlepeople" instead of "Dear ladies and gentlemen", makes a big difference. Also, consider having T-shirts in "fitted" and "unisex" cut instead of "woman's" and "man's" cut. Having some gender-neutral bathrooms in addition to gendered bathrooms might also help to make the space more inclusive to non-binary people, and maybe also to binary trans* people. Finally, a but of positive feedback again: I think the discussion on (male) allies is a really good and important one, I was really pleased to see it. I've met lots of male allies at RIPE, even those who aren't active advocates and don't call themselves feminist (yet?), but who encourage me in my work and mentor me. If some of these men become more feminist, that's really awesome, and thank you for working on that. Hope to see you at a RIPE meeting next year! Best, Theresa -- Theresa Enghardt Wissenschaftliche Mitarbeiterin / Research Assistant Phone: +49 30 314 78628 Office: MAR 4.032 FG / Group "Internet Network Architectures" (INET) Technische Universität Berlin Sekr. MAR 4-4, Marchstraße 23, 10587 Berlin

2 1

Meeting Notes - Diversity TF Meeting 20181015
by Brian Nisbet 19 Oct '18

19 Oct '18

Folks, Here are my notes from yesterday's meeting, please let me know if there are any mistakes or omissions. RIPE Diversity TF 20181015 Present: Mirjam, Denesh, Shane, Vesna, Jelte, Salam, Julia, Amdanda, Sasha, E, Brian General Point: Diversity/Inclusivity is more than "just" gender and race. Also around food, travel, cost etc. Metrics: - Shane has updated the metrics based on name of attendees, continuing over time. He will publish the info to the list. RIPE77 seems to have more women attending than the last meeting in Amsterdam, but fewer than the last five meetings. Around 16%. Being checked against NCC self declaration information. - NCC info 10% self identified as female, 25% declined to answer, 1 NB, 2 Other, all other male - SREcon in Düsseldorf, 13% women, 13% declined to answer, 74% men - Shane looking at pulling out AMS meetings to try and get a trend based on same location - Can also get information from t-shirt types and sizes. 103/800 looking for women's cut - Data is all in Github, so others can work on it. - But Shane isn't sure what the right approach/direction is, so hence part of the reason for the BoF on Tuesday. That might give more info on what metrics to track. Action: Shane to send out information and continue to think about the metrics Local Communities: - Vesna contacted some of the hackerspace communities - Hackerspace visit on Wednesday - Need to make a push for RIPE78 - Looking to get school age girls to come, but communications broke down with the relevant local people Childcare: - Only 2 kids registered for RIPE77 - Unfortunately can't be continued if kids aren't being registered - Very visible for RIPE77 registration - Cost now at €10/day - Reduced cost due to local providers - Forecast uncertain for RIPE78 at present - Going to look at gaining information in advance again, both during 77 feedback and maybe opening registration early to get information more in advance? - General feeling that we should continue it if at all possible Mentoring: - Official mentoring programme launched at the end of August - Around 13 people signed up to be mentors - Almost all mentors signed up with mentees TF Update: - Plan now to put one slide into HPH's closing plenary presentation. General vibe that we are continuing, that progress is happening, and TF to recheck need for TF. Current feeling is we continue to need it. RIPE CoC: - Trusted Contacts received training from Hubert Consult, Vesna to send the details to the list - Need to review and improve at this point in time - Especially in regards to the procedure around dealing with reports and who can take the action to remove someone from the meeting? - Sasha has a template for a possible changes to/rewrite of the CoC - Sasha will send an email to the list with the JangoCon Europe information and we can file off the relevant serial numbers - TF to consider how to make updating the CoC and associated procedures easier - Brian & Shane to inform the PC and WG Chairs that this work is ongoing Helping Other Communities: - Need to look at checklist for NCC sponsored events Open Action: Gender diversity in speakers and leadership still isn't where we want it to be. Open Action: UKNOF update not on programme, hopefully for Iceland Open Action: Vesna will try again to reach Dutch office of Women & Girls in Tech Open Action: Need to make it easier to change the name of a speaker after submission has been made, NCC working on this for PCSS Open Action: Amanda was talking to HPH about restricting questions to online submission and led by session chair, so no questions from the mic. HPH interested in the idea. Suggestion that both pronoun stickers and "Do not photograph" stickers/badges should be available Brian Nisbet Network 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

4 9

RIPE77 meeting: updated list of actions
by Vesna Manojlovic 15 Oct '18

15 Oct '18

Hi everyone, as a preparation for the in-person meeting on Monday, here is the updated list of actions: Ongoing efforts: - approach local communities - mentoring - child-care - encourage diverse panels in CfP - ask for gender at the registration form - follow metrics to see if we are making progress - report from the TF on the progress since the previous RIPE meeting Open actions: - Denesh : do a talk "an update from UKNOF how are we approaching diversity", by Liz Stevens (July 2018) - RIPE NCC: cooperate with the managing director for the Dutch office of girls and women in tech: https://www.vhto.nl/ (July 2018) - Vesna : talk to RIPE NCC's Web Services to make the PC system more flexible to be able to change names/presenters more easily. (July 2018) - RIPE NCC: come up with a proposal and send it to the diversity list: how to reward other kinds of participants & not the "first 3 who registered" (July 2018) - TF: start addressing the lack of diversity in leadership roles in the RIPE community - specifically, the RIPE Programme Committee and the Working Group Chairs (May 2018) - Vesna - organise meeting with Sara from Europol (May 2018) You can find these, and older actions, here: http://etherpad.tools.ietf.org:9000/p/ripe-diversity-tf-2017 Also, any volunteer to take notes on Monday? Thanks, Vesna

2 2

Deciding on the time for the Task Force meetup at RIPE77
by Vesna Manojlovic 11 Oct '18

11 Oct '18

Hi, in about a month the RIPE77 meeting is happening in Amsterdam - and that's an opportunity for the "members" of the Diversity Task Force to meet in person. Usually it's quite busy & the time suiting everyone is hard to find... I made a "poll" to help us choose the date&time: https://doodle.com/poll/7qbtuc5ewxu7fi4b Please reply by Thursday, 20.9., noon (UTC+1) Afterwards, I will send the best-voted slot to the list. You can join this TF meeting if you are interested in helping with the ongoing actions, those that are still outstanding, or if you have another activity to suggest. "members" are simply people who do some work - and that can be *you* :) More info is here: https://www.ripe.net/participate/ripe/tf/ripe-diversity-task-force https://labs.ripe.net/diversity We will agree on more detailed agenda for the meeting beginning of October. Regards, Vesna ps I know there are privacy concerns with a "free" service that uses advertisements on the page, so if you have a suggestion for something else then d00dle for the next survey, please let me know

2 6

Workshop on Internet Governance and Feminist Internet
by Vesna Manojlovic 11 Oct '18

11 Oct '18

Dear all, The RIPE NCC is hosting a workshop in our office together with a tech-focused feminist organisation from Germany and we'd like to extend an invitation for you to join. We see this initiative as an extension of our work to increase diversity and inclusion in the RIPE community. When: Thursday, 20 September 2018, 14:00 - 17:00 What: Workshop on Internet Governance and Feminist Internet Perspective Where: RIPE NCC offices, Stationsplein 11, Amsterdam Programme: - Mirjam Kuehne: Governing the Internet Infrastructure as a Commons https://18.re-publica.com/en/session/governing-internet-infrastructure-comm… - Vesna Manojlovic: Ethics in Technology and RIPE Atlas https://program.sha2017.org/events/311.html - Amanda Gowland: RIPE Community Diversity Efforts https://labs.ripe.net/diversity - Discussion: Feminist Perspectives on Internet Governance https://feministinternet.org/ and https://techfestival.co/event/feminist-internet-summit/ You are invited to join! Places are limited. Please let us know if you are interested before 18 September 2018, 12:00 UTC, by replying to me. Kind Regards, Vesna Manojlovic Community Builder RIPE NCC

2 4

Fwd: N2Women: Rising Stars in Computer Networking and Communications 2018
by Vesna Manojlovic 02 Oct '18

02 Oct '18

Cross-posting: an example of the similar community (slightly more academic) , where they promote the work of young researchers, from diverse disciplines. Also a good list of possible contributors / speakers for some of our future projects / events. Cheers, Vesna -------- Forwarded Message -------- Subject: [n2women] N2Women: Rising Stars in Computer Networking and Communications 2018 Date: Mon, 1 Oct 2018 16:39:54 +0000 Reply-To: subarna chatterjee <chatterjeesubarna(a)yahoo.com> To: n2women(a)ACM.ORG Dear all, We are very excited to announce the fourth list of “/N2Women: Rising Stars in Computer Networking and Communications/”. We received a large number of nominations for a wide range of amazing researchers in our field, and it was difficult to choose only 10 amazing women. We focused on young women whose career start has already impacted research in networking and/or communications. We also wanted a list that represented our diversity, e.g., diversity in the area of networking/communications and, thus, chose the list accordingly. For 2018, in alphabetical order (by the last name), here are the 10 Rising Stars in Computer Networking and Communications! 1. Behnaz Arzani (https://www.microsoft.com/en-us/research/people/bearzani/) 2. Leyre Azpilicueta (https://scholar.google.com.mx/citations?user=2vjBtoEAAAAJ&hl=en&oi=ao) 3. Aruna Balasubramanian (https://www.cs.stonybrook.edu/~arunab/) 4. Shehar Bano (https://sheharbano.com/) 5. Carlee Joe-Wong (https://www.andrew.cmu.edu/user/cjoewong/) 6. Fotini Karinou (https://www.microsoft.com/en-us/research/people/fokarino/) 7. Radhika Mittal (http://people.eecs.berkeley.edu/~radhika/) 8. Justine Sherry (http://www.justinesherry.com/) 9. Anna Vizziello (http://tlclab.unipv.it/index.php/people/the-team/23-people/78-anna-vizziello) 10. Noa Zilberman (https://www.cl.cam.ac.uk/~nz247/)  Details on these outstanding women, as well as quotes from one of the many people who nominated these women, will soon be available at: http://n2women.comsoc.org/  We sincerely thank the nominators for taking out the time to submit the nominations thereby encouraging several young women researchers to acquire visibility. The "N2Women: Rising Stars in Computer Networking and Communications” is an annual list. This list focuses on amazing young women whose career start has already impacted research in networking and/or communications. Best, Subarna Chatterjee, Angela Sara Cacciapuoti, Ying Zhang, N2Women Awards Co-Chairs Katia Jaffrès-Runser and Sami Rollins, N2Women Board Co-Chairs http://n2women.comsoc.org/ <http://n2women.comsoc.org/> P.S. Networking Networking Women (N2Women) is a discipline-specific community for researchers in the communications and networking research fields. N2Women is an ACM SIGMOBILE program that is supported by the IEEE Communications Society, Microsoft Research, HP Labs, Google, Facebook, ACM SIGCOMM and IEEE Computer Society (CS) Technical Committee on Computer Communications (TCCC). We are very grateful for the support of these fabulous organisations. **

1 0

Overcoming divisions, making participation inclusive
by Vesna Manojlovic 28 Sep '18

28 Sep '18

Hi, I was reading this article & I found it strangely relevant for the RIPE community, so I wanted to share it with you: http://netdem.nl/en/articles/new-democracy-overcoming-social-division/ (althou I don't agree with the conclusion of the "fix" ) Vesna Some quotes: In my view, the success of the RIPE community is in its ability to "overcome [] divisions and bring the conflicting groups together at the negotiation table." For example: ISPs, governments/regulators & vendors . And we share some similar challenges: "it is becoming more difficult to find candidates for [volunteering positions] ... it has also become increasingly difficult to develop policy, which would account for the interests of all [] groups." "How to make [] participation inclusive?" "That’s why it is important to keep inventing and enlarging the repertoire of methods for citizens to be active outside of the established procedures." Of course, the differences are that the original article talks about democracy & politics, not the Internet Governance, but the overlap seems more and more prominent. OTOH, there is again the sparkling diversity discussion at IETF... https://www.ietf.org/mail-archive/web/ietf/current/msg109519.html https://tools.ietf.org/html/draft-carpenter-community-leaders-00 https://www.theengineroom.org/diversity-is-a-competency/

1 0

"Free speech" in the RIPE Code of Conduct
by Sasha Romijn 11 Sep '18

11 Sep '18

Hello all, I noticed the following in the RIPE mailing list and RIPE meeting Code of Conduct (emphasis mine): > Please treat each other with tolerance and respect. Free speech and an open exchange of ideas is encouraged and celebrated. Demeaning, intimidating or harming other community members 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. Earlier, the CoC also mentions "diversity of views”. My concern with this wording is that, in my personal experience, “free speech” and “diversity of views” are often used as arguments by people to justify sharing discriminatory views, or demanding that space is made for their ideas. It makes it seem like CoC decisions are taken in a way where free speech and the diversity of views are balanced against harm, rather than just saying that harmful statements are not ok. Even in the more restricted European legal interpretation of free speech, there are many statements that are inappropriate and harmful for a community that aims to be inclusive, yet most certainly within the legal bounds. By making free speech and diversity of views seem equally important to the incidence of harm, I think the current wording allows too much freedom, and can reduce the reporting rate. Increasing the reporting rate is a general struggle for communities, and anything that makes people more hesitant to report weakens the CoC. Personally, I’d be reluctant to report anything non-physical under a CoC that mentions free speech and diversity of ideas as values. If my memory serves me right, the text of the CoC was decided by the WG chairs. Was there an actual expert involved? And what was the reason for the chairs (or whoever else was involved) to mention free speech and diversity of views this way? Did they consider the potential negative impact? Writing CoC language is quite difficult and sensitive, and small changes can have large impacts. Sasha

4 3

talks at monitorama
by Stephen D. Strowes 06 Sep '18

06 Sep '18

Hey, Monitorama EU, took place this week in Amsterdam. The conference aims to be positive and welcoming to all. There were two talks at the conference this week specifically focussed on diversity/inclusivity that folks on this list may be interested in: Monica Sarbu opened the conference on Tuesday: - title: You don’t look like an Engineer - slides: https://speakerdeck.com/monicasarbu/you-dont-look-like-an-engineer-2 - video: https://www.youtube.com/watch?v=2V1G0Lb6r-g&t=29m50s Quintessence Anx spoke later the same day: - title: Unquantified Serendipity: Diversity in Development - video: https://www.youtube.com/watch?v=2V1G0Lb6r-g&t=2h45m S.

1 0

[Moderated]
by Moderated 17 Aug '18

17 Aug '18

This message has been removed from the archive.

1 0

Minutes of today's Diversity Task Force Call - 13 July 2018
by Mirjam Kuehne 13 Jul '18

13 Jul '18

Hi all, Here are some notes of today's diversity task force call. Kind regards, Mirjam ====== Diversity Task Force Meeting 13 July 2018 Brian, Vesna, Amanda, Mirjam, Sami (for the first ten minutes) Denesh sent his apologies and an update from UKNOF: “I am working on having us do a talk at the next RIPE meeting about how we have and are approaching diversity. I am hoping the talk will be given by someone else rather than me and at the moment, one of our new board members (from a couple of months ago) - Liz Stevens - has tentatively agreed to do this.” Updates from RIPE 76 -------------------- Amanda reported that we received a report from the organisation who facilitated the childcare at RIPE 76 and also from the participants. Everyone was very positive. There were five kids last time, we expect around ten at RIPE 77. More information on RIPE Labs: https://labs.ripe.net/Members/agowland/ripe-meeting-diversity-efforts-on-si… Plans for RIPE 77 ------------------ After it was such a success at RIPE 76, we will provide the same service at RIPE 77. We are also trying to promote it some more (e.g. on the registration page). We already found a childcare organisation in Amsterdam for RIPE 77. We are still looking for sponsors, but the RIPE NCC is also considering to ask for contributions from the parents (25 EUR per day). During the RIPE 77 week, there are school holidays in the south of the Netherlands. We are currently working with sponsor for the Women in Tech lunch. From now on, we will have a banner for “women and inclusion sponsor” on the RIPE Meeting website (in addition to the other sponsor banners). The mentorship programme will be offered again for RIPE 77. Mentors can sign up online for multiple meetings. Newcomers (and other interested participants) can sign up if they want to have a mentor. Registration for RIPE 77 will open on Monday and will include information childcare and mentorship. The gender metrics question will now also be included on the registration form. The RIPE Fellowship and the RACI programmes also help to increase diversity. See more details about the RIPE fellows at RIPE 76 on RIPE Labs: https://labs.ripe.net/Members/agowland/ripe-fellows-share-their-ripe-76-exp… There was also a nice RIPE Labs articles about the benefits of role models: https://labs.ripe.net/Members/agowland/why-role-models-matter-especially-in… Vesna announced that there will be a hackathon in Amsterdam prior to RIPE 77 in collaboration with the University of Delft. Benno Overeinder introduced us to the managing director for the Dutch office of girls and women in tech: https://www.vhto.nl/ We will see how we can collaborate with her and possibly organise a session around RIPE 77. Brian mentioned that the RIPE Meeting Code of Conduct and the pointer to the childcare is now in the Call for Presentations. Also, the PC agreed to ask presenters of larger organisations to possibly consider proposing another speaker/colleague to increase diversity in general. There is now also a line in the CfP about panels to increase more diversity in terms of companies/organisations. In the future, the PC would also like to include another sentence, something like: “We would also ask you to consider the diversity of the panel (in terms of gender, culture, etc.).” Vesna suggested to make the PC system more flexible to be able to change names/presenters more easily. Vesna will follow-up with the PC and the RIPE NCC web services team. Vesna also mentioned that she will talk to local groups in the Netherlands. And we we will also encourage others to do that. Other activities ----------------- Vesna is involved in organising a feminist meeting in Amsterdam in September. She will present about Internet Governance and will promote our diversity efforts. Mirjam reported that Shane looked at other methodologies to measure diversity at RIPE. He also suggested to look at the criteria we use to hand out prices at the end of the RIPE Meeting (current first person who registers wins a price and first Newcomer who registers wins a price). Maybe it’s time to look at other criteria? The idea used to be to encourage participation. But that is not really necessary anymore. Brian said it’s meant to be a silly fun thing and cautioned us to over-engineer it. Other suggestions were made on the call: - possibly take the first five or ten registrants and pick one of them (only if that person is in the room). - possibly award the 77th registration at RIPE 77 and so on (if that person is not in the room, pick another silly number). The RIPE NCC will come up with a proposal and send it to the diversity list. We agreed to do another call in September.

2 1

Video-conference meeting invitation: Diversity TF, 13 July 2018, 11AM EST
by Vesna Manojlovic 13 Jul '18

13 Jul '18

Dear all, let's have a pre-summer-holidays meeting, to discuss diversity topics! Everybody is welcome to join this video-call, not just "members" -- you become a member by being active! Agenda: - updates from RIPE NCC - updates from RIPE PC - open actions - preparations for RIPE77 - other contributions See you there! Vesna https://www.ripe.net/participate/ripe/tf/ripe-diversity-task-force *Diversity TF* Friday, July 13, 2018 11:00 am | Europe Summer Time (Amsterdam, GMT+02:00) | 1 hr Meeting number (access code): 705 350 265 Meeting password: C37cUX3q When it's time, join the meeting: https://ripencc.webex.com/ripencc/j.php?MTID=mc46a5825350add9093c80b2944bff… *Join by phone* *+44-203-478-5289* Call-in toll number (UK) Global call-in numbers <https://ripencc.webex.com/ripencc/globalcallin.php?serviceType=MC&ED=621456…> Can't join the meeting? <https://collaborationhelp.cisco.com/article/WBX000029055> IMPORTANT NOTICE: Please note that this WebEx service allows audio and other information sent during the session to be recorded, which may be discoverable in a legal matter. By joining this session, you automatically consent to such recordings. If you do not consent to being recorded, discuss your concerns with the host or do not join the session.

2 2

FW: [RIPE PC] For review: Draft call for presentations RIPE 77
by Brian Nisbet 21 Jun '18

21 Jun '18

Folks, The PC are looking at the CFP for RIPE 77 and we're looking at adding in some text about a few things. The first is a reference to the CoC, the second to childcare and the last is to something we were discussing in the PC around encouraging speakers, especially from big companies to consider if other, more diverse, voices might be able to present the material. Leslie has already suggested the following re: childcare Did you know that RIPE meetings now have onsite childcare? Read about the experiences of our next generation of engineers at https://labs.ripe.net/Members/agowland/ripe-meeting-diversity-efforts-on-si… The CfP is already quite long, so we need to make sure we don't make it too much longer, but your input would be gratefully received. Obviously we would ask the CfP not be spread outside this group until it goes public as there may be other things we need to change before next week. Thanks, Brian Brian Nisbet Network 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 On 18/06/2018, 14:13, "PC on behalf of Benno Overeinder" <pc-bounces(a)ripe.net on behalf of benno(a)NLnetLabs.nl> wrote: Hi all, Just before you go on holiday, we need to send out the CFP for RIPE 77 in Amsterdam. Find the draft text below. It is an updated CFP from the RIPE 76. There are two items I want to discuss with you: - the terms & conditions as discussed with Athina during PC lunch - inclusiveness in CFP: reference to, e.g., help with child care, code of conduct, etc. The terms & conditions text should be ready for/present in the PC submission system. Normally it does not appear in the CFP. The inclusiveness paragraph in CFP (maybe just 2 or 3 sentences): - is this a good idea? - next, who can provide some text for this paragraph (the Diversity TF?)? We would like to send out the CFP next week Monday, June 25th. Cheers, -- Benno ----------> %%%%% <---------- Call for Presentations A RIPE Meeting is an open event where Internet Service Providers, network operators and other interested parties get together. Although the meeting is mostly technical, it is also a chance for people to meet and network with others in their field. RIPE 77 will take place from 15-19 October in Amsterdam, The Netherlands. The RIPE Programme Committee (PC) is now seeking content proposals from the RIPE community for the plenary sessions, BoFs (Birds of a Feather sessions), panels, workshops, tutorials and lightning talks at RIPE 77. See the full descriptions of the different presentation formats, https://ripe77.ripe.net/submit-topic/presentation-formats/. Proposals for plenary sessions, BoFs, panels, workshops and tutorials must be submitted for full consideration no later than *26 August 2018*. Proposals submitted after this date will be considered depending on the remaining available space in the programme. The PC is looking for presentations covering topics of network engineering and operations, including but not limited to: - IPv6 deployment - Managing IPv4 scarcity - Data centre technologies - Network and DNS operations - Internet governance and regulatory practices - Network and routing security - Content delivery - Internet peering and mobile data exchange - Connected Things (aka. Internet of Things - IoT) Speakers Presenters, RIPE Working Group Chairs and the RIPE Programme Committee are required to cover their own costs to attend a RIPE Meeting (meeting ticket, travel and accommodation). We have various ticket options available depending on your needs. In extraordinary circumstances, the RIPE Chair can waive the meeting fee for presenters. These requests are dealt with on a case-by-case basis via pc(a)ripe.net. Also note that, on an individual basis, participants can apply for a RIPE Fellowship to develop their professional or academic career. For more information, please visit: https://www.ripe.net/participate/ripe/ripe-fellowship Submissions Presenters should be clear on whether they wish to submit a presentation for a plenary or working group (WG) session. At present, most working groups will solicit policy proposals, discussion points or other content directly via their mailing lists. If you’re not sure what kind of session you should be presenting at, please visit: https://ripe77.ripe.net/plenary-or-wg/ RIPE Meeting attendees are quite sensitive to keeping presentations non-commercial, and product marketing talks are strongly discouraged. Repeated audience feedback shows that the most successful talks focus on operational experience, research results, or case studies. For example, presenters wishing to describe a commercial solution should focus on the underlying technology and not attempt a product demonstration. Presenters should indicate how much time they will require. In general, the time allocated for the different presentation formats is as follows: - Plenary presentations: 20-25 minutes presentation with 5-10 minutes discussion - Tutorials: up to two hours (Monday morning) - Workshops: one hour (during evening sessions) to two hours (Monday morning) - BoFs: approximately one hour (during evening sessions) - Lightning talks: 10 minutes total for both presentation and any discussion The following general requirements apply: - Proposals must be submitted using the meeting submission system, https://ripe77.ripe.net/submit-topic/ - Lightning talks should also be submitted using the meeting submission system (https://ripe77.ripe.net/submit-topic/) and can be submitted any time up to and including the meeting week. The allocation of lightning talks will be announced on short notice, in some cases on the same day but often one day prior to the time slot allocated. - Presenters who propose a panel or BoF are encouraged to include speakers from several (perhaps even competing) companies and/or a neutral facilitator. - All presentation proposals will only be considered by the PC if they contain at least draft presentation slides (slides may be updated later on). For panels, proposals must contain a clear description, as well as the names of invited panellists, presenters and moderators. If you have any questions or requests concerning content submissions, please email pc(a)ripe.net. -- Benno J. Overeinder NLnet Labs https://www.nlnetlabs.nl/

4 8

Reviewing our on-site childcare pilot at RIPE 76
by Amanda Gowland 18 Jun '18

18 Jun '18

Hi all, We just published an article looking back on our childcare pilot at RIPE 76: https://labs.ripe.net/ Warm regards, Amanda

1 0

Harvard's Gender Tech 2018 Event - on now
by Amanda Gowland 05 Jun '18

05 Jun '18

Following the #HarvardGenderTech18 feed on Twitter is proving to be very interesting - highly recommend!

1 0