Add PERMISSIONS_OWNERS for reviewing PermissionContext subclass changes

chrome/browser/permissions/PERMISSIONS_OWNERS

Index: chrome/browser/permissions/PERMISSIONS_OWNERS
diff --git a/chrome/browser/permissions/PERMISSIONS_OWNERS b/chrome/browser/permissions/PERMISSIONS_OWNERS
new file mode 100644
index 0000000000000000000000000000000000000000..44d11c8f600614a066973d87ff9e7b82f8d16d38
--- /dev/null
+++ b/chrome/browser/permissions/PERMISSIONS_OWNERS
@@ -0,0 +1,8 @@
+# permission_context subclasses require a Security UX review by one of the

[benwells, 2017/07/06 07:20:59]

Nit: PermissionContext subclasses...

[raymes, 2017/07/11 01:57:35]

Done.

+# following:
+
+benwells@chromium.org
+dominickn@chromium.org
+kcarattini@chromium.org
+raymes@chromium.org
+timloh@chromium.org

[Peter Beverloo, 2017/07/06 11:29:34]

If you're going down the route of `set noparent` (which we have a general
dislike for, but you know that), it's good practice to try to grow a more
geographically distributed set of OWNERS.

[mlamouri (slow - plz ping), 2017/07/07 09:40:46]

If that's an issue, I'm pretty sure I can review the PermissionContext
subclasses.

[raymes, 2017/07/11 01:57:35]

Good point - I didn't think about that. I think changes to these files tend to
be quite rare by non-permissions folks right now so having a geographical
distribution might not be too important yet. A quick look shows only about 5-6
changes in the last 6 months by non-permissions OWNERS. Given some of the
nuances in the code it might be good to have a smaller set of owners for the
time being but we can expand that if needed :)