1---
2name: RFC / Proposal
3about: Submit an RFC / Proposal
4title: ''
5labels: RFC
6assignees: ''
7
8---
9
10## Introduction
11
12<!--
13This section targets end users, TSC members, maintainers and anyone else that might
14need a quick explanation of your proposed change.
15-->
16
17### Problem description
18<!--
19Why do we want this change and what problem are we trying to address?
20-->
21
22### Proposed change
23<!--
24A brief summary of the proposed change - the 10,000 ft view on what it will
25change once this change is implemented.
26-->
27
28## Detailed RFC
29<!--
30In this section of the document the target audience is the dev team. Upon
31reading this section each engineer should have a rather clear picture of what
32needs to be done in order to implement the described feature.
33-->
34
35### Proposed change (Detailed)
36<!--
37This section is freeform - you should describe your change in as much detail
38as possible. Please also ensure to include any context or background info here.
39For example, do we have existing components which can be reused or altered.
40
41By reading this section, each team member should be able to know what exactly
42you're planning to change and how.
43-->
44
45### Dependencies
46<!--
47Highlight how the change may affect the rest of the project (new components,
48modifications in other areas), or other teams/projects.
49-->
50
51### Concerns and Unresolved Questions
52<!--
53List any concerns, unknowns, and generally unresolved questions etc.
54-->
55
56## Alternatives
57<!--
58List any alternatives considered, and the reasons for choosing this option
59over them.
60-->
61