tauri-apps/archived-rfcs
1
0
Fork 0
mirror of https://github.com/tauri-apps/rfcs.git synced 2026-01-31 00:35:24 +01:00
Code Issues Packages Projects Releases Wiki Activity

Update README.md

Browse Source 
Co-authored-by: Fabian-Lars <fabianlars@fabianlars.de>
This commit is contained in:
Lorenzo Lewis
2023-03-12 13:09:15 +00:00
committed by GitHub
parent 7f2bc54837
commit 440e07b30e
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@@ -23,6 +23,6 @@ Once you have enough information to begin an RFC you can follow this process to
1) **Fork this repo**
2) **Copy the template** Move your copy of `template.md` into the `texts` folder, naming it in the scheme of `0000-feature.md`. Note: the number is literal and will be adjusted just before merging.
3) **Fill the template out** Replace all relevant sections with explanations. Put care into the details, as it will serve as a reference through the development process.
3) **Fill out the template** Replace all relevant sections with explanations. Put care into the details, as it will serve as a reference through the development process.
4) **Open a PR** After opening a PR, the RFC is open for comment. Discussion should happen in the comments of the PR. RFCs that are "invalid" (don't follow the format/proceedure, violate CoC, or are otherwise unable to be used) may be closed immediately.
5) **Merged into the repo** The final stage of an RFC that signals it is accepted is it being merged into this repo. If a PR for an implementation is already submitted then it will be used to track the status from there. Otherwise a tracking issue will be created in the respective repo to capture the implementation status.