chromium/src
0
Fork 0
Code Activity

Update third party documentation to refer to chrome-atls-discuss@

Browse Source 
This is an internally-public version of chrome-atls@

Change-Id: Ieed4da9b9fb6321485cd38d0d8782cc3032a03c5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4220142
Reviewed-by: Rick Byers <rbyers@chromium.org>
Commit-Queue: Rick Byers <rbyers@chromium.org>
Auto-Submit: John Abd-El-Malek <jam@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1101950}
This commit is contained in:
John Abd-El-Malek
2023-02-07 02:39:11 +00:00
committed by Chromium LUCI CQ
parent 84e981c924
commit f44dc07bda
1 changed files with 2 additions and 2 deletions

4
docs/adding_to_third_party.md

@ -23,7 +23,7 @@ there.
To make sure the inclusion of a new third_party project makes sense for the
Chromium project, you should first obtain
[Chrome ATL](../ATL_OWNERS) approval. Please include the following information in an
email to chrome-atls@google.com:
email to chrome-atls-discuss@google.com:
* Motivation of your project
* Design docs
* Additional checkout size
@ -70,7 +70,7 @@ mitigations).
(memory/crashes/undefined behavior) bugs, when compared to the existing
third-party library and related C++ code required to use the library. We realize
assessing risk is quite complex and very nuanced. If this is the criteria by
which the third-party library is being added, chrome-atls@google.com and
which the third-party library is being added, chrome-atls-discuss@google.com and
chrome-rust@google.com may ask for more data.
Support for third-party libraries written in Rust is in active development. If