proposal: bestow arbitership upon rsc Change-Id: Ifd805448f7d6f2ffa97bb9a5c2ab1387f96018dc Reviewed-on: https://go-review.googlesource.com/29330 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org> Reviewed-by: Russ Cox <rsc@golang.org>
diff --git a/README.md b/README.md index c713b0c..c909a14 100644 --- a/README.md +++ b/README.md
@@ -71,7 +71,7 @@ - In Go development historically, a lack of agreement means the author should write a design doc. - If there is disagreement about whether there is agreement, - [adg@](mailto:adg@golang.org) is the arbiter. + [rsc@](mailto:rsc@golang.org) is the arbiter. - It's always fine to label a suggestion issue with Proposal to opt in to this process. @@ -105,7 +105,7 @@ - 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, - [adg@](mailto:adg@golang.org) is the arbiter. + [rsc@](mailto:rsc@golang.org) is the arbiter. - The author (and/or other contributors) do the work as described by the "Implementation" section of the proposal. @@ -135,7 +135,5 @@ (Note that the list is moderated, and that first-time posters should expect a delay while their message is held for moderation.) -If you want to talk to someone off-list, contact Andrew Gerrand at <adg@golang.org>. - To learn about contributing to Go in general, see the [contribution guidelines](https://golang.org/doc/contribute.html).