contributor-site
contributor-site copied to clipboard
Steering Spotlight Blog
Steering will be pinged this week
/assign arpit
@kaslin: GitHub didn't allow me to assign the following users: arpit.
Note that only kubernetes members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. For more information please see the contributor guide
In response to this:
/assign arpit
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.
/assign @Hii-Arpit
Doc to be sent next week.
Doc has been sent. Awaiting response.
Responses received, some edits by interviewees in progress
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle stale - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
Working on the 1st draft, will submit this week
/remove-lifecycle stale
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle stale - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
as @kaslin moved this from In Progress to Ready for Review in SIG Contribex Comms Status.
@Hii-Arpit can you add a comment here with the updated status of this one?
@Hii-Arpit you started to give an update in the comms meeting, but there were signal issues. Could you update here?
@Hii-Arpit is there a PR for this?
I have shared the final draft with @fsmunoz, I think he will be raiding a PR soon.
@fsmunoz @Hii-Arpit any updates on this?
#589 is the PR for this. Currently in review.
#589 is the PR for this. Currently in review.
https://www.kubernetes.dev/blog/2025/09/22/k8s-steering-spotlight-2025/ wss published. Thanks, everyone.
/close
@pacoxu: Closing this issue.
In response to this:
#589 is the PR for this. Currently in review.
https://www.kubernetes.dev/blog/2025/09/22/k8s-steering-spotlight-2025/ wss published. Thanks, everyone.
/close
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.