1# RFCs 2 3The Salsa RFC process is used to describe the motivations for major changes made 4to Salsa. RFCs are recorded here in the Salsa book as a historical record of the 5considerations that were raised at the time. Note that the contents of RFCs, 6once merged, is typically not updated to match further changes. Instead, the 7rest of the book is updated to include the RFC text and then kept up to 8date as more PRs land and so forth. 9 10## Creating an RFC 11 12If you'd like to propose a major new Salsa feature, simply clone the repository 13and create a new chapter under the list of RFCs based on the [RFC template]. 14Then open a PR with a subject line that starts with "RFC:". 15 16[RFC template]: ./rfcs/template.md 17 18## RFC vs Implementation 19 20The RFC can be in its own PR, or it can also includ work on the implementation 21together, whatever works best for you. 22 23## Does my change need an RFC? 24 25Not all PRs require RFCs. RFCs are only needed for larger features or major 26changes to how Salsa works. And they don't have to be super complicated, but 27they should capture the most important reasons you would like to make the 28change. When in doubt, it's ok to just open a PR, and we can always request an 29RFC if we want one.