RFC Process - Wasmtime

## Keyboard shortcuts

Press `←` or `→` to navigate between chapters

Press `S` or `/` to search in the book

Press `?` to show this help

Press `Esc` to hide this help

# RFC Process

For changes that will significantly affect Wasmtime's or Cranelift's internals, downstream projects, contributors, and other stakeholders, a Bytecode Alliance RFC should be used to gather feedback on the proposed change's design and implementation, and to build consensus.

It is recommended that regular Wasmtime and Cranelift contributors, as well as any other project stakeholders, subscribe to notifications in the RFC repository to stay up to date with significant change proposals.

## Authoring New RFCs

The RFC repository has two templates that can help you author new proposals:

1. A draft RFC template, for seeking early feedback on ideas that aren't yet fully baked. It is expected that as the discussion evolves, these draft RFCs will grow into fully-formed RFCs.

2. A full RFC template, for building consensus around a mature proposal.

You can also look at historical Wasmtime RFCs in the repository's `accepted` subdirectory and their associated discussions in its merged pull requests to 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 by creating a new thread in the relevant Zulip channels (e.g. `#wasmtime` or `#cranelift`).