From a2ef612d0320be1788b5d937c6b3c110265d0dd2 Mon Sep 17 00:00:00 2001 From: Brandon Wilson Date: Thu, 8 Feb 2024 14:44:27 -0500 Subject: [PATCH] Update contributing guide to explicitly state changes that don't meaningfully change the specification only require one approval. We should add a tag to mark and track these as well. --- CONTRIBUTING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 18541a5..43943d4 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -57,8 +57,8 @@ Submissions fall into one of two categories: 1. **Contributions that _do not_ change the specifications, or their interpretation** These are issues and PRs largely aimed at improving legibility, fixing editorial errors, - clearing up ambiguities, or adding examples to existing specifications. - These may be progressed and merged without much process. + clearing up ambiguities, adding examples to existing specifications, or updating the tooling that generates the documentation. + These may be progressed and merged without much process and typically only require one approval from a member of the LAC working group. 2. **Contributions that _do_ meaningfully change the specifications** These must progress through the stages of RFC, guided by a sponsor until