org SIG Cloud Provider update

Updated OWNERS_ALIASES in kubernetes/org for https://github.com/kubernetes/community/issues/7865. Updated milestone maintainers team in kubernetes/org.

/sig cloud-provider

May 22 '24 13:05 bridgetkromhout

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: bridgetkromhout Once this PR has been reviewed and has the lgtm label, please assign mrbobbytables for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment

May 22 '24 13:05 k8s-ci-robot

PR needs rebase.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

May 29 '24 17:05 k8s-ci-robot

@bridgetkromhout, could you also review below GH teams for any required changes? Thanks!

https://github.com/kubernetes/org/blob/main/config/kubernetes/sig-cloud-provider/teams.yaml#L102-L108

Jun 04 '24 10:06 Priyankasaggu11929

adding some links to help with info

needed by https://github.com/kubernetes/community/pull/7815

Jul 08 '24 13:07 elmiko

PR needs rebase, as well as updates suggested in https://github.com/kubernetes/org/pull/4964#issuecomment-2147158251

Jul 09 '24 05:07 Priyankasaggu11929

/lifecycle stale

Sep 25 '24 00:09 cblecker

i think we still want to do this, @bridgetkromhout do you have time to pick this back up?

Sep 25 '24 19:09 elmiko

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

This bot triages PRs 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 PR is closed

You can:

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

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

/lifecycle rotten

Oct 25 '24 20:10 k8s-triage-robot

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

This bot triages PRs 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 PR is closed

You can:

Reopen this PR with /reopen
Mark this PR as fresh with /remove-lifecycle rotten
Offer to help out with Issue Triage

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

/close

Nov 24 '24 20:11 k8s-triage-robot

@k8s-triage-robot: Closed this PR.

In response to this:

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

This bot triages PRs 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 PR is closed

You can:

Reopen this PR with /reopen

Mark this PR as fresh with /remove-lifecycle rotten

Offer to help out with Issue Triage

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

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Nov 24 '24 20:11 k8s-ci-robot