This is a pretty good guide to getting started on contributing to Chromium.
I was an external contributor for Chromium for 2 years and it took me a while to figure out some of the procedures and best practices, like building the Release build instead of Debug or changing my GYP defines to using SHARED_LIBRARY -- those tweaks will literally save double digit minutes even on machines with very beefy CPUs.
The only other thing I can think of that I would add to this guide would be to search for "Hotlist:GoodFirstBug" in the issue tracker when trying to get started. Not every bug there is actually easy for a first-timer on the project to tackle, but you can normally find something to dive into and try to fix, even without much knowledge of the codebase.
I overall had a great experience with the project and it really helped me grow as a stronger developer early in my career.
Code Firefox, a series of videos demonstrating how to download the code and build it (which, btw, takes less than ten minutes for a full clean build on my three-year-old MacBook Pro :)
Bugs Ahoy!, a Bugzilla search engine for "good first bugs" with a mentor's contact information, filtered by programming language or feature area matching your interests:
Hello, this is certainly off-topic but I am curious about your username. Is it in reference to Waldorf schools? My daughter just started preschool at one and I'm wondering if "notwaldorf" is a shot at Waldorf schools. As a parent I would obviously love to know about any negative experiences.
"I gave a talk about how to get started contributing to Chromium, but ... my slides by themselves look like cold-medicine induced hallucinations (which, to be fair, they were)."
Is she serious? Hardcore. That stuff will "make pure LSD seem like Ginger Beer..."
I was an external contributor for Chromium for 2 years and it took me a while to figure out some of the procedures and best practices, like building the Release build instead of Debug or changing my GYP defines to using SHARED_LIBRARY -- those tweaks will literally save double digit minutes even on machines with very beefy CPUs.
The only other thing I can think of that I would add to this guide would be to search for "Hotlist:GoodFirstBug" in the issue tracker when trying to get started. Not every bug there is actually easy for a first-timer on the project to tackle, but you can normally find something to dive into and try to fix, even without much knowledge of the codebase.
I overall had a great experience with the project and it really helped me grow as a stronger developer early in my career.