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

remove Jason Detiberus from capi ilsts #7661

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

cprivitere
Copy link
Member

Remove Jason Detiberus's emails from the various CAPI related email lists here.

Jason retired from CAPI a couple years ago. Also, the @equinix.com address is no longer valid.

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Jan 7, 2025
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: cprivitere
Once this PR has been reviewed and has the lgtm label, please assign neolit123 for approval. For more information see the 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:

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

@k8s-ci-robot k8s-ci-robot added area/access Define who has access to what via IAM bindings, role bindings, policy, etc. area/groups Google Groups management, code in groups/ sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra. labels Jan 7, 2025
@fabriziopandini
Copy link
Member

cc @detiber

No strong opinions from me, but we usually let folks to self remove from those lists (might be they still want to receive those emails)

@blind3dd
Copy link

blind3dd commented Jan 8, 2025

Perhaps it's worth defining a process that would automatically create those kind of PRs after coming up with dedicated logic, maybe emailing that person first to make sure they're still interested as they may come back at certain point, and if there is no answer for more than xyz, than perhaps this kind of PRs should be automatically open for review.

Copy link
Member Author

@cprivitere cprivitere left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, not trying to kick @detiber off any lists, was just tidying up while I was in these files. Happy to cancel the PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/access Define who has access to what via IAM bindings, role bindings, policy, etc. area/groups Google Groups management, code in groups/ cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants