vacp2p/vac-book
1
0
Fork 0
mirror of https://github.com/vacp2p/vac-book.git synced 2026-01-09 05:17:55 -05:00
Code Issues Packages Projects Releases Wiki Activity

update rfc process

Browse Source
This commit is contained in:
ksr
2023-04-19 10:40:57 +02:00
parent 469ddb64c4
commit 56584c7c50
1 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
scratch/rfc_process_update_suggestion.md
View File

@@ -16,8 +16,10 @@ Every team can publish raw RFCs, with reviewers from their respective team or ot
Raw RFCs can be published without any formal process. Raw RFCs can be published without any formal process.
This allows all teams to publish specs without being blocked. This allows all teams to publish specs without being blocked.
Promoting RFCs from raw to draft, as well as updating draft RFCs SHOULD involve Vac. It is RECOMMENDED to involve Vac for promoting RFCs from raw to draft, as well as updating draft RFCs.
Promoting RFCs from draft to stable MUST involve Vac. Promoting RFCs from draft to stable SHOULD involve Vac.
Involving Vac in the process will add the `vac` tag to the RFC.
Vac would check various aspects of RFCs before promoting: Vac would check various aspects of RFCs before promoting:
* spec parlance? * spec parlance?