change SIG Cloud Provider from google groups to kubernetes.io

[bridgetkromhout]

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

[mrbobbytables]

/sig contributor-experience
/sig cloud-provider

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

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:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[elmiko]

/remove-lifecycle rotten

@bridgetkromhout do we need to test the new list? not sure where we left off here.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[elmiko]

/remove-lifecycle stale

i wonder if we can close this?

[mrbobbytables]

it does still need to happen, and for pretty much every sig. =/

[elmiko]

thanks @mrbobbytables , i did't see that we still had an item to take care of here.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[elmiko]

kinda lost track of this, @bridgetkromhout do you know what we need to do next?

/remove-lifecycle stale