Technical Discussion Groups

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

Google Chrome Help Center or Discussion Groups.

Technical discussion:

• chromium-dev
  • 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 builders, and so forth.

Sub Lists:

• android-webview-dev
  • Technical discussions about the Android WebView (src/android_webview).
• animations-dev
  • Technical discussions about animations in blink.
• apps-dev
  • Implementation discussions for the Chrome Packaged Apps platform and APIs.
• attribution-reporting-api-dev
  • A place to discuss implementation questions about the Attribution Reporting API, and to notify developers of upcoming changes.
• bfcache-dev
  • Back-Forward Cache. Speeds up common uses of the 'back' browser button. Implementation status.
• bidi-dev
  • Discussion about the WebDriver BiDi standard and its implementation in Chromium.
• binary-size
  • Discussion about measuring and/or reducing binary size.
• blink-dev
  • List for discussing technical issues related to the Blink rendering engine.
• blink-network-dev
  • Technical discussions about the web platform networking APIs - covering XMLHttpRequest, Fetch API, Streams, WebSocket, etc.
• build
  • Discussion of build-related issues for the Chromium browser
• chromium-accessibility
  • 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.
• chromium-apps
  • This list is for people creating apps for Chromium or Google Chrome. Discussion about upcoming apps APIs and webstore issues also happens here.
• chromium-design-docs
  • List to email and discuss public design docs for the Chromium project. Public design docs should all be sent here.
• chromium-enterprise
  • A place to discuss chromium changes that affect enterprise users, and to notify of upcoming changes
• chromium-extensions
  • This list is for people creating extensions for Chromium or Google Chrome. Discussion about upcoming extension APIs and webstore issues also happens here.
• chromium-mojo
  • Discussion of development and use of Mojo IPC system.
• chromium-polymer
  • List for discussing the use of Polymer in Chromium WebUI and Apps.
• cxx
  • For proposing use of new C++11 language and library features.
• device-dev
  • Device Team communication related to APIs such as Gamepad, NFC, Sensors, Serial, HID, USB, etc.
• devtools-dev
  • Discussion forum for Chrome DevTools.
• dom-dev
  • List for technical discussions related to DOM, HTML, Forms, and the DOM Team.
• ecosystem-infra
  • Discussion for the ecosystem infrastructure team (eg. tooling for web-platform-tests and other cross-cutting issues around interoperability)
• embedder-dev
  • Technical discussions about embedding Chromium and changes in that area.
• experimentation-dev
  • Discussion forum for experimenting with web platform features, specifically Origin Trials.
• feature-control
  • 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.).
• fugu-dev
  • Project Fugu is an effort to close gaps in web's capabilities, enabling new classes of applications to run on the web. See web-capabilities-fugu.
• 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.
• headless-dev
  • Discussions about running Chromium in a headless/server environment.
• infra-dev
  • List for discussing technical issues related to the infrastructure (continuous build, code review, commit queue, etc).
• intervention-dev
  • Discuss user agent interventions.
• input-dev
  • Discussions related to input handling in chromium and blink with a focus on making touch-based interactions on mobile fast, rich and rational.
• layout-dev
  • Discussion forum for the Layout team.
• loading-dev
  • Technical discussions related to the full experience of the initial load of web content (resource fetching/scheduling, parsing, initial layout/paint).
• navigation-dev
  • Technical discussions related to navigation, loading, session history, and similar topics.
• media-dev
  • Technical discussions related to media playback in Chromium covering the media stack, the media experience and media APIs.
• midi-dev
  • Discussions forum for MIDI in Chromium.
• net-dev
  • Technical discussions about networking in Chrome - covering HTTP, SSL/TLS, DNS, TCP - as well as the APIs for networking
• network-service-dev
  • Discussions related to the Network Service effort of servicification.
• offline-dev
  • Technical discussions related to Offline Pages, MHTML, Download Page functionality.
• ozone-dev
  • Technical discussion about ports to different windowing systems, graphics drivers, & input devices.
• paint-dev
  • Discussion forum for the Paint team.
• pepper-dev
  • 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.
• platform-architecture-dev
  • Discussion forum for the Platform Architecture Team.
• platform-predictability
  • Discussion forum for the Web Platform Predictability effort.
• progressive-web-metrics
  • Discussion of creating a modern set of metrics used in all Chrome Speed projects and in all of our Web Developer facing projects.
• project-warden
  • Warden is a project to cleanup and fix long standing issues in order to increase developer productivity. See goo.gl/VEv1YQ
• pwa-dev
  • Technical discussion about features related to progressive web apps.
• python
  • Discussions regarding the Chromium Python style guide.
• rust-dev
  • Discussions about Rust development in Chromium.
• scheduler-dev
  • Discussion about scheduling work (e.g., rendering, input handling tasks) in different parts of Chromium.
• security-dev
  • 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 [email protected].
• services-dev
  • Discussion about servicification effort in Chromium
• site-isolation-dev
  • Discussions related to out-of-process iframes and the general Site Isolation effort to protect web sites from each other using Chrome's sandbox.
• sensors-dev
  • Discussing Generic Sensors and derivative APIs.
• storage-dev
  • List for discussing implementation of web storage technologies: Cookies, IndexedDB, AppCache, FileSystem, Local/Session storage, Quotas, and, yes, WebSQL.
• tast-users
  • Discussion about using the Tast testing framework to write Chrome OS integration tests.
• threaded-rendering-dev
  • Discussion about leveraging threads / asynchrony for a faster web. AnimationWorklet, position:sticky, snap points, metrics, etc.
• web-bluetooth
  • Implementation discussions for Web Bluetooth.
• worker-dev
  • List for discussing implementation of web workers and worklets. See the Worker Team.
• v8-dev
  • List for discussing implementation of the V8 engine.

Reviews/Check-ins/bugs:

• chromium-reviews

  • 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.

• chromium-checkins

  • 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.

• chromium-bugs

  • 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.

• blink-reviews

  • 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.
  • See the WATCHLISTS file for what these lists cover.

• blink-checkins

  • 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.

• feature-media-reviews

  • 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.

• vaapi-reviews

  • Code reviews related to VA API, a video/image encode/decode accelerator API; all email threads on this list originate from code reviews. Please do not start new threads on this list ! :-)

• v8-reviews

  • 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

  • paint-bugs: bugs tracked by the paint team

Other discussion:

• branches
  • Discussions related to branch stabilization and release processes, e.g. milestone branch length, merge and release blocking processes

Note: On 1/21/2010 we switched our mailing lists to be hosted on chromium.org. Posts before that date for the above lists are available at chromium-dev, chromium-reviews, chromium-checkins, chromium-bugs, and chromium-extensions.