summaryrefslogtreecommitdiff
path: root/chromium/content/OWNERS
diff options
context:
space:
mode:
authorAllan Sandfeld Jensen <allan.jensen@qt.io>2020-10-12 14:27:29 +0200
committerAllan Sandfeld Jensen <allan.jensen@qt.io>2020-10-13 09:35:20 +0000
commitc30a6232df03e1efbd9f3b226777b07e087a1122 (patch)
treee992f45784689f373bcc38d1b79a239ebe17ee23 /chromium/content/OWNERS
parent7b5b123ac58f58ffde0f4f6e488bcd09aa4decd3 (diff)
downloadqtwebengine-chromium-85-based.tar.gz
BASELINE: Update Chromium to 85.0.4183.14085-based
Change-Id: Iaa42f4680837c57725b1344f108c0196741f6057 Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
Diffstat (limited to 'chromium/content/OWNERS')
-rw-r--r--chromium/content/OWNERS11
1 files changed, 11 insertions, 0 deletions
diff --git a/chromium/content/OWNERS b/chromium/content/OWNERS
index c64c6832d22..b57e6b25668 100644
--- a/chromium/content/OWNERS
+++ b/chromium/content/OWNERS
@@ -1,3 +1,14 @@
+# src/content is a large and complex component. In general, files should be in
+# subdirectories that have specific owners who are the experts in reviewing that
+# code. Top level content/OWNERS are reviewers who are qualified to review
+# changes across all of content and are responsible for its architecture. They
+# will defer to subdirectory owners as needed. As such we expect that a
+# content/OWNER has made substantial contributions to content/ in the recent
+# past, specifically both in the browser and renderer subdirectories as they
+# encapsulate the main architecture, and demonstrated overall knowledge of the
+# content architecture by doing code reviews for changes that affect different
+# parts of content even before being a content/OWNER.
+
alexmos@chromium.org
avi@chromium.org
clamy@chromium.org