This is the repository that houses documentation related to the Diversity & Inclusion Badging Project
The purpose of this repository is to serve as a "starting point" for the Diversity and Inclusion Badging Program
- Problem statement
- Opportunity
- Goal
- Applying for Badges
- Reviewing Badging submissions
- Work to date
- Contributors
Diversity in open source is opaque to participants, newcomers, and stakeholders because contributors are distributed, and in many cases are an agglomeration of individuals in different locations. Inclusivity for open source projects is impeded by long standing practices that have side effects that act to reproduce the current state of limited diversity.
The project aims to increase understanding of the open source project and event practices that encourage greater diversity and wider inclusion of people from different backgrounds.
The goal of the Diversity & Inclusion Badging Program is to encourage projects and events to obtain D&I badges for reasons of leadership, self-reflection, and self-improvement on issues critical to building the Internet as a social good.
Here are the primary deliverables of the Diversity & Inclusion Badging Program:
- Establish an environment where projects and events can engage in the badging program
- Aligning the badging program with best practices, guidelines and recommendations from Diversity & Inclusion efforts on the CHAOSS project
- Connecting with existing badging standards of IMS Global including
- Building an open, peer-review system for the D&I Badging Program
The Event Badging section of CHAOSS Badging is about measuring inclusivity of different technical events through human reviews.
In order to submit an application for a project, go through the following documents:
- Applicant role - This document describes the GitHub permissions and the responsibilities of a CHAOSS Badging Applicant.
- Event submission requirements - Minimum requirements for a Event to be eligible for participation in CHAOSS Badging process.
- Event submission guidelines - Guidelines and steps on how a Event can gain a badge under the CHAOSS Badging program.
Badges are assigned according to how the Reviewers mark out the review checklist according to the the information initially filled in by the Applicant.
The percentages are calculated excluding the initial checks, based of the average of checklists of at least two reviewers.
| Level | Badge | Percentage of Requirements Met |
|---|---|---|
| Pending |  |
Less than 40% |
| Passing |  |
Greater than or equal to 40% and less than 60% |
| Silver |  |
Greater than or equal to 60% and less than 80% |
| Gold |  |
Greater than 80% |
Reviewers are an essential part of CHAOSS Badging since their feedback and interaction with an applicant would determine the direction an application takes.
In order to get familiar with what is expected of reviewers, go through the following documents:
- Reviewer role - This document describes the GitHub permmissions and the responsibilities of a CHAOSS Badging Reviewer.
- Reviewer guide
To become a part of the process, open an issue on this repository with the title Reviewer Application and introduce yourself
The CHAOSS Badging Project has performed a pilot test and we are in preparation for another pilot test and the project launch. Please email Matt Snell for more information!
Maintainers
Core Contributors