Subject: Guidance Needed for Starting Contributions to Chromium
Harsha Guduri
Dear Chromium Team,
I am Harsha and I have got a strong background in C++, Go, Python, debugging workflows and Git development/management, and I am interested in starting to contribute alongside the Chromium team. I built/rebuilt Chromium using `depot_tools` and `GN/Ninja` for building/changing it and at this time, I seek direction on ways to start meaningful contributions.
If you could please provide guidance on;
- What are some recommended beginner-friendly issues for contributors with skills at the systems level (networks, renderers, content layer, build/tooling)?
- What are best practices for working with the codebase, including how to use tools such as: `gn desc`, `Perfetto`, `chrome://tracing`, symbolized builds and sanitizer configurations (`ASan`/`UBSan`/`Tsan`)?
- Tips for creating clean and ready-for-review CLs and to use the `Gerrit`+`CQ` process appropriately.
- If you could relay any information about other communication channels (e.g., corresponding chats for active contributors, live discussion groups, community `Discord`/`Slack` channels, internal mentoring programs) that typically exist between new contributors and maintainers or technical questions.
I would greatly appreciate any direction or next steps you could recommend.
Thank you,
Harsha
Sidhin Thomas
There is a GoodFirstBug hotlist to get started - https://issues.chromium.org/hotlists/5483263
--
--
Chromium Discussion mailing list: chromium...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-discuss
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-discu...@chromium.org.