Repository navigation
[v1.0] Expand maintainer capacity and document project governance #252
Description
Goal
Reduce bus-factor risk and make contribution and release decisions sustainable.
Scope
- Document maintainer roles, review expectations, release ownership, and security escalation.
- Define a path for adding co-maintainers and trusted reviewers.
- Publish decision records for API, contract, and compatibility changes.
- Add contributor onboarding for issue triage, local validation, and release rehearsal.
- Track response and review health as the project grows.
Acceptance criteria
- Governance and maintainer responsibilities are discoverable from CONTRIBUTING.md.
- At least one additional trained reviewer can run the quality and release gates.
- Security and release continuity do not depend on one person.
- Governance changes are reflected in the support and API-stability policies.
Project fields
- Status: Backlog
- Priority: P2
- Area: Product
- Initiative: Adoption Polish
- Size: M
Metadata
Metadata
Assignees
Type
Projects
- Status
Activity
codeforester commentedon Sep 1, 2026
Review follow-up (2026-09-01): milestone
v1.0.0is still open with a due date of 2026-08-31, while the repository now has 27 open issues, including unresolved P1 runtime, release, security, CI, and platform-contract work. Add milestone re-baselining to this governance scope: publish a new target date or explicitly mark it unscheduled, define the P1 exit criteria/dependency graph, and identify a second reviewer for release/security approvals. Avoid leaving an expired date that implies readiness unsupported by the current gates.codeforester commentedon Sep 12, 2026
2026-09-12 repository review refresh
Still outstanding: this repository has CODE_OF_CONDUCT.md and CONTRIBUTING.md but no MAINTAINERS/GOVERNANCE file and one contributor in the live repository API. Publish real decision/review/release/succession responsibility and train another reviewer. Current CNCF Sandbox guidance explicitly requests a MAINTAINERS file with Name, ID and Company/Organization, considers employer diversity (not a fixed Sandbox requirement), and requires TOC approval/contribution agreement before affiliation claims: https://github.com/cncf/sandbox/blob/main/README.md . This is a maturity path, not a recommendation to apply now.
Validated against current main (
7faf347a5b90969e169c88f3ac18e7202d142dd0). This review files and scopes work; it does not claim implementation or authorize release/admin changes.security: gate releases on reviewed main provenance (#375)
codeforester commentedon Oct 22, 2026
Implementation evidence is in PR #464: #464
The PR adds discoverable governance, role/continuity rules, release/security review expectations, and a concrete reviewer onboarding checklist. It intentionally does not claim that write access equals training: the additional reviewer training record is still required before this issue can be closed. The issue remains In Review pending review and that evidence.
codeforester commentedon Oct 23, 2026
Review follow-up completed in PR #464. SECURITY.md now states 0.3.x explicitly, and GOVERNANCE.md no longer asserts an untracked November ship date. Commit: c120750. Documentation/style checks pass locally; all review threads are resolved.
docs: establish maintainer and release governance (#252) (#464)