Technical Discussion Groups

Feature requests, help/support queries, or other end user questions:

Technical discussion:

The engineering (developer) team uses this to discuss technical issues and for announcements. This is a moderate volume, high technical content mailing list. Topical posts include items such as plans to reduce memory consumption, discussion around how certain code areas are implemented and how to extend or improve such code, announcements of new tests being added to the buildbots, and so forth.

The engineering (developer) team uses this to discuss technical issues related to Chromium accessibility, including compatibility with assistive technology such as screen readers, magnifiers, voice controllers, and more.

Discussion relating to the infrastructure and APIs in chromium that control the exposure of APIs to the web and reports on when and how they are used (Origin trials, UseCounters, Feature Policy, Reporting API, etc.).

The engineering (developer) team uses this to discuss technical issues related to Chromium's graphics stack. This is a low volume, high technical content mailing list covering the Chromium compositor, GPU command buffer stack, and other graphics-related parts of the code.

Discussions related to security engineering and development on Chrome, with a particular focus on security features and designs. Note: this is not a bug announcement list. If that is what your looking for, please see the Chrome Security page for more information on security-notify@chromium.org.

Reviews/Check-ins/bugs

The engineering (developer) team uses this to conduct code reviews of changes to the Chromium source. This is a high volume, high technical content mailing list. Topical posts are strictly limited to code reviews. All email threads on this list originate from code reviews. Please do not start new threads on this list.

This is a read-only list that can be used to monitor individual checkins to the Chromium source. This is a high volume, high technical content mailing list. All emails to this list are automatically generated when code is checked in. Please do not send emails to this list.

The engineering (developer) team uses this to conduct code reviews of changes to the Blink source. This is a high volume, high technical content mailing list. Topical posts are strictly limited to code reviews. All email threads on this list originate from code reviews. Please do not start new threads on this list

Some sublists are:

blink-reviews-paint

blink-reviews-animation

blink-reviews-bindings

blink-reviews-css

blink-reviews-dom

blink-reviews-events

blink-reviews-platform-graphics

blink-reviews-html

blink-reviews-api

blink-reviews-layout

To subscribe to them, edit the URL for blink-reviews to add the suffix.

This is a read-only list that can be used to monitor individual checkins to the Blink rendering engine. This is a high volume, high technical content mailing list. All emails to this list are automatically generated when code is checked in. Please do not send emails to this list.

This is a read-only list that can be used to monitor code reviews related to media in Chromium. This is a high volume, high technical content mailing list. All emails to this list are automatically generated when a media-related code review is updated. Please do not start new threads on this list.

The engineering (developer) team uses this to conduct code reviews fo changes to the V8 source. This is a high volume, high technical content mailing list. Topical posts are strictly limited to code reviews. All email threads on this list originate from code reviews. Please do not start new threads on this list.

There are some mailing lists that are auto-cc'd on certain crbug.com issue categories