1# RFC Process
2
3For changes that will significantly affect Wasmtime's or Cranelift's internals,
4downstream projects, contributors, and other stakeholders, a [Bytecode Alliance
5RFC](https://github.com/bytecodealliance/rfcs/) should be used to gather
6feedback on the proposed change's design and implementation, and to build
7consensus.
8
9It is recommended that regular Wasmtime and Cranelift contributors, as well as
10any other project stakeholders, subscribe to notifications in [the RFC
11repository](https://github.com/bytecodealliance/rfcs/) to stay up to date with
12significant change proposals.
13
14## Authoring New RFCs
15
16The RFC repository has two templates that can help you author new proposals:
17
181. [A draft RFC
19   template](https://github.com/bytecodealliance/rfcs/blob/main/template-draft.md),
20   for seeking early feedback on ideas that aren't yet fully baked. It is
21   expected that as the discussion evolves, these draft RFCs will grow into
22   fully-formed RFCs.
23
242. [A full RFC
25   template](https://github.com/bytecodealliance/rfcs/blob/main/template-full.md),
26   for building consensus around a mature proposal.
27
28You can also look at historical Wasmtime RFCs in [the repository's `accepted`
29subdirectory](https://github.com/bytecodealliance/rfcs/tree/main/accepted) and
30their associated discussions in its [merged pull
31requests](https://github.com/bytecodealliance/rfcs/pulls?q=is%3Apr+is%3Amerged+)
32to gather inspiration for your new RFC. A few good examples include:
33
34* Add a Long Term Support (LTS) Channel of Releases for Wasmtime -
35  [RFC](https://github.com/bytecodealliance/rfcs/blob/main/accepted/wasmtime-lts.md) -
36  [Discussion](https://github.com/bytecodealliance/rfcs/pull/42)
37* Pulley: A Portable, Optimizing Interpreter for Wasmtime -
38  [RFC](https://github.com/bytecodealliance/rfcs/blob/main/accepted/pulley.md) -
39  [Discussion](https://github.com/bytecodealliance/rfcs/pull/35)
40* Debugging Support in Wasmtime -
41  [RFC](https://github.com/bytecodealliance/rfcs/blob/main/accepted/wasmtime-debugging.md) -
42  [Discussion](https://github.com/bytecodealliance/rfcs/pull/34)
43* Redesign Wasmtime's API -
44  [RFC](https://github.com/bytecodealliance/rfcs/blob/main/accepted/new-api.md) -
45  [Discussion](https://github.com/bytecodealliance/rfcs/pull/11)
46
47After creating a pull request for your new RFC, advertise its existence by
48creating a new thread in the relevant
49[Zulip](https://bytecodealliance.zulipchat.com/) channels (e.g. `#wasmtime` or
50`#cranelift`).
51