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:08:44 +00:00
committed by GitHub
parent 77565868cc
commit 7f2bc54837
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

@@ -15,7 +15,7 @@ Be sure to check through the [existing feature requests in the Tauri repo](https
3) After this time period a member of the Tauri Working Group will handle closing the RFC. If accepted, the RFC will be assigned a number.
4) If an implementation is already underway then the respective PR will be added to the RFC to track. If no implementation is started then a tracking issue in the respective repo will be created and added to the RFC to track.
An accepted RFC does not necessairly mean that Tauri will be actively working on implimentation, but instead signals that the the details in the RFC align with the overall goals of Tauri. The tracking issue or implimentation PR are where the status of an RFC's implementation (in implimentation, open to someone contributing, etc.) can be found.
An accepted RFC does not necessarily mean that Tauri will be actively working on implementation, but instead signals that the the details in the RFC align with the overall goals of Tauri. The tracking issue or implementation PR are where the status of an RFC's implementation (in implementation, open to someone contributing, etc.) can be found.
## Creating an RFC