mirror of
https://github.com/storytold/craft-contrib.git
synced 2026-11-19 09:01:31 +01:00
An accepted RFC isn't edited: a later RFC changes it, with Updates: or Obsoletes: under its title as IETF RFCs do, and the old one gets an Updated by: or Obsoleted by: back-link. Fixes that don't change the meaning are ordinary PRs. An RFC can name a living document for the current rules. Updates RFC-0000, which gets its back-link here. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
881 B
881 B
RFC-0000: How we make decisions
Updated by: RFC-0013
Changes to this repo, and decisions that affect several apps, are made
through RFCs: pull requests here that add rfcs/NNNN-short-title.md.
This process is changed the same way.
- Maintainers are the
craft-app-teamGitHub team. Owners are the storytold org's admins, and are also maintainers. - Anyone can open an RFC or comment on one.
- A maintainer starts the comment period by commenting its end date: 7 days for adding or removing an app or changing this process, 3 days for everything else.
- After the period, the RFC merges with approval from a maintainer other than the author, if no maintainer's objection is unresolved. An objection gives a reason and says what would resolve it.
- An owner can decide an objection, or merge or close an RFC early, and says why on the PR.