[DirectoryOwnership] Add TEAM/COMPONENT into OWNERS files.

[DirectoryOwnership] Add TEAM/COMPONENT into OWNERS files.

We are adding COMPONENT/TEAM information into OWNERS file
(signin).

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=mlerman@chromium.org

Review-Url: https://codereview.chromium.org/2744513003
Cr-Commit-Position: refs/heads/master@{#456709}
Committed: https://chromium.googlesource.com/chromium/src/+/6f78a7a80b37afd562cd45f57c1b9a4a3ff711e1

[ymzhang1, 2017-03-09 22:57:33]

ymzhang@chromium.org changed reviewers:
+ msarda@chromium.org, rogerta@chromium.org

[ymzhang1, 2017-03-09 22:57:33]

Hello,

We are adding COMPONENT/TEAM information into OWNERS file. Would you mind
helping us to verify the added TEAM/COMPONENT or suggest the correct
TEAM/COMPONENT in your OWNERS files? Thank you very much!

[msarda, 2017-03-10 14:21:25]

msarda@chromium.org changed reviewers:
+ ewald@google.com, tengs@google.com

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

https://codereview.chromium.org/2744513003/diff/1/chrome/browser/signin/OWNERS
File chrome/browser/signin/OWNERS (right):

https://codereview.chromium.org/2744513003/diff/1/chrome/browser/signin/OWNER...
chrome/browser/signin/OWNERS:17: # COMPONENT: UI>ProximityAuth
# 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]

https://codereview.chromium.org/2744513003/diff/1/chrome/browser/signin/OWNERS
File chrome/browser/signin/OWNERS (right):

https://codereview.chromium.org/2744513003/diff/1/chrome/browser/signin/OWNER...
chrome/browser/signin/OWNERS:17: # COMPONENT: UI>ProximityAuth
On 2017/03/10 14:21:26, msarda wrote:
> # TEAM: mailto: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.

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!

[ymzhang1, 2017-03-13 21:58:44]

mlerman@, msarda@, rogerta@:

Could (one of) you please lgtm this change in chrome/browser/signin/OWNERS?
Thanks.

[Mike Lerman, 2017-03-14 00:50:39]

On 2017/03/13 21:58:44, ymzhang1 wrote:
> mlerman@, msarda@, rogerta@:
> 
> Could (one of) you please lgtm this change in chrome/browser/signin/OWNERS?
> Thanks.

msarda's the current, active TL of this project; Roger and I both work on
different areas now.
He should be the one to provide l-g-t-m.

[msarda, 2017-03-14 03:02:08]

lgtm

[ymzhang1, 2017-03-14 15:35:32]

The CQ bit was checked by ymzhang@chromium.org

[commit-bot: I haz the power, 2017-03-14 15:36:15]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-03-14 15:45:26]

CQ is committing da patch.

Bot data: {"patchset_id": 20001, "attempt_start_ts": 1489505732170130,
"parent_rev": "31afd3a4d2c0763304f080c519776cb37ee743a7", "commit_rev":
"6f78a7a80b37afd562cd45f57c1b9a4a3ff711e1"}

[commit-bot: I haz the power, 2017-03-14 15:46:07]

Description was changed from

==========
[DirectoryOwnership] Add TEAM/COMPONENT into OWNERS files.

We are adding COMPONENT/TEAM information into OWNERS file
(signin).

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=mlerman@chromium.org
==========

to

==========
[DirectoryOwnership] Add TEAM/COMPONENT into OWNERS files.

We are adding COMPONENT/TEAM information into OWNERS file
(signin).

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=mlerman@chromium.org

Review-Url: https://codereview.chromium.org/2744513003
Cr-Commit-Position: refs/heads/master@{#456709}
Committed:
https://chromium.googlesource.com/chromium/src/+/6f78a7a80b37afd562cd45f57c1b...
==========

[commit-bot: I haz the power, 2017-03-14 15:46:08]

Committed patchset #2 (id:20001) as
https://chromium.googlesource.com/chromium/src/+/6f78a7a80b37afd562cd45f57c1b...