This file describes maintainer responsibilities and operational expectations.
| Role | Name | Contact |
|---|---|---|
| Code Maintainer | Jeff Bishop | jeff@jeffbishop.com |
| Translation Coordinator | Vacant — see below | open a GitHub issue with label translation |
@Community-Access)CODE_OF_CONDUCT.md and
SECURITY.md.Maintainers should apply both a type and an area label:
bug, feature,
documentation, securityaccessibility, ai,
intake, snippets, dictation,
performance, stabilityPriority labels:
p0: release blocker (launch crash, data loss, severe
accessibility break)p1: major workflow breakTriage target: new issues receive an initial maintainer response within 5 business days.
Maintainers should request changes when a PR:
docs/QUILL-PRD.md,If a maintainer is unavailable, another maintainer should take ownership of:
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.
CONTRIBUTING.mdGOVERNANCE.mdSECURITY.mdRELEASE.mddocs/translating.mddocs/translating.md