-
Notifications
You must be signed in to change notification settings - Fork 155
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
Steering Spotlight Blog #517
Comments
/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. In response to this:
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:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
Working on the 1st draft, will submit this week |
/remove-lifecycle stale |
Steering will be pinged this week
The text was updated successfully, but these errors were encountered: