content/renderer/OWNERS - Issue 2641543002: add COMPONENT/TEAM to OWNERS

Side by Side Diff: content/renderer/OWNERS

Issue 2641543002: add COMPONENT/TEAM to OWNERS (Closed)

Patch Set: Created 3 years, 11 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

OLD	NEW
1 # For Blink API usage	1 # For Blink API usage

2 esprehn@chromium.org	2 esprehn@chromium.org

3	3

4 # For Android	4 # For Android

5 aelias@chromium.org	5 aelias@chromium.org

6	6

7 # Mac Sandbox profiles.	7 # Mac Sandbox profiles.

8 per-file *.sb=set noparent	8 per-file *.sb=set noparent

9 per-file *.sb=rsesek@chromium.org	9 per-file *.sb=rsesek@chromium.org

10	10

11 # DirectWrite specific changes.	11 # DirectWrite specific changes.

12 per-file renderer_font_platform_win.*=scottmg@chromium.org	12 per-file renderer_font_platform_win.*=scottmg@chromium.org

13 per-file renderer_font_platform_win.*=cpu@chromium.org	13 per-file renderer_font_platform_win.*=cpu@chromium.org

14	14

15 # WebSocket	15 # WebSocket

16 per-file websocket=ricea@chromium.org	16 per-file websocket=ricea@chromium.org

17 per-file websocket=tyoshino@chromium.org	17 per-file websocket=tyoshino@chromium.org

18 per-file websocket=yhirano@chromium.org	18 per-file websocket=yhirano@chromium.org

	19

	20 # TEAM: layout-dev@chromium.org

	21 # COMPONENT: Internals>Core
	tyoshino (SeeGerritForStatus) 2017/01/18 10:26:32 This directly contains code of various teams. So, This directly contains code of various teams. So, adding only layout-dev@chromium.org shouldn't make much sense, I think. Adding eae@ to see if having layout-dev@ is ok. But still need to list all the TEAMs who have code they own here. eae 2017/01/18 16:53:55 No, layout-dev only owns a small fraction of the c Show quoted text On 2017/01/18 10:26:32, tyoshino wrote: > This directly contains code of various teams. So, adding only > mailto:layout-dev@chromium.org shouldn't make much sense, I think. > > Adding eae@ to see if having layout-dev@ is ok. But still need to list all the > TEAMs who have code they own here. No, layout-dev only owns a small fraction of the code in this direcotry. ymzhang1 2017/01/18 18:18:50 We will only have one component and one team for e Show quoted text On 2017/01/18 16:53:55, eae wrote: > On 2017/01/18 10:26:32, tyoshino wrote: > > This directly contains code of various teams. So, adding only > > mailto:layout-dev@chromium.org shouldn't make much sense, I think. > > > > Adding eae@ to see if having layout-dev@ is ok. But still need to list all the > > TEAMs who have code they own here. > > No, layout-dev only owns a small fraction of the code in this direcotry. We will only have one component and one team for each directory or none (if there's no major component). Would it be better if I remove TEAM and COMPONENT information here? Charlie Harrison 2017/01/18 18:21:24 Yes, please remove the TEAM/COMPONENT, this direct Show quoted text On 2017/01/18 18:18:50, ymzhang1 wrote: > On 2017/01/18 16:53:55, eae wrote: > > On 2017/01/18 10:26:32, tyoshino wrote: > > > This directly contains code of various teams. So, adding only > > > mailto:layout-dev@chromium.org shouldn't make much sense, I think. > > > > > > Adding eae@ to see if having layout-dev@ is ok. But still need to list all > the > > > TEAMs who have code they own here. > > > > No, layout-dev only owns a small fraction of the code in this direcotry. > > We will only have one component and one team for each directory or none (if > there's no major component). Would it be better if I remove TEAM and COMPONENT > information here? Yes, please remove the TEAM/COMPONENT, this directory shares code between many teams working inside and outside Blink. ymzhang1 2017/01/18 19:11:36 Done. Show quoted text On 2017/01/18 18:21:24, Charlie Harrison wrote: > On 2017/01/18 18:18:50, ymzhang1 wrote: > > On 2017/01/18 16:53:55, eae wrote: > > > On 2017/01/18 10:26:32, tyoshino wrote: > > > > This directly contains code of various teams. So, adding only > > > > mailto:layout-dev@chromium.org shouldn't make much sense, I think. > > > > > > > > Adding eae@ to see if having layout-dev@ is ok. But still need to list all > > the > > > > TEAMs who have code they own here. > > > > > > No, layout-dev only owns a small fraction of the code in this direcotry. > > > > We will only have one component and one team for each directory or none (if > > there's no major component). Would it be better if I remove TEAM and COMPONENT > > information here? > > Yes, please remove the TEAM/COMPONENT, this directory shares code between many > teams working inside and outside Blink. Done.
OLD	NEW

« no previous file with comments | « content/browser/websockets/OWNERS ('k') | net/data/websocket/OWNERS » ('j') | net/data/websocket/OWNERS » ('J')