Maintainers¶
Current maintainers, with the areas they own. See GOVERNANCE.md for how this
list changes, what each role can decide, and the Format Steward's rotation.
| maintainer | role | areas | since |
|---|---|---|---|
| shivanshjain456 | Maintainer + Format Steward | everything | 2026-10 |
The founding maintainer is the author of the initial implementation, the specification and the
conformance vectors, and holds the Format Steward role for the first year as described in
GOVERNANCE.md. That is a statement about continuity, not privilege: the
governance document removes founders' special rights deliberately, and the format-change
process binds this maintainer exactly as it binds everyone else.
Emeritus: none yet.
What maintainers do here¶
- triage issues and pull requests (target: first response within a week; 72 hours for the recorded in this file and in the release notes);
- cut releases: tag, CI build, signed
SHA256SUMS, release notes fromCHANGELOG.md; - own the security response window described in
SECURITY.md; - keep the specification and the vectors in step with the implementations — the one non-negotiable responsibility in this project.
How to become one¶
Sustained participation described in GOVERNANCE.md.
The short version: reviews that catch real problems, fixes for issues you did not create, and
a verifier or integration you keep alive rather than merely contribute once.