OWNERS: restrict core/important subdirs to domain experts
Changes to this tree are infrequent enough that we can reasonably
restrict approval to general ebuild/eclass experts, and lock down
the accounts to the security team.
BUG=None
TEST=None
Change-Id: Id62989f49bff326c94e8ee233bf8f5a9a61d7d74
Reviewed-on: https://chromium-review.googlesource.com/1672532
Tested-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com>
Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org>
Reviewed-by: Chris McDonald <cjmcdonald@chromium.org>
Reviewed-by: Jorge Lucangeli Obes <jorgelo@chromium.org>
Reviewed-by: Ned Nguyen <nednguyen@google.com>
diff --git a/OWNERS b/OWNERS
new file mode 100644
index 0000000..4a9eb01
--- /dev/null
+++ b/OWNERS
@@ -0,0 +1 @@
+include chromiumos/overlays/portage-stable:/OWNERS.general
diff --git a/profiles/base/accounts/OWNERS b/profiles/base/accounts/OWNERS
new file mode 100644
index 0000000..b4644f1
--- /dev/null
+++ b/profiles/base/accounts/OWNERS
@@ -0,0 +1,9 @@
+set noparent
+# The helper scripts are a bit more lenient.
+per-file *.py = file: /OWNERS
+
+# The security team are domain experts in account isolation.
+allenwebb@chromium.org
+jorgelo@chromium.org
+mnissler@chromium.org
+vapier@chromium.org
