RFC Process
For changes that will significantly affect Wasmtime's or Cranelift's internals,downstream projects, contributors, and other stakeholders, aBytecode AllianceRFC should be used to gatherfeedback on the proposed change's design and implementation, and to buildconsensus.
It is recommended that regular Wasmtime and Cranelift contributors, as well asany other project stakeholders, subscribe to notifications inthe RFCrepository to stay up to date withsignificant change proposals.
Authoring New RFCs
The RFC repository has two templates that can help you author new proposals:
A draft RFCtemplate,for seeking early feedback on ideas that aren't yet fully baked. It isexpected that as the discussion evolves, these draft RFCs will grow intofully-formed RFCs.
A full RFCtemplate,for building consensus around a mature proposal.
You can also look at historical Wasmtime RFCs inthe repository'sacceptedsubdirectory andtheir associated discussions in itsmerged pullrequeststo gather inspiration for your new RFC. A few good examples include:
- Add a Long Term Support (LTS) Channel of Releases for Wasmtime -RFC -Discussion
- Pulley: A Portable, Optimizing Interpreter for Wasmtime -RFC -Discussion
- Debugging Support in Wasmtime -RFC -Discussion
- Redesign Wasmtime's API -RFC -Discussion
After creating a pull request for your new RFC, advertise its existence bycreating a new thread in the relevantZulip channels (e.g.#wasmtime or#cranelift).