add TEAM/COMPONENT information to OWNERS file

content/OWNERS

Index: content/OWNERS
diff --git a/content/OWNERS b/content/OWNERS
index 76b90a449bcc531807e093d824fffac16c350a76..a528702a1d5010c617bf91ca51688dd77ce74e56 100644
--- a/content/OWNERS
+++ b/content/OWNERS
@@ -25,3 +25,6 @@ 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