-
Notifications
You must be signed in to change notification settings - Fork 637
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]: Skooner project #1315
Comments
Requested an update from project maintainers both in the repo and via email. The project appears to no longer be supported by the current maintainer list. |
Requested public confirmation to move to TOC vote to archive. Maintainer confirmed privately. xref: skooner-k8s/skooner#460 |
Per skooner-k8s/skooner#460 can move to a vote to archive. cc: @jeefy @mrbobbytables |
/vote |
Vote created@mrbobbytables has called for a vote on The members of the following teams have binding votes:
Non-binding votes are also appreciated as a sign of support! How to voteYou can cast your vote by reacting to
Please note that voting for multiple options is not allowed and those votes won't be counted. The vote will be open for |
/check-vote |
Vote statusSo far Summary
Binding votes (7)
|
Vote closedThe vote passed! 🎉
Summary
Binding votes (8)
|
closing as the vote passed and archive issue created |
Project name
Skooner
Concern
It would appear the Skooner project may be abandoned, or at least the current maintainers are unable to devote any time to the project.
Dependabot PRs have had failing CI for over a year. There hasn't been much response to new PRs or Issues filed. There was some concern raised in the past that did get some response, but the situation seems to have gotten worse since then.
Looking at the Devstats for the project, most maintainers were from Indeed. They went through a massive layoff in 2023 that, if I remember right, heavily impacted their folks working in open source. Sadly, this could be the cause for the lack of activity.
Prior engagement
Not to my knowledge.
Additional Information
No response
The text was updated successfully, but these errors were encountered: