This working group aims at bringing experiences measuring diversity and inclusion in open source projects.
Its main goal focuses on understanding from a qualitative and quantitative point of view how diversity and inclusion can be measured. This will bring four main outcomes:
- First a set of metrics curated by the community focused on understanding and measuring diversity
- Second learn good practices from open source communities on improving their diversity and inclusion
- Third produce useful software to measure diversity from a quantitative point of view. This is expected to produce generic software to analyze several repositories of information such as Git repositories or Mailing lists
- Fourth, good practices on how to deal with such data, maintain and ways of collaboration with open source communities.
- Fifth, a method that other communities can reproduce the report for themselves.
An example of the expected outcomes is the OpenStack Gender Report that focuses on the analysis of the gender-diversity in the OpenStack Foundation. This project sponsored by Intel and Bitergia aims at helping the community with data. And we need data to make decisions!
This project is under the CHAOSS project that is part of The Linux Foundation.
As the CHAOSS project consists of two Technical Committees: Software and Metrics, this project aims at working closely with both and learn their best practices. In addition, this working group expects to discuss new ideas in terms of metrics and software with both committees improving the knowledge base around this topic.
Note: We want to make our tools and report inclusive globally.
- Integrate results with the general Metrics group
- Write down all of the goal-question-metric ideas we have in this document
- #14 Migrate Google Docs D&I GQM approach to this repository
- Validate with experts in the field.
- Produce reusable outcomes by third parties when measuring D&I
- #15 Create a method that other communities can reproduce the report for themselves
- Dissemination of the results across several communities
- Open Source Summit NA / Europe
- OSCON
- CHAOSScon NA
- Others
- We meet every other week. Next meeting:
June 6th,June 7th, 2018 at 6pm Eurpean Central Time (9am US Pacific Time). We will use the CHAOSS Zoom room: https://unomaha.zoom.us/j/720431288
We use the CHAOSS mailing list: https://wiki.linuxfoundation.org/chaoss/metrics#mail-list Please append email subject with: [wg-di]
See file di_metrics.md
(Following section is outdated. We need to compare this the current metrics and make sure we have everything.)
More to be done.
Metrics used in OpenStack Gender Report --- starting point for thinking about other diversity and inclusion metrics.
Governance and Leadership
- Board of Directors
- Technical Committee
- User Committee
- Working Groups Chairs
- OpenStack Ambassadors
- Project Technical Leaders
- OpenStack Foundation Officers
- Ratio of minority identification to whole community
- Role in community (basis for calculating minority ratios within each committee/workgroup/organ)
Summits Representation
- Keynote summits representation
- Summit attendees
- Summit speakers
Technical Contributions
- Number of commits by minority over time
- Number of developers by minority authoring those commits over time
- Types of contributions (code and others) by minority within those commits over time
- Number of code review submissions by minority over time
- Number of developers who have submitted changesets, by minority over time
- Number of code review votes undertaken by developers, by minority over time
- Number of developers who have voted in a code review process, by minority over time
- Number of core code review votes undertaken by developers, by minority over time
- Number of core code review votes undertaken by developers, by minority over time
- Number of developers who have participated in a core code review process, by minority over time
- Ratio_Authors: The number in this column denotes the ratio of minority developers for every 100 developers for a given project.
- Ratio_Commits: The number in this column denotes the ratio of commits submitted by minority developers for every 100 commits submitted by all developers for a given project.
- Authors: The number in this column denotes the total number of individuals identified as minority who have contributed to a given project, as tracked through the Git repositories.
- Commits: The number in this column denotes the total number of changes to the source code for a given project. A commit is usually submitted through a code review process.
Non Technical Contributions
- Number of emails by gender
- Emails activity by gender
- Characterization of mailing lists (development, users)
Minority identities
Standard survey questions for identity relating to diversity: https://github.com/drnikki/open-demographics/tree/master/doc-source/questions
- Age
- Disability
- Education
- Gender
- Language
- Location
- Race
- Religion
- Sexual and Romantic Orientation
- Socioeconomic Class
To be done
This project is open to anyone interested in the topic of diversity and inclusion. And this includes several areas of work such as diversity and inclusion from a broader perspective, mining software repositories, Python development, tech writing, people interested in speaking at events and others.
The collaboration guide is still in progress, but a first good step would be to introduce yourself at the CHAOSS Metrics or CHAOSS Software mailing lists explaining a bit your interest.
Most of the work in the metrics side will be done through pull requests to the markdown files containing discussions about the metrics used or to be used. This is the same method as when updating the software side of the project.
Collection of initiatives and related works that can inform our work or that we can collaborate with.