Skip to main content

RFC Template

Title:
Descriptive name of the RFC

Author:
Your Name

Date:
MM/DD/YYYY

Status:
[Draft/Final/Accepted/Rejected]


1. Overview​

Problem Statement:
A brief description of the problem this RFC aims to address.

Proposed Solution:
A high-level summary of the solution you are proposing.

2. Motivation​

Why is this change necessary? What problem does it solve? Provide any background context or scenarios that led to this RFC.

3. Detailed Design​

Architecture/Design Details:
Describe the detailed solution, including any technical specifications, diagrams, or changes to current systems.

Implementation Plan:
How will this change be implemented? Break it down into actionable steps or phases.

4. Alternatives Considered​

List other possible approaches that were considered and explain why they were not chosen.

5. Drawbacks​

What are the potential downsides of the proposed solution? Are there risks or trade-offs?

6. Dependencies​

Are there any dependencies (technical, team-related, or other) for this proposal to be implemented successfully?

7. Impact​

Describe the impact of this RFC on existing systems, codebases, or workflows.

8. Unresolved Questions​

List any open questions or areas that need further exploration.

9. Timeline​

What is the expected timeline for implementation? Include key milestones if necessary.