--- robots: nofollow, noindex tags: RFC --- # Fluent UI RFC Template An RFC can be anything. A question, a suggestion, a plan. The purpose of this template is to give some structure to help folks write successful RFCs. However, don't feel constrained by this template; use your best judgement. Tips for writing a successful RFC: - Simple plain words that make your point, fancy words obfuscate - Try to stay concise, but don't gloss over important details - Try to write a neutral problem statement, not one that motivates your desired solution - Remember, "Writing is thinking". It's natural to realize new ideas while writing your proposal --- *List contributors to the proposal up front* ## Summary Explain the proposed change ## Background If there is relevant background include it here ## Problem statement Why are we making this change? What problem are we solving? What do we expect to gain from this? This section is important as the motivation or problem statement is indepenent from the proposed change. Even if this RFC is not accepted this Motivation can be used for alternative solutions. In the end, please make sure to present a neutral Problem statement, rather than one that motivates a particular solution ## Detailed Design or Proposal This is the bulk of the RFC. Explain the proposal or design in enough detail for the inteded audience to understand. ### Pros and Cons Enumerate the pros and cons of the proposal. Make sure to think about and be clear on the cons or drawbacks of this propsoal. If there are multiple proposals include this for each. ## Discarded Solutions As you enumerate possible solutions, try to keep track of the discarded ones. This should include why we discarded the solution. ## Open Issues Optional section, but useful for first drafts. Use this section to track open issues on unanswered questions regarding the design or proposal.