Skip to content

Conversation

shyamjvs
Copy link
Member

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

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Feb 18, 2025
@k8s-ci-robot k8s-ci-robot added the sig/scalability Categorizes an issue or PR as relevant to SIG Scalability. label Feb 18, 2025
@shyamjvs shyamjvs force-pushed the update-sig-scale-chairs branch from 0b3b724 to 806844a Compare February 18, 2025 20:47
@shyamjvs
Copy link
Member Author

Think I manually edited an autogen file - fixed it now and verify should pass.

@wojtek-t
Copy link
Member

+1

I'll wait for a week and tag after that.

@mengqiy
Copy link
Member

mengqiy commented Feb 19, 2025

Thanks @shyamjvs for recognition and nomination!

@marseel
Copy link
Member

marseel commented Feb 20, 2025

+1

Thanks @shyamjvs and @mengqiy

@k8s-ci-robot k8s-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 22, 2025
@wojtek-t
Copy link
Member

@shyamjvs - can you please rebase?

@shyamjvs shyamjvs force-pushed the update-sig-scale-chairs branch from 806844a to 843d5ad Compare February 25, 2025 18:40
@k8s-ci-robot k8s-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 25, 2025
@shyamjvs
Copy link
Member Author

Done!

@wojtek-t
Copy link
Member

/lgtm
/approve
/hold cancel

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Feb 26, 2025
@wojtek-t
Copy link
Member

/assign @soltysh

Can you please approve?

@shyamjvs
Copy link
Member Author

shyamjvs commented Mar 3, 2025

In case @soltysh isn't available, @BenTheElder @aojea - could one of you approve instead?

Copy link
Contributor

@soltysh soltysh left a 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:

  1. can you open an issue (there's a Leadership Change template for that), which will help you track all the necessary changes
  2. can you link me a ML thread where this was announced?

/hold
to get these 2 resolved

@k8s-ci-robot k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 4, 2025
@k8s-ci-robot
Copy link
Contributor

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 4, 2025
@shyamjvs shyamjvs mentioned this pull request Mar 5, 2025
17 tasks
@shyamjvs
Copy link
Member Author

shyamjvs commented Mar 5, 2025

Sorry I missed this part of the process. Opened the github issue (will own the tasks there along with @mengqiy) - #8370. We don't have an ML thread (can send one if needed), but we discussed it as part recent SIG meeting on 27th Feb (notes).

@soltysh
Copy link
Contributor

soltysh commented Mar 5, 2025

Sorry I missed this part of the process. Opened the github issue (will own the tasks there along with @mengqiy) - #8370. We don't have an ML thread (can send one if needed), but we discussed it as part recent SIG meeting on 27th Feb (notes).

Thanks for opening that issue 😄
For future, it's good practice to also announce on ML, but since you've announced this during public call and it was broadly aware, I'm ok as is.

/hold cancel

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. sig/scalability Categorizes an issue or PR as relevant to SIG Scalability. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants