[diversity] Finalizing (draft) charter of the Diversity TF by 2nd October

Vesna,

At 2017-09-04 12:23:07 +0200
Vesna Manojlovic <BECHA at 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://mailman.ripe.net/
> 
> 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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: </ripe/mail/archives/diversity/attachments/20170911/371ac297/attachment.sig>