The ChromiumOS project has many communication channels. Finding out which one makes sense for your question/issue can be overwhelming.
We strongly discourage e-mailing or messaging specific developers:
- Direct contact does not scale (especially when a developer is contacted by many different groups).
- Most questions tend to be generic and either covered in existing documentation or answerable by the wider team.
- Answers to questions not covered by existing documentation can then be used for reference with others via mailing list archive links (private threads are never archived).
- Questions without an existing answer often solicit input from the team.
If you're a developer who just joined the project, you should make sure to subscribe to at least the chromium-os-dev group. Important project discussions & PSA's are sent here.
While anyone may join these groups and browse their archives, due to spam problems, people who join are initially & automatically moderated. Once their accounts & posts are verified to not be spam related, they are approved to post freely. However this initial moderation step might take some time (especially on nights & weekends), so please be patient when first joining.
- Google Chrome Help Center: Official documentation for Chrome and Chrome OS. Lots of articles for common user questions.
- Chromebook Help Community: All users should start with the official Chromebook Help Community product forums. The number of active, knowledgeable, and helpful people there is quite staggering. Any question related to ChromeOS, Chromebooks, etc... is OK!
- chromium-os-discuss: Group for non-development related questions. There aren't as many people in this group, and responses can take longer. This group was created long before the Chromebook Help Community which is why it still exists.
- chromium-dev: For all Chromium browser development related questions. Any UI you see (including the login screen) is browser code.
- chromium-os-dev: For all OS development related questions. Browser questions should use chromium-dev instead.
- chromium-extensions: For all Chrome Extension & Chrome App related questions. The API layers are all in the browser, so this is a better group to find help than asking the OS developers (who don't write HTML or JS at all).
For more specific developer groups, see this page: https://dev.chromium.org/developers/technical-discussion-groups
Please see the Reporting ChromeOS bugs document for more details. That covers all types of reports: public, private, security, etc...
Please see the Contributing document. It includes tips for finding suitable reviewers.
Keep in mind that the vast majority of questions about the project can be posted to our public discussion groups. The private groups are meant to be used for unreleased projects, sensitive topics, and partner-specific only. We strongly encourage people to try and stick to the public groups whenever possible.
- chops-cros-help: Internal mailing list for infrastructure questions. Any infrastructure related question (Build, Test, CI, Release, etc...) is good here and will be routed appropriately.
- chrome-discuss: Internal mailing list for general Chrome (browser) discussion. More user rather than engineering focused. Sees many questions and bug reports that haven't been formally filed. ChromeOS related topics should be in the next group.
- chromeos-discuss: Internal mailing list for general ChromeOS discussion. More user rather than engineering focused. Sees many questions/bug reports that haven't been formally filed. Chrome (browser) specified topics should be in the previous group.
- chromeos-chatty-eng: Internal mailing list for general engineering questions. While it is a high-volume "chatty" group, the focus is on Chrome OS. Browser topics would be better served on browser-specific groups.
- chromeos-chatty-kernel: Internal mailing list for kernel questions.
- chromeos-chatty-firmware: Internal mailing list for firmware questions.
We don't generally support users trying to run other distros instead of CrOS. Please contact those projects directly for support instead.
Check out the VM/containers document for more details.
Check out the Reporting ChromeOS bugs document. It has a section specifically about filing security sensitive bugs.