root: add CRYPTO_OWNERS

Per discussion on chrome-security-leads@, this change centralizes
ownership of cryptographic code in chromium within a single root-level
file. Existing OWNERS files for crypto code are left in place (since
they reflect expertise within specific directories) but //CRYPTO_OWNERS
is added as a fallback owner to all of them.

Bug: None
Change-Id: I069f3c9085219f78504f533e84046aadb01fa11d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5770906
Reviewed-by: Nico Weber <thakis@chromium.org>
Reviewed-by: Adam Langley <agl@chromium.org>
Reviewed-by: Emily Stark <estark@chromium.org>
Commit-Queue: Elly FJ <ellyjones@chromium.org>
Reviewed-by: Andrew Whalley <awhalley@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1341684}

This commit is contained in:

Elly

2024-08-14 15:40:02 +00:00

committed by

Chromium LUCI CQ

parent 1c890d9b6c

commit cf0751e7da

5 changed files with 21 additions and 0 deletions

CRYPTO_OWNERS

components

encrypted_messages

OWNERS

webcrypto

OWNERS

crypto

OWNERS

third_party/boringssl

OWNERS

13

CRYPTO_OWNERS Normal file

 @ -0,0 +1,13 @@
 # People listed in this file are responsible for making decisions about
 # cryptography use in Chromium. If you are adding new cryptographic code, or
 # adding complex uses of existing cryptographic code, please consult one of
 # these people.
 agl@chromium.org
 bbe@chromium.org
 davidben@chromium.org
 ellyjones@chromium.org
 estark@chromium.org
 mattm@chromium.org
 svaldez@chromium.org
 tsepez@chromium.org