1# List of OWNERS files that can be used together with "set noparent". See 2# docs/code_reviews.md#owners-file-details for more details. 3 4# Overall project governance. 5file://ATL_OWNERS 6 7# Third-party dependency review, see //docs/adding_to_third_party.md 8file://third_party/OWNERS 9 10# Security reviews 11file://build/fuchsia/SECURITY_OWNERS 12file://chromeos/SECURITY_OWNERS 13file://content/browser/CHILD_PROCESS_SECURITY_POLICY_OWNERS 14file://ipc/SECURITY_OWNERS 15file://net/base/SECURITY_OWNERS 16file://sandbox/linux/OWNERS 17file://sandbox/mac/OWNERS 18file://sandbox/OWNERS 19file://sandbox/win/OWNERS 20file://third_party/blink/SECURITY_OWNERS 21 22# Privacy reviews 23file://tools/traffic_annotation/summary/TRAFFIC_ANNOTATION_OWNERS 24file://tools/metrics/ukm/PRIVACY_OWNERS 25file://base/metrics/METRICS_OWNERS 26file://chrome/browser/ui/hats/HATS_PRIVACY_OWNERS 27 28# Blink API owners are responsible for decisions about what APIs Blink should 29# expose to the open web. 30file://third_party/blink/API_OWNERS 31 32# third_party/blink/web_tests/VirtualTestSuites need special care. 33file://third_party/blink/web_tests/VIRTUAL_OWNERS 34 35# Extension related files. 36file://chrome/browser/extensions/component_extensions_allowlist/EXTENSION_ALLOWLIST_OWNERS 37file://extensions/common/api/API_OWNERS 38 39# This restriction is in place to avoid accidental addition to our top level 40# layout files, such as add duplicated assets, or introducing new colors when 41# we don't want them. 42file://ui/android/java/res/LAYOUT_OWNERS 43 44# Enterprise policies 45# Updating policy templates can have drastic effects for systems depending 46# on policy definitions (for example, Google's cloud management tools for 47# Chrome and Chrome OS). 48# The rules are documented at: 49# https://sites.google.com/a/chromium.org/dev/developers/how-tos/enterprise/adding-new-policies 50file://components/policy/ENTERPRISE_POLICY_OWNERS 51 52# This restriction is in place due to the policies and compliance regulations around this code. 53file://components/search_engines/COMPLIANCE_OWNERS 54file://components/search_engines/search_engine_choice/COMPLIANCE_OWNERS 55file://chrome/android/java/src/org/chromium/chrome/browser/searchwidget/COMPLIANCE_OWNERS 56 57# Notification channels appear in system UI and are persisted forever by 58# Android, so should not be added or removed lightly, and the proper 59# deprecation and versioning steps must be taken when doing so. 60file://chrome/browser/notifications/android/java/src/org/chromium/chrome/browser/notifications/channels/NOTIFICATION_CHANNEL_OWNERS 61 62# New features for lock/login UI on Chrome OS need to work stably in all corner 63# cases. 64file://ash/login/LOGIN_LOCK_OWNERS 65 66# Changes to the CQ/CI configuration can have a significant impact on infra cost 67# and performance. Approval should be limited to a small subset of the users 68# that can make infra changes. 69file://infra/config/groups/cq-usage/CQ_USAGE_OWNERS 70file://infra/config/groups/sheriff-rotations/CHROMIUM_OWNERS 71 72# Origin Trials owners are responsible for determining trials that need to be 73# completed manually. 74file://third_party/blink/common/origin_trials/OT_OWNERS 75 76# New notifiers added to //ash/constants/notifier_catalogs.h and 77# //ash/constants/quick_settings_catalogs.h should be reviewed 78# by //ash/system owners to ensure that the correct notifier is being used. 79file://ash/system/OWNERS 80 81# WebUI surfaces are user visible and frequently are kept around indefinitely. 82# New WebUI additions should be reviewed by WebUI PLATFORM_OWNERS to ensure 83# they follow the guidance at https://www.chromium.org/developers/webui 84file://ui/webui/PLATFORM_OWNERS 85 86# Core Views framework needs reviews from direct owners. Limits leakage of +1 87# from higher folder owners. 88file://ui/views/VIEWS_OWNERS 89 90# ChromeOS dependencies reviews 91file://chrome/browser/ash/REFACTORING_OWNERS 92