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

Add Curve 2023 annual review #1144

Merged
merged 1 commit into from
Nov 29, 2023
Merged

Add Curve 2023 annual review #1144

merged 1 commit into from
Nov 29, 2023

Conversation

aspirer
Copy link
Contributor

@aspirer aspirer commented Aug 14, 2023

related to issue: opencurve/curve#2692

Copy link
Contributor

@TheFoxAtWork TheFoxAtWork left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Annual Review Summary
The below is a brief summarization of Curve 2023 Annual Review Evaluation. It contains recommendations the project should strongly consider in order to achieve preparation for Incubation level.

The project scope and goals remain consistent, with community development and growth ongoing. It is worth noting that the bi-weekly meetings repository for the project which is linked throughout the repos appears to have been archived in September with no further record of meetings beyond August. The project appears to have appropriate governance for its maturity level however the maintainer records do not appear up to date across the repositories and docs (likely also the result of this PR also being open for a period of time). It was not discoverable if this project engages in long term planning. While the project uses tags and milestones for tracking versioned releases and development activities towards that, it was not immediately clear what further improvements are planned, and when they are anticipated to occur or initiate. Regarding adoption, it is not immediately clear if adoption is picking up beyond the information provided in this PR.

Recommendations:

  • Adopt the CNCF code of conduct. the project may retain the code of conduct committee they currently have, however Recommend they list the members of the alias in use for reporting to allow reporters peace of mind when submitting reports.
  • Update appropriate repository with meeting notes, information, times, etc. for contributors to discover meetings and review past notes.
  • verify and update the maintainer listings for all repos of the project, as appropriate.
  • develop a roadmap or other long-term planning document that lays out the desired improvements to Curve as it progresses towards Incubation maturity.
  • create an ADOPTERS.md file to track documented adopters of Curve.
  • [edit] Continue efforts to identify contributors interested in moving to maintainership.

@aspirer
Copy link
Contributor Author

aspirer commented Nov 28, 2023

Got it, thanks for the recommendations.

@aspirer
Copy link
Contributor Author

aspirer commented Nov 28, 2023

  • Update appropriate repository with meeting notes, information, times, etc. for contributors to discover meetings and review past notes.
  • We changed the repo for storing documents, meeting notices, meeting minutes, etc. to the curve-book . As you can see, we froze the previous repo curve-meetup-slides. The information in the curve-book will be automatically published to our project website: https://docs.opencurve.io/category/2023
  • We also added a simple migration statement(In Simple Chinese) to the README document of the previous repository.
  • verify and update the maintainer listings for all repos of the project, as appropriate.
  • develop a roadmap or other long-term planning document that lays out the desired improvements to Curve as it progresses towards Incubation maturity.
  • create an ADOPTERS.md file to track documented adopters of Curve.

@TheFoxAtWork TheFoxAtWork merged commit 22701f5 into cncf:main Nov 29, 2023
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.

2 participants