[diversity] FW: [RIPE PC] For review: Draft call for presentations RIPE 77

Gergana,

Thanks for this. I'm a little nervous of the word junior. I know exactly what you mean and young voices are definitely welcome, but I don't want people to think that young/different = more junior or that the person on stage isn't as good and as capable of presenting as the person who might otherwise have been up there, if that makes sense? But I might be over reacting here?

I do certainly think a focus on people who haven't presented before is good, but I'm wondering if that could be included in "new and different voices"?

Of course I'm now wondering when we'll get our first speaker presenting in sign language with an interpreter, but I'll leave that to a different day!

So to tweak it further:

" The RIPE PC and Community are always looking to hear new and different voices in the sessions, so when submitting, please always consider if another member of your project or team may be able to present the material."

But I've hacked off a lot of what you put in, Gergana, so I'm not sure if it's back to too short?

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 at heanet.ie www.heanet.ie
Registered in Ireland, No. 275301. CRA No. 20036270

> -----Original Message-----
> From: diversity <diversity-bounces at ripe.net> On Behalf Of Gergana Petrova
> Sent: Thursday 21 June 2018 13:53
> To: diversity at ripe.net
> Subject: Re: [diversity] FW: [RIPE PC] For review: Draft call for presentations
> RIPE 77
> 
> Hi all,
> 
> What about "if another (a junior) member of your project or team", just to
> get them thinking a little that having young people present is ok.
> 
> Or we can do "The RIPE PC are always looking for new voices in the sessions,
> so when submitting, please always consider if another member of your
> project or team may be able to present the material. Maybe someone junior,
> or someone who has never had the chance to present before."
> 
> Oh, I deleted "plenary", because I suppose the same is valid for the WG
> sessions, no?
> 
> Cheers,
> Gergana
> 
> On 20/06/2018 14:12, Brian Nisbet wrote:
> > Mirjam,
> >
> > Absolutely not a requirement, just trying to figure out how to phrase it.
> >
> > I mean, I'm wondering if something like:
> >
> > The RIPE PC are always looking for new voices in the Plenary sessions, so
> when submitting, please always consider if another member of your project
> or team may be able to present the material.
> >
> > But I'm really unsure about this.
> >
> > 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 at heanet.ie www.heanet.ie
> > Registered in Ireland, No. 275301. CRA No. 20036270
> >
> >> -----Original Message-----
> >> From: Mirjam Kuehne <mir at ripe.net>
> >> Sent: Tuesday 19 June 2018 12:44
> >> To: Brian Nisbet <brian.nisbet at heanet.ie>; Amanda Gowland
> >> <agowland at ripe.net>; diversity at ripe.net
> >> Subject: Re: [diversity] FW: [RIPE PC] For review: Draft call for
> >> presentations RIPE 77
> >>
> >> Hi Brian,
> >>
> >> I like the idea of asking speakers to consider their colleagues to
> >> present in order to increase diversity (and to giver others a
> >> chance). I am not sure how to phrase that. But I guess if we would
> >> make it a suggestion or recommendation rather than a requirement.
> >>
> >> Having said that, I have presented at conferences that did require
> >> moderators to ensure 50% male speakers for a panel session for instance.
> >>
> >> Mirjam
> >>
> >>
> >>
> >> On 19/06/2018 13:36, Brian Nisbet wrote:
> >>> Amanda,
> >>>
> >>> Thanks, that seems pretty good to me. And the kids t-shirts sound
> >>> great
> >> too! Marginal cost against everything else.
> >>>
> >>> On trying to encourage companies to consider who is presenting (such
> >>> as
> >> engineers from FB or the like where anyone on the team, in theory,
> >> could present the material) are there any thoughts?
> >>>
> >>> 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 at heanet.ie www.heanet.ie
> >>> Registered in Ireland, No. 275301. CRA No. 20036270
> >>>
> >>>> -----Original Message-----
> >>>> From: diversity <diversity-bounces at ripe.net> On Behalf Of Amanda
> >>>> Gowland
> >>>> Sent: Tuesday 19 June 2018 10:41
> >>>> To: diversity at ripe.net
> >>>> Subject: Re: [diversity] FW: [RIPE PC] For review: Draft call for
> >>>> presentations RIPE 77
> >>>>
> >>>> Hi Brian and Diversity TF,
> >>>>
> >>>> Great thinking...I've just made a tweak to what Leslie suggested
> >>>> and added a couple lines for the CoC...
> >>>>
> >>>> BTW - I'm thinking of doing a small batch of mini RIPE Meeting
> >>>> t-shirts for the childcare kids :)
> >>>>
> >>>> What do you think?
> >>>>
> >>>> Thanks,
> >>>>
> >>>> Amanda
> >>>>
> >>>> ----
> >>>>
> >>>>
> >>>>       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 takes 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 at 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
> >>>>
> >>>> Diversity and Inclusion - On-Site Childcare and RIPE Meeting Code
> >>>> of Conduct
> >>>>
> >>>> Did you know that RIPE Meetings now have on-site childcare?
> >>>> Registration for RIPE 77 (ages 6m-10yo) opens in early July on the
> >>>> meeting website - space is limited, so be quick to reserve!
> >>>>
> >>>> Read about the experiences of our next generation of engineers at:
> >>>> https://labs.ripe.net/Members/agowland/ripe-meeting-diversity-effor
> >>>> ts
> >>>> -
> >>>> on-site-childcare-at-ripe-76
> >>>>
> >>>> Ensuring that RIPE Meeting values are upheld and attendees
> >>>> experience a professional, respectful and safe meeting is a
> >>>> priority. Please see the RIPE Meeting Code of Conduct:
> >>>> https://www.ripe.net/participate/meetings/ripe-meetings/ripe-
> meetin
> >>>> g-
> >>>> code-of-conduct
> >>>>
> >>>>
> >>>>       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 at ripe.net>.On 19/06/2018 10:39, Brian Nisbet
> wrote:
> >>>>> 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-
> effo
> >>>>> rt
> >>>>> s-
> >>>>> on-site-childcare-at-ripe-76
> >>>>>
> >>>>> 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 at 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 at ripe.net on behalf of benno at 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 at 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 at ripe.net.
> >>>>>
> >>>>>
> >>>>>
> >>>>>       --
> >>>>>       Benno J. Overeinder
> >>>>>       NLnet Labs
> >>>>>       https://www.nlnetlabs.nl/
> >>>>>
> >>>>>
> >>>>>
> >>>>> _______________________________________________
> >>>>> diversity mailing list
> >>>>> diversity at ripe.net
> >>>>> https://mailman.ripe.net/
> >>>>
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> diversity mailing list
> >>>> diversity at ripe.net
> >>>> https://mailman.ripe.net/
> >>> _______________________________________________
> >>> diversity mailing list
> >>> diversity at ripe.net
> >>> https://mailman.ripe.net/
> >>>
> >
> > _______________________________________________
> > diversity mailing list
> > diversity at ripe.net
> > https://mailman.ripe.net/
> >
> 
> _______________________________________________
> diversity mailing list
> diversity at ripe.net
> https://mailman.ripe.net/