RFCs — Request for Comments

RFCs are how Warble Cloud makes significant decisions in public. If a change is large enough that “I’ll just open a PR” feels wrong, write an RFC.

When to RFC

• New cross-product features or APIs
• Breaking changes to public APIs
• New Working Groups
• Governance changes
• Anything you’d want a wide range of voices on before you commit

Process

1. Draft — Copy TEMPLATE.md to rfcs/NNNN-short-name.md (next number).
2. Open a PR — Tag relevant maintainers and #rfc on Discord.
3. Discussion — Minimum 7 days for discussion. Address feedback in-place.
4. Resolution — Maintainers in the affected area reach lazy consensus. If contested, escalate to Stewards.
5. Merge — RFC merged when accepted. Implementation links added in a follow-up edit.

Statuses

• draft — Open PR, in discussion
• accepted — Merged, ready to implement
• implemented — Done; PRs linked
• withdrawn — Author closed without resolution
• rejected — Maintainers declined; reasoning recorded in the PR

Index