Commit 021fec42 authored by ymzhang's avatar ymzhang Committed by Commit bot

[DirectoryOwnership] Add TEAM/COMPONENT into OWNERS files.

We are adding COMPONENT/TEAM information into OWNERS files
(*installer, chrome_elf, etc). Thanks.

Proposal to add TEAM/COMPONENT information into OWNERS files
http://bit.ly/add-team-component-proposal
Proposal about how to get suggested component for directory.
http://bit.ly/directory-mapping-proposal
TEAM-COMPONENT mapping
http://bit.ly/component-team-mapping

Additional Information:
Component lists
https://bugs.chromium.org/p/chromium/adminComponents

BUG=679905
R=robertshield@chromium.org
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.win:win10_chromium_x64_rel_ng

Review-Url: https://codereview.chromium.org/2713793003
Cr-Commit-Position: refs/heads/master@{#453422}
parent bd0fec20
mad@chromium.org
robertshield@chromium.org
# COMPONENT: Internals>PlatformIntegration
caitkp@chromium.org
grt@chromium.org
robertshield@chromium.org
# COMPONENT: Services>SafeBrowsing
csharp@chromium.org
robertshield@chromium.org
# COMPONENT: UI>Browser>Preferences>Protector
......@@ -3,3 +3,5 @@ grt@chromium.org
robertshield@chromium.org
per-file policy_path_parser.*=file://chrome/browser/policy/OWNERS
# COMPONENT: Internals>Installer
gab@chromium.org
grt@chromium.org
robertshield@chromium.org
# COMPONENT: Internals>Installer
gab@chromium.org
grt@chromium.org
robertshield@chromium.org
# COMPONENT: Internals>Installer
......@@ -6,3 +6,5 @@ brucedawson@chromium.org
# FILES.cfg OWNERS as in parent owner file.
per-file FILES.cfg=kerz@chromium.org
per-file FILES.cfg=mmoss@chromium.org
# COMPONENT: Build
......@@ -2,3 +2,5 @@ caitkp@chromium.org
robertshield@chromium.org
# For early browser process security and nt_registry:
pennymac@chromium.org
# COMPONENT: Internals>Core
caitkp@chromium.org
csharp@chromium.org
robertshield@chromium.org
# COMPONENT: Internals>Core
grt@chromium.org
robertshield@chromium.org
# COMPONENT: Internals>Installer
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment