Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.charmos.io/llms.txt

Use this file to discover all available pages before exploring further.

This page will document how Charm makes open-source project decisions. Charm’s governance model should make it clear who reviews changes, how releases are approved, and how contributors can participate.

​
Planned Sections

  • Maintainers.
  • Workstream owners.
  • Review expectations.
  • Release approval.
  • Security escalation.
  • Community standards.

​
Maintainers

Maintainers are responsible for:
  • reviewing pull requests,
  • protecting project quality,
  • triaging issues,
  • approving releases,
  • enforcing community standards,
  • coordinating security fixes.
The initial maintainer list should be published before the first formal open-source release.

​
Workstream Ownership

Charm should assign owners for:
  • SDK and package publishing,
  • runner and infrastructure,
  • Store and web app,
  • docs and templates,
  • database migrations,
  • security and disclosure.

​
Decision Making

Small changes can be approved through normal pull request review. Larger changes should include:
  • a design note or issue,
  • affected repositories,
  • migration/deploy impact,
  • compatibility risks,
  • rollout plan.

​
Release Approval

Production-impacting releases should have approval from the release owner and the relevant workstream owner.

​
Community Standards

All participation is covered by the Code of Conduct.