RFC process
Note
RFC: accepted. This page defines the process for proposing changes to Shiin’s specifications.
When to use an RFC
An RFC is required when a change:
- Changes an accepted specification.
- Adds a new action-type namespace.
- Adds a policy-language feature.
- Adds, removes, or reorders milestone scope.
Process
- Copy the RFC template to
NNNN-short-title.md. - Open a pull request with the proposal.
- Reviewers discuss and the maintainers accept or reject.
- An accepted RFC produces an ADR.
Statuses
| Status | Meaning |
|---|---|
draft | The proposal is written and open for review. |
accepted | The proposal is accepted and produces an ADR. |
rejected | The proposal is not accepted. |
superseded | Replaced by a later RFC. |
Current proposals
- RFC-0001: Remote approver transport proposes opt-in signed polling over outbound HTTPS.