-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
change SIG Cloud Provider from google groups to kubernetes.io #7518
Comments
/sig contributor-experience |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
/remove-lifecycle rotten @bridgetkromhout do we need to test the new list? not sure where we left off here. |
I have edited the sharing on the current agenda doc for Kubernetes SIG Cloud Provider so that the sharing permissions are set up with read for dev@kubernetes.io and write for kubernetes-sig-cloud-provider@googlegroups.com. However, I am given to understand that we will want to migrate this google group to a mailing list at kubernetes.io.
Per @mrbobbytables, we now should migrate that kubernetes-sig-cloud-provider@googlegroups.com list to sig-cloud-provider@kubernetes.io. I would like us to test the migration - thanks!
/cc @elmiko
The text was updated successfully, but these errors were encountered: