-
Notifications
You must be signed in to change notification settings - Fork 5.2k
Move testing-commons subproject to best-effort #5440
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
Move testing-commons subproject to best-effort #5440
Conversation
Move discussion to main sig-testing meeting/channel
61c86a2
to
167ad0c
Compare
/cc @mrbobbytables @coderanger |
done |
/hold cancel I've removed the testing-commons meeting from zoom and sig-testing's calendar |
/lgtm |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/assign @cblecker @nikhita @mrbobbytables @alisondy |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
/hold
for explicit review by slack admins. @mrbobbytables @coderanger can you take a look?
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: nikhita, spiffxp 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 |
/lgtm |
/hold cancel |
Also closed the testing-commons project board: https://github.com/orgs/kubernetes/projects/44 |
After discussion with current testing-commons subproject owners
@alejandrox1 and @andrewsykim we have decided to move the
testing-commons subproject to best-effort.
It is important that we have oversight of kubernetes/kubernetes tests,
but folks now lack the bandwidth to consistently set and drive an agenda
in this area.
Best-effort means we are stopping the testing-commons meeting and
archiving the testing-commons slack channel, and ask those contributors
interested in this topic to bring discussion to the sig-testing meeting
and sig-testing slack channel.
While I was here, I went ahead and moved sig-testing related slack
config into its own directory.
/hold
for lazy consensus, deadline 3pm PT Friday (kubernetes-sig-testing@ thread)
/cc @BenTheElder @stevekuznetsov
for sig-testing approval
/cc @alejandrox1 @andrewsykim
for current subproject owner approval
FYI @kubernetes/steering