Governance
GuestCraft is at an early stage and is maintained by a single maintainer. This document describes how decisions are made today and how that changes as the project grows. It does not pretend that a committee exists.
- Maintainers review and merge pull requests, cut releases, handle security reports and enforce the Code of Conduct. They are listed in MAINTAINERS.md.
- Code owners must approve changes to sensitive areas (the core, database migrations and RLS, authentication and security code, public contracts and CI). The areas are defined in
.github/CODEOWNERS. - Contributors are everyone who opens issues, reviews or submits changes.
Decisions
Section titled “Decisions”- Day-to-day changes are decided in pull requests.
- Architecture decisions are recorded as ADRs in
docs/adrand proposed through pull requests, so that the discussion stays public. - Changes to public contracts (the API, events, SDK, extension points) follow the stability and deprecation rules of the technical analysis (chapters 9 and 17).
- While there is one maintainer, that maintainer decides. When there are at least three maintainers, decisions that cannot reach consensus are taken by majority of the maintainers, and changes to this document need a two-thirds majority.
Becoming a maintainer
Section titled “Becoming a maintainer”A contributor with a record of good reviews and contributions over several months can be proposed by any maintainer; the existing maintainers decide. Inactive maintainers (no activity for six months) move to an emeritus list.
Continuity
Section titled “Continuity”The maintainers keep the repository settings, release credentials and the security contact documented and shared among at least two people as soon as there are two maintainers, so that the project survives the absence of any one of them.
Trademark
Section titled “Trademark”The use of the GuestCraft name and logo is described in TRADEMARK.md.