An abstract, tl;dr or executive summary of your RFC.
Describe the problem your RFC is trying to solve.
Describe your proposal, with a focus on clarity of meaning. You MAY use RFC2119-style MUST, SHOULD and MAY language to help clarify your intentions.
- Describe any changes to code or documentation that will need to happen if this RFC is accepted. For example, this might be modifying the playbook or a template project. Include checkboxes so we can mark the actions as completed later. After the RFC is adopted, you SHOULD update it to link to any followup issues that are created.