File: OWNERS

package info (click to toggle)
chromium 120.0.6099.224-1~deb11u1
  • links: PTS, VCS
  • area: main
  • in suites: bullseye
  • size: 6,112,112 kB
  • sloc: cpp: 32,907,025; ansic: 8,148,123; javascript: 3,679,536; python: 2,031,248; asm: 959,718; java: 804,675; xml: 617,256; sh: 111,417; objc: 100,835; perl: 88,443; cs: 53,032; makefile: 29,579; fortran: 24,137; php: 21,162; tcl: 21,147; sql: 20,809; ruby: 17,735; pascal: 12,864; yacc: 8,045; lisp: 3,388; lex: 1,323; ada: 727; awk: 329; jsp: 267; csh: 117; exp: 43; sed: 37
file content (65 lines) | stat: -rw-r--r-- 2,582 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
# src/content is a large and complex component. In general, files should be in
# subdirectories that have specific owners who are the experts in reviewing that
# code. Top level content/OWNERS are reviewers who are qualified to review
# changes across all of content and are responsible for its architecture. They
# will defer to subdirectory owners as needed. As such we expect that a
# content/OWNER has made substantial contributions to content/ in the recent
# past, specifically both in the browser and renderer subdirectories as they
# encapsulate the main architecture, and demonstrated overall knowledge of the
# content architecture by doing code reviews for changes that affect different
# parts of content even before being a content/OWNER.
#
# For public questions directed to OWNERS, you can send email
# to content-owners@chromium.org.

set noparent
# NOTE: keep this in sync with lsc-owners-override@chromium.org owners
# by emailing lsc-policy@chromium.org when this list changes.
alexmos@chromium.org
altimin@chromium.org
arthursonzogni@chromium.org
avi@chromium.org
clamy@chromium.org
creis@chromium.org
dgozman@chromium.org
jam@chromium.org
kinuko@chromium.org
nasko@chromium.org
rakina@chromium.org
# NOTE: keep this in sync with lsc-owners-override@chromium.org owners
# by emailing lsc-policy@chromium.org when this list changes.

# per-file rules:

# For threading and startup/shutdown sequences
# gab@chromium.org (see per-file rules in subdirectories)

# This is 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 BUILD.gn=*

per-file content_resources.grd=file://ui/webui/PLATFORM_OWNERS
per-file dev_ui_content_resources.grd=file://ui/webui/PLATFORM_OWNERS

# The remaining rules are for platform-specific implementation changes.
# Do NOT add other per-file changes as they would also apply to public/.

# For Fuchsia-specific changes:
per-file ...fuchsia*=file://build/fuchsia/OWNERS

# For Mac-specific changes:
per-file ..._mac.*=ellyjones@chromium.org
per-file ..._mac.*=mark@chromium.org
per-file ..._mac.*=rsesek@chromium.org
per-file ..._mac.*=tapted@chromium.org
per-file ..._mac_*=ellyjones@chromium.org
per-file ..._mac_*=mark@chromium.org
per-file ..._mac_*=rsesek@chromium.org
per-file ..._mac_*=tapted@chromium.org
per-file ....mm=ellyjones@chromium.org
per-file ....mm=mark@chromium.org
per-file ....mm=rsesek@chromium.org
per-file ....mm=tapted@chromium.org

# Translation artifacts:
per-file ....xtb=file://tools/translation/TRANSLATION_OWNERS