Benedikt Meurer
ff321ef155
Bug: 354102605 Change-Id: I8f253844aeae4a386f967140a472f4ee12b666f3 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/5803966 Auto-Submit: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by: Philip Pfaffe <pfaffe@chromium.org> Commit-Queue: Benedikt Meurer <bmeurer@chromium.org>
2.1 KiB
Chromium DevTools Contribution Guide
goo.gle/devtools-contribution-guide
This page assumes a working Chromium DevTools checkout and build.
Legal stuff
All contributors must have valid Gerrit/Google accounts (which means you must be old enough to manage your own account) and complete the contributor license agreement.
For individual contributors, please complete the Individual Contributor License Agreement] online. Corporate contributors must fill out the Corporate Contributor License Agreement and send it to us as described on that page.
First-time contributors
Add your or your organization's name and contact info to the AUTHORS
file for Chromium DevTools. Please include this as part of your first patch and
not as a separate standalone patch.
External contributor checklist for reviewers
Before LGTMing a change from a non-chromium.org address, ensure that the
contribution can be accepted:
- Definition: The "author" is the email address that owns the code review request on https://chromium-review.googlesource.com
- Ensure the author is already listed in the
AUTHORS. In some cases, the author's company might have a wildcard rule (e.g.*@google.com). - If the author or their company is not listed, the CL should include a new
AUTHORSentry.- Ensure the new entry is reviewed by a reviewer who works for Google.
- Contributor License Agreement can be verified by Googlers at http://go/cla.
- If there is a corporate CLA for the author's company, it must list the person explicitly (or the list of authorized contributors must say something like "All employees"). If the author is not on their company's roster, do not accept the change.