add TEAM/COMPONENT information to OWNERS file

content/OWNERS

 alexmos@chromium.org
 avi@chromium.org
 clamy@chromium.org
 creis@chromium.org
 darin@chromium.org
 dgozman@chromium.org
 jam@chromium.org
 jochen@chromium.org
 kinuko@chromium.org
 nasko@chromium.org
 nick@chromium.org
 pfeldman@chromium.org
 piman@chromium.org
 
 # per-file rules:
 # These are for the common case of adding or renaming files. If you're doing
 # structural changes, please get a review from a reviewer in this file.
 per-file *.gypi=*
 per-file content_nacl_nonsfi.gyp=*
 
 # Mac Sandbox profiles.
 per-file *.sb=set noparent
 per-file *.sb=rsesek@chromium.org
 
 per-file *.isolate=maruel@chromium.org
 per-file *.isolate=tandrii@chromium.org
 per-file *.isolate=vadimsh@chromium.org
+
+# TEAM: layout-dev@chromium.org

[dgozman, 2017/01/14 01:06:45]

layout-dev is incorrect here. Not sure about the right one.

[jam, 2017/01/17 23:57:29]

What's the intent of the TEAM mailing list here? content/ will be too broad
(i.e. like src/chrome/), so I think it'll be better if you add it in more fine
grained directories underneath.

[ymzhang1, 2017/01/18 00:14:16]

We would like to add component/team information in every OWNERS when applicable.
The team will be responsible for triage the corresponding component. (related
proposal
https://docs.google.com/document/d/1jty6UsFMW9-SYgpQC-ztEc3lltziOQBBArMkROCST...)

Fine grained directories will add TEAM/COMPONENT information also. If a
directory is too broad and we couldn't find any proper component, we will not
add team/component as suggested.

For content/, maybe it's better to remove both TEAM and COMPONENT information?

[ymzhang1, 2017/01/18 19:32:13]

Done.

+# COMPONENT: Internals>Core