Skip to content

Commit c6d2280

Browse files
committed
Clarify how process RFCs are approved
1 parent 1cd3323 commit c6d2280

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

accepted/rfc-process.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -88,6 +88,10 @@ When should you open an RFC, rather than just writing code and opening a traditi
8888

8989
The proposal above assumes the presence of tooling to manage the GitHub workflow around RFCs. The intent is to use Rust's [rfcbot](https://github.com/rust-lang/rfcbot-rs). It will need some modifications to support the proposed workflow; these can hopefully land upstream so we can share the tool with the Rust community, but otherwise the BA will maintain its own fork.
9090

91+
## Approval of this RFC and future process-related RFCs
92+
93+
This RFC, and any future RFCs targeting similar process-related questions, will go before the Bytecode Alliance Steering Committee (eventually replaced by the Technical Steering Committee, once that group has been formed).
94+
9195
# Rationale and alternatives
9296

9397
## Stakeholder and FCP approach

0 commit comments

Comments
 (0)