OWNERS.setnoparent 3.1 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879
  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. # Overall project governance.
  4. file://ENG_REVIEW_OWNERS
  5. # Third-party dependency review, see //docs/adding_to_third_party.md
  6. file://third_party/OWNERS
  7. # Security reviews
  8. file://build/fuchsia/SECURITY_OWNERS
  9. file://chromeos/SECURITY_OWNERS
  10. file://content/browser/SITE_ISOLATION_OWNERS
  11. file://ipc/SECURITY_OWNERS
  12. file://net/base/SECURITY_OWNERS
  13. file://sandbox/linux/OWNERS
  14. file://sandbox/mac/OWNERS
  15. file://sandbox/OWNERS
  16. file://sandbox/win/OWNERS
  17. file://third_party/blink/SECURITY_OWNERS
  18. # Privacy reviews
  19. file://tools/traffic_annotation/summary/TRAFFIC_ANNOTATION_OWNERS
  20. file://tools/metrics/ukm/PRIVACY_OWNERS
  21. file://base/metrics/OWNERS
  22. # Blink API owners are responsible for decisions about what APIs Blink should
  23. # expose to the open web.
  24. file://third_party/blink/API_OWNERS
  25. # third_party/blink/web_tests/VirtualTestSuites need special care.
  26. file://third_party/blink/web_tests/VIRTUAL_OWNERS
  27. # Extension related files.
  28. file://chrome/browser/extensions/component_extensions_allowlist/EXTENSION_ALLOWLIST_OWNERS
  29. file://extensions/common/api/API_OWNERS
  30. # This restriction is in place to avoid accidental addition to our top level
  31. # layout files, such as add duplicated assets, or introducing new colors when
  32. # we don't want them.
  33. file://ui/android/java/res/LAYOUT_OWNERS
  34. # Updating policy_templates.json can have drastic effects for systems depending
  35. # on policy definitions (for example, Google's cloud management tools for
  36. # Chrome and Chrome OS).
  37. # The rules are documented at:
  38. # https://sites.google.com/a/chromium.org/dev/developers/how-tos/enterprise/adding-new-policies
  39. file://components/policy/ENTERPRISE_POLICY_OWNERS
  40. # This restriction is in place due to the complicated compliance regulations
  41. # around this code.
  42. file://chrome/android/java/src/org/chromium/chrome/browser/searchwidget/COMPLIANCE_OWNERS
  43. # Notification channels appear in system UI and are persisted forever by
  44. # Android, so should not be added or removed lightly, and the proper
  45. # deprecation and versioning steps must be taken when doing so.
  46. file://chrome/browser/notifications/android/java/src/org/chromium/chrome/browser/notifications/channels/NOTIFICATION_CHANNEL_OWNERS
  47. # The Weblayer API is supposed to be stable and will be used outside of the
  48. # chromium repository.
  49. file://weblayer/API_OWNERS
  50. # New features for lock/login UI on Chrome OS need to work stably in all corner
  51. # cases.
  52. file://ash/login/LOGIN_LOCK_OWNERS
  53. # Changes to the CQ/CI configuration can have a significant impact on infra cost
  54. # and performance. Approval should be limited to a small subset of the users
  55. # that can make infra changes.
  56. file://infra/config/groups/cq-usage/CQ_USAGE_OWNERS
  57. file://infra/config/groups/sheriff-rotations/CHROMIUM_OWNERS
  58. # Origin Trials owners are responsible for determining trials that need to be
  59. # completed manually.
  60. file://third_party/blink/common/origin_trials/OT_OWNERS
  61. # New notifiers added to //ash/constants/notifier_catalogs.h should be reviewed
  62. # by //ash/system owners to ensure that the correct notifier is being used.
  63. file://ash/system/OWNERS