Skip to content

Becoming a Maintainer

concept10 edited this page Feb 23, 2017 · 6 revisions

Becoming a Maintainer

We always welcome people who are interested in becoming a maintainer.

Requirements

It's simple.

  1. Show a history of contributions to the project.
  2. Request to be a maintainer by choosing your desired role(s).

The first point is self-explanatory. We like friendly faces over strangers. That and it gives you a taste of what's required to be a maintainer.

Roles

Code

If you're on GitHub, this is probably your natural element. Bugs need to get fixed, features need to get implemented, and documentation must be maintained. PRs need to be tested and merged, or rejected if it doesn't suit the project goals.

Issue Triage

Issues need to be groomed and categorized into feature requests or bugs. You will need to request missing information and follow up. You may even have to create a virtual machine to replicate the exact environment of the user who sees an error to reproduce -- it's not uncommon for bugs to be OS and desktop environment dependent.