Add code author expectation.
As code reviewers are expected to perform multiple review passes per
work day, code authors should feel empowered to add different reviewers
if the initial reviewer is not responsive.
Change-Id: I3e15bb0af755a660ce06afd751c8091b6b070f8b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6305072
Commit-Queue: Erik Chen <[email protected]>
Reviewed-by: Rick Byers <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1425383}
diff --git a/docs/code_reviews.md b/docs/code_reviews.md
index d169d99..e8a340b 100644
--- a/docs/code_reviews.md
+++ b/docs/code_reviews.md
@@ -51,6 +51,11 @@
* Don't generally discourage people from sending you code reviews. This
includes using a blanket "slow" in your status field.
+#### Expectations for all authors
+
+* If a reviewer does not respond within 2 works days, add another
+ reviewer onto the CL. Do not remove the initial reviewer.
+
## OWNERS files
In various directories there are files named `OWNERS` that list the email
