[DirectoryOwnership] Add TEAM/COMPONENT into OWNERS files.

chrome/browser/signin/OWNERS

Index: chrome/browser/signin/OWNERS
diff --git a/chrome/browser/signin/OWNERS b/chrome/browser/signin/OWNERS
index 265baae0f0de7d23f53d5aa6b4a3b5e4d314db6b..66484c014b8c5de829af79470bc4b278f652cb59 100644
--- a/chrome/browser/signin/OWNERS
+++ b/chrome/browser/signin/OWNERS
@@ -13,3 +13,5 @@ per-file easy_unlock_*=xiyuan@chromium.org
 per-file screenlock_bridge*=tbarzic@chromium.org
 per-file screenlock_bridge*=tengs@chromium.org
 per-file screenlock_bridge*=xiyuan@chromium.org
+
+# COMPONENT: UI>ProximityAuth

[msarda, 2017/03/10 14:21:26]

# TEAM: chrome-signin@chromium.org (I doubt this group exists now as we were
only using a Google internal group. Should I create this group?)
# COMPONENT: Services>SignIn


easy_unlock* files have a different component though:
#TEAM: 
#COMPONENT: UI>ProximityAuth
I think that tengs@ can advise on this.

[ymzhang1, 2017/03/10 18:06:06]

Thanks for the comments! I'll add chrome-signin@chromium.org for now. I maintain
a list of component-team(including internal group) yet only public mailing lists
will be added in OWNERS files.

We would like to add only one primary component in OWNERS file. Many thanks for
information about easy_unlock*. I'll save this mapping (easy_unlock*:
UI>ProximityAuth) separately. Team information is also welcome for component
UI>ProximityAuth. Thanks!