QUILL Maintainers

QUILL Maintainers

This file describes maintainer responsibilities and operational expectations.

Named maintainers

Role Name Contact
Code Maintainer Jeff Bishop jeff@jeffbishop.com
Translation Coordinator Vacant — see below open a GitHub issue with label translation

Maintainer team

Responsibilities

  1. Triage issues and guide contributors to the right template/workflow.
  2. Review pull requests for correctness, accessibility, and maintainability.
  3. Keep release process and documentation current.
  4. Enforce CODE_OF_CONDUCT.md and SECURITY.md.
  5. Protect user trust: no silent network behavior, no unsafe defaults.

Triage and labeling standards

Maintainers should apply both a type and an area label:

Priority labels:

Triage target: new issues receive an initial maintainer response within 5 business days.

Review expectations

Maintainers should request changes when a PR:

Availability and handoff

If a maintainer is unavailable, another maintainer should take ownership of:

  1. Security reports
  2. Release-blocking regressions
  3. Accessibility regressions

Role descriptions

Code Maintainer — Reviews and merges pull requests, triages bug reports and feature requests, cuts releases, enforces code quality gates and CI requirements, and sets technical direction for the project.

Translation Coordinator — Sends translation calls to Language Coordinators before each release, onboards new language teams, maintains the Crowdin project configuration, resolves translation disputes that Language Coordinators escalate, and ensures the Translation Style Guide stays current. Must be available during the two-week pre-release window. This is a named maintainer role, not a casual volunteer position.

To apply for Translation Coordinator, open a GitHub issue with the label translation. For full information about translation contribution, including the four-tier role model and how to get started, see docs/translating.md.