third_party/WebKit/Source/modules/OWNERS - Issue 2627003007: Add TEAM/COMPONENT information

Side by Side Diff

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

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Side by Side Diff: third_party/WebKit/Source/modules/OWNERS

Issue 2627003007: Add TEAM/COMPONENT information (Closed)

Patch Set: update team compo 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:

View unified diff | Download patch

« third_party/WebKit/Source/bindings/OWNERS ('K') | « third_party/WebKit/Source/bindings/OWNERS ('k') | third_party/WebKit/Source/platform/heap/OWNERS » ('j') | third_party/WebKit/Source/platform/heap/OWNERS » ('J')
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

OLD	NEW
1 esprehn@chromium.org	1 esprehn@chromium.org

2 haraken@chromium.org	2 haraken@chromium.org

3 mkwst@chromium.org	3 mkwst@chromium.org

4 mlamouri@chromium.org	4 mlamouri@chromium.org

5	5

6 # Reviewers for inspector-related code:	6 # Reviewers for inspector-related code:

7 dgozman@chromium.org	7 dgozman@chromium.org

8 pfeldman@chromium.org	8 pfeldman@chromium.org

9	9

10 per-file modules.gypi=*	10 per-file modules.gypi=*

	11

	12 # TEAM: blink-dev@chromium.org
	haraken 2017/01/19 02:05:35 How is the email address going to be used? It woul 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@ ? ymzhang1 2017/01/19 22:31:18 The email address won't be used in any automation Show quoted text 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...
	13 # COMPONENT: Blink
	haraken 2017/01/19 02:05:35 Blink>Internals>Modularization Blink>Internals>Modularization ymzhang1 2017/01/19 22:31:19 Done. Show quoted text On 2017/01/19 02:05:35, haraken wrote: > > Blink>Internals>Modularization Done.
OLD	NEW