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
amp-ac channel in amphtml.slack.com workspace #16
Comments
cc @ampproject/ac |
I don't know what the practice is, here, but we probably want to keep it open, as I suspect the WG have theirs. Let's just check with @mrjoro what the practice is here, and follow along (including for naming consistency). |
I invited everyone. |
The Working Group channels are open so that people who are interested can follow along/participate. We looked into whether we could have "anyone can view, only members can post" channels, but it appears that Slack doesn't support that. |
@mrjoro any thoughts on channel naming for consistency purposes? |
I don't think there's a pattern for non-wg channels. amp-ac sounds fine to me. |
I went ahead and created #amp-ac |
Thanks, @levidurfee. Can you announce it on the mailing list, please? |
I suggest we start a private channel (#amp-ac) in the amphtml.slack.com workspace. Any thoughts on that one way or another?
(If you need an invite to that workspace, it looks like I have (everyone has?) privileges to do so, let me know)
The text was updated successfully, but these errors were encountered: