An AMP Working Group is a segment of the community with knowledge/interest in specific area of AMP. Working Groups are created by AMP’s Technical Steering Committee.

Most Working Groups provide ~bi-weekly status updates.

AMP’s Working Groups are:

• AMP4Email.

  • Responsible for the AMP4Email project.
  • Facilitator: @nainar
  • AMP4Email WG Github repo
  • Slack channel: #wg-amp4email

• Approvers.

  • Responsible for approving changes that have a significant impact on AMP's behavior or significant new features as described in the feature and bug fix process.
  • Facilitator: @dvoytenko
  • Approvers WG Github repo

• Code of Conduct.

  • Responsible for enforcing AMP's Code of Conduct. (The Technical Steering Committee delegates its responsibility for enforcement of the Code of Conduct to this Working Group.)
  • Facilitator: @nainar
  • CoC WG Github repo

• Components.

  • Responsible for AMP's visual components, interactions, integrations (including analytics), and AMP's overall accessibility and user experience (including published guidelines for AMP UX). The Components WG also has overall responsibility for ensuring AMP is accessible, though each WG is responsible for ensuring accessibility within their areas of responsibility.
  • Facilitator: @alanorozco
  • Components WG Github repo
  • Slack channel: #wg-components

• Foundation Onboarding.

  • Responsible for ensuring the successful completion of the OpenJS Foundation's onboarding process.
  • Facilitator: @tobie
  • Foundation Onboarding WG Github repo

• Infrastructure.

  • Responsible for AMP's infrastructure, including building, testing and release.
  • Facilitator: @rsimha
  • Infrastructure WG Github repo
  • Slack channel: #wg-infra

• Monetization.

  • Responsible for advertisements and generic subscription integrations in AMP.
  • Facilitator: @powerivq
  • Monetization WG Github repo
  • Slack channel: #wg-monetization

• Outreach.

  • Responsible for helping developers who use AMP remain productive and keeping the AMP community healthy. This includes maintaining and enhancing AMP's developer-facing sites and documentation, maintaining communication channels, organizing community events, etc.
  • Facilitator: @pbakaus
  • Outreach WG Github repo
  • Slack channel: #wg-outreach

• Performance.

  • Responsible for monitoring and improving AMP's load and runtime performance across all formats. Additionally this group is responsible for AMP's core runtime, including layout/rendering and data binding. Lastly, this group evaluates, designs, and implements the architecture in which AMP elements can be used without AMP Runtime.
  • Facilitator: @erwinmombay
  • Performance WG Github repo
  • Slack channel: #wg-performance

• Stories.

  • Responsible for implementing and improving AMP's story format (amp-story).
  • Facilitator: @newmuis
  • Stories WG Github repo
  • Slack channel: #wg-stories

• Validation & Caching.

  • Responsible for AMP's validator and features related to AMP caches.
  • Facilitator: @Gregable
  • Caching WG Github repo
  • Slack channel: #wg-caching

• Viewers.

  • Responsible for ensuring support for AMP viewers and for the amp-viewer project.
  • Facilitator: @enriqe
  • Viewers WG Github repo
  • Slack channel: #wg-viewers