Skip to content
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

Open
mfahlandt opened this issue Jul 5, 2024 · 9 comments
Open

Steering Spotlight Blog #517

mfahlandt opened this issue Jul 5, 2024 · 9 comments
Assignees

Comments

@mfahlandt
Copy link
Contributor

Steering will be pinged this week

@mfahlandt mfahlandt converted this from a draft issue Jul 5, 2024
@kaslin
Copy link
Contributor

kaslin commented Jul 26, 2024

/assign arpit

@k8s-ci-robot
Copy link
Contributor

@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.

@kaslin
Copy link
Contributor

kaslin commented Jul 26, 2024

/assign @Hii-Arpit

@kaslin
Copy link
Contributor

kaslin commented Aug 2, 2024

Doc to be sent next week.

@kaslin
Copy link
Contributor

kaslin commented Aug 16, 2024

Doc has been sent. Awaiting response.

@kaslin
Copy link
Contributor

kaslin commented Sep 6, 2024

Responses received, some edits by interviewees in progress

@k8s-triage-robot
Copy link

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/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was 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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 5, 2024
@Hii-Arpit
Copy link
Contributor

Working on the 1st draft, will submit this week

@pacoxu
Copy link
Member

pacoxu commented Dec 6, 2024

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In Progress
Development

No branches or pull requests

6 participants