Badging Roles
Different roles undertake different responsibilities in D&I Badging workflow. The Badging roles are applicants, reviewers, moderators, and maintainers. These roles exist to ensure submissions and reviews are smooth and efficient. This is especially true for the GitHub section of the workflow.
Applicants and reviewers are the most fundamental and indispensable roles of D&I Badging since they are a part of the core sections of the badging workflow: applying and reviewing. Besides this, we also need moderators to coordinate between applicants and reviewers, and maintainers who are responsible for the whole project.
Click the following tab bar to see the definition of each role.
Applicant
Reviewer
Moderator
Maintainer
An applicant is a person who initiates a badge submission and opens an issue on GitHub.
A reviewer is a person who reviews the submission, complete the checklist, and gives feedback through issue comments.
A moderator is a person who facilitates the interaction between the applicant and the reviewer within an issue.
A maintainer is a person who takes overall responsibilities within D&I badging project, making sure everything works regularly.
As most of the responsibilities are related to the workflow on GitHub, it's important to understand that each role has its GitHub permission that specified what can do and what should be avoided. See the permission table below.
Repository Permission | Applicant | Reviewer | Maintainer | Moderator |
Create a CHAOSS Badging application | Y | N | N | N |
Edit the Review Checklist | N | Y | N | N |
Request reviews | N | N | N | Y |
Edit the opening Issue comment | Y | N | N | N |
Generate the Badge | N | N | N | Y |
Close the Issue | N | N | Y | Y |
In each subsection, we will elaborate on responsibilities and GitHub permissions of different kinds of roles, and provide information about the frequently asked questions.
Last modified 2yr ago