Last year we implemented changes in AMP’s governance model to encourage a wider variety of voices in the AMP community and to make it more clear how people can have a voice. I’m happy to provide some updates on our progress towards these goals.
AMP’s Technical Steering Committee and Advisory Committee have started meeting
As part of AMP’s new governance model the Technical Steering Committee (TSC) sets AMP’s product and technical direction and the Advisory Committee (AC) provides advice to the TSC. With these two groups we have representatives from nearly 20 companies & open web advocates helping to guide the AMP community towards our vision of “a strong, user-first open web forever.”
The TSC has now had several meetings, covering a range of topics from GitHub repository best practices to what AMP’s first set of Working Groups should be. The AC also had their first meeting where they kicked off a conversation regarding horizontal reviews, a topic on which the TSC has asked for input.
If you have something you’d like to raise with one of these committees, you’ll find out how to do this in their “working mode” documents (TSC, AC).
Working Groups are ready for you to get involved
One of the TSC’s first acts was to establish the initial set of AMP Working Groups (WGs).
Working Groups are where the day-to-day work in AMP gets done. A Working Group is responsible for a certain part of AMP, such as the Stories WG, which is responsible for AMP’s story format.
The Working Groups are intended to make it easier for people to keep track of different parts of AMP and to get involved. To help with this, each Working Group has a GitHub repository that documents how to get updates on the Working Group’s work and how to get involved–from participating in discussions on issues and Slack to contributing bug fixes, features or other improvements.
I encourage you to find the Working Groups responsible for the areas you’re passionate about and to get involved!
We’ve made our process for making changes to AMP more clear
Although we’ve always said we strongly encourage contributions to AMP, we’ve heard it can be challenging to figure out the process for proposing and making changes and even to know where to get help.
Due to this feedback we’ve been working to improve and clarify the process for making changes in AMP, inspired by Chromium’s process for launching features.
Some of the highlights of these updates:
- We’ve made it more clear that small changes are easy to make without a lot of process overhead.
- We’ve added a slightly more formal launch process for significant changes, including the use of Intent-to-implement (I2I) and Intent-to-ship (I2S) issues and a more well-defined way of getting approval for making significant changes.
- We’ve made it easier to find a reviewer who can help you through the process of getting your change built and launched.
With AMP’s new governance model and contribution process updates in place we hope it’s easier than ever for you to stay up-to-date on what’s happening in AMP and to get involved!
Posted by Joey Rozier, AMP Engineering Manager at Google