LogoLogo
  • CHAOSS Community Handbook - Table of Contents
  • Handbook Usage
  • ABOUT
    • CHAOSS History
    • Values
    • Roadmap
    • Roles and Responsibilities
    • Community Guidelines
    • Path to Leadership
    • Terminology
      • CHAOSS Specific Terms
      • CHAOSS Committees
      • CHAOSS Community Working Group Terminology
      • CHAOSS Community Mentorship Terminology
    • Terminology Usage
    • General FAQ
  • COMMUNITY
    • Working Groups
      • WG Repository Structure
    • Metrics
      • Releases
      • Translation
      • Metrics FAQ
    • Community Report
    • CHAOSScon
    • CHAOSScast
    • CHAOSS Meetings
  • CONTRIBUTING
    • Development
      • Contributing Workflow
    • Documentation
      • Style Guide
    • Design
      • Design Workflow
      • Design Contribution
      • CHAOSS Visual Identity
    • Outreach
  • MENTORSHIPS
    • Google Summer of Code
    • Google Season of Docs
    • GSoC/GSoD Roles & Responsibilities
    • Outreachy
  • D&I BADGING
    • Overview of the D&I Badging
    • How to contribute
    • Apply for a badge
      • Apply for an In-Person Event
      • Apply for a Virtual Event
    • Reviewing for CHAOSS
      • Apply to Review
      • The Review Process
      • Conflict of Interest Policy
    • Badging Roles
      • Applicant
      • Reviewer
      • Moderator
      • Maintainer
    • The badging-bot
    • D&I Badging Code of Conduct
Powered by GitBook
On this page
  • Responsibilities
  • GitHub Permissions
  • FAQ

Was this helpful?

Export as PDF
  1. D&I BADGING
  2. Badging Roles

Maintainer

Responsibilities

The responsibility of a maintainer would be to ensure that the whole project is under control, and completing the processing of a Badging application. A maintainer will also maintain the reviewer team and responsible for the training of new reviewers.

GitHub Permissions

Repository permission level: Maintain / Administrate

A maintainer will be expected to:

  • Assign reviewers and add their GitHub handles to .github/reviewers.md.

Maintainers won't be expected to:

  • Edit the Application, Review Checklist, and comments directly.

FAQ

Q What kind of commitment is required to maintain for Event Badging? A Maintaining the project requires sufficient command of the Badging workflow and long-term connection to the community. We expect, at the highest load, for the project to require about 20 minutes every couple of days for each maintainer.

Q What are the sources of maintainers for CHAOSS D&I Badging Project? A Maintainers are long-standing members of the CHAOSS community that become core-contributors to the D&I Badging Project. To become a maintainer, a contributor needs to show constant activity related to the project.

Q We are looking forward to answering more questions!

PreviousModeratorNextThe badging-bot

Last updated 4 years ago

Was this helpful?