-
Notifications
You must be signed in to change notification settings - Fork 634
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
K8up 2022 Annual Review #1067
K8up 2022 Annual Review #1067
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good so far. I've just added one goal I personally think would really help with K8up's adoption.
As K8up is already pretty old in terms of operators it really doesn't align very well with how modern operators are expected to be configured and worked with.
Signed-off-by: Tobias Brunner <tobias.brunner@vshn.ch>
Hello people, following is the recommendation from tag-storage after the review of the project. This is a light weight and first annual review of the K8up project and it can continue to be the part of CNCF sandbox group. The project seems to be active and have adopters though there are items flagged in this document that require immediate attention. Following are some suggested remediations that should be taken. Maintainers should reach out to TAG storage within 6 months to present an update on the remediations taken:
CNCF Sandbox Annual Review Guidline Doc: |
Thanks for the review and feedback, we'll be taking appropriate actions in the next 2–3 months. |
@mattfarina & @nikhita as Liaisons for TAG Storage, would you review/approve/merge? |
Marking this as complete, annual reviews are no longer a requirement for sandbox. |
Thank you very much for the review. We've taken the following measures:
This is done in: Deployed here: https://k8up.io/k8up/about/community.html#_monthly_community_meeting
We had that before (not Slack), but it might not have been very discoverable. As a measure, we switched to Slack and documented that here: Deployed here: https://k8up.io/k8up/about/community.html
Done in: Deployed here: https://k8up.io/k8up/index.html
Done in: Deployed here: https://k8up.io/k8up/about/code_of_conduct.html
Done in: Deployed here: https://k8up.io/k8up/about/community.html#_maintainer
We'll do that progressively during the upcoming community meetings. The link to the roadmap is in the README, as well as here: https://k8up.io/k8up/about/roadmap.html |
This PR adds the annual review for the k8up - A Kubernetes Backup Operator CNCF Sandbox project