proposal: without clear agreement, the arbiter decides
This is not a policy change,
but rather a clarification of the existing wording.
Reviewed-by: Russ Cox <email@example.com>
Reviewed-by: Brad Fitzpatrick <firstname.lastname@example.org>
Reviewed-by: Robert Griesemer <email@example.com>
Reviewed-by: Jaana Burcu Dogan <firstname.lastname@example.org>
diff --git a/README.md b/README.md
index c909a14..4e92db1 100644
@@ -103,9 +103,9 @@
- The goal of the final discussion is to reach agreement on the next step:
(1) accept or (2) decline.
- The discussion is expected to be resolved in a timely manner.
- - In Go development historically, a lack of agreement means decline.
- - If there is disagreement about whether there is agreement,
- [rsc@](mailto:email@example.com) is the arbiter.
+ - If clear agreement cannot be reached, the arbiter
+ ([rsc@](mailto:firstname.lastname@example.org)) reviews the discussion
+ and makes the decision to accept or decline.
- The author (and/or other contributors) do the work as described by the
"Implementation" section of the proposal.