-
Notifications
You must be signed in to change notification settings - Fork 5.3k
SIG scalability leadership change #8343
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
SIG scalability leadership change #8343
Conversation
0b3b724
to
806844a
Compare
Think I manually edited an autogen file - fixed it now and verify should pass. |
+1 I'll wait for a week and tag after that. |
Thanks @shyamjvs for recognition and nomination! |
@shyamjvs - can you please rebase? |
806844a
to
843d5ad
Compare
Done! |
/lgtm |
/assign @soltysh Can you please approve? |
In case @soltysh isn't available, @BenTheElder @aojea - could one of you approve instead? |
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.
In case @soltysh isn't available, @BenTheElder @aojea - could one of you approve instead?
I'm back so
/approve
but I have 2 questions:
- can you open an issue (there's a
Leadership Change
template for that), which will help you track all the necessary changes - can you link me a ML thread where this was announced?
/hold
to get these 2 resolved
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: shyamjvs, soltysh, wojtek-t 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 |
Thanks for opening that issue 😄 /hold cancel |
Following up on earlier conversation with other leads, I'm nominating @mengqiy as the new SIG co-chair in my stead as I step to SIG lead role. David has been instrumental in making several improvements to our testbed and is actively helping triage issues with scalability job health. He's also a regular participant in our bi-weekly community meetings and brings up interesting issues for discussion (xref).
/cc @wojtek-t @marseel - I'll wait for your consensus