chromium/src
0
Fork 0
Code Activity

Add code author expectation.

Browse Source 
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 <erikchen@chromium.org>
Reviewed-by: Rick Byers <rbyers@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1425383}
This commit is contained in:
Erik Chen
2025-02-26 13:30:29 -08:00
committed by Chromium LUCI CQ
parent 35c149f87f
commit 8bda7ba733
1 changed files with 5 additions and 0 deletions

5
docs/code_reviews.md

@ -51,6 +51,11 @@ these are advisory and not policy.
* 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