Skip to content

docs: establish maintainer and release governance (#252) - #464

Merged
codeforester merged 4 commits into
mainfrom
documentation/252-20261023-project-governance
Oct 25, 2026
Merged

codeforester merged 4 commits into
mainfrom
documentation/252-20261023-project-governance

Conversation

@codeforester

Copy link
Copy Markdown
Contributor

Summary

Addresses #252's governance and continuity scope.

  • Add GOVERNANCE.md with current maintainer and independent reviewer responsibilities, review/decision rules, release continuity, reviewer onboarding, health metrics, and succession path.
  • Link governance from contributor, documentation, security, and release guidance.
  • Refresh the security-support table from 0.4.x to the current 0.5.x line.
  • Document the reviewer-training checklist without claiming completion from repository access alone.

The remaining acceptance item is to record completion of the independent reviewer training checklist in the governance/release record.

Validation

  • UV_CACHE_DIR=/private/tmp/base-cli-uv-cache uv run --extra dev --extra typer --extra quality ./tests/full_validate.sh --gate contracts
  • UV_CACHE_DIR=/private/tmp/base-cli-uv-cache uv run --extra quality ./tests/full_validate.sh --gate style
  • git diff --check

Comment thread SECURITY.md
Comment thread GOVERNANCE.md Outdated
@codeforester
codeforester merged commit 98d0229 into main Oct 25, 2026
120 checks passed
@codeforester
codeforester deleted the documentation/252-20261023-project-governance branch October 25, 2026 16:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant