├── LICENSE ├── README.md ├── moderator-guide.md ├── reviewer-guide.md └── roles ├── README.md ├── applicant.md ├── maintainer.md ├── moderator.md └── reviewer.md /LICENSE: -------------------------------------------------------------------------------- 1 | MIT License 2 | 3 | Copyright (c) 2020 CHAOSS 4 | 5 | Permission is hereby granted, free of charge, to any person obtaining a copy 6 | of this software and associated documentation files (the "Software"), to deal 7 | in the Software without restriction, including without limitation the rights 8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 9 | copies of the Software, and to permit persons to whom the Software is 10 | furnished to do so, subject to the following conditions: 11 | 12 | The above copyright notice and this permission notice shall be included in all 13 | copies or substantial portions of the Software. 14 | 15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 21 | SOFTWARE. 22 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Diversity and Inclusion Badging 2 | 3 | 4 | 5 | This is the repository that houses documentation related to the Diversity & Inclusion Badging Project 6 | 7 | The purpose of this repository is to serve as a "starting point" for the Diversity and Inclusion Badging Program 8 | 9 | ## Table of contents 10 | 11 | - [Problem statement](#problem-statement) 12 | - [Opportunity](#opportunity) 13 | - [Goal](#goal) 14 | - [Applying for Badges](#applying-for-badges) 15 | - [Reviewing Badging submissions](#reviewing-badging-submissions) 16 | - [Work to date](#work-to-date) 17 | - [Contributors](#contributors) 18 | 19 | ## Problem Statement 20 | 21 | 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. 22 | 23 | ## Opportunity 24 | 25 | 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. 26 | 27 | ## Goal 28 | 29 | 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. 30 | 31 | Here are the primary deliverables of the Diversity & Inclusion Badging Program: 32 | 33 | * Establish an environment where projects and events can engage in the badging program 34 | * Aligning the badging program with best practices, guidelines and recommendations from Diversity & Inclusion efforts on the CHAOSS project 35 | * Connecting with existing badging standards of IMS Global including 36 | * Building an open, peer-review system for the D&I Badging Program 37 | 38 | ## Applying for Badges 39 | 40 | ### Event Badging 41 | 42 | The Event Badging section of CHAOSS Badging is about measuring inclusivity of different technical events through human reviews. 43 | 44 | In order to submit an application for a project, go through the following documents: 45 | - [Applicant role](./roles/applicant.md) - This document describes the GitHub permissions and the responsibilities of a CHAOSS Badging Applicant. 46 | - [Event submission requirements](https://github.com/badging/event-diversity-and-inclusion/blob/master/submission/requirements.md) - Minimum requirements for a Event to be eligible for participation in CHAOSS Badging process. 47 | - [Event submission guidelines](https://github.com/badging/event-diversity-and-inclusion/blob/master/submission/guidelines.md) - Guidelines and steps on how a Event can gain a badge under the CHAOSS Badging program. 48 | 49 | #### Badge Levels 50 | 51 | Badges are assigned according to how the Reviewers mark out the [review checklist](https://github.com/badging/event-diversity-and-inclusion/blob/master/.github/checklist.md) according to the the information initially filled in by the Applicant. 52 | 53 | The percentages are calculated excluding the initial checks, based of the average of checklists of at least two reviewers. 54 | 55 | 56 | | Level | Badge | Percentage of Requirements Met 57 | |--------------|--------------|------------------------------------- 58 | | Pending | ![Pending] | Less than 40% 59 | | Passing | ![Passing] | Greater than or equal to 40% and less than 60% 60 | | Silver | ![Silver] | Greater than or equal to 60% and less than 80% 61 | | Gold | ![Gold] | Greater than 80% 62 | 63 | ## Reviewing Badging submissions 64 | 65 | Reviewers are an essential part of CHAOSS Badging since their feedback and interaction with an applicant would determine the direction an application takes. 66 | 67 | In order to get familiar with what is expected of reviewers, go through the following documents: 68 | - [Reviewer role](./roles/reviewer.md) - This document describes the GitHub permmissions and the responsibilities of a CHAOSS Badging Reviewer. 69 | - [Reviewer guide](./reviewer-guide.md) 70 | 71 | **To become a part of the process, open an issue on this repository with the title `Reviewer Application` and introduce yourself** 72 | 73 | ## Work to Date 74 | 75 | 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](msnell@unomaha.edu) for more information! 76 | 77 | ## Contributors 78 | 79 | **Maintainers** 80 | 81 | - [Matt Snell](https://github.com/nebrethar) 82 | - [Saleh Abdel Motaal](https://github.com/smotaal) 83 | 84 | **Core Contributors** 85 | 86 | - [Ore-Aruwaji Oloruntola](https://github.com/thecraftman) 87 | - [Aastha Bist](https://github.com/bistaastha) 88 | 89 | [Pending]: https://img.shields.io/badge/D%26I-Pending-red?style=flat-square&labelColor=583586&logo=data:image/svg+xml;base64,PHN2ZyB2ZXJzaW9uPSIxLjEiIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwL3N2ZyIgdmlld0JveD0iMCAwIDI1MCAyNTAiPgo8cGF0aCBmaWxsPSIjMUM5QkQ2IiBkPSJNOTcuMSw0OS4zYzE4LTYuNywzNy44LTYuOCw1NS45LTAuMmwxNy41LTMwLjJjLTI5LTEyLjMtNjEuOC0xMi4yLTkwLjgsMC4zTDk3LjEsNDkuM3oiLz4KPHBhdGggZmlsbD0iIzZBQzdCOSIgZD0iTTE5NC42LDMyLjhMMTc3LjIsNjNjMTQuOCwxMi4zLDI0LjcsMjkuNSwyNy45LDQ4LjVoMzQuOUMyMzYuMiw4MC4yLDIxOS45LDUxLjcsMTk0LjYsMzIuOHoiLz4KPHBhdGggZmlsbD0iI0JGOUNDOSIgZD0iTTIwNC45LDEzOS40Yy03LjksNDMuOS00OS45LDczLTkzLjgsNjUuMWMtMTMuOC0yLjUtMjYuOC04LjYtMzcuNS0xNy42bC0yNi44LDIyLjQKCWM0Ni42LDQzLjQsMTE5LjUsNDAuOSwxNjIuOS01LjdjMTYuNS0xNy43LDI3LTQwLjIsMzAuMS02NC4ySDIwNC45eiIvPgo8cGF0aCBmaWxsPSIjRDYxRDVGIiBkPSJNNTUuNiwxNjUuNkMzNS45LDEzMS44LDQzLjMsODguOCw3My4xLDYzLjVMNTUuNywzMy4yQzcuNSw2OS44LTQuMiwxMzcuNCwyOC44LDE4OEw1NS42LDE2NS42eiIvPgo8L3N2Zz4K 90 | 91 | [Passing]: https://img.shields.io/badge/D%26I-Passing-passing?style=flat-square&labelColor=583586&logo=data:image/svg+xml;base64,PHN2ZyB2ZXJzaW9uPSIxLjEiIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwL3N2ZyIgdmlld0JveD0iMCAwIDI1MCAyNTAiPgo8cGF0aCBmaWxsPSIjMUM5QkQ2IiBkPSJNOTcuMSw0OS4zYzE4LTYuNywzNy44LTYuOCw1NS45LTAuMmwxNy41LTMwLjJjLTI5LTEyLjMtNjEuOC0xMi4yLTkwLjgsMC4zTDk3LjEsNDkuM3oiLz4KPHBhdGggZmlsbD0iIzZBQzdCOSIgZD0iTTE5NC42LDMyLjhMMTc3LjIsNjNjMTQuOCwxMi4zLDI0LjcsMjkuNSwyNy45LDQ4LjVoMzQuOUMyMzYuMiw4MC4yLDIxOS45LDUxLjcsMTk0LjYsMzIuOHoiLz4KPHBhdGggZmlsbD0iI0JGOUNDOSIgZD0iTTIwNC45LDEzOS40Yy03LjksNDMuOS00OS45LDczLTkzLjgsNjUuMWMtMTMuOC0yLjUtMjYuOC04LjYtMzcuNS0xNy42bC0yNi44LDIyLjQKCWM0Ni42LDQzLjQsMTE5LjUsNDAuOSwxNjIuOS01LjdjMTYuNS0xNy43LDI3LTQwLjIsMzAuMS02NC4ySDIwNC45eiIvPgo8cGF0aCBmaWxsPSIjRDYxRDVGIiBkPSJNNTUuNiwxNjUuNkMzNS45LDEzMS44LDQzLjMsODguOCw3My4xLDYzLjVMNTUuNywzMy4yQzcuNSw2OS44LTQuMiwxMzcuNCwyOC44LDE4OEw1NS42LDE2NS42eiIvPgo8L3N2Zz4K 92 | 93 | [Silver]: https://img.shields.io/badge/D%26I-Silver-silver?style=flat-square&labelColor=583586&logo=data:image/svg+xml;base64,PHN2ZyB2ZXJzaW9uPSIxLjEiIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwL3N2ZyIgdmlld0JveD0iMCAwIDI1MCAyNTAiPgo8cGF0aCBmaWxsPSIjMUM5QkQ2IiBkPSJNOTcuMSw0OS4zYzE4LTYuNywzNy44LTYuOCw1NS45LTAuMmwxNy41LTMwLjJjLTI5LTEyLjMtNjEuOC0xMi4yLTkwLjgsMC4zTDk3LjEsNDkuM3oiLz4KPHBhdGggZmlsbD0iIzZBQzdCOSIgZD0iTTE5NC42LDMyLjhMMTc3LjIsNjNjMTQuOCwxMi4zLDI0LjcsMjkuNSwyNy45LDQ4LjVoMzQuOUMyMzYuMiw4MC4yLDIxOS45LDUxLjcsMTk0LjYsMzIuOHoiLz4KPHBhdGggZmlsbD0iI0JGOUNDOSIgZD0iTTIwNC45LDEzOS40Yy03LjksNDMuOS00OS45LDczLTkzLjgsNjUuMWMtMTMuOC0yLjUtMjYuOC04LjYtMzcuNS0xNy42bC0yNi44LDIyLjQKCWM0Ni42LDQzLjQsMTE5LjUsNDAuOSwxNjIuOS01LjdjMTYuNS0xNy43LDI3LTQwLjIsMzAuMS02NC4ySDIwNC45eiIvPgo8cGF0aCBmaWxsPSIjRDYxRDVGIiBkPSJNNTUuNiwxNjUuNkMzNS45LDEzMS44LDQzLjMsODguOCw3My4xLDYzLjVMNTUuNywzMy4yQzcuNSw2OS44LTQuMiwxMzcuNCwyOC44LDE4OEw1NS42LDE2NS42eiIvPgo8L3N2Zz4K 94 | 95 | [Gold]: https://img.shields.io/badge/D%26I-Gold-yellow?style=flat-square&labelColor=583586&logo=data:image/svg+xml;base64,PHN2ZyB2ZXJzaW9uPSIxLjEiIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwL3N2ZyIgdmlld0JveD0iMCAwIDI1MCAyNTAiPgo8cGF0aCBmaWxsPSIjMUM5QkQ2IiBkPSJNOTcuMSw0OS4zYzE4LTYuNywzNy44LTYuOCw1NS45LTAuMmwxNy41LTMwLjJjLTI5LTEyLjMtNjEuOC0xMi4yLTkwLjgsMC4zTDk3LjEsNDkuM3oiLz4KPHBhdGggZmlsbD0iIzZBQzdCOSIgZD0iTTE5NC42LDMyLjhMMTc3LjIsNjNjMTQuOCwxMi4zLDI0LjcsMjkuNSwyNy45LDQ4LjVoMzQuOUMyMzYuMiw4MC4yLDIxOS45LDUxLjcsMTk0LjYsMzIuOHoiLz4KPHBhdGggZmlsbD0iI0JGOUNDOSIgZD0iTTIwNC45LDEzOS40Yy03LjksNDMuOS00OS45LDczLTkzLjgsNjUuMWMtMTMuOC0yLjUtMjYuOC04LjYtMzcuNS0xNy42bC0yNi44LDIyLjQKCWM0Ni42LDQzLjQsMTE5LjUsNDAuOSwxNjIuOS01LjdjMTYuNS0xNy43LDI3LTQwLjIsMzAuMS02NC4ySDIwNC45eiIvPgo8cGF0aCBmaWxsPSIjRDYxRDVGIiBkPSJNNTUuNiwxNjUuNkMzNS45LDEzMS44LDQzLjMsODguOCw3My4xLDYzLjVMNTUuNywzMy4yQzcuNSw2OS44LTQuMiwxMzcuNCwyOC44LDE4OEw1NS42LDE2NS42eiIvPgo8L3N2Zz4K 96 | 97 | [Pending]: https://img.shields.io/badge/D%26I-Pending-red?style=flat-square&labelColor=583586&logo=data:image/svg+xml;base64,PHN2ZyB2ZXJzaW9uPSIxLjEiIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwL3N2ZyIgdmlld0JveD0iMCAwIDI1MCAyNTAiPgo8cGF0aCBmaWxsPSIjMUM5QkQ2IiBkPSJNOTcuMSw0OS4zYzE4LTYuNywzNy44LTYuOCw1NS45LTAuMmwxNy41LTMwLjJjLTI5LTEyLjMtNjEuOC0xMi4yLTkwLjgsMC4zTDk3LjEsNDkuM3oiLz4KPHBhdGggZmlsbD0iIzZBQzdCOSIgZD0iTTE5NC42LDMyLjhMMTc3LjIsNjNjMTQuOCwxMi4zLDI0LjcsMjkuNSwyNy45LDQ4LjVoMzQuOUMyMzYuMiw4MC4yLDIxOS45LDUxLjcsMTk0LjYsMzIuOHoiLz4KPHBhdGggZmlsbD0iI0JGOUNDOSIgZD0iTTIwNC45LDEzOS40Yy03LjksNDMuOS00OS45LDczLTkzLjgsNjUuMWMtMTMuOC0yLjUtMjYuOC04LjYtMzcuNS0xNy42bC0yNi44LDIyLjQKCWM0Ni42LDQzLjQsMTE5LjUsNDAuOSwxNjIuOS01LjdjMTYuNS0xNy43LDI3LTQwLjIsMzAuMS02NC4ySDIwNC45eiIvPgo8cGF0aCBmaWxsPSIjRDYxRDVGIiBkPSJNNTUuNiwxNjUuNkMzNS45LDEzMS44LDQzLjMsODguOCw3My4xLDYzLjVMNTUuNywzMy4yQzcuNSw2OS44LTQuMiwxMzcuNCwyOC44LDE4OEw1NS42LDE2NS42eiIvPgo8L3N2Zz4K 98 | 99 | [Badging]: https://img.shields.io/badge/D%26I-Badging-passing?style=flat-square&labelColor=583586&logo=data:image/svg+xml;base64,PHN2ZyB2ZXJzaW9uPSIxLjEiIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwL3N2ZyIgdmlld0JveD0iMCAwIDI1MCAyNTAiPgo8cGF0aCBmaWxsPSIjMUM5QkQ2IiBkPSJNOTcuMSw0OS4zYzE4LTYuNywzNy44LTYuOCw1NS45LTAuMmwxNy41LTMwLjJjLTI5LTEyLjMtNjEuOC0xMi4yLTkwLjgsMC4zTDk3LjEsNDkuM3oiLz4KPHBhdGggZmlsbD0iIzZBQzdCOSIgZD0iTTE5NC42LDMyLjhMMTc3LjIsNjNjMTQuOCwxMi4zLDI0LjcsMjkuNSwyNy45LDQ4LjVoMzQuOUMyMzYuMiw4MC4yLDIxOS45LDUxLjcsMTk0LjYsMzIuOHoiLz4KPHBhdGggZmlsbD0iI0JGOUNDOSIgZD0iTTIwNC45LDEzOS40Yy03LjksNDMuOS00OS45LDczLTkzLjgsNjUuMWMtMTMuOC0yLjUtMjYuOC04LjYtMzcuNS0xNy42bC0yNi44LDIyLjQKCWM0Ni42LDQzLjQsMTE5LjUsNDAuOSwxNjIuOS01LjdjMTYuNS0xNy43LDI3LTQwLjIsMzAuMS02NC4ySDIwNC45eiIvPgo8cGF0aCBmaWxsPSIjRDYxRDVGIiBkPSJNNTUuNiwxNjUuNkMzNS45LDEzMS44LDQzLjMsODguOCw3My4xLDYzLjVMNTUuNywzMy4yQzcuNSw2OS44LTQuMiwxMzcuNCwyOC44LDE4OEw1NS42LDE2NS42eiIvPgo8L3N2Zz4K 100 | -------------------------------------------------------------------------------- /moderator-guide.md: -------------------------------------------------------------------------------- 1 | # Moderator guide 2 | Moderators are responsible for ensuring that reviewers and applicants understand the Badging workflow. This is done through issue comments, pull request comments, and other Badging discussions. The Moderators in the Badging organization are required to have a strong understanding of D&I practices within an open source organziation. 3 | 4 | ## Roles of the Moderator 5 | - Generate a badge when the reviewers have filed out the checklist and the applicants have implemented all feedback. 6 | - Provide advice and understanding where applicants and reviewers are having trouble. 7 | 8 | # References 9 | - https://haacked.com/archive/2019/06/03/suggested-changes/ 10 | -------------------------------------------------------------------------------- /reviewer-guide.md: -------------------------------------------------------------------------------- 1 | # Reviewer Guide 2 | 3 | ## Working with checklists 4 | 5 | A CHAOSS Badging application starts when an Applicant opens an issue on the [event](https://github.com/badging/event-diversity-and-inclusion) badging repository. They fill out a form to create a GitHub issue, which contains the information a reviewer looks at. Upon being assigned an issue, a checklist is generated in the form of a comment. This will contain the name of the reviewer. 6 | 7 | During a review, a Reviewer would analyse the information given by an Applicant using the Review Checklist. The checklist can be found [here](https://github.com/badging/event-diversity-and-inclusion/blob/master/.github/checklist.md). 8 | 9 | ## Guidelines 10 | 11 | For all submissions: 12 | - Make sure the Initial checks are met. These are the basic requirements which help to ensure that the application is at a bare minimum standard. 13 | - Mark your observations according to the Review Checklist, and give feedback on how an application can be improved if certain checks are not met. 14 | - If you have feedback outside of the scope of what the review checklist asks for, create a new comment informing the applicant about that. 15 | 16 | For Events: 17 | - Currently, there are five metrics which can be applied for by an Event Badging applicant. 18 | - Event badges are assigned according to four Badge levels. 19 | - Event reviews go on until all the metrics the Applicant gave their statement for qualify all the given checks. For example, if an applicant gave their statement for adhering to Code of Conduct and Speaker Demographic metrics (which form the first metric set), their Badge status would be pending until the qualitative checks related to both these metrics are passed. 20 | -------------------------------------------------------------------------------- /roles/README.md: -------------------------------------------------------------------------------- 1 | # Roles 2 | 3 | ## Permission table 4 | 5 | |Repository Permission|Applicant|Reviewer|Maintainer|Moderator| 6 | |:-------------------:|:-------:|:------:|:--------:|:-------:| 7 | |Can create a CHAOSS Badging application|Y|N|N|N| 8 | |Can edit the Review Checklist|N|Y|N|N| 9 | |Merge PR|N|N|Y|N| 10 | |Request reviews|N|N|N|Y| 11 | |Edit the opening PR comment|Y|N|N|N| 12 | -------------------------------------------------------------------------------- /roles/applicant.md: -------------------------------------------------------------------------------- 1 | # CHAOSS Badging role - Applicant 2 | 3 | ## Responsibilities 4 | 5 | Applicants would be the primary stakeholders for any CHAOSS Badging review. They will be responsible for: 6 | 7 | - Applying for an Event/Project related badge. 8 | - Making improvements according to reviewer feedback. 9 | - Possibly be the single point of contact between their own community, other participants and CHAOSS. 10 | 11 | ## GitHub Permissions 12 | 13 | > Repository permission level: Read 14 | 15 | Things applicants will be able to do: 16 | 17 | - Submit details required for a Badging review. 18 | - Edit details and make improvements in their application. 19 | 20 | Things applicants will not be able to do: 21 | 22 | - Edit the Review Checklist. 23 | -------------------------------------------------------------------------------- /roles/maintainer.md: -------------------------------------------------------------------------------- 1 | # CHAOSS Badging role - Maintainer 2 | 3 | ## Responsibilities 4 | 5 | Completing the processing of a Badging application would be the work of a maintainer. 6 | 7 | ## GitHub Permissions 8 | 9 | > Repository permission level: Maintain / Admin 10 | 11 | Things maintainers would be expected to do: 12 | 13 | - Assign reviewers, and add their usernames to `.github/reviewers.md`. 14 | 15 | Things maintainers would't be expected to do: 16 | 17 | - Edit the Application, Review Checklist and comments directly. 18 | -------------------------------------------------------------------------------- /roles/moderator.md: -------------------------------------------------------------------------------- 1 | # CHAOSS Badging role - Moderator 2 | 3 | ## Responsibilities 4 | 5 | This will be a role which will be belong to participants who would help in closing a Badging Application and declaring the final badge for an application. 6 | 7 | ## GitHub Permissions 8 | 9 | > Repository permission level: Maintain / Admin / Write 10 | 11 | Things a moderator would be expected to do: 12 | 13 | - Check if all the `Initial Checks` are marked positive in both checklists. 14 | - Confirm if Review Checklists are adequately marked by the reviewers according to how they interpret the information submitted by the applicant. 15 | - When the review ends, comment `/end` to mark the application as closed. This will also generate the links which the Applicant can use. 16 | -------------------------------------------------------------------------------- /roles/reviewer.md: -------------------------------------------------------------------------------- 1 | # CHAOSS Badging role - Reviewer 2 | 3 | ## Responsibilities 4 | 5 | The reviewer role would belong to people who would be responsible for reviewing the details submitted by an applicant. 6 | Reviewers will have access to the review checklist, which is a list written in Markdown detailing the criteria a submission has to be measured against. 7 | 8 | ## GitHub Permissions 9 | 10 | > Repository permission level: Write 11 | 12 | Things reviewers would be able to do: 13 | 14 | - Edit their own comments. 15 | - Edit the Review Checklists. 16 | 17 | Things reviewers won't be able to do: 18 | 19 | - Edit an applicant's comment. 20 | --------------------------------------------------------------------------------