Finalizing (draft) charter of the Diversity TF by 2nd October
Dear all, after the attempt to discuss the charter through Etherpad, here is the new approach: let's do it on the mailing list. It's a mini-project, and here is the description. Please do your part. Thanks, Vesna ========== Goal: formulating charter (web page!) of the RIPE Diversity Task Force (Inverse) Timeline: - December: have the charter accepted / approved by RIPE community (how?) - November: include any suggested modifications - present draft charter during TF report @ RIPE75 - make a web-page & send to RIPE list on 6. October (Friday) - finalize draft charter before 2. October (Monday) - take 3-4 weeks to go through several iterations - re-start the discussion on the mailing list 4. September - discussion started on Etherpad/mailing list in July Examples: https://www.ripe.net/participate/ripe/tf/ripe-accountability-task-force // https://www.ripe.net/participate/ripe/tf/bcop Elements of the web page (charter): - short history (introduction) - short description of the scope & goal & timeline - list of members - a chair-persons, or multiple co-chairs - links Tasks: - Vesna: send initial email (this) - All: comment on the text for the web page - on the list (also say if you agree, so we can see that there is a consensus) - All: let me know (offlist) if you do NOT want to be listed as "member" (and you were present on one of the TF meetings) - All: let me know (offlist) if you DO want me to add you as a member - Vesna: keep track of time-line & send reminders - Someone: volunteer to be a co-chair (please start a new thread ;-) - co-chairs (or Vesna): keep track of comments; declare a consensus by 2nd October - Vesna: work with RIPE NCC webmaster to make the page - Vesna: email the page to ripe-list (for info / additional comments) =========text========== Introduction The RIPE Diversity Task Force was formed in May 2017 at RIPE 74 in Madrid. (new) Goal of the TF is increasing diversities in RIPE community. (new) Various diversities (gender diversity, race diversity, age diversity, socioeconomic diversity, regional diversity...) help to ensure larger variety of expertise and experiences available to the RIPE community to achieve its goals of "technical coordination necessary to enable the operation of the Internet." The task force will report on diversity/inclusion at RIPE Meetings currently, propose actions to increase diversity and then evaluate and report on the efficacy of the actions taken. Draft scope The RIPE Diversity Task Force agrees to: - Review and report on the current state of RIPE Meeting diversity - Work with the RIPE NCC to gather diversity metrics for benchmarking purposes - Identify key areas of action and delegate to the appropriate people (either community volunteers or the RIPE NCC) - Report progress on action points via RIPE web sites, the RIPE Diversity mailing list and RIPE Meetings (new) Timeline Although "increasing diversities" is a continuing activity, the effectiveness of the TF will be evaluated during the period RIPE 81 – RIPE 82 to ascertain it is still serving its purpose. Links: Main page about the task force: TBD; link will be somewhere here: https://www.ripe.net/participate/ripe/tf RIPE Labs articles: https://labs.ripe.net/Members/shane/measuring-diversity-at-ripe-meetings https://labs.ripe.net/Members/agowland/diversity-discussions-at-ripe-74 Archived presentations during RIPE Meetings: https://ripe73.ripe.net/archives/video/1246/ https://ripe74.ripe.net/archives/video/164 https://ripe74.ripe.net/presentations/154-Diversity-RIPE74v2.pdf Mailing list: https://lists.ripe.net/mailman/listinfo/diversity Live working document for the TF collaboration: http://etherpad.tools.ietf.org:9000/p/ripe-diversity-tf-2017 Members: - all that were present on one of the TF meetings (in person or on-line)
Vesna, At 2017-09-04 12:23:07 +0200 Vesna Manojlovic <BECHA@ripe.net> wrote:
after the attempt to discuss the charter through Etherpad, here is the new approach: let's do it on the mailing list.
Valuable lesson: Etherpad is not great for discussions. ;-)
==========
Goal: formulating charter (web page!) of the RIPE Diversity Task Force
(Inverse) Timeline: - December: have the charter accepted / approved by RIPE community (how?)
Traditionally the RIPE Chair approves the charter as proposed by a task force, right?
- November: include any suggested modifications - present draft charter during TF report @ RIPE75
Seems reasonable.
- make a web-page & send to RIPE list on 6. October (Friday) - finalize draft charter before 2. October (Monday)
Seems reasonable.
- take 3-4 weeks to go through several iterations - re-start the discussion on the mailing list 4. September
I think this is plenty of time.
- discussion started on Etherpad/mailing list in July
Examples: https://www.ripe.net/participate/ripe/tf/ripe-accountability-task-force // https://www.ripe.net/participate/ripe/tf/bcop
Elements of the web page (charter): - short history (introduction) - short description of the scope & goal & timeline - list of members - a chair-persons, or multiple co-chairs - links
Tasks: - Vesna: send initial email (this) - All: comment on the text for the web page - on the list (also say if you agree, so we can see that there is a consensus) - All: let me know (offlist) if you do NOT want to be listed as "member" (and you were present on one of the TF meetings) - All: let me know (offlist) if you DO want me to add you as a member - Vesna: keep track of time-line & send reminders - Someone: volunteer to be a co-chair (please start a new thread ;-) - co-chairs (or Vesna): keep track of comments; declare a consensus by 2nd October - Vesna: work with RIPE NCC webmaster to make the page - Vesna: email the page to ripe-list (for info / additional comments)
=========text==========
Introduction
The RIPE Diversity Task Force was formed in May 2017 at RIPE 74 in Madrid.
(new) Goal of the TF is increasing diversities in RIPE community.
Alternate version: The goal of the task force is to increase diversity in the RIPE community. A note about "diversities": I think that "diversity" is a word like "fish" in English... so generally you get "more diversity" like you get "more fish". In principle you do have situations where "fishes" is correct - for example when talking about different types of fish - even correct usage sounds a bit strange. So while technically "diversities" is fine here, I tend to think that "diversity" sounds more natural here...
(new) Various diversities (gender diversity, race diversity, age diversity, socioeconomic diversity, regional diversity...) help to ensure larger variety of expertise and experiences available to the RIPE community to achieve its goals of "technical coordination necessary to enable the operation of the Internet."
...while here "diversities" is probably okay, since we are talking about different types of diversity and examples are provided. (An alternate wording might be "Various types of diversity", but I think the current text is fine.)
The task force will report on diversity/inclusion at RIPE Meetings currently, propose actions to increase diversity and then evaluate and report on the efficacy of the actions taken.
Draft scope
The RIPE Diversity Task Force agrees to:
- Review and report on the current state of RIPE Meeting diversity - Work with the RIPE NCC to gather diversity metrics for benchmarking purposes - Identify key areas of action and delegate to the appropriate people (either community volunteers or the RIPE NCC) - Report progress on action points via RIPE web sites, the RIPE Diversity mailing list and RIPE Meetings
In this formulation the TF doesn't actually do anything, merely point out things to do and ask other people to do them. Any project management and so on needs to be outsourced. This isn't a problem, I just felt like pointing it out. ;-)
(new) Timeline
Although "increasing diversities" is a continuing activity, the effectiveness of the TF will be evaluated during the period RIPE 81 – RIPE 82 to ascertain it is still serving its purpose.
Does this mean "between RIPE 81 and RIPE 82", or does it mean "we're not sure when, but perhaps some time like RIPE 81 or RIPE 82"? In either case, I would be happier both if we picked a date for review and made that review a lot sooner. Can we agree on RIPE 79 for this? (That's 2 years from now, right?)
Links:
Main page about the task force: TBD; link will be somewhere here: https://www.ripe.net/participate/ripe/tf
RIPE Labs articles: https://labs.ripe.net/Members/shane/measuring-diversity-at-ripe-meetings https://labs.ripe.net/Members/agowland/diversity-discussions-at-ripe-74
Archived presentations during RIPE Meetings: https://ripe73.ripe.net/archives/video/1246/ https://ripe74.ripe.net/archives/video/164 https://ripe74.ripe.net/presentations/154-Diversity-RIPE74v2.pdf
Mailing list: https://lists.ripe.net/mailman/listinfo/diversity
Live working document for the TF collaboration: http://etherpad.tools.ietf.org:9000/p/ripe-diversity-tf-2017
Members: - all that were present on one of the TF meetings (in person or on-line)
Cheers, -- Shane
On 11/09/2017 12:37, Shane Kerr wrote:
(Inverse) Timeline: - December: have the charter accepted / approved by RIPE community (how?) Traditionally the RIPE Chair approves the charter as proposed by a task force, right?
Close. The Charter is presented to the RIPE community, and the RIPE Chair is responsible for declaring when the community has approved it. In practice, the process typically would have the charter sent to the mailing list first, then when it looks like there's consensus it will be scheduled for a slot in a plenary session at the RIPE meeting, and if it still looks like there's consensus the RIPE Chair will announce this at the conclusion of the relevant slot. At which point it's considered to have been endorsed by the community. This is also how approval of a taskforce's final report works (and a bunch of other stuff I should think). -- Malcolm Hutty | tel: +44 20 7645 3523 Head of Public Affairs | Read the LINX Public Affairs blog London Internet Exchange | http://publicaffairs.linx.net/ London Internet Exchange Ltd Monument Place, 24 Monument Street London EC3R 8AJ Company Registered in England No. 3137929 Trinity Court, Trinity Street, Peterborough PE1 1DA
thanks for your comments, Malcolm, Shane. Anyone else wants to add something? I'll be also looking at the comments that Daniel Karrenberg & Filiz Yilmaz gave for the charter of "accountability task force" back in the day... https://www.ripe.net/ripe/mail/archives/ripe-list/2017-March/001126.html https://www.ripe.net/ripe/mail/archives/ripe-list/2017-April/001130.html https://www.ripe.net/ripe/mail/archives/ripe-list/2017-May/001143.html Thanks, Vesna
Hi all,
Goal of the TF is increasing diversity in RIPE community.
I’m not entirely sure on the wording of this goal. I see these kind of efforts more as: removing barriers for participation, particularly those that disproportionally affect underrepresented and marginalised groups in the community, encourage and support their participation and inclusion, which will result in a more diverse community. So to me it’s more: if this TF does a great job, as a result we’ll see diversity increased, but that is not the direct goal - to me the direct goal is more removing barriers that prevent diversity, and looking for ways to offset barriers we can’t remove. I don’t immediately know how to word this concisely, and don’t feel strongly if people want to keep the current goal, but maybe someone else has an idea on how to improve it.. Thanks, Sasha (yes, changed name 🌈)
On Tue, Sep 26, 2017 at 7:04 AM, Sasha Romijn <sasha@mxsasha.eu> wrote:
Hi all,
Goal of the TF is increasing diversity in RIPE community.
I’m not entirely sure on the wording of this goal. I see these kind of efforts more as: removing barriers for participation, particularly those that disproportionally affect underrepresented and marginalised groups in the community, encourage and support their participation and inclusion, which will result in a more diverse community.
So to me it’s more: if this TF does a great job, as a result we’ll see diversity increased, but that is not the direct goal - to me the direct goal is more removing barriers that prevent diversity, and looking for ways to offset barriers we can’t remove.
I like your way of looking at this :) Leslie
I don’t immediately know how to word this concisely, and don’t feel strongly if people want to keep the current goal, but maybe someone else has an idea on how to improve it..
Thanks, Sasha (yes, changed name 🌈) _______________________________________________ diversity mailing list diversity@ripe.net https://lists.ripe.net/mailman/listinfo/diversity
Leslie wrote: [...]
So to me it’s more: if this TF does a great job, as a result we’ll see diversity increased, but that is not the direct goal - to me the direct goal is more removing barriers that prevent diversity, and looking for ways to offset barriers we can’t remove.
I like your way of looking at this :)
May I ask why the TF's goal should not be an actual increase in diversity and instead should just be the removal of (some) barriers? How can we know whether the TF's work addresses the right barriers if the goal is defined by the work being done and not the outcome of the work? Kind regards, Leo Vegoda
Leo & all, At 2017-09-26 14:31:56 +0000 Leo Vegoda <leo.vegoda@icann.org> wrote:
Leslie wrote:
[...]
So to me it’s more: if this TF does a great job, as a result we’ll see diversity increased, but that is not the direct goal - to me the direct goal is more removing barriers that prevent diversity, and looking for ways to offset barriers we can’t remove.
I like your way of looking at this :)
May I ask why the TF's goal should not be an actual increase in diversity and instead should just be the removal of (some) barriers? How can we know whether the TF's work addresses the right barriers if the goal is defined by the work being done and not the outcome of the work?
I agree. The goal should not be to have a RIPE community that could in theory be diverse, but rather to have a RIPE community that *is* diverse. Cheers, -- Shane
On 27 September 2017 10:57:37 GMT+01:00, Shane Kerr <shane@time-travellers.org> wrote:
Leo & all,
At 2017-09-26 14:31:56 +0000 Leo Vegoda <leo.vegoda@icann.org> wrote:
Leslie wrote:
[...]
So to me it’s more: if this TF does a great job, as a result we’ll see diversity increased, but that is not the direct goal - to me the direct goal is more removing barriers that prevent diversity, and looking for ways to offset barriers we can’t remove.
I like your way of looking at this :)
May I ask why the TF's goal should not be an actual increase in diversity and instead should just be the removal of (some) barriers? How can we know whether the TF's work addresses the right barriers if the goal is defined by the work being done and not the outcome of the work?
I agree.
The goal should not be to have a RIPE community that could in theory be diverse, but rather to have a RIPE community that *is* diverse.
Can't it be both? So increasing diversity by multiple methods including/primarily reducing the barriers etc? Brian Brian Nisbet Network Operations Manager, HEAnet, Ireland's National Research & Education Network
On 27/09/2017 10:57, Shane Kerr wrote:
So to me it’s more: if this TF does a great job, as a result we’ll see diversity increased, but that is not the direct goal - to me the direct goal is more removing barriers that prevent diversity, and looking for ways to offset barriers we can’t remove.
I like your way of looking at this :)
May I ask why the TF's goal should not be an actual increase in diversity and instead should just be the removal of (some) barriers? How can we know whether the TF's work addresses the right barriers if the goal is defined by the work being done and not the outcome of the work?
I agree.
The goal should not be to have a RIPE community that could in theory be diverse, but rather to have a RIPE community that *is* diverse.
There may be factors in society at large that mean fewer women want to come to a RIPE meeting. We can address some of those, by being a more welcoming place, and by actively showing that we are. But we can't fix everything: it's not given to us in this TF to persuade more women to become network engineers in the first place, or to study STEM topics. I think "fixing RIPE" is ambitious enough. Fixing society, well that's a rabbit hole beyond the scope of this TF. But we don't need to limit ourselves to "some" barriers. Any barrier that RIPE places in the way of diverse participation that reasonably can be removed, without causing more problems than it solves, we should address. In short, let's try to do what we can. But not more. -- Malcolm Hutty | tel: +44 20 7645 3523 Head of Public Affairs | Read the LINX Public Affairs blog London Internet Exchange | http://publicaffairs.linx.net/ London Internet Exchange Ltd Monument Place, 24 Monument Street London EC3R 8AJ Company Registered in England No. 3137929 Trinity Court, Trinity Street, Peterborough PE1 1DA
Malcolm Hutty wrote: [...]
May I ask why the TF's goal should not be an actual increase in diversity and instead should just be the removal of (some) barriers? How can we know whether the TF's work addresses the right barriers if the goal is defined by the work being done and not the outcome of the work?
I agree.
The goal should not be to have a RIPE community that could in theory be diverse, but rather to have a RIPE community that *is* diverse.
There may be factors in society at large that mean fewer women want to come to a RIPE meeting. We can address some of those, by being a more welcoming place, and by actively showing that we are. But we can't fix everything: it's not given to us in this TF to persuade more women to become network engineers in the first place, or to study STEM topics.
The lack of research into why diversity is so low is indeed disappointing. It could be that gender diversity is so low because the companies and universities hiring the people RIPE needs to attract also have problem hiring women. But gender is just one diversity dimension. If participation in RIPE is lower than we'd expect based on wider society, supply is unlikely to be the problem. Or at least not the only problem. A structured research programme would be very helpful in understanding the issues and so allow the TF and wider community to develop suitable approaches.
I think "fixing RIPE" is ambitious enough. Fixing society, well that's a rabbit hole beyond the scope of this TF.
This is the other part of where research would help. It would help identify the appropriate scope for goal setting. Kind regards, Leo
On 26/09/2017 15:16, Leslie wrote:
On Tue, Sep 26, 2017 at 7:04 AM, Sasha Romijn <sasha@mxsasha.eu> wrote:
Hi all,
Goal of the TF is increasing diversity in RIPE community.
I’m not entirely sure on the wording of this goal. I see these kind of efforts more as: removing barriers for participation, particularly those that disproportionally affect underrepresented and marginalised groups in the community, encourage and support their participation and inclusion, which will result in a more diverse community.
So to me it’s more: if this TF does a great job, as a result we’ll see diversity increased, but that is not the direct goal - to me the direct goal is more removing barriers that prevent diversity, and looking for ways to offset barriers we can’t remove.
I like your way of looking at this :)
+1 -- Malcolm Hutty | tel: +44 20 7645 3523 Head of Public Affairs | Read the LINX Public Affairs blog London Internet Exchange | http://publicaffairs.linx.net/ London Internet Exchange Ltd Monument Place, 24 Monument Street London EC3R 8AJ Company Registered in England No. 3137929 Trinity Court, Trinity Street, Peterborough PE1 1DA
Hi all, here is an update: - there was a suggestion from Shane to modify the text to focus on "diversity" rather then "diversities" , and move review to RIPE 79. - there was a suggestion form Sasha to add this text: "removing barriers for participation, particularly those that disproportionally affect underrepresented and marginalised groups in the community, encourage and support their participation and inclusion,' - new tasks: - after the TF is approved by RIPE Chair - activate the web page: https://www.ripe.net/participate/ripe/tf/ripe-diversity-task-force - add a link to TF on this web page: https://www.ripe.net/participate/ripe/tf New version of the text: Introduction The RIPE Diversity Task Force was formed in May 2017 at RIPE 74 in Madrid. The goal of the task force is to increase diversity in the RIPE community by various methods, for example by removing barriers for participation, particularly those that disproportionally affect underrepresented and marginalised groups in the community; and by encouraging and supporting their participation and inclusion. Various types of diversity (gender diversity, race diversity, age diversity, socioeconomic diversity, regional diversity...) help to ensure larger variety of expertise and experiences available to the RIPE community to achieve its goals of "technical coordination necessary to enable the operation of the Internet." Draft scope The RIPE Diversity Task Force agrees to: - Review and report on the current state of RIPE Meeting diversity - Identify key areas of action and delegate to the appropriate people (either community volunteers or the RIPE NCC) - Evaluate on the efficacy of the actions taken - Report progress on action points via RIPE web sites, the RIPE Diversity mailing list and RIPE Meetings - Work with the RIPE NCC to gather diversity metrics for benchmarking purposes NEW: - Hold meetings that are open to everyone - Maintain a work plan / list of actions ^^^ do we want to add this?? for transparency / accountability reasons Timeline Although "increasing diversities" is a continuing activity, the effectiveness of the TF will be evaluated during at RIPE 79, to ascertain it is still serving its purpose. Links Members ===== More comments? Thanks, Vesna On 04/09/2017 12:23, Vesna Manojlovic wrote:
Dear all,
after the attempt to discuss the charter through Etherpad, here is the new approach: let's do it on the mailing list.
It's a mini-project, and here is the description.
Please do your part.
Thanks, Vesna
==========
Goal: formulating charter (web page!) of the RIPE Diversity Task Force
(Inverse) Timeline: - December: have the charter accepted / approved by RIPE community (how?) - November: include any suggested modifications - present draft charter during TF report @ RIPE75 - make a web-page & send to RIPE list on 6. October (Friday) - finalize draft charter before 2. October (Monday) - take 3-4 weeks to go through several iterations - re-start the discussion on the mailing list 4. September - discussion started on Etherpad/mailing list in July
Examples: https://www.ripe.net/participate/ripe/tf/ripe-accountability-task-force // https://www.ripe.net/participate/ripe/tf/bcop
Elements of the web page (charter): - short history (introduction) - short description of the scope & goal & timeline - list of members - a chair-persons, or multiple co-chairs - links
Tasks: - Vesna: send initial email (this) - All: comment on the text for the web page - on the list (also say if you agree, so we can see that there is a consensus) - All: let me know (offlist) if you do NOT want to be listed as "member" (and you were present on one of the TF meetings) - All: let me know (offlist) if you DO want me to add you as a member - Vesna: keep track of time-line & send reminders - Someone: volunteer to be a co-chair (please start a new thread ;-) - co-chairs (or Vesna): keep track of comments; declare a consensus by 2nd October - Vesna: work with RIPE NCC webmaster to make the page - Vesna: email the page to ripe-list (for info / additional comments)
=========text==========
Introduction
The RIPE Diversity Task Force was formed in May 2017 at RIPE 74 in Madrid.
(new) Goal of the TF is increasing diversities in RIPE community.
(new) Various diversities (gender diversity, race diversity, age diversity, socioeconomic diversity, regional diversity...) help to ensure larger variety of expertise and experiences available to the RIPE community to achieve its goals of "technical coordination necessary to enable the operation of the Internet."
The task force will report on diversity/inclusion at RIPE Meetings currently, propose actions to increase diversity and then evaluate and report on the efficacy of the actions taken.
Draft scope
The RIPE Diversity Task Force agrees to:
- Review and report on the current state of RIPE Meeting diversity - Work with the RIPE NCC to gather diversity metrics for benchmarking purposes - Identify key areas of action and delegate to the appropriate people (either community volunteers or the RIPE NCC) - Report progress on action points via RIPE web sites, the RIPE Diversity mailing list and RIPE Meetings
(new) Timeline
Although "increasing diversities" is a continuing activity, the effectiveness of the TF will be evaluated during the period RIPE 81 – RIPE 82 to ascertain it is still serving its purpose.
Links:
Main page about the task force: TBD; link will be somewhere here: https://www.ripe.net/participate/ripe/tf
RIPE Labs articles: https://labs.ripe.net/Members/shane/measuring-diversity-at-ripe-meetings https://labs.ripe.net/Members/agowland/diversity-discussions-at-ripe-74
Archived presentations during RIPE Meetings: https://ripe73.ripe.net/archives/video/1246/ https://ripe74.ripe.net/archives/video/164 https://ripe74.ripe.net/presentations/154-Diversity-RIPE74v2.pdf
Mailing list: https://lists.ripe.net/mailman/listinfo/diversity
Live working document for the TF collaboration: http://etherpad.tools.ietf.org:9000/p/ripe-diversity-tf-2017
Members: - all that were present on one of the TF meetings (in person or on-line)
_______________________________________________ Diversity mailing list Diversity@ripe.net https://lists.ripe.net/mailman/listinfo/diversity
Vesna, On 29/09/2017 10:24, Vesna Manojlovic wrote:
Hi all,
here is an update:
- there was a suggestion from Shane to modify the text to focus on "diversity" rather then "diversities" , and move review to RIPE 79.
- there was a suggestion form Sasha to add this text:
"removing barriers for participation, particularly those that disproportionally affect underrepresented and marginalised groups in the community, encourage and support their participation and inclusion,'
- new tasks: - after the TF is approved by RIPE Chair - activate the web page: https://www.ripe.net/participate/ripe/tf/ripe-diversity-task-force - add a link to TF on this web page: https://www.ripe.net/participate/ripe/tf
New version of the text:
Introduction
The RIPE Diversity Task Force was formed in May 2017 at RIPE 74 in Madrid.
RIPE 74 in Budapest.
The goal of the task force is to increase diversity in the RIPE community by various methods, for example by removing barriers for participation, particularly those that disproportionally affect underrepresented and marginalised groups in the community; and by encouraging and supporting their participation and inclusion.
I really like this.
Various types of diversity (gender diversity, race diversity, age diversity, socioeconomic diversity, regional diversity...) help to ensure larger variety of expertise and experiences available to the RIPE community to achieve its goals of "technical coordination necessary to enable the operation of the Internet."
The repetition of the word "diversity" grates on my prose composition nerves, but if others are ok with it, I'm not going to argue. :)
Draft scope
The RIPE Diversity Task Force agrees to:
- Review and report on the current state of RIPE Meeting diversity - Identify key areas of action and delegate to the appropriate people (either community volunteers or the RIPE NCC) - Evaluate on the efficacy of the actions taken - Report progress on action points via RIPE web sites, the RIPE Diversity mailing list and RIPE Meetings - Work with the RIPE NCC to gather diversity metrics for benchmarking purposes
NEW: - Hold meetings that are open to everyone - Maintain a work plan / list of actions ^^^ do we want to add this?? for transparency / accountability reasons
I think we should say this, yes. Our BoF (and I think I'm still the only candidate for moderator?) in Dubai is one of these meetings. We're not saying all our meetings are open to everyone, but I have no problem with open meetings as long as everyone is respectful and constructive. I think we should (and are) maintain that work plan.
Timeline
Although "increasing diversities" is a continuing activity, the effectiveness of the TF will be evaluated during at RIPE 79, to ascertain it is still serving its purpose.
Argh, I do think I prefer "increasing diversity" because it makes more sense to me, sorry. I think pushing this out to 79 is sensible. Gives us two years.
More comments?
Thank you again for all your work on 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@heanet.ie www.heanet.ie Registered in Ireland, No. 275301. CRA No. 20036270
On 04/09/2017 12:23, Vesna Manojlovic wrote:
Dear all,
after the attempt to discuss the charter through Etherpad, here is the new approach: let's do it on the mailing list.
It's a mini-project, and here is the description.
Please do your part.
Thanks, Vesna
==========
Goal: formulating charter (web page!) of the RIPE Diversity Task Force
(Inverse) Timeline: - December: have the charter accepted / approved by RIPE community (how?) - November: include any suggested modifications - present draft charter during TF report @ RIPE75 - make a web-page & send to RIPE list on 6. October (Friday) - finalize draft charter before 2. October (Monday) - take 3-4 weeks to go through several iterations - re-start the discussion on the mailing list 4. September - discussion started on Etherpad/mailing list in July
Examples: https://www.ripe.net/participate/ripe/tf/ripe-accountability-task-force // https://www.ripe.net/participate/ripe/tf/bcop
Elements of the web page (charter): - short history (introduction) - short description of the scope & goal & timeline - list of members - a chair-persons, or multiple co-chairs - links
Tasks: - Vesna: send initial email (this) - All: comment on the text for the web page - on the list (also say if you agree, so we can see that there is a consensus) - All: let me know (offlist) if you do NOT want to be listed as "member" (and you were present on one of the TF meetings) - All: let me know (offlist) if you DO want me to add you as a member - Vesna: keep track of time-line & send reminders - Someone: volunteer to be a co-chair (please start a new thread ;-) - co-chairs (or Vesna): keep track of comments; declare a consensus by 2nd October - Vesna: work with RIPE NCC webmaster to make the page - Vesna: email the page to ripe-list (for info / additional comments)
=========text==========
Introduction
The RIPE Diversity Task Force was formed in May 2017 at RIPE 74 in Madrid.
(new) Goal of the TF is increasing diversities in RIPE community.
(new) Various diversities (gender diversity, race diversity, age diversity, socioeconomic diversity, regional diversity...) help to ensure larger variety of expertise and experiences available to the RIPE community to achieve its goals of "technical coordination necessary to enable the operation of the Internet."
The task force will report on diversity/inclusion at RIPE Meetings currently, propose actions to increase diversity and then evaluate and report on the efficacy of the actions taken.
Draft scope
The RIPE Diversity Task Force agrees to:
- Review and report on the current state of RIPE Meeting diversity - Work with the RIPE NCC to gather diversity metrics for benchmarking purposes - Identify key areas of action and delegate to the appropriate people (either community volunteers or the RIPE NCC) - Report progress on action points via RIPE web sites, the RIPE Diversity mailing list and RIPE Meetings
(new) Timeline
Although "increasing diversities" is a continuing activity, the effectiveness of the TF will be evaluated during the period RIPE 81 – RIPE 82 to ascertain it is still serving its purpose.
Links:
Main page about the task force: TBD; link will be somewhere here: https://www.ripe.net/participate/ripe/tf
RIPE Labs articles: https://labs.ripe.net/Members/shane/measuring-diversity-at-ripe-meetings https://labs.ripe.net/Members/agowland/diversity-discussions-at-ripe-74
Archived presentations during RIPE Meetings: https://ripe73.ripe.net/archives/video/1246/ https://ripe74.ripe.net/archives/video/164 https://ripe74.ripe.net/presentations/154-Diversity-RIPE74v2.pdf
Mailing list: https://lists.ripe.net/mailman/listinfo/diversity
Live working document for the TF collaboration: http://etherpad.tools.ietf.org:9000/p/ripe-diversity-tf-2017
Members: - all that were present on one of the TF meetings (in person or on-line)
_______________________________________________ Diversity mailing list Diversity@ripe.net https://lists.ripe.net/mailman/listinfo/diversity
_______________________________________________ diversity mailing list diversity@ripe.net https://lists.ripe.net/mailman/listinfo/diversity
Hi all, after the review of the technical writers, here is the final version of the text - in the form of the screenshot of the web page. Can we take another few days to wait for the last comments, and if there is no objection, someone other then me should pronounce the consensus. So the new deadline is Monday 9th October, 8:00 UTC. If so, then I can send the link to the actual page to the ripe-list for more input, and then RIPE Chair has to officially decide... Thanks, Vesna -------->8----------------8<------------------ RIPE Diversity Task Force The RIPE Diversity Task Force was formed in May 2017 at RIPE 74 in Budapest. The goal of the task force is to increase diversity in the RIPE community. We aim to remove barriers that prevent participation, particularly those that affect underrepresented and marginalised groups in the community. The RIPE community should be a welcoming place for everyone, regardless of race, ethnicity, culture, national origin, colour, immigration status, social and economic class, educational level, sex, sexual orientation, gender identity and expression, age, size, family status, political belief, religion, and mental and physical ability. A diverse RIPE community provides a wider variety of expertise and experiences to help achieve its goals of "technical coordination necessary to enable the operation of the Internet." Draft scope The RIPE Diversity Task Force agrees to: Review and report on the current state of RIPE Meeting diversity Identify key areas of action and delegate to the appropriate people (either community volunteers or the RIPE NCC) Evaluate the actions taken Report progress on action points through the RIPE Diversity mailing list and RIPE Meetings Work with the RIPE NCC to gather diversity metrics for benchmarking purposes Hold meetings that are open to everyone Maintain a work plan / list of actions Timeline Although "increasing diversity" is a continuing activity, the effectiveness of the TF will be evaluated at RIPE 79 to determine if it is still serving its purpose. Task Force Members RIPE community: Brian Nisbet Denesh Bhabuta Donal Cunningham Malcolm Hutty Shane Kerr RIPE NCC: Amanda Gowland Gergana Petrova Vesna Manojlovic Mirjam Kuehne RIPE Forum The RIPE Forum is an additional way to participate in RIPE community mailing list discussions using a web-based interface rather than an email client. -------->8----------------8<------------------
I think this looks very good. -hph On Thu, 5 Oct 2017 at 16:56, Vesna Manojlovic <BECHA@ripe.net> wrote:
Hi all,
after the review of the technical writers, here is the final version of the text - in the form of the screenshot of the web page.
Can we take another few days to wait for the last comments, and if there is no objection, someone other then me should pronounce the consensus. So the new deadline is Monday 9th October, 8:00 UTC.
If so, then I can send the link to the actual page to the ripe-list for more input, and then RIPE Chair has to officially decide...
Thanks, Vesna
-------->8----------------8<------------------
RIPE Diversity Task Force
The RIPE Diversity Task Force was formed in May 2017 at RIPE 74 in Budapest.
The goal of the task force is to increase diversity in the RIPE community. We aim to remove barriers that prevent participation, particularly those that affect underrepresented and marginalised groups in the community.
The RIPE community should be a welcoming place for everyone, regardless of race, ethnicity, culture, national origin, colour, immigration status, social and economic class, educational level, sex, sexual orientation, gender identity and expression, age, size, family status, political belief, religion, and mental and physical ability.
A diverse RIPE community provides a wider variety of expertise and experiences to help achieve its goals of "technical coordination necessary to enable the operation of the Internet."
Draft scope
The RIPE Diversity Task Force agrees to:
Review and report on the current state of RIPE Meeting diversity Identify key areas of action and delegate to the appropriate people (either community volunteers or the RIPE NCC) Evaluate the actions taken Report progress on action points through the RIPE Diversity mailing list and RIPE Meetings Work with the RIPE NCC to gather diversity metrics for benchmarking purposes Hold meetings that are open to everyone Maintain a work plan / list of actions Timeline
Although "increasing diversity" is a continuing activity, the effectiveness of the TF will be evaluated at RIPE 79 to determine if it is still serving its purpose.
Task Force Members
RIPE community: Brian Nisbet Denesh Bhabuta Donal Cunningham Malcolm Hutty Shane Kerr
RIPE NCC: Amanda Gowland Gergana Petrova Vesna Manojlovic Mirjam Kuehne
RIPE Forum
The RIPE Forum is an additional way to participate in RIPE community mailing list discussions using a web-based interface rather than an email client.
-------->8----------------8<------------------
_______________________________________________ diversity mailing list diversity@ripe.net https://lists.ripe.net/mailman/listinfo/diversity
-- -- Hans Petter Holen Mobile +47 45 06 60 54 | hph@oslo.net | http://hph.oslo.net
participants (8)
-
Brian Nisbet -
Hans Petter Holen -
Leo Vegoda -
Leslie -
Malcolm Hutty -
Sasha Romijn -
Shane Kerr -
Vesna Manojlovic