Parent Issue - Improvements to OpenEBS Project #3701
Comments
|
Thanks for the update @avishnu - Let me know where I can help with any/all updates. - ❤️ 🚀 OpenEBS |
|
An update for everyone: In the Community repository, there are draft documents for Vision, Governance, Contributing. The idea is: these will apply as an umbrella across all projects/repositories in the OpenEBS organization. The stuff we're working on is being tracked in the Community repo Issues |
|
Happy Monday, as announced in #3709, today project team moved 44 repos from the OpenEBS org to OpenEBS-archive org. The archive org is intended to provide as-is snapshots of legacy artifacts, and not for active development. We expect to add more to the archive over time |
|
The last release that included the now-archived-repos was OpenEBS Standard 3.10. We updated the helm charts, so this installation is working OK. See: https://openebs.io/docs/3.10.x/user-guides/installation From OpenEBS 4.0 onwards, these legacy engines and projects will not be not available in the OpenEBS installation. |
|
Update: We moved openebs/charts from openebs-archive to openebs org, because of issues with the helm charts for the archived projects |
|
As I've stated in the CNCF archival issues, I do not think OpenEBS is ready for readmittance any time soon. An organisation making amateuristic mistakes with Helm Charts, causing breakage along their complete userbase, has so much to learn, or needs so much oversight, that it has no place within the CNCF landscape. That is: The consequence of which, imho, should be that OpenEBS should not be readmitted and should only be allowed readmittence when it has proven to show reasonable oversight to prevent these issues in the future. |
|
@Ornias1993 you've posted this on multiple forums. Everyone sees your problem. In the OpenEBS project, we try to be respectful of differing opinions, viewpoints, and experiences. Its OK to criticize the project, but not derogatory comments about the contributors. Again I'm happy to talk it thru. |
I've not "posted it on multiple forums", just here and with the CNCF where it is actually an issue.
Lets turn a valid argument about a specific employee of Mayadata making huge mistakes potentially leading to production downtime multiple times into a "you're mean" issue. Just because the truth is nasty and you don't want to hear it, does not make it less true. I've also tried to stay somewhat polite about it in this discourse, baring my initial statement on one of the first fuckups that it was done "by an intern". If that's what you're refering to: Its a needless distraction from taking accountability to reference comments because they are "not nice" while skirting around the subject at hand
I'll leave it at being a CNCF issue, as I don't see any productive resolution and taking of accountability from MayaData. I've no interest in a "de-escalation talk", I want to see actual steps to ensure these huge fuckups don't happen in the future and taking of responsibility. Which I'm not seeing. If you would actually be interested in that, you would already have publically listed all the steps, procedures and consequences put-in-place to prevent this level of mistakes in the future. Also: all my contact details are public, in case you want to share any of the above steps are taken but cannot due to privacy reasons for the people above/ |
|
Update on governance for the OpenEBS umbrella project: The next community meeting will be Thursday 27 June, then monthly on last-thursday-of-the-month. The material improvements to the OpenEBS project are complete, and the project will start adhering to its governance procedures |
|
In the last few months we've made the following improvements to the project:
There is always more work to do! hopefully everyone appreciates the work so far. Any questions, comments, concerns: please add them into this issue and we will address them |
|
Continuing the improvements: Maintainers voted to archive data populator, because functionality is provided by other community projects. Repo will be archived after three weeks (on or after 10 July) |
|
OpenEBS was accepted into Sandbox last week see: cncf/sandbox#104 @avishnu I recommend we close this issue now |
|
Yes, OpenEBS has been voted in for Sandbox!! Any further improvements will be taken up via separate issues. Closing this now. Thanks to all. |
OpenEBS is the most popular and widely used CNCF Kubernetes storage platform project. More than 700,000 people rely on our project for fast + reliable Kubernetes native storage. OpenEBS has been a CNCF sandbox project since 2019, open source and completely free. DataCore Software sponsors the project and donates significant community resources to the daily engineering of the project via a world-class storage engineering team of 20+ engineers, working together with hundreds of community contributors from across the world.
The CNCF Technical Oversight Committee (TOC) advised the project team to make changes to the project: improve community experience for repo + project structure, ensure documentation is current, improve project governance (see issue #1051). In Feb 2024, CNCF TOC changed the project status to “Archive” and invited our team to implement these changes, then re-apply for promotion to Sandbox.
To TOC and our hundreds-of-thousands of users: thank you for your support. Yes we intend to make these improvements and re-apply to CNCF Sandbox after they are completed. During this process, we will update our community with what we intend to do, and progress against plan.
This is the parent issue for tracking our improvement project. We will post information soon on changes that unify product functionality and project roadmaps.
Finally, if you’re using OpenEBS, and if you’ve had a positive experience, and wish to show your support, please leave a comment below and add yourself to our ADOPTERS.md file.
The text was updated successfully, but these errors were encountered: