-
Notifications
You must be signed in to change notification settings - Fork 40.9k
emeritus spiffxp and backfill OWNERS #132220
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
emeritus spiffxp and backfill OWNERS #132220
Conversation
spiffxp moved on from the project years ago, he is still missed
To backfill from removing spiffxp. I have been active in Kubernetes testing and conformance related discussions and PRs for 8+ years now and I am a SIG Testing TL. I'd lke to help review these additional directories. I already approve the test/, including nearly all of the e2e tests and images, and the conformance image in particular for many years now.
I'm not sure the one remaining reviewer is active, I am active in code organization and build + test tooling for many years now.
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The 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. |
/lgtm |
LGTM label has been added. Git tree hash: ed1830e82f26de384f7212a4b24b351eab1e3797
|
/remove-sig api-machinery |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: BenTheElder, dims The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Removes a long inactive approver, backfills some current reviewers/approvers in place.
I'm signing up for some reviews, and for the sig-testing specific alias I'm adding the other current testing TLs.
Which issue(s) this PR is related to:
Special notes for your reviewer:
I put more details in the commit messages, but in particular:
... I'm hoping folks are familiar with my participation by now 🙃
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:
/cc @dims
/assign @dims
/sig testing architecture