-
Notifications
You must be signed in to change notification settings - Fork 633
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
Health of VS Code Kubernetes Tools #1241
Comments
Thanks @caniszczyk . Let's try to get a response by March 1st 2024. CC @bnookala , @lstocchi , @itowlson |
Kia ora @TheFoxAtWork - sorry, I'm no longer involved with this project. cc @Tatsinnit who I believe is working on the extension. |
yup, I'm also here along with Tats. I had thought we'd completed the onboarding process, but I can help finish that up. This extension is widely used as a dependency for other K8s-related extensions. |
@squillace and @Tatsinnit, thanks for the update. Please work with CNCF staff to resolve outstanding onboarding items. @krook when onboarding is complete can you follow up here so we may close this issue? |
Will do! |
@krook is onboarding complete? |
Not yet, there are a few tasks outstanding, two of which staff has been working on this week (Insights onboarding and closing on the trademark transfer). For the others, I'll bump the onboarding issue. |
An update, @squillace has met with the development team to understand the remaining open items on the onboarding checklist. We will sit down at KubeCon to work through and close out the final items here on site. |
The TOC determined that the VS Code Kubernetes Tools project's health is currently unknown and isn't fully onboarded. This issue is created to track the Roadmap request to bring the project back into alignment with expectations of sandbox projects.
cncf/sandbox#181
The text was updated successfully, but these errors were encountered: