Add TEAM/COMPONENT information

add TEAM/COMPONENT information

BUG=679905
Please help us to verify the TEAM/COMPONENT information. If the current information is incorrect, please suggest the correct team or component or None(if not applicable).

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

[ymzhang1, 2017-01-12 23:38:28]

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

[ymzhang1, 2017-01-12 23:38:29]

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 file? Thank you very much!


-Yang

[ymzhang1, 2017-01-12 23:39:42]

Description was changed from

==========
add TEAM/COMPONENT information

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

to

==========
add TEAM/COMPONENT information

BUG=679905

Please help us to verify the TEAM/COMPONENT information. If the current
information is incorrect, please suggest the correct team or component or
None(if not applicable).
==========

[haraken, 2017-01-13 02:02:47]

On 2017/01/12 23:38:29, ymzhang1 wrote:
> 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 file? Thank you very much!
> 
> 
> -Yang

How did you choose the TEAMs? Most of the lists don't make sense to me. I'm
happy to correct but want to understand how you chose it :)

[ymzhang1, 2017-01-13 19:31:06]

On 2017/01/13 02:02:47, haraken wrote:
> On 2017/01/12 23:38:29, ymzhang1 wrote:
> > 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 file? Thank you very much!
> > 
> > 
> > -Yang
> 
> How did you choose the TEAMs? Most of the lists don't make sense to me. I'm
> happy to correct but want to understand how you chose it :)

It would be great if you could help to correct! 

The TEAMs is assigned based on Component. The current assumption is one
component match to one team mailing list(Correct me if this assumption is not
proper). And here is a mapping between component and team
(https://docs.google.com/spreadsheets/d/19JEFMvsxD3eThyGiJRqAjcpx362LHUDdVzICA...).


For component, we learned a prediction model based the collected data
(directory-component mapping) and similarity between component key words and
directory key words. We would like to recommend a component that matches a
directory best. If a directory includes too many different things, then we will
not add any COMPONENT/TEAM information in its OWNERS.

[haraken, 2017-01-16 01:41:50]

https://codereview.chromium.org/2627003007/diff/1/base/allocator/partition_al...
File base/allocator/partition_allocator/OWNERS (right):

https://codereview.chromium.org/2627003007/diff/1/base/allocator/partition_al...
base/allocator/partition_allocator/OWNERS:4: # TEAM: oilpan-reviews@chromium.org

platform-architecture-dev@chromium.org

https://codereview.chromium.org/2627003007/diff/1/content/browser/memory/OWNERS
File content/browser/memory/OWNERS (right):

https://codereview.chromium.org/2627003007/diff/1/content/browser/memory/OWNE...
content/browser/memory/OWNERS:5: # TEAM: chrome-owp-storage@chromium.org

platform-architecture-dev@chromium.org

https://codereview.chromium.org/2627003007/diff/1/content/browser/memory/OWNE...
content/browser/memory/OWNERS:6: # COMPONENT: Blink>Storage

Blink>MemoryAllocator

https://codereview.chromium.org/2627003007/diff/1/content/child/memory/OWNERS
File content/child/memory/OWNERS (right):

https://codereview.chromium.org/2627003007/diff/1/content/child/memory/OWNERS...
content/child/memory/OWNERS:5: # TEAM: chrome-owp-storage@chromium.org

platform-architecture-dev@chromium.org

https://codereview.chromium.org/2627003007/diff/1/content/child/memory/OWNERS...
content/child/memory/OWNERS:6: # COMPONENT: Blink>Storage

Blink>MemoryAllocator

https://codereview.chromium.org/2627003007/diff/1/third_party/WebKit/Source/b...
File third_party/WebKit/Source/bindings/OWNERS (right):

https://codereview.chromium.org/2627003007/diff/1/third_party/WebKit/Source/b...
third_party/WebKit/Source/bindings/OWNERS:14: # TEAM: layout-dev@chromium.org

platform-architecture-dev@chromium.org

https://codereview.chromium.org/2627003007/diff/1/third_party/WebKit/Source/w...
File third_party/WebKit/Source/web/OWNERS (right):

https://codereview.chromium.org/2627003007/diff/1/third_party/WebKit/Source/w...
third_party/WebKit/Source/web/OWNERS:24: # TEAM: blink-html-dom@chromium.org

platform-architecture-dev@chromium.org

https://codereview.chromium.org/2627003007/diff/1/third_party/WebKit/Source/w...
third_party/WebKit/Source/web/OWNERS:25: # COMPONENT: Blink>Forms

Blink>Internals>Modularization

https://codereview.chromium.org/2627003007/diff/1/third_party/WebKit/Source/w...
File third_party/WebKit/Source/wtf/OWNERS (right):

https://codereview.chromium.org/2627003007/diff/1/third_party/WebKit/Source/w...
third_party/WebKit/Source/wtf/OWNERS:11: # TEAM: oilpan-reviews@chromium.org

platform-architecture-dev@chromium.org

https://codereview.chromium.org/2627003007/diff/1/third_party/WebKit/Source/w...
third_party/WebKit/Source/wtf/OWNERS:12: # COMPONENT: Blink>MemoryAllocator

Blink>Internals>WTF

https://codereview.chromium.org/2627003007/diff/1/third_party/WebKit/public/O...
File third_party/WebKit/public/OWNERS (right):

https://codereview.chromium.org/2627003007/diff/1/third_party/WebKit/public/O...
third_party/WebKit/public/OWNERS:22: # TEAM: chrome-owp-storage@chromium.org

platform-architecture-dev@chromium.org

https://codereview.chromium.org/2627003007/diff/1/third_party/WebKit/public/O...
third_party/WebKit/public/OWNERS:23: # COMPONENT: Blink>DataTransfer

Blink>Internals>Modularization

https://codereview.chromium.org/2627003007/diff/1/third_party/jinja2/OWNERS
File third_party/jinja2/OWNERS (right):

https://codereview.chromium.org/2627003007/diff/1/third_party/jinja2/OWNERS#n...
third_party/jinja2/OWNERS:5: # COMPONENT: Internals

platform-architecture-dev@chromium.org

Blink>Internals

https://codereview.chromium.org/2627003007/diff/1/tools/clang/blink_gc_plugin...
File tools/clang/blink_gc_plugin/OWNERS (right):

https://codereview.chromium.org/2627003007/diff/1/tools/clang/blink_gc_plugin...
tools/clang/blink_gc_plugin/OWNERS:6: # COMPONENT: Tools

oilpan-reviews@chromium.org

Blink>MemoryAllocator

https://codereview.chromium.org/2627003007/diff/1/tools/idl_parser/OWNERS
File tools/idl_parser/OWNERS (right):

https://codereview.chromium.org/2627003007/diff/1/tools/idl_parser/OWNERS#new...
tools/idl_parser/OWNERS:5: # COMPONENT: Tools

platform-architecture-dev@chromium.org

Blink>Bindings

[ymzhang1, 2017-01-17 18:45:27]

https://codereview.chromium.org/2627003007/diff/1/base/allocator/partition_al...
File base/allocator/partition_allocator/OWNERS (right):

https://codereview.chromium.org/2627003007/diff/1/base/allocator/partition_al...
base/allocator/partition_allocator/OWNERS:4: # TEAM: oilpan-reviews@chromium.org
On 2017/01/16 01:41:49, haraken wrote:
> 
> mailto:platform-architecture-dev@chromium.org

Thank you very much for providing detail information!

One question: 
It seems Blink>MemoryAllocator has mapped to
platform-architecture-dev@chromium.org and oilpan-reviews (e.g.
third_party/WebKit/Source/platform/heap/OWNERS). We would like to have one
component-one team. Could you suggest which one is the primary team to triage
Blink>MemoryAllocator?

+ Shruthi regarding component-team mapping requirement

[haraken, 2017-01-18 00:13:06]

On 2017/01/17 18:45:27, ymzhang1 wrote:
>
https://codereview.chromium.org/2627003007/diff/1/base/allocator/partition_al...
> File base/allocator/partition_allocator/OWNERS (right):
> 
>
https://codereview.chromium.org/2627003007/diff/1/base/allocator/partition_al...
> base/allocator/partition_allocator/OWNERS:4: # TEAM:
mailto:oilpan-reviews@chromium.org
> On 2017/01/16 01:41:49, haraken wrote:
> > 
> > mailto:platform-architecture-dev@chromium.org
> 
> Thank you very much for providing detail information!
> 
> One question: 
> It seems Blink>MemoryAllocator has mapped to
> mailto:platform-architecture-dev@chromium.org and oilpan-reviews (e.g.
> third_party/WebKit/Source/platform/heap/OWNERS). We would like to have one
> component-one team. Could you suggest which one is the primary team to triage
> Blink>MemoryAllocator?

platform-architecture-dev@chromium.org in general. For Oilpan (platform/heap/)
stuff, oilpan-reviews@ is better.

> 
> + Shruthi regarding component-team mapping requirement

[ymzhang1, 2017-01-18 17:42:06]

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

[ymzhang1, 2017-01-18 18:05:15]

https://codereview.chromium.org/2627003007/diff/1/base/allocator/partition_al...
File base/allocator/partition_allocator/OWNERS (right):

https://codereview.chromium.org/2627003007/diff/1/base/allocator/partition_al...
base/allocator/partition_allocator/OWNERS:4: # TEAM: oilpan-reviews@chromium.org
On 2017/01/16 01:41:49, haraken wrote:
> 
> mailto:platform-architecture-dev@chromium.org

Done.

https://codereview.chromium.org/2627003007/diff/1/content/browser/memory/OWNERS
File content/browser/memory/OWNERS (right):

https://codereview.chromium.org/2627003007/diff/1/content/browser/memory/OWNE...
content/browser/memory/OWNERS:5: # TEAM: chrome-owp-storage@chromium.org
On 2017/01/16 01:41:49, haraken wrote:
> 
> mailto:platform-architecture-dev@chromium.org

Done.

https://codereview.chromium.org/2627003007/diff/1/content/browser/memory/OWNE...
content/browser/memory/OWNERS:6: # COMPONENT: Blink>Storage
On 2017/01/16 01:41:49, haraken wrote:
> 
> Blink>MemoryAllocator

Done.

https://codereview.chromium.org/2627003007/diff/1/content/child/memory/OWNERS
File content/child/memory/OWNERS (right):

https://codereview.chromium.org/2627003007/diff/1/content/child/memory/OWNERS...
content/child/memory/OWNERS:5: # TEAM: chrome-owp-storage@chromium.org
On 2017/01/16 01:41:49, haraken wrote:
> 
> mailto:platform-architecture-dev@chromium.org

Done.

https://codereview.chromium.org/2627003007/diff/1/content/child/memory/OWNERS...
content/child/memory/OWNERS:6: # COMPONENT: Blink>Storage
On 2017/01/16 01:41:49, haraken wrote:
> 
> Blink>MemoryAllocator

Done.

https://codereview.chromium.org/2627003007/diff/1/third_party/WebKit/Source/b...
File third_party/WebKit/Source/bindings/OWNERS (right):

https://codereview.chromium.org/2627003007/diff/1/third_party/WebKit/Source/b...
third_party/WebKit/Source/bindings/OWNERS:14: # TEAM: layout-dev@chromium.org
On 2017/01/16 01:41:49, haraken wrote:
> 
> mailto:platform-architecture-dev@chromium.org

Done.

https://codereview.chromium.org/2627003007/diff/1/third_party/WebKit/Source/w...
File third_party/WebKit/Source/web/OWNERS (right):

https://codereview.chromium.org/2627003007/diff/1/third_party/WebKit/Source/w...
third_party/WebKit/Source/web/OWNERS:24: # TEAM: blink-html-dom@chromium.org
On 2017/01/16 01:41:49, haraken wrote:
> 
> mailto:platform-architecture-dev@chromium.org

Done.

https://codereview.chromium.org/2627003007/diff/1/third_party/WebKit/Source/w...
third_party/WebKit/Source/web/OWNERS:25: # COMPONENT: Blink>Forms
On 2017/01/16 01:41:49, haraken wrote:
> 
> Blink>Internals>Modularization

Done.

https://codereview.chromium.org/2627003007/diff/1/third_party/WebKit/Source/w...
File third_party/WebKit/Source/wtf/OWNERS (right):

https://codereview.chromium.org/2627003007/diff/1/third_party/WebKit/Source/w...
third_party/WebKit/Source/wtf/OWNERS:11: # TEAM: oilpan-reviews@chromium.org
On 2017/01/16 01:41:49, haraken wrote:
> 
> mailto:platform-architecture-dev@chromium.org

Done.

https://codereview.chromium.org/2627003007/diff/1/third_party/WebKit/Source/w...
third_party/WebKit/Source/wtf/OWNERS:12: # COMPONENT: Blink>MemoryAllocator
On 2017/01/16 01:41:50, haraken wrote:
> 
> Blink>Internals>WTF

Done.

https://codereview.chromium.org/2627003007/diff/1/third_party/WebKit/public/O...
File third_party/WebKit/public/OWNERS (right):

https://codereview.chromium.org/2627003007/diff/1/third_party/WebKit/public/O...
third_party/WebKit/public/OWNERS:22: # TEAM: chrome-owp-storage@chromium.org
On 2017/01/16 01:41:50, haraken wrote:
> 
> mailto:platform-architecture-dev@chromium.org

Done.

https://codereview.chromium.org/2627003007/diff/1/third_party/WebKit/public/O...
third_party/WebKit/public/OWNERS:23: # COMPONENT: Blink>DataTransfer
On 2017/01/16 01:41:50, haraken wrote:
> 
> Blink>Internals>Modularization

Done.

https://codereview.chromium.org/2627003007/diff/1/third_party/jinja2/OWNERS
File third_party/jinja2/OWNERS (right):

https://codereview.chromium.org/2627003007/diff/1/third_party/jinja2/OWNERS#n...
third_party/jinja2/OWNERS:5: # COMPONENT: Internals
On 2017/01/16 01:41:50, haraken wrote:
> 
> mailto:platform-architecture-dev@chromium.org
> 
> Blink>Internals

Done.

https://codereview.chromium.org/2627003007/diff/1/tools/clang/blink_gc_plugin...
File tools/clang/blink_gc_plugin/OWNERS (right):

https://codereview.chromium.org/2627003007/diff/1/tools/clang/blink_gc_plugin...
tools/clang/blink_gc_plugin/OWNERS:6: # COMPONENT: Tools
On 2017/01/16 01:41:50, haraken wrote:
> 
> mailto:oilpan-reviews@chromium.org
> 
> Blink>MemoryAllocator

We would like to have only one team for each component. Or maybe create a
sub-component. Do you mind using platform-architecture-dev@chromium.org here?

[haraken, 2017-01-18 23:56:45]

On 2017/01/18 18:05:15, ymzhang1 wrote:
>
https://codereview.chromium.org/2627003007/diff/1/base/allocator/partition_al...
> File base/allocator/partition_allocator/OWNERS (right):
> 
>
https://codereview.chromium.org/2627003007/diff/1/base/allocator/partition_al...
> base/allocator/partition_allocator/OWNERS:4: # TEAM:
mailto:oilpan-reviews@chromium.org
> On 2017/01/16 01:41:49, haraken wrote:
> > 
> > mailto:platform-architecture-dev@chromium.org
> 
> Done.
> 
>
https://codereview.chromium.org/2627003007/diff/1/content/browser/memory/OWNERS
> File content/browser/memory/OWNERS (right):
> 
>
https://codereview.chromium.org/2627003007/diff/1/content/browser/memory/OWNE...
> content/browser/memory/OWNERS:5: # TEAM:
mailto:chrome-owp-storage@chromium.org
> On 2017/01/16 01:41:49, haraken wrote:
> > 
> > mailto:platform-architecture-dev@chromium.org
> 
> Done.
> 
>
https://codereview.chromium.org/2627003007/diff/1/content/browser/memory/OWNE...
> content/browser/memory/OWNERS:6: # COMPONENT: Blink>Storage
> On 2017/01/16 01:41:49, haraken wrote:
> > 
> > Blink>MemoryAllocator
> 
> Done.
> 
> https://codereview.chromium.org/2627003007/diff/1/content/child/memory/OWNERS
> File content/child/memory/OWNERS (right):
> 
>
https://codereview.chromium.org/2627003007/diff/1/content/child/memory/OWNERS...
> content/child/memory/OWNERS:5: # TEAM: mailto:chrome-owp-storage@chromium.org
> On 2017/01/16 01:41:49, haraken wrote:
> > 
> > mailto:platform-architecture-dev@chromium.org
> 
> Done.
> 
>
https://codereview.chromium.org/2627003007/diff/1/content/child/memory/OWNERS...
> content/child/memory/OWNERS:6: # COMPONENT: Blink>Storage
> On 2017/01/16 01:41:49, haraken wrote:
> > 
> > Blink>MemoryAllocator
> 
> Done.
> 
>
https://codereview.chromium.org/2627003007/diff/1/third_party/WebKit/Source/b...
> File third_party/WebKit/Source/bindings/OWNERS (right):
> 
>
https://codereview.chromium.org/2627003007/diff/1/third_party/WebKit/Source/b...
> third_party/WebKit/Source/bindings/OWNERS:14: # TEAM:
mailto:layout-dev@chromium.org
> On 2017/01/16 01:41:49, haraken wrote:
> > 
> > mailto:platform-architecture-dev@chromium.org
> 
> Done.
> 
>
https://codereview.chromium.org/2627003007/diff/1/third_party/WebKit/Source/w...
> File third_party/WebKit/Source/web/OWNERS (right):
> 
>
https://codereview.chromium.org/2627003007/diff/1/third_party/WebKit/Source/w...
> third_party/WebKit/Source/web/OWNERS:24: # TEAM:
mailto:blink-html-dom@chromium.org
> On 2017/01/16 01:41:49, haraken wrote:
> > 
> > mailto:platform-architecture-dev@chromium.org
> 
> Done.
> 
>
https://codereview.chromium.org/2627003007/diff/1/third_party/WebKit/Source/w...
> third_party/WebKit/Source/web/OWNERS:25: # COMPONENT: Blink>Forms
> On 2017/01/16 01:41:49, haraken wrote:
> > 
> > Blink>Internals>Modularization
> 
> Done.
> 
>
https://codereview.chromium.org/2627003007/diff/1/third_party/WebKit/Source/w...
> File third_party/WebKit/Source/wtf/OWNERS (right):
> 
>
https://codereview.chromium.org/2627003007/diff/1/third_party/WebKit/Source/w...
> third_party/WebKit/Source/wtf/OWNERS:11: # TEAM:
mailto:oilpan-reviews@chromium.org
> On 2017/01/16 01:41:49, haraken wrote:
> > 
> > mailto:platform-architecture-dev@chromium.org
> 
> Done.
> 
>
https://codereview.chromium.org/2627003007/diff/1/third_party/WebKit/Source/w...
> third_party/WebKit/Source/wtf/OWNERS:12: # COMPONENT: Blink>MemoryAllocator
> On 2017/01/16 01:41:50, haraken wrote:
> > 
> > Blink>Internals>WTF
> 
> Done.
> 
>
https://codereview.chromium.org/2627003007/diff/1/third_party/WebKit/public/O...
> File third_party/WebKit/public/OWNERS (right):
> 
>
https://codereview.chromium.org/2627003007/diff/1/third_party/WebKit/public/O...
> third_party/WebKit/public/OWNERS:22: # TEAM:
mailto:chrome-owp-storage@chromium.org
> On 2017/01/16 01:41:50, haraken wrote:
> > 
> > mailto:platform-architecture-dev@chromium.org
> 
> Done.
> 
>
https://codereview.chromium.org/2627003007/diff/1/third_party/WebKit/public/O...
> third_party/WebKit/public/OWNERS:23: # COMPONENT: Blink>DataTransfer
> On 2017/01/16 01:41:50, haraken wrote:
> > 
> > Blink>Internals>Modularization
> 
> Done.
> 
> https://codereview.chromium.org/2627003007/diff/1/third_party/jinja2/OWNERS
> File third_party/jinja2/OWNERS (right):
> 
>
https://codereview.chromium.org/2627003007/diff/1/third_party/jinja2/OWNERS#n...
> third_party/jinja2/OWNERS:5: # COMPONENT: Internals
> On 2017/01/16 01:41:50, haraken wrote:
> > 
> > mailto:platform-architecture-dev@chromium.org
> > 
> > Blink>Internals
> 
> Done.
> 
>
https://codereview.chromium.org/2627003007/diff/1/tools/clang/blink_gc_plugin...
> File tools/clang/blink_gc_plugin/OWNERS (right):
> 
>
https://codereview.chromium.org/2627003007/diff/1/tools/clang/blink_gc_plugin...
> tools/clang/blink_gc_plugin/OWNERS:6: # COMPONENT: Tools
> On 2017/01/16 01:41:50, haraken wrote:
> > 
> > mailto:oilpan-reviews@chromium.org
> > 
> > Blink>MemoryAllocator
> 
> We would like to have only one team for each component. Or maybe create a
> sub-component. Do you mind using mailto:platform-architecture-dev@chromium.org
here?

ok. Would you update the CL?

[ymzhang1, 2017-01-19 00:26:39]

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

[ymzhang1, 2017-01-19 00:26:39]

Here is the updated CL.

+tkent
regarding team/component in third_party/WebKit/public/OWNERS.

[tkent, 2017-01-19 01:31:55]

> +tkent
> regarding team/component in third_party/WebKit/public/OWNERS.

It looks ok.

[haraken, 2017-01-19 02:05:35]

https://codereview.chromium.org/2627003007/diff/20001/third_party/WebKit/Sour...
File third_party/WebKit/Source/bindings/OWNERS (right):

https://codereview.chromium.org/2627003007/diff/20001/third_party/WebKit/Sour...
third_party/WebKit/Source/bindings/OWNERS:14: # TEAM:
platform-architecture-dev@chromium.org

blink-reviews-bindings@

https://codereview.chromium.org/2627003007/diff/20001/third_party/WebKit/Sour...
File third_party/WebKit/Source/modules/OWNERS (right):

https://codereview.chromium.org/2627003007/diff/20001/third_party/WebKit/Sour...
third_party/WebKit/Source/modules/OWNERS:12: # TEAM: blink-dev@chromium.org

How is the email address going to be used? It would be noisy if people start
sending an email to blink-dev@.

platform-architecture-dev@ ?

https://codereview.chromium.org/2627003007/diff/20001/third_party/WebKit/Sour...
third_party/WebKit/Source/modules/OWNERS:13: # COMPONENT: Blink

Blink>Internals>Modularization

https://codereview.chromium.org/2627003007/diff/20001/third_party/WebKit/Sour...
File third_party/WebKit/Source/platform/heap/OWNERS (right):

https://codereview.chromium.org/2627003007/diff/20001/third_party/WebKit/Sour...
third_party/WebKit/Source/platform/heap/OWNERS:7: # COMPONENT:
Blink>MemoryAllocator

oilpan-reviews@
Blink>MemoryAllocator>GarbageCollection

https://codereview.chromium.org/2627003007/diff/20001/tools/clang/blink_gc_pl...
File tools/clang/blink_gc_plugin/OWNERS (right):

https://codereview.chromium.org/2627003007/diff/20001/tools/clang/blink_gc_pl...
tools/clang/blink_gc_plugin/OWNERS:7: # COMPONENT: Blink>MemoryAllocator

oilpan-reviews@
Blink>MemoryAllocator>GarbageCollection

https://codereview.chromium.org/2627003007/diff/20001/tools/idl_parser/OWNERS
File tools/idl_parser/OWNERS (right):

https://codereview.chromium.org/2627003007/diff/20001/tools/idl_parser/OWNERS...
tools/idl_parser/OWNERS:5: # TEAM: platform-architecture-dev@chromium.org

blink-bindings-reviews@

[ymzhang1, 2017-01-19 22:31:19]

https://codereview.chromium.org/2627003007/diff/20001/third_party/WebKit/Sour...
File third_party/WebKit/Source/bindings/OWNERS (right):

https://codereview.chromium.org/2627003007/diff/20001/third_party/WebKit/Sour...
third_party/WebKit/Source/bindings/OWNERS:14: # TEAM:
platform-architecture-dev@chromium.org
On 2017/01/19 02:05:35, haraken wrote:
> 
> blink-reviews-bindings@

Done.

https://codereview.chromium.org/2627003007/diff/20001/third_party/WebKit/Sour...
File third_party/WebKit/Source/modules/OWNERS (right):

https://codereview.chromium.org/2627003007/diff/20001/third_party/WebKit/Sour...
third_party/WebKit/Source/modules/OWNERS:12: # TEAM: blink-dev@chromium.org
On 2017/01/19 02:05:35, haraken wrote:
> 
> How is the email address going to be used? It would be noisy if people start
> sending an email to blink-dev@.
> 
> platform-architecture-dev@ ?

The email address won't be used in any automation as part of current plans. It
is only a way to record contact information of the team that owns the directory.


Mailing list for broad team is added and will serve as the escalation point for
any sub-directories that don't have owner teams currently. 

More details could be find in the following proposal. 
https://docs.google.com/document/d/1jty6UsFMW9-SYgpQC-ztEc3lltziOQBBArMkROCST...

https://codereview.chromium.org/2627003007/diff/20001/third_party/WebKit/Sour...
third_party/WebKit/Source/modules/OWNERS:13: # COMPONENT: Blink
On 2017/01/19 02:05:35, haraken wrote:
> 
> Blink>Internals>Modularization

Done.

https://codereview.chromium.org/2627003007/diff/20001/third_party/WebKit/Sour...
File third_party/WebKit/Source/platform/heap/OWNERS (right):

https://codereview.chromium.org/2627003007/diff/20001/third_party/WebKit/Sour...
third_party/WebKit/Source/platform/heap/OWNERS:7: # COMPONENT:
Blink>MemoryAllocator
On 2017/01/19 02:05:35, haraken wrote:
> 
> oilpan-reviews@
> Blink>MemoryAllocator>GarbageCollection

Done.

https://codereview.chromium.org/2627003007/diff/20001/tools/clang/blink_gc_pl...
File tools/clang/blink_gc_plugin/OWNERS (right):

https://codereview.chromium.org/2627003007/diff/20001/tools/clang/blink_gc_pl...
tools/clang/blink_gc_plugin/OWNERS:7: # COMPONENT: Blink>MemoryAllocator
On 2017/01/19 02:05:35, haraken wrote:
> 
> oilpan-reviews@
> Blink>MemoryAllocator>GarbageCollection

Done.

https://codereview.chromium.org/2627003007/diff/20001/tools/idl_parser/OWNERS
File tools/idl_parser/OWNERS (right):

https://codereview.chromium.org/2627003007/diff/20001/tools/idl_parser/OWNERS...
tools/idl_parser/OWNERS:5: # TEAM: platform-architecture-dev@chromium.org
On 2017/01/19 02:05:35, haraken wrote:
> 
> blink-bindings-reviews@

Done.

[haraken, 2017-01-20 00:17:35]

LGTM

https://codereview.chromium.org/2627003007/diff/40001/tools/directory_ownersh...
File tools/directory_ownership/log.json (right):

https://codereview.chromium.org/2627003007/diff/40001/tools/directory_ownersh...
tools/directory_ownership/log.json:8: }

What is this file?

[ymzhang1, 2017-01-20 00:45:39]

https://codereview.chromium.org/2627003007/diff/40001/tools/directory_ownersh...
File tools/directory_ownership/log.json (right):

https://codereview.chromium.org/2627003007/diff/40001/tools/directory_ownersh...
tools/directory_ownership/log.json:8: }
On 2017/01/20 00:17:35, haraken wrote:
> 
> What is this file?

Oops, I'll remove this. Mistakenly upload.

[ymzhang1, 2017-01-20 00:45:45]

The CQ bit was checked by ymzhang@chromium.org

[ymzhang1, 2017-01-20 00:45:46]

The patchset sent to the CQ was uploaded after l-g-t-m from haraken@chromium.org
Link to the patchset: https://codereview.chromium.org/2627003007/#ps60001
(title: "Merge branch 'master' of https://chromium.googlesource.com/chromium/src
into ha_adding")

[commit-bot: I haz the power, 2017-01-20 00:46:36]

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-01-20 01:57:36]

CQ is committing da patch.

Bot data: {"patchset_id": 60001, "attempt_start_ts": 1484873145962460,
"parent_rev": "8f3596ad8588a28907ccfca0f9c9af984e3c5681", "commit_rev":
"ad51088c0e8776e8dcd963dbe752c4035ba6dab6"}

[commit-bot: I haz the power, 2017-01-20 01:58:08]

Description was changed from

==========
add TEAM/COMPONENT information

BUG=679905

Please help us to verify the TEAM/COMPONENT information. If the current
information is incorrect, please suggest the correct team or component or
None(if not applicable).
==========

to

==========
add TEAM/COMPONENT information

BUG=679905

Please help us to verify the TEAM/COMPONENT information. If the current
information is incorrect, please suggest the correct team or component or
None(if not applicable).

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

[commit-bot: I haz the power, 2017-01-20 01:58:09]

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

[Wez, 2017-02-07 22:34:20]

wez@chromium.org changed reviewers:
+ asvitkine@chromium.org

[Wez, 2017-02-07 22:34:21]

Hallo asvitkine@chromium.org!
Due to a depot_tools patch which mistakenly removed the OWNERS check for
non-source files (see crbug.com/684270), the following files landed in this CL
and need a retrospective review from you:
	tools/metrics/histograms/OWNERS
Thanks,
Wez

[Alexei Svitkine (slow), 2017-02-07 22:42:04]

tools/metrics/histograms/OWNERS lgtm