[DirectoryOwnership] Add TEAM/COMPONENT into OWNERS files.

[DirectoryOwnership] Add TEAM/COMPONENT into OWNERS files.

We are adding COMPONENT/TEAM information into OWNERS file (sync, etc).

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

Review-Url: https://codereview.chromium.org/2712103003
Cr-Commit-Position: refs/heads/master@{#453663}
Committed: https://chromium.googlesource.com/chromium/src/+/a1d9b2dc55999f3e2cb00e861116c2baeb398560

[ymzhang1, 2017-02-24 20:55:01]

Patchset #1 (id:1) has been deleted

[ymzhang1, 2017-02-24 20:55:21]

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!

[Nicolas Zea, 2017-02-24 22:50:10]

zea@chromium.org changed reviewers:
+ estark@chromium.org, sergeyu@chromium.org

[Nicolas Zea, 2017-02-24 22:50:10]

https://codereview.chromium.org/2712103003/diff/20001/components/network_time...
File components/network_time/OWNERS (right):

https://codereview.chromium.org/2712103003/diff/20001/components/network_time...
components/network_time/OWNERS:4: # COMPONENT: Internals>Network
Hmm, this isn't really network related. I wonder if perhaps, given it's most in
use by the security side, if we should make it part of the security component?
+estark

https://codereview.chromium.org/2712103003/diff/20001/ios/chrome/browser/serv...
File ios/chrome/browser/services/OWNERS (right):

https://codereview.chromium.org/2712103003/diff/20001/ios/chrome/browser/serv...
ios/chrome/browser/services/OWNERS:3: # COMPONENT: Services>SupervisedUser
This should be CloudMessaging

https://codereview.chromium.org/2712103003/diff/20001/jingle/OWNERS
File jingle/OWNERS (right):

https://codereview.chromium.org/2712103003/diff/20001/jingle/OWNERS#newcode4
jingle/OWNERS:4: # COMPONENT: Factory
Sergey, thoughts about having CloudPrint own this?

[ymzhang1, 2017-02-24 22:55:48]

https://codereview.chromium.org/2712103003/diff/20001/jingle/OWNERS
File jingle/OWNERS (right):

https://codereview.chromium.org/2712103003/diff/20001/jingle/OWNERS#newcode4
jingle/OWNERS:4: # COMPONENT: Factory
On 2017/02/24 22:50:10, Nicolas Zea wrote:
> Sergey, thoughts about having CloudPrint own this?

I will remove this line since the directory touches several components. Feel
free to let me know if I could put a primary component here.

[estark, 2017-02-28 18:08:18]

https://codereview.chromium.org/2712103003/diff/20001/components/network_time...
File components/network_time/OWNERS (right):

https://codereview.chromium.org/2712103003/diff/20001/components/network_time...
components/network_time/OWNERS:4: # COMPONENT: Internals>Network
On 2017/02/24 22:50:10, Nicolas Zea wrote:
> Hmm, this isn't really network related. I wonder if perhaps, given it's most
in
> use by the security side, if we should make it part of the security component?
> +estark

Yeah, agree that Internals>Network isn't quite right; I'd be fine with having
this in UI>Browser>Interstitials, since we use it for modifying SSL interstitial
behavior.

[ymzhang1, 2017-02-28 18:29:58]

https://codereview.chromium.org/2712103003/diff/20001/components/network_time...
File components/network_time/OWNERS (right):

https://codereview.chromium.org/2712103003/diff/20001/components/network_time...
components/network_time/OWNERS:4: # COMPONENT: Internals>Network
On 2017/02/28 18:08:18, estark wrote:
> On 2017/02/24 22:50:10, Nicolas Zea wrote:
> > Hmm, this isn't really network related. I wonder if perhaps, given it's most
> in
> > use by the security side, if we should make it part of the security
component?
> > +estark
> 
> Yeah, agree that Internals>Network isn't quite right; I'd be fine with having
> this in UI>Browser>Interstitials, since we use it for modifying SSL
interstitial
> behavior.

Done.

https://codereview.chromium.org/2712103003/diff/20001/ios/chrome/browser/serv...
File ios/chrome/browser/services/OWNERS (right):

https://codereview.chromium.org/2712103003/diff/20001/ios/chrome/browser/serv...
ios/chrome/browser/services/OWNERS:3: # COMPONENT: Services>SupervisedUser
On 2017/02/24 22:50:10, Nicolas Zea wrote:
> This should be CloudMessaging

Done.

[Nicolas Zea, 2017-02-28 18:37:01]

LGTM with one more change

https://codereview.chromium.org/2712103003/diff/40001/ios/chrome/browser/ui/w...
File ios/chrome/browser/ui/webui/gcm/OWNERS (right):

https://codereview.chromium.org/2712103003/diff/40001/ios/chrome/browser/ui/w...
ios/chrome/browser/ui/webui/gcm/OWNERS:6: # COMPONENT: UI>Browser>WebUI
This should be CloudMessaging too

[ymzhang1, 2017-02-28 18:44:30]

https://codereview.chromium.org/2712103003/diff/40001/ios/chrome/browser/ui/w...
File ios/chrome/browser/ui/webui/gcm/OWNERS (right):

https://codereview.chromium.org/2712103003/diff/40001/ios/chrome/browser/ui/w...
ios/chrome/browser/ui/webui/gcm/OWNERS:6: # COMPONENT: UI>Browser>WebUI
On 2017/02/28 18:37:01, Nicolas Zea wrote:
> This should be CloudMessaging too

Done. Thanks!

[ymzhang1, 2017-02-28 18:44:48]

The CQ bit was checked by ymzhang@chromium.org

[ymzhang1, 2017-02-28 18:44:48]

The patchset sent to the CQ was uploaded after l-g-t-m from zea@chromium.org
Link to the patchset: https://codereview.chromium.org/2712103003/#ps60001
(title: "update component")

[commit-bot: I haz the power, 2017-02-28 18:45:25]

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-02-28 19:27:48]

CQ is committing da patch.

Bot data: {"patchset_id": 60001, "attempt_start_ts": 1488307488146890,
"parent_rev": "5c88a0f3700057690cd3e644e346e5fef84ae666", "commit_rev":
"a1d9b2dc55999f3e2cb00e861116c2baeb398560"}

[commit-bot: I haz the power, 2017-02-28 19:28:30]

Description was changed from

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

We are adding COMPONENT/TEAM information into OWNERS file (sync, etc).

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

to

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

We are adding COMPONENT/TEAM information into OWNERS file (sync, etc).

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

Review-Url: https://codereview.chromium.org/2712103003
Cr-Commit-Position: refs/heads/master@{#453663}
Committed:
https://chromium.googlesource.com/chromium/src/+/a1d9b2dc55999f3e2cb00e861116...
==========

[commit-bot: I haz the power, 2017-02-28 19:28:31]

Committed patchset #3 (id:60001) as
https://chromium.googlesource.com/chromium/src/+/a1d9b2dc55999f3e2cb00e861116...