Skip to content

repo: Add RFC process document #3

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
tingerrr wants to merge 8 commits into
base: main
Choose a base branch
from
Open

repo: Add RFC process document #3

Changes from 1 commit
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
241a125
[wip] repo: Add RFC process document
tingerrr Jul 2, 2025
256c215
[fixup] Review by SillyFreak v1
tingerrr Jul 4, 2025
2e28c20
[fixup] Review by Sillyfreak v2
tingerrr Jul 5, 2025
e954673
[fixup] Concerns by Mentonin (Community Discord)
tingerrr Aug 5, 2025
49c9022
[fixup] Additional suggestions by Sillyfreak
tingerrr Sep 14, 2025
086763e
Bring README.md in line with the RFC process
tingerrr Jul 7, 2025
0b2035f
[fixup] Review by McZen v1
tingerrr Oct 28, 2025
01e1e9f
[fixup] Review by McZen v2
tingerrr Dec 13, 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
2 changes: 1 addition & 1 deletion docs/process.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -112,7 +112,7 @@ At that point the RFC is "active" and may be implemented with the goal of eventu
Put care into the details: RFCs that do not present convincing motivation, demonstrate lack of understanding of the design's impact, or are disingenuous about the drawbacks or alternatives tend to be poorly-received.
- Submit a pull request.
As a pull request the RFC will receive design feedback from the larger community, and the author should be prepared to revise it in response.
The pull request should start with `RFC`/`Draft RFC` to clearly distinguish it form non-RFCs.
The pull request should start with `RFC`/`Draft RFC` to clearly distinguish it from non-RFCs.
The PR description should have a link to the markdown document so it can be viewed as a rendered page on your fork.
You can get do this by going to the file in the PR changes, clicking `View File` and replacing the commit hash with the branch name, this creates a link like so: `https://github.com/<your account>/<your fork>/blob/<your PR branch name>/<your RFC document path>`.
Comment thread
tingerrr marked this conversation as resolved.
Outdated
Comment thread
tingerrr marked this conversation as resolved.
Outdated
- Now that your RFC has an open pull request, use the issue number of the PR to rename the file: update your `0000-` prefix to that number.
Expand Down