New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update METADATA.yaml #64
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@zhouyx for approval.
Co-authored-by: Raghu Simha <rsimha@amp.dev>
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. ℹ️ Googlers: Go here for more info. |
The Google bot is confused by the Github suggestions tool. I'll merge this since I (a Googler with signed CLAs) was the one to merge this suggestion. |
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. ℹ️ Googlers: Go here for more info. |
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. ℹ️ Googlers: Go here for more info. |
@googlebot I fixed it. |
@robinvanopstal Sorry about the CLA noise. We recently switched from Google to OpenJS. If you respond to the last comment and sign the CLA, all your PRs should be in good shape. |
@googlebot I fixed it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for picking this up!
login: nainar | ||
name: Naina Raisinghani | ||
login: zhouyx | ||
name: Yuxuan Zhou |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yuxuan has left the team. The updated membership can be found at https://github.com/ampproject/wg-components.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The facilitator listed for the group at the link above is @micajuine-ho FYI
title: Components | ||
merged: | ||
- ui-and-a11y | ||
description: wg-components Working Group is responsible for AMP components, the overall health of AMP Pages, analytics features, and integrations with partner technologies. For overall accessibility, this group is also the first point of contact, however each WG is responsbile for ensuring accessibility within their areas of responsibility. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
description: wg-components Working Group is responsible for AMP components, the overall health of AMP Pages, analytics features, and integrations with partner technologies. For overall accessibility, this group is also the first point of contact, however each WG is responsbile for ensuring accessibility within their areas of responsibility. | |
description: wg-components Working Group is responsible for AMP components, the overall health of AMP Pages, analytics features, and integrations with partner technologies. |
- item: "UI Working Group will post **Quarterly Roadmap** as an issue labeled with `Type: Roadmap` in this repository." | ||
- item: "Components Working Group will post **Status Updates** every two weeks as an issue labeled with `Type: Status Update` in this repository." | ||
- item: "Components Working Group will post **Announcements and Notices** regarding events as an issue labeled with `Type: Event` in this repository." | ||
- item: "Components Working Group will post **Quarterly Roadmap** as an issue labeled with `Type: Roadmap` in this repository." |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- item: "Components Working Group will post **Quarterly Roadmap** as an issue labeled with `Type: Roadmap` in this repository." | |
- item: "Components Working Group will post **Quarterly Roadmap** as an issue labeled with `Type: Roadmap` in this repository." | |
- item: "Components Working Group will post **Monthly Office Hours** as an issue labeled with `Type: Meeting` in this repository." |
- login: alanorozco | ||
name: Alan Orozco |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please keep Alan here.
name: Daniel Young | ||
- login: joneleven | ||
name: Jonathan Leventhal | ||
- login: micajuine-ho |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- login: micajuine-ho | |
- login: caroqliu | |
name: Caroline Liu | |
- login: dmanek | |
name: Dhruv Manek | |
- login: micajuine-ho |
@micajuine-ho Can you please review/merge when this is ready? Doesn't look like I have the permissions :) |
I don't have write permission either. @kristoferbaxter Can you take a look? |
No description provided.