[DirectoryOwnership] Add TEAM/COMPONENT into OWNERS files.

[DirectoryOwnership] Add TEAM/COMPONENT into OWNERS files.

We are adding COMPONENT/TEAM information into OWNERS file. Please help us to
verify the added TEAM/COMPONENT or suggest the correct TEAM/COMPONENT in your
OWNERS files. 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:
List of components
https://bugs.chromium.org/p/chromium/adminComponents

BUG=679905
Review-Url: https://codereview.chromium.org/2696903004
Cr-Commit-Position: refs/heads/master@{#454081}
Committed: https://chromium.googlesource.com/chromium/src/+/c7f36df401d6c79813e1137e4d67e0bb0ecf8557

[ymzhang1, 2017-02-14 22:58:55]

ymzhang@chromium.org changed reviewers:
+ sergeyu@chromium.org

[ymzhang1, 2017-02-14 22:58:56]

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!

[Sergey Ulanov, 2017-02-15 00:20:37]

https://codereview.chromium.org/2696903004/diff/1/chrome/test/remoting/OWNERS
File chrome/test/remoting/OWNERS (right):

https://codereview.chromium.org/2696903004/diff/1/chrome/test/remoting/OWNERS...
chrome/test/remoting/OWNERS:9: # COMPONENT: Test>Missing
This should be Services>Chromoting

https://codereview.chromium.org/2696903004/diff/1/content/browser/renderer_ho...
File content/browser/renderer_host/p2p/OWNERS (right):

https://codereview.chromium.org/2696903004/diff/1/content/browser/renderer_ho...
content/browser/renderer_host/p2p/OWNERS:4: # COMPONENT: Content>WebApps
Blink>WebRTC

https://codereview.chromium.org/2696903004/diff/1/content/renderer/p2p/OWNERS
File content/renderer/p2p/OWNERS (right):

https://codereview.chromium.org/2696903004/diff/1/content/renderer/p2p/OWNERS...
content/renderer/p2p/OWNERS:4: # COMPONENT: Content>WebApps
Blink>WebRTC

https://codereview.chromium.org/2696903004/diff/1/jingle/OWNERS
File jingle/OWNERS (right):

https://codereview.chromium.org/2696903004/diff/1/jingle/OWNERS#newcode4
jingle/OWNERS:4: # COMPONENT: EnterpriseRetailMode
This code is used by Chrome Sync, CloudPrint and Chromoting. I'm not sure what's
the right component to set here.

https://codereview.chromium.org/2696903004/diff/1/remoting/OWNERS
File remoting/OWNERS (right):

https://codereview.chromium.org/2696903004/diff/1/remoting/OWNERS#newcode9
remoting/OWNERS:9: # COMPONENT: IO
Services>Chromoting

https://codereview.chromium.org/2696903004/diff/1/remoting/android/OWNERS
File remoting/android/OWNERS (right):

https://codereview.chromium.org/2696903004/diff/1/remoting/android/OWNERS#new...
remoting/android/OWNERS:9: # COMPONENT: IO
Can this directory inherit component from remoting/OWNERS?

https://codereview.chromium.org/2696903004/diff/1/remoting/client/jni/OWNERS
File remoting/client/jni/OWNERS (right):

https://codereview.chromium.org/2696903004/diff/1/remoting/client/jni/OWNERS#...
remoting/client/jni/OWNERS:9: # COMPONENT: IO
same here. If components are not inherited, then this should be
Services>Chromoting

https://codereview.chromium.org/2696903004/diff/1/testing/chromoting/OWNERS
File testing/chromoting/OWNERS (right):

https://codereview.chromium.org/2696903004/diff/1/testing/chromoting/OWNERS#n...
testing/chromoting/OWNERS:6: # COMPONENT: Test
Services>Chromoting

https://codereview.chromium.org/2696903004/diff/1/third_party/libjingle/OWNERS
File third_party/libjingle/OWNERS (right):

https://codereview.chromium.org/2696903004/diff/1/third_party/libjingle/OWNER...
third_party/libjingle/OWNERS:7: # COMPONENT: Internals>Network>Library
Blink>WebRTC

https://codereview.chromium.org/2696903004/diff/1/third_party/libjingle_xmpp/...
File third_party/libjingle_xmpp/OWNERS (right):

https://codereview.chromium.org/2696903004/diff/1/third_party/libjingle_xmpp/...
third_party/libjingle_xmpp/OWNERS:7: # COMPONENT: Internals>Network>Library
libjingle_xmpp is used mainly in /jingle, so it should be the same component as
in /jingle. But that dir is shared between multiple features, so I'm not sure
which component this dir belongs to.

https://codereview.chromium.org/2696903004/diff/1/third_party/opus/OWNERS
File third_party/opus/OWNERS (right):

https://codereview.chromium.org/2696903004/diff/1/third_party/opus/OWNERS#new...
third_party/opus/OWNERS:4: # COMPONENT: Internals>Network>Library
Opus is used by media and webrtc. I'm not sure what's the right component here.
Do we need components for third-party deps that are shared between multiple
teams?

[ymzhang1, 2017-02-15 00:51:50]

ymzhang@chromium.org changed reviewers:
+ sshruthi@chromium.org

[ymzhang1, 2017-02-15 00:51:51]

+Shruthi 

Regarding multiple components.

https://codereview.chromium.org/2696903004/diff/1/chrome/test/remoting/OWNERS
File chrome/test/remoting/OWNERS (right):

https://codereview.chromium.org/2696903004/diff/1/chrome/test/remoting/OWNERS...
chrome/test/remoting/OWNERS:9: # COMPONENT: Test>Missing
On 2017/02/15 00:20:36, Sergey Ulanov wrote:
> This should be Services>Chromoting 

Done.

https://codereview.chromium.org/2696903004/diff/1/content/browser/renderer_ho...
File content/browser/renderer_host/p2p/OWNERS (right):

https://codereview.chromium.org/2696903004/diff/1/content/browser/renderer_ho...
content/browser/renderer_host/p2p/OWNERS:4: # COMPONENT: Content>WebApps
On 2017/02/15 00:20:37, Sergey Ulanov wrote:
> Blink>WebRTC

Done.

https://codereview.chromium.org/2696903004/diff/1/content/renderer/p2p/OWNERS
File content/renderer/p2p/OWNERS (right):

https://codereview.chromium.org/2696903004/diff/1/content/renderer/p2p/OWNERS...
content/renderer/p2p/OWNERS:4: # COMPONENT: Content>WebApps
On 2017/02/15 00:20:37, Sergey Ulanov wrote:
> Blink>WebRTC

Done.

https://codereview.chromium.org/2696903004/diff/1/remoting/OWNERS
File remoting/OWNERS (right):

https://codereview.chromium.org/2696903004/diff/1/remoting/OWNERS#newcode9
remoting/OWNERS:9: # COMPONENT: IO
On 2017/02/15 00:20:37, Sergey Ulanov wrote:
> Services>Chromoting 

Done.

https://codereview.chromium.org/2696903004/diff/1/remoting/android/OWNERS
File remoting/android/OWNERS (right):

https://codereview.chromium.org/2696903004/diff/1/remoting/android/OWNERS#new...
remoting/android/OWNERS:9: # COMPONENT: IO
On 2017/02/15 00:20:37, Sergey Ulanov wrote:
> Can this directory inherit component from remoting/OWNERS?

Yes. It would be good if we could put component information here also. Thx!

https://codereview.chromium.org/2696903004/diff/1/remoting/client/jni/OWNERS
File remoting/client/jni/OWNERS (right):

https://codereview.chromium.org/2696903004/diff/1/remoting/client/jni/OWNERS#...
remoting/client/jni/OWNERS:9: # COMPONENT: IO
On 2017/02/15 00:20:37, Sergey Ulanov wrote:
> same here. If components are not inherited, then this should be
> Services>Chromoting 

Done.

https://codereview.chromium.org/2696903004/diff/1/testing/chromoting/OWNERS
File testing/chromoting/OWNERS (right):

https://codereview.chromium.org/2696903004/diff/1/testing/chromoting/OWNERS#n...
testing/chromoting/OWNERS:6: # COMPONENT: Test
On 2017/02/15 00:20:37, Sergey Ulanov wrote:
> Services>Chromoting 

Done.

https://codereview.chromium.org/2696903004/diff/1/third_party/libjingle/OWNERS
File third_party/libjingle/OWNERS (right):

https://codereview.chromium.org/2696903004/diff/1/third_party/libjingle/OWNER...
third_party/libjingle/OWNERS:7: # COMPONENT: Internals>Network>Library
On 2017/02/15 00:20:37, Sergey Ulanov wrote:
> Blink>WebRTC

Done.

https://codereview.chromium.org/2696903004/diff/1/third_party/opus/OWNERS
File third_party/opus/OWNERS (right):

https://codereview.chromium.org/2696903004/diff/1/third_party/opus/OWNERS#new...
third_party/opus/OWNERS:4: # COMPONENT: Internals>Network>Library
On 2017/02/15 00:20:37, Sergey Ulanov wrote:
> Opus is used by media and webrtc. I'm not sure what's the right component
here.
> Do we need components for third-party deps that are shared between multiple
> teams?

+ Shruthi 
regarding multiple teams question.

[ymzhang1, 2017-02-24 22:28:51]

I have remove component information for those don't have a matched component.
Thanks!

https://codereview.chromium.org/2696903004/diff/1/jingle/OWNERS
File jingle/OWNERS (right):

https://codereview.chromium.org/2696903004/diff/1/jingle/OWNERS#newcode4
jingle/OWNERS:4: # COMPONENT: EnterpriseRetailMode
On 2017/02/15 00:20:37, Sergey Ulanov wrote:
> This code is used by Chrome Sync, CloudPrint and Chromoting. I'm not sure
what's
> the right component to set here.

I will remove this information.

https://codereview.chromium.org/2696903004/diff/1/remoting/android/OWNERS
File remoting/android/OWNERS (right):

https://codereview.chromium.org/2696903004/diff/1/remoting/android/OWNERS#new...
remoting/android/OWNERS:9: # COMPONENT: IO
On 2017/02/15 00:51:51, ymzhang1 wrote:
> On 2017/02/15 00:20:37, Sergey Ulanov wrote:
> > Can this directory inherit component from remoting/OWNERS?
> 
> Yes. It would be good if we could put component information here also. Thx!

I would like to remove this line if there's no proper component.

https://codereview.chromium.org/2696903004/diff/1/third_party/libjingle_xmpp/...
File third_party/libjingle_xmpp/OWNERS (right):

https://codereview.chromium.org/2696903004/diff/1/third_party/libjingle_xmpp/...
third_party/libjingle_xmpp/OWNERS:7: # COMPONENT: Internals>Network>Library
On 2017/02/15 00:20:37, Sergey Ulanov wrote:
> libjingle_xmpp is used mainly in /jingle, so it should be the same component
as
> in /jingle. But that dir is shared between multiple features, so I'm not sure
> which component this dir belongs to.

remove for now.

[ymzhang1, 2017-02-24 22:52:47]

Patchset #2 (id:20001) has been deleted

[Sergey Ulanov, 2017-02-27 21:30:01]

https://codereview.chromium.org/2696903004/diff/40001/chrome/browser/extensio...
File chrome/browser/extensions/api/messaging/OWNERS (right):

https://codereview.chromium.org/2696903004/diff/40001/chrome/browser/extensio...
chrome/browser/extensions/api/messaging/OWNERS:9: # COMPONENT: Blink>Messaging
I'm not sure Blink>Messaging is related to extension messaging API.
I think this should be Platform>Extensions>API

https://codereview.chromium.org/2696903004/diff/40001/extensions/browser/api/...
File extensions/browser/api/messaging/OWNERS (right):

https://codereview.chromium.org/2696903004/diff/40001/extensions/browser/api/...
extensions/browser/api/messaging/OWNERS:5: # COMPONENT: Blink>Messaging
Platform>Extensions>API

https://codereview.chromium.org/2696903004/diff/40001/remoting/client/jni/OWNERS
File remoting/client/jni/OWNERS (right):

https://codereview.chromium.org/2696903004/diff/40001/remoting/client/jni/OWN...
remoting/client/jni/OWNERS:9: # COMPONENT: Services>Chromoting
Remove this and inherit from remoting/OWNERS?

[ymzhang1, 2017-02-28 00:35:20]

https://codereview.chromium.org/2696903004/diff/40001/chrome/browser/extensio...
File chrome/browser/extensions/api/messaging/OWNERS (right):

https://codereview.chromium.org/2696903004/diff/40001/chrome/browser/extensio...
chrome/browser/extensions/api/messaging/OWNERS:9: # COMPONENT: Blink>Messaging
On 2017/02/27 21:30:01, Sergey Ulanov wrote:
> I'm not sure Blink>Messaging is related to extension messaging API.
> I think this should be Platform>Extensions>API

Done.

https://codereview.chromium.org/2696903004/diff/40001/extensions/browser/api/...
File extensions/browser/api/messaging/OWNERS (right):

https://codereview.chromium.org/2696903004/diff/40001/extensions/browser/api/...
extensions/browser/api/messaging/OWNERS:5: # COMPONENT: Blink>Messaging
On 2017/02/27 21:30:01, Sergey Ulanov wrote:
> Platform>Extensions>API

Done.

https://codereview.chromium.org/2696903004/diff/40001/remoting/client/jni/OWNERS
File remoting/client/jni/OWNERS (right):

https://codereview.chromium.org/2696903004/diff/40001/remoting/client/jni/OWN...
remoting/client/jni/OWNERS:9: # COMPONENT: Services>Chromoting
On 2017/02/27 21:30:01, Sergey Ulanov wrote:
> Remove this and inherit from remoting/OWNERS?

Done.

[ymzhang1, 2017-02-28 18:35:35]

Patchset #3 (id:60001) has been deleted

[ymzhang1, 2017-02-28 18:41:13]

Remove the deleted file third_party/libjingle/OWNERS.

[Sergey Ulanov, 2017-03-01 22:21:33]

lgtm

[ymzhang1, 2017-03-01 22:22:49]

The CQ bit was checked by ymzhang@chromium.org

[commit-bot: I haz the power, 2017-03-01 22:23:22]

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-01 22:57:25]

CQ is committing da patch.

Bot data: {"patchset_id": 80001, "attempt_start_ts": 1488406969623000,
"parent_rev": "d0d459e8dda997152b63f3fee88a1bf35b323a20", "commit_rev":
"c7f36df401d6c79813e1137e4d67e0bb0ecf8557"}

[commit-bot: I haz the power, 2017-03-01 22:58:06]

Description was changed from

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

We are adding COMPONENT/TEAM information into OWNERS file. Please help us to
verify the added TEAM/COMPONENT or suggest the correct TEAM/COMPONENT in your
OWNERS files. 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:
List of components
https://bugs.chromium.org/p/chromium/adminComponents

BUG=679905
==========

to

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

We are adding COMPONENT/TEAM information into OWNERS file. Please help us to
verify the added TEAM/COMPONENT or suggest the correct TEAM/COMPONENT in your
OWNERS files. 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:
List of components
https://bugs.chromium.org/p/chromium/adminComponents

BUG=679905

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

[commit-bot: I haz the power, 2017-03-01 22:58:21]

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