Skip to content
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

Communication channel between CPC and AMP infra WG #31

Closed
tobie opened this issue Nov 12, 2019 · 12 comments
Closed

Communication channel between CPC and AMP infra WG #31

tobie opened this issue Nov 12, 2019 · 12 comments

Comments

@tobie
Copy link
Contributor

tobie commented Nov 12, 2019

One of the graduation requirements for AMP from the CPC was to draft a clear plan to disentangle the CDN for the AMP runtime from the Google AMP Cache. This is tracked in https://github.com/ampproject/wg-infra/issues/18.

As there are multiple options and open questions, it's important to establish a communication channel between the CPC and the AMP infra WG, so that there's an upfront consensus as to solutions the CPC will find acceptable.

Just tagging people on the GitHub issue doesn't seem sufficient, please advise how we should proceed.

@brianwarner
Copy link

Good point, Tobie. Let's go with a slack channel. I'll set something up.

@danielrozenberg
Copy link

We have the #wg-infra channel in the AMP Slack instance, does that work for you?

@tobie
Copy link
Contributor Author

tobie commented Nov 12, 2019

I want to make sure folks on the CPC (which is a much larger group that operates on a voluntary basis) get easy access to this conversation channel and provide input along the way. The best way to guarantee this is to minimize friction by having that conversation happen on the foundation’s Slack rather than on AMP’s (granted the CPC prefers slack over a mailing list).

@tobie
Copy link
Contributor Author

tobie commented Nov 12, 2019

/cc @bnb, @mhdawson, @evenstensberg, others: what medium would you prefer? mailing list, Slack, or both?

@evenstensberg
Copy link
Member

My take, as mentioned during this week CPC meeting, is that we can have slack to agree on the relevant topic and how we wish to go through with expectations and goals, mainly used for fast-feedback on minor inconveniences or questions and then having a mailing list to discuss, as people are more flexible and efficient when there's a mailing list involved.

In experience, mailing lists work better for this kind of comms

@tobie
Copy link
Contributor Author

tobie commented Nov 13, 2019

Worth nothing that the whole AMP infra WG will be at the Collab Summit in Montreal. Worth organizing a face to face meeting/session then. /cc @rsimha.

@mhdawson
Copy link
Member

I'm +1 on the mailing list supplemented by slack. Also good to take advantage of face to face time in Montreal.

@tobie
Copy link
Contributor Author

tobie commented Nov 13, 2019

Awesome. I'll get an email thread started so folks can share their preferred email for the mailing list and Slack channel invitations.

@brianwarner
Copy link

Thanks @tobie! I'll spin up the mailing list. Anybody who wants to be on the mailing list, send me an email at bwarner@linuxfoundation.org.

@tobie
Copy link
Contributor Author

tobie commented Nov 13, 2019

@brianwarner Thanks! Feel free to close this once folks have been invited to the list.

@joesepi
Copy link
Member

joesepi commented Jan 28, 2020

Made progress at Collab Summit; have issues created and have Slack channel and an email list. @tobie says its cool to close.

Mailing list:
https://lists.openjsf.org/g/amp-onboarding-infrastructure/topics

@joesepi joesepi closed this as completed Jan 28, 2020
@teodora82
Copy link

Nice

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants