Skip to content

feat: add project governance documentation #130

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
NJX-njx wants to merge 1 commit into
base: main
Choose a base branch
from
Open

feat: add project governance documentation #130

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions docs/_sidebar.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,6 +21,10 @@
- **Tutorials**
- [Tutorial](https://github.com/VersusControl/devops-ai-guidelines/blob/main/04-ai-agent-for-aws/00-toc.md)

- **Community**
- [Project Governance](/governance.md)
- [Contributing](../CONTRIBUTING.md)
Copy link

Copilot AI Mar 3, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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).

Suggested change
- [Contributing](../CONTRIBUTING.md)
- [Contributing](https://github.com/VersusControl/ai-infrastructure-agent#contributing)

Copilot uses AI. Check for mistakes.

- **Resources**
- [GitHub Repository](https://github.com/VersusControl/ai-infrastructure-agent)
- [Issues](https://github.com/VersusControl/ai-infrastructure-agent/issues)
Expand Down
103 changes: 103 additions & 0 deletions docs/governance.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,103 @@
# Project Governance

This document describes the governance model, decision-making process, and community structure for the AI Infrastructure Agent project.

## Governance Model

The project follows a **benevolent dictator** model with a core maintainer team. Decisions are made by consensus when possible, with maintainers having final say on technical and process matters.

## Maintainer Roles and Responsibilities

### Core Maintainers

- **Technical leadership**: Approve architectural changes, review critical PRs, ensure code quality.
- **Release management**: Cut releases, maintain changelog, versioning.
- **Community**: Triage issues, guide contributors, moderate discussions.

### Maintainer Expectations

- Respond to issues and PRs in a timely manner
- Uphold the [Code of Conduct](../CODE_OF_CONDUCT.md)
- Mentor new contributors
Comment on lines +19 to +21
Copy link

Copilot AI Mar 3, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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).

Copilot uses AI. Check for mistakes.
- Participate in RFC discussions when relevant

### Maintainer Onboarding

New maintainers are invited by existing maintainers based on:

- Sustained contributions to the project
- Demonstrated technical judgment
- Alignment with project goals and values

## 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.

Comment on lines +32 to +43
Copy link

Copilot AI Mar 3, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copilot uses AI. Check for mistakes.
### Escalation Path

1. Discuss in issue or PR comments
2. Open a dedicated RFC issue if needed
3. Maintainers make final decision

## RFC (Request for Comments) Process

For substantial changes:

1. **Create an RFC issue** with the `rfc` label (if available) or `enhancement`.
2. **Title**: `[RFC] Brief description`
3. **Content**: Problem statement, proposed solution, alternatives, impact.
4. **Discussion**: Allow at least 1 week for community feedback.
5. **Decision**: Maintainers summarize and decide.

## Release Planning and Versioning

### Versioning

We follow [Semantic Versioning](https://semver.org/):

- **MAJOR**: Breaking changes
- **MINOR**: New features (backward compatible)
- **PATCH**: Bug fixes and minor improvements

### Release Cadence

- **Patch releases**: As needed for bug fixes and security updates.
- **Minor releases**: When significant features are ready.
- **Major releases**: Planned with migration guides where possible.

### Release Process

1. Update changelog
2. Tag release (e.g., `v1.2.0`)
3. Create GitHub release with notes
4. Announce in Discussions (if applicable)

## Conflict Resolution

- **Code conflicts**: Resolved through PR review and maintainer feedback.
- **Interpersonal conflicts**: Refer to [Code of Conduct](../CODE_OF_CONDUCT.md). Maintainers may step in to mediate.
- **Disagreements on direction**: Use RFC process; maintainers have final say.

## Project Roadmap Communication

- **Roadmap**: Tracked in [GitHub Projects](https://github.com/orgs/VersusControl/projects) and referenced in the README.
- **Updates**: Major milestones communicated via release notes and Discussions.
- **Feedback**: Open issues and Discussions for community input on priorities.

## Community Leadership Structure

- **Maintainers**: Core team with merge and release authority.
- **Contributors**: Anyone who submits PRs or participates in issues.
- **Users**: Consumers of the project; feedback encouraged via issues and Discussions.

---

For contribution guidelines, see [CONTRIBUTING.md](../CONTRIBUTING.md).
Copy link

Copilot AI Mar 3, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Suggested change
For contribution guidelines, see [CONTRIBUTING.md](../CONTRIBUTING.md).
Contribution guidelines will be documented in the main project README.

Copilot uses AI. Check for mistakes.
Loading