wg-caching Working Group is responsible for AMPHTML's validator and features related to AMPHTML caches.
Facilitator: @gregable
- @amaltas - Amaltas Bohra
- @antiphoton - Boxiao Cao
- @banaag - Allan Banaag
- @gaul - Andrew Gaul
- @georgeluo - George Luo
- @honeybadgerdontcare
- @hiroshimizuno - Hiroshi Mizuno
- @jeffjose - Jeff Jose
- @kumagi - Hiroki Kumazaki
- @gregable - Greg Grothaus (Facilitator)
- @gusmachine - Yu Sugawara
- @michaelrybak - Mike Rybak
- @nhant01 - Nhan Thuan Nguyen
- @tomokinat - Tomoki Nakagawa
- @twifkak - Devin Mullins
- @yuizumi - Yusuke Izumi
- @yunchengz - Yuncheng Zhu
Github team https://github.com/orgs/ampproject/teams/wg-caching also includes UI WG members.
- Caching Working Group members will use
#wg-cachingchannel on AMP's Slack (signup) for real-time discussion. The channel is open to anyone, regardless of membership in UI working group. However, support is better suited to the#caching-discuss,#signed-exchanges, and#validator-discusschannels. - Caching Working Group will post Status Updates every two weeks as an issue labeled with
Type: Status Updatein this repository. - Caching Working Group will post Announcements and Notices regarding events as an issue labeled with
Type: Eventin this repository.
Any bugs or feature requests related to AMP should NOT be filed in this repository and https://github.com/ampproject/amphtml/issues should be used instead.
@ampproject/wg-caching can be used to mention the Caching Working Group in issues and PRs.
The Caching Working Group follows the AMP open source project code of conduct.