We use the following groups for high technical content discussions about implementation details within Chromium. The intended audience is engineers contributing code to Chromium.
These groups are not the right place to post feature requests, help/support queries, or other end user questions!
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 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.
This is a read-only list that contains all of the bug database email traffic. All email threads originate from bugs opened in the bug database. Please do not create new threads on this list.
This list is for people creating extensions for Chromium or Google Chrome. Discussion about upcoming extension APIs and webstore issues also happens here.
This list is for people creating apps for Chromium or Google Chrome. Discussion about upcoming apps APIs and webstore issues also happens here.
graphics-dev
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.
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.
List for discussing technical issues related to the Pepper APIs in Chromium, including proposals for new APIs, changes to existing APIs and discussion around the implementation of APIs in the browser.
List for discussing technical issues related to the Blink rendering engine.
List for discussing implementation of web storage technologies: Cookies, IndexedDB, AppCache, FileSystem, Local/Session storage, Quotas, and, yes, WebSQL.
