Skip to content

Add a template RFC #1818

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Add a template RFC #1818

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
06708dc
add a template rfc
magicmark Sep 15, 2025
5edb991
Update TEMPLATE.md
magicmark Sep 15, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions rfcs/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,3 +16,4 @@ That said, please follow these suggestions:

* New proposals should be presented in a [working group meeting](../agendas). Submitting a document here is not sufficient or required to introduce a new proposal.
* Favor documents which define a problem and explore a solution space rather than propose a specific change. The intent of documents found here are to help ask and answer questions to build confidence and advance an RFC.
* A template is provided [here](./TEMPLATE.md) as a starting point for new RFCs.
45 changes: 45 additions & 0 deletions rfcs/TEMPLATE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,45 @@
<!-- This template is provided as a suggested starting point. You may alter the
format where necessary. -->

# RFC: <Title>

**Proposed by:** [<Full Name>](https://github.com/<username>) - <Organization>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
**Proposed by:** [<Full Name>](https://github.com/<username>) - <Organization>
**Proposed by:** [<Full Name>](https://github.com/<username>) - <Organization>
**Current champion:** [<Full Name>](https://github.com/<username>) - <Organization>


<!-- Briefly summarize and explainin the concepts introduced by the RFC. Usually
one or two short sentences or paragraphs. -->

## 📜 Problem Statement

<!-- Briefly explain the problem being solved. Assume no prior knowledge (other
than the current GraphQL specification) and start from first principles. Usually
one or two short paragraphs. -->

**Example**

<!-- Provide a minimal code example here if possible. -->

## 💡 Proposed Solution

<!-- Explain the proposal! Be detailed enough to explain the idea and major edge
cases - but avoid being overly detailed. The primary goal is to communicate the
idea at a high level. The specification edit PR will cover all the precise
implementation details. -->

## ⚠️ Risks

<!-- Think: Why *shouldn't* we do this proposal? List any unaddressed risks or
edge cases we need to consider. -->

## Appendix

<!-- Additional appendix sections are encourged as the editor sees fit. You are
encouraged to keep the main body of the RFC focused on the chosen solution. -->

### 🎨 Prior Art

<!-- If applicable, list any existing userland solutions that relate to this
RFC. -->

### 🤔 Alternatives Considered

<!-- If applicable, list any alternate naming or implementations considered. -->