Skip to content

GOVERNANCE.md

Latest commit

 

History

History
50 lines (33 loc) · 2.76 KB

GOVERNANCE.md

File metadata and controls

50 lines (33 loc) · 2.76 KB
Raw

Governance

DevCloud is a small, volunteer-driven open-source project. This document describes how decisions are made and how the roles evolve as the project grows.

Current state

  • Benevolent maintainer model. One maintainer (@skyoo2003) has final say on roadmap, releases, and merge decisions.
  • Apache License 2.0. All contributions are accepted under this license; see CONTRIBUTING.md.
  • Best-effort response. No SLA; see SUPPORT.md for expectations.

This is appropriate at the project's current size. It is a statement about who decides, not about API stability — what a release promises is docs/compatibility-policy.md.

How decisions are made

Decision type Who decides How
Small bug fixes Maintainer (self-merge) Reviewer approval + green CI
Features, new services Maintainer After PR review; contributor discussion welcomed in issues
Architecture changes Maintainer Open design issue first; gather input before implementation
Roadmap priorities Maintainer Guided by roadmap.md and issue reactions
Security fixes Maintainer + reporter Follow SECURITY.md; patches issued before public disclosure
Releases Maintainer Following semver; see CHANGELOG.md

How to influence direction

  • Open issues. Features, bugs, questions — all go through Issues or Discussions.
  • React to existing issues to surface priority.
  • Submit PRs. Working code speaks loudest. See CONTRIBUTING.md.
  • Discuss architecture early. For non-trivial changes, open a design issue before writing code.

Future governance

As DevCloud grows, the governance model will evolve. Likely milestones:

  • 2+ active maintainers — introduce a lightweight maintainer charter (who can merge what, conflict resolution).
  • First external contributor with sustained commits — document maintainer eligibility criteria.
  • Foundation consideration — if the project reaches the scale where vendor-neutral governance matters, a formal foundation model will be evaluated.

Until then, this one-page document is the full governance.

Maintainers

See .github/CODEOWNERS for review ownership.

Changes to this document

Meta-changes (governance model, maintainer list) are themselves governed by this process: open an issue, discuss, PR. Substantial governance changes (e.g., moving to a multi-maintainer model) will be publicized in CHANGELOG.md.