---
# System prepended metadata

title: Fluent UI Web RFC template proposal
tags: [RFC]

---

---
robots: nofollow, noindex,
tags: RFC
---

# Fluent UI Web RFC template proposal

# Summary
This RFC proposes that we formalize our RFC process with a template and a lightweight process.

# Problem statement
We have been using RFCs and Proposals in our our own team. So far it is has been ad-hoc, we should continue to invest in this further as a way to discuss proposals in the open. There is also an ongoing challenge around getting the right eyes on RFCs and encouraging review. Lastely, it's not possible for those outside our team to know how to submit an RFC or proposed change to the Fluent UI Web project.

# Proposal(s)
We should formalize our RFC process in a lightweight way. 

## Propsal 1
This includes
1. An RFC Template: [Fluent UI RFC Template](/xINbpxrXToSWjYGU4sXYGQ) exposed as an issue template in our repo
2. A wiki page explaining RFC process which is as follows:
    1. File an RFC as an issue
    2. Assign issues to intended reviewers (if known)
    3. Reviewers should comment on RFC
    4. Use thumbs up reaction to indicate agrement with proposal

### Pros and Cons
- :+1: Lightweight process, easy evolution from what we do today (use issues ad-hoc)
- :-1: It will be hard to make comments a lengthy proposal, no inline comments (PRs would be better here)
- :-1: Loose review process, might be hard to get RFCs attention

## Proposal 2
This includes
1. An RFC Template: [Fluent UI RFC Template](/xINbpxrXToSWjYGU4sXYGQ) exposed as a file in the repo
2. A wiki page explaining RFC process which is as follows:
    1. Create a PR adding a new RFC to a folder


# Discarded Proposals
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. 