feat: add project governance documentation#130
feat: add project governance documentation#130NJX-njx wants to merge 1 commit intoVersusControl:mainfrom
Conversation
- Governance model (benevolent dictator + maintainer team) - Maintainer roles, responsibilities, onboarding - Decision-making process and escalation path - RFC process for significant changes - Release planning and semantic versioning - Conflict resolution procedures - Roadmap communication - Add governance link to docs sidebar Closes VersusControl#80 Made-with: Cursor
There was a problem hiding this comment.
Pull request overview
Adds initial governance documentation for the project and surfaces it in the docs navigation, aligning with Issue #80’s community infrastructure requirements.
Changes:
- Added a new
docs/governance.mddescribing governance model, maintainer responsibilities, RFC flow, release versioning, and conflict resolution. - Updated
docs/_sidebar.mdto include a new “Community” section linking to governance docs (and contributing).
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.
| File | Description |
|---|---|
| docs/governance.md | Introduces governance, decision-making, RFC, release, conflict resolution, and roadmap communication documentation. |
| docs/_sidebar.md | Adds navigation entries for the new governance documentation and contribution links. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| ## Decision-Making Process | ||
|
|
||
| ### Routine Changes | ||
|
|
||
| - **Bug fixes, docs, minor features**: PR review and approval by at least one maintainer. | ||
| - **No breaking changes** without explicit discussion. | ||
|
|
||
| ### Significant Changes | ||
|
|
||
| - **New AWS services, major refactors, breaking changes**: Require an RFC or design discussion in an issue before implementation. | ||
| - **Consensus**: Aim for maintainer consensus; in case of disagreement, maintainers may escalate to the project lead. | ||
|
|
There was a problem hiding this comment.
Issue #80’s technical notes call out documenting “community voting mechanisms,” but the decision-making section currently describes consensus with maintainers having final say and doesn’t specify any voting process (when it applies, who votes, quorum/threshold, tie-breaking). If the intent is to close #80, consider adding a short voting mechanism subsection here.
| - Respond to issues and PRs in a timely manner | ||
| - Uphold the [Code of Conduct](../CODE_OF_CONDUCT.md) | ||
| - Mentor new contributors |
There was a problem hiding this comment.
The governance doc links to ../CODE_OF_CONDUCT.md, but there is no CODE_OF_CONDUCT.md in the repository, so this will be a broken link in the rendered docs. Either add the Code of Conduct file in this PR or update the link to the correct location (e.g., a GitHub URL or the actual docs path).
|
|
||
| --- | ||
|
|
||
| For contribution guidelines, see [CONTRIBUTING.md](../CONTRIBUTING.md). |
There was a problem hiding this comment.
This document references ../CONTRIBUTING.md, but the repo doesn’t contain a CONTRIBUTING.md file, so the link will be broken. Consider either adding CONTRIBUTING.md, linking to the appropriate section of the main README, or using a GitHub blob URL until contribution guidelines exist as a standalone doc.
| For contribution guidelines, see [CONTRIBUTING.md](../CONTRIBUTING.md). | |
| Contribution guidelines will be documented in the main project README. |
|
|
||
| - **Community** | ||
| - [Project Governance](/governance.md) | ||
| - [Contributing](../CONTRIBUTING.md) |
There was a problem hiding this comment.
The sidebar adds a link to ../CONTRIBUTING.md, but there is no CONTRIBUTING.md in the repo, so this will render as a broken link. Update this to point at the actual contribution guidelines location (e.g., a docs page under docs/ or a GitHub URL / README section).
| - [Contributing](../CONTRIBUTING.md) | |
| - [Contributing](https://github.com/VersusControl/ai-infrastructure-agent#contributing) |
Summary
Adds project governance documentation per Task 1.13 (#80).
Changes
Dependencies: Complements #79 (contribution guidelines). Can be merged independently.
Closes #80