chromium/src
0
Fork 0
Code Activity

Update adding_to_third_party to add explicit link to Chrome Eng Review

Browse Source 
Change-Id: I567141992ec4a9269068c03a1798f2561dba24f6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1879946
Commit-Queue: Tim van der Lippe <tvanderlippe@chromium.org>
Auto-Submit: Tim van der Lippe <tvanderlippe@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#709859}
This commit is contained in:
Tim van der Lippe
2019-10-28 12:21:04 +00:00
committed by Commit Bot
parent 339c7f0bd5
commit 8c749839f6
1 changed files with 2 additions and 0 deletions

2
docs/adding_to_third_party.md

@ -143,6 +143,8 @@ following sign-offs. Some of these are accessible to Googlers only.
Non-Googlers can email one of the people in
[//third_party/OWNERS](../third_party/OWNERS) for help.
* Make sure you have the approval from Chrome Eng Review as mentioned
[above](#before-you-start).
* Get security@chromium.org approval. Email the list with relevant details and
a link to the CL. Third party code is a hot spot for security vulnerabilities.
When adding a new package that could potentially carry security risk, make