From 56584c7c50f4129319b7bf51fe4a63d758f6c71a Mon Sep 17 00:00:00 2001 From: ksr Date: Wed, 19 Apr 2023 10:40:57 +0200 Subject: [PATCH] update rfc process --- scratch/rfc_process_update_suggestion.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/scratch/rfc_process_update_suggestion.md b/scratch/rfc_process_update_suggestion.md index 7af37e8..e8c6711 100644 --- a/scratch/rfc_process_update_suggestion.md +++ b/scratch/rfc_process_update_suggestion.md @@ -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. 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. -Promoting RFCs from draft to stable MUST 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 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: * spec parlance?