References — bi-14 Contributing to Chromium
Primary sources first. In-tree Chromium docs beat any external source, including these modules.
The process
- Contributing to Chromium — the canonical walkthrough. Note it still contains stale references to
bugs.chromium.org; the tracker is now issues.chromium.org. - Chromium code review — OWNERS,
git cl upload, review etiquette - Contributor License Agreement — required before your first CL lands
- Gerrit — the review system; patchsets, not force-pushes
Finding a first change
- Good First Bugs — curated starter issues
- Chromium Slack / discussion groups —
chromium-devfor design questions, subsystem lists for specifics - A WPT test closing a coverage gap is often more reviewable than a code change, and teaches the same process.
Style and expectations
- C++ style guide
- Commit message conventions
- Chromium security guidelines — especially the Rule of 2
Related modules
- bi-01 — Navigating Chromium
- bi-06 — Chromium C++
- bi-13 — Tests & WPT — every CL needs a test
When a claim here proves stale, record it in PROGRESS.md section 7.