This working group aims at bringing experiences measuring diversity and inclusion in open source projects.
https://lists.linuxfoundation.org/mailman/listinfo/chaoss-diversity-inclusion
- The D&I Working Group meets every Monday at 9:30am CT (usually 16:30 CET, check your local time) via Zoom.
- Agenda and meeting minutes: http://bit.ly/chaoss-diwg
We have five Objectives for 2019. Read more.
The tech industry has a well-documented representation gap, and this issue is even more prevalent in open source communities. While there has been a marked emphasis on increasing diversity in these communities in recent years, numbers lag and the ability to foster inclusive environments remains challenging. With no standards or best practices for measuring inclusion, contributors, users and project teams lack the opportunity to make ethical, data-driven decisions.
For the D&I Working Group, within the CHAOSS project.
CHAOSS mission from website:
The CHAOSS community is developing metrics, methodologies, and software for expressing open source project health and sustainability. By measuring open source project health and sustainability, CHAOSS seeks to improve the transparency of open source project health and sustainability so that relevant stakeholders can make more informed decisions about open source project engagement.
Community health cannot exist without diversity and inclusion. Diversity and inclusion is thus central to the CHAOSS project goals. See Objective 3 for more details on adding D&I to the CHAOSS mission.
The CHAOSS D&I Working Group establishes and broadly communicates an ethical, peer-validated, research-informed, set of standards and best practices for measuring diversity and inclusion in open source projects, and ensures that CHAOSS project software can implement D&I metrics according to identified goals for inclusion with validation from key industry partnerships in open source.
The CHAOSS D&I Working Group has between January 2018 and December 2018:
- established collaboration spaces, including a mailing list, GitHub repository, and weekly calls.
- defined 7 focus areas which group metrics.
- established a template for resource pages that describe why D&I metrics are helpful and how to measure them.
- filled out an initial 10 resource pages.
- presented at 5 conferences via presentations, panels, and tutorials.
We are compiling dimensions of diversity and inclusion that can be used in the following areas of analysis:
| Focus Area | Goal |
|---|---|
| 1. Event Diversity | Identify the diversity and inclusion at events. |
| 2. Contributor Community Diversity | Identify the diversity of the contributions within a community, and howe those different contributions are valued. |
| 3. Communication Inclusivity | Identify how we are communicating with contributors, and potential contributors. |
| 4. Recognition of Good Work | Identify how we recognize/reward good work in our community. |
| 5. Leadership | Identify how healthy our community leadership is. |
| 6. Governance | Identify how diverse and inclusive our governance is. |
| 7. Project and Community | Identify how diverse and inclusive our project places, where community engagement occurs, are. |
Each area lists a collection of relevant questions. If you are interested in answering a question for your community, go to the associated resource page where we collect strategies for answering the question.
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 mailing list 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.
Maintainers
Core Contributors
The criteria for becoming a core contributor is to participate at least once per month over a period of 3 months. Participation could include providing feedback in the weekly D&I meetings, providing feedback on docs, or making other contributions on GitHub (commits / issues). People not participating over a 3 month period may be removed as core contributors.
If you'd like to be on our squad, an easy way to start is by going through the issue list and fixing some. 🎉
All Contributors Ordered by first name
Akshita Gupta, Alexander Serebrenik, Brian Proffitt, Chris Clark, Daniel Izquierdo Cortazar, Dawn Foster, Drashti, Emma Irwin, Georg Link, Jaice Singer Du Mars, Joshua R. Simmons, Kevin Lumbard, Laura Gaetano, Luis Villa, Matt Germonprez, Nicole Huesman, Nithya Ruff, Rupa Dachere, Sarah Conway, Shreyas, UTpH
Are you eligible to be on this list? You are if you helped in any capacity, for example: Filed an issue. Created a Pull Request. Gave feedback on our work. The team will try to update this list monthly, but please open an issue or post on the mailing list if we've missed anyone.
If you find yourself missing, please create a pull request or reach out to a maintainer. We started to maintain this list after starting the working group and are likely missing some of you. If you find yourself listed here and want to be removed, please create a pull request or ask a maintainer.
Collection of initiatives and related works that can inform our work or that we can collaborate with.