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

K8up 2022 Annual Review #1067

Merged
merged 1 commit into from
Jan 2, 2024
Merged

K8up 2022 Annual Review #1067

merged 1 commit into from
Jan 2, 2024

Conversation

tobru
Copy link
Contributor

@tobru tobru commented Jun 1, 2023

This PR adds the annual review for the k8up - A Kubernetes Backup Operator CNCF Sandbox project

Copy link

@Kidswiss Kidswiss left a 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.

reviews/sandbox/2022/2022-k8up-annual.md Show resolved Hide resolved
Signed-off-by: Tobias Brunner <tobias.brunner@vshn.ch>
@tobru tobru changed the title Provide the k8up annual report for 2022 K8up 2022 Annual Review Jun 2, 2023
@tobru tobru marked this pull request as ready for review June 2, 2023 08:33
@tobru tobru requested a review from Kidswiss June 2, 2023 08:34
@sonasingh46
Copy link

sonasingh46 commented Sep 15, 2023

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:

  • Document the community meeting call time, how to join it and record the meetings to be published as e.g. youtube. The meeting should also be added to the CNCF calendar.
  • There should be some medium where async conversations regarding the project and project development can happen e.g. slack. Also, document this so that contributors or users know where to go to ask questions or collaborate in the development of the project.
  • Clarify the maturity of the project e.g. alpha vs beta vs stable or maintenance.
  • CNCF CoC should be added in the repo https://github.com/k8up-io/k8up.
  • Update the maintainers list in a publicly accessible way and also disclose the maintainer affiliation with their company.
  • Update the roadmap to clearly specify the current state of the project and next milestone and goals.

CNCF Sandbox Annual Review Guidline Doc:
https://docs.google.com/document/d/1cE9zutKh3ZGzEzZr5CZ_ck66JJ1J5mLeNYELVLbxf-Q/edit

@tobru
Copy link
Contributor Author

tobru commented Sep 18, 2023

Thanks for the review and feedback, we'll be taking appropriate actions in the next 2–3 months.

@TheFoxAtWork
Copy link
Contributor

@mattfarina & @nikhita as Liaisons for TAG Storage, would you review/approve/merge?

@amye
Copy link
Contributor

amye commented Jan 2, 2024

Marking this as complete, annual reviews are no longer a requirement for sandbox.
We'll be rolling out more efficient ways to show project health and metrics in 2024.

@amye amye merged commit 1b0119a into cncf:main Jan 2, 2024
1 check passed
@tobru
Copy link
Contributor Author

tobru commented Feb 1, 2024

Thank you very much for the review. We've taken the following measures:

Document the community meeting call time, how to join it and record the meetings to be published as e.g. youtube. The meeting should also be added to the CNCF calendar.

This is done in:

Deployed here: https://k8up.io/k8up/about/community.html#_monthly_community_meeting

There should be some medium where async conversations regarding the project and project development can happen e.g. slack. Also, document this so that contributors or users know where to go to ask questions or collaborate in the development of the project.

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

Clarify the maturity of the project e.g. alpha vs beta vs stable or maintenance.

Done in:

Deployed here: https://k8up.io/k8up/index.html

CNCF CoC should be added in the repo https://github.com/k8up-io/k8up.

Done in:

Deployed here: https://k8up.io/k8up/about/code_of_conduct.html

Update the maintainers list in a publicly accessible way and also disclose the maintainer affiliation with their company.

Done in:

Deployed here: https://k8up.io/k8up/about/community.html#_maintainer

Update the roadmap to clearly specify the current state of the project and next milestone and goals.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

None yet

5 participants