In September 2018, Malte Ubl—then AMP’s tech lead—announced a new open governance model for AMP built around a series of working groups and two committees: the Technical Steering Committee (TSC), responsible for the direction of the AMP project and day to day operations, and the Advisory Committee (AC), which provides perspective and advice to the TSC.
An important goal of this governance change was to ensure that the voices of those who do not contribute code to AMP, but are nonetheless impacted by it, get heard. This responsibility is shared across all contributors but falls particularly on the shoulders of the AC, which has a duty to ensure its membership is as representative and diverse as possible.
Despite spanning nine(!) time zones, representing a wide variety of constituencies, and being fairly diverse, the AC’s membership is still predominantly US-based, white, and male. This is one of the main reasons why the AC has decided to expand its membership by about four members and is running a midterm election (terms are a year and are renewable).
All candidates are welcomed and encouraged to apply, but preference will be given to those who bring an underrepresented perspective to the AC and help broaden its horizon.
Financial support for travel expenses is provided to members for whom the position isn’t relevant to their day job, who are self-employed or unemployed, or who are working for structures for which such expenses wouldn’t be possible.
This year’s AMP Contributor Summit will be held October 8-10, 2019 in New York City, and we need your help to help make it happen!
The AMP Contributor Summit is a technical summit for AMP’s open source contributors. At the first AMP Contributor Summit last year more than 80 members of the community got together to meet face-to-face, talk about the latest developments in AMP and discuss where AMP should head into the future. At the end of the summit 100% of those who responded to a post-summit survey said they’d recommend the summit to members of the community.
Starting this year the AMP Contributor Summit will be organized by the community with guidance from the Outreach Working Group. We’re looking for volunteers to help with all of the aspects of planning a successful summit–everything from setting a theme to vetting talks to dealing with schedule logistics.
If you’re excited about bringing the AMP community together and would like to get involved in planning the summit, please let us know by Tuesday, June 11. We’re planning on having an organizational kickoff meeting on June 12 and it would be great to have you there!
If you have any questions, reach out to mrjoro on Slack or GitHub.
For everyone in the community, please save the dates of October 8-10, 2019, and keep an eye out for details on applying to attend the summit soon!
Posted by Joey Rozier, member of AMP’s Outreach Working Group and Engineering Manager at Google
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
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 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.
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
Two key features of AMP’s new governance model are the Technical Steering Committee (TSC) and the Advisory Committee (AC). We have endeavored to ensure that these committees consist of people who bring a wide variety of perspectives, with representatives from different AMP constituencies. The initial membership of these committees is:
Charles Vazac, Akamai
Dane Knecht, Cloudflare
Dave Merrell, The Washington Post
Elisa Budelli, Automattic
Guilherme Souza, Terra
Joe Alicata, Vox Media
Léonie Watson, The Paciello Group
Levi Durfee, Bulldog Creative Services
Nicole Sullivan, Google
Pablo Delgado, El País
Senthil Padmanabhan, eBay
Sumantro Das, 1-800-Flowers.com
Tim Jones, The New York Times
Tobie Langel, CodeSpeaks
Yinhuang Lu, AliExpress
Technical Steering Committee
Chris Papazian, Pinterest
David Strauss, Pantheon
Dima Voytenko, Google
Malte Ubl, Google
Paul Armstrong, Twitter
Rudy Galfi, Google
Saulo Santos, Microsoft
Another key feature of the new governance model is the Working Groups, where most of the day-to-day work in AMP is done. A proposal for the initial set of Working Groups has been made. The Technical Steering Committee (TSC), who is responsible for creating Working Groups, had their founding meeting November 29, 2018 and discussed the proposal as well as made recommendations for additional groups. The initial list will be confirmed in the next TSC meeting in 2 weeks.
I am excited to see AMP entering this next phase, and I am looking forward to working with the entire AMP community towards achieving our vision of a strong, user-first open web forever.
Posted by Malte Ubl, Member of the AMP Project Technical Steering Committee
Over the last 2 years AMP has grown from a tiny open source project with just 2 contributors to a much larger one with over 700 folks contributing over 10,000 commits running on many millions of websites. When choosing a governance model (a system that describes how decisions are made) for AMP, we initially focused on agility. AMP has always been powered by the voices and feedback of the developers and organizations that use it; however, governance was centered around the tech lead (which is me, the author of this post ), who ultimately decided what got executed and how.
While this works great for smaller projects, we’ve found that it doesn’t scale to the size of the AMP Project today. Instead we want to move to a model that explicitly gives a voice to all constituents of the community, including those who cannot contribute code themselves, such as end-users. The change we are proposing is based on months of research, through which we’ve decided to follow the lead of the Node.js project and move to a consensus-seeking governance model.
Encourage a wider variety of voices at all levels of contribution, including code contributions, setting the future direction of AMP and deciding which features and bug fixes should be worked on. This also means ensuring that the voices of those who do not contribute with code, but are nonetheless impacted by AMP, get heard.
Make it more clear how an individual and a company can have a voice in AMP, from approving code changes to setting AMP’s technical and product roadmap.
Avoid slowing down day-to-day work on AMP due to the governance model. The net effect of changes to the way people work on AMP should be neutral to positive in terms of productivity.
Learn from what’s worked and what hasn’t worked for other open source projects. To this end the AMP team talked to people from projects such as Node.js and Kubernetes, looked at governance philosophies from places like the JS Foundation and reviewed a wide variety of other open source and web standards governance documents.
The proposal has full details but some of the significant changes proposed in the new model are:
The power to make significant decisions in the AMP Project will move from a single Tech Lead to a Technical Steering Committee (TSC) which includes representatives from companies that have committed resources to building AMP, with the end goal of not having any company sit on more than a third of the seats.
An Advisory Committee with representation from many of AMP’s constituencies will advise the TSC.
Working Groups with ownership over certain aspects of AMP (such as the UI, infrastructure and documentation) will replace the informal teams that exist today. These Working Groups will have a clear mechanism for input and a well-defined decision making process.
One of our first tasks in working towards the new system is to complete the initial membership of AMP’s governance groups. If you are interested in being involved in any of these governance groups please let us know. This is real work, and we want to pay for it if it isn’t covered by your day job! If you need financial support, please let us know in the form. One area that we are particularly interested in is representation from folks with experience in consumer rights and protection. Meanwhile we’re excited to announce that we’ve talked to a few folks up front and they agreed to join the Advisory Committee including representatives from publishers (El País, Washington Post and Terra), e-commerce sites (AliExpress and eBay) and platforms (Cloudflare and Automattic) as well as advocates for an open web (Léonie Watson of The Paciello Group, Nicole Sullivan of Google/Chrome, and Terence Eden).
Additionally, we’re exploring moving AMP to a foundation in the future, and we’ll seek the input of the TSC, the AC, and the community over the coming months. We see the governance changes as a first step in that direction.
We’re looking forward to working with the rest of the AMP community to refine the governance proposal, including at next week’s AMP Contributor Summit. We encourage you to review and comment on the proposal and attend the design review that has been scheduled to discuss the proposal. The review period for the proposal will end on October 25, 2018 with a goal of implementing the new governance model shortly thereafter.
We’re excited to see the AMP community take this next step, and hope you will join us in making the web a better place for users and developers alike.
Posted by Malte Ubl, Tech Lead for the AMP Project at Google