[Sandbox] OpenEBS - Promotion from Archive -> Sandbox #104
Comments
edrob999
changed the title
edrob999
changed the title
edrob999
changed the title
|
adding prefix [Sandbox] |
edrob999
changed the title
|
Update: Project team presented to Tag Storage today (7/24). |
|
Update2: Since beginning of June, OpenEBS has held weekly maintainer meetings, and minute the meetings, for transparency. Minutes of the weekly meetings are here |
|
@edrob999 Are the meetings recorded? Please link the recording location. |
|
Sorry @angellk - b/c project is in archive, most CNCF project resources were turned off. See Reference. We've got some access, but not Zoom or ability to publish community mtgs on CNCF calendar yet. For now, we're using free Google Meet, no recording capability, we're announcing the community mtgs on Slack. Looking forward to getting full access to the project resources again! |
|
Hi @edrob999 - many open source projects are not part of an official foundation and do record and upload to various channels for community engagement, including google drive or video channels. The free version of Zoom allows local recording to upload anywhere (including YouTube). As your project is applying to be promoted from archive, I was interested to see how community meetings are held, how features are discussed, as well as open discussion around the roadmap. Please update if you are able to record community sessions. |
|
Hi @angellk. If this is "critical" for our sandbox application, let me know - we'll cancel the existing community mtgs and set them up using free Zoom, although recording is limited to 40 mins. I would prefer we set the vid recording up after we've been accepted to Sandbox and have access to the CNCF Zoom. But let me know - we are happy to take guidance, and are making a genuine effort for transparency. Ed |
|
Thank you @edrob999 - having a way for community members to engage with your community meetings would be great - and being able to view the recordings is one way to do that. Please connect with TAG Contributor Strategy - if you have not already done so - for guidance on building your community. Also, please update your README and Community Pages for accuracy and to communicate access to your community meetings. I cannot locate a resource that shows how to join your community meetings live. |
|
@angellk - good points, I'll make the change to ReadMe as you suggest. I need to push back on switching to recorded Zoom for our community meeting this week (DM me if you want to talk thru it), we do understand the importance of the recordings. Following @TheFoxAtWork suggestion, I joined Tag Contributor Strategy(governance) working group about 3 weeks ago, both to help OpenEBS, and to contribute. We did a verbal review with @riaankleinhans, @jberkus, @geekygirldawn. Like all projects we have stuff to work on. Within the project leadership, I have the most interest in governance/contributor strategy.
All of these require work, and I wish progress was faster. Most important for me is to ensure improvements "stick", beyond the tenure of myself + other individuals. I believe our current project governance already compares well against Sandbox projects. But we have more work to do, and I appreciate ongoing guidance and best practices as the project moves forward. Ed |
|
@angellk: We revised the org Readme, so community meetings are easier to find (including the next meeting): The vid from last week's meeting is here: https://www.youtube.com/watch?v=CjjqzrPGxVU The links to the vids, plus minutes from weekly maintainers meetings are all in the openEBS Community repo discussions: |
|
Reviewing the document, fixed some typos. May fix some more |
|
The maintainers asked for some language changes made to the submission tracked in this GitHub issue. |
|
Best of luck with the Sandbox Application, we all see the work you're putting in, and Civo relies on OpenEBS for Civo Platform, used by hundreds of companies |
|
FYI: OpenEBS has been working with TAG-CS on their governance. |
|
In February when CNCF archived OpenEBS, we committed to making changes, and re-applying. This Sandbox application is the first step: we addressed the technical issues and re-worked project governance (including maintainer lifecycle). We put in place transparency: the project is now publishing minutes of regular maintainer meetings, videos of community meetings. If the Sandbox application is approved, the second step comes next: DataCore commits to ensuring OpenEBS becomes a true community project, with a growing contributor base, and a diverse group of maintainers leading the project. We will work with CNCF to make this happen as the project moves towards incubation then graduation. Dave Zabrowski |
|
Microsoft supports the OpenEBS application to Sandbox. Azure Container Storage is based in part on several OpenEBS components. We are talking with the maintainers about how Microsoft can contribute back to the project. |
|
The TAG Storage review is here: https://docs.google.com/document/d/1Biq0gWG8o2npNfjvUiM4WIeFuM9o3I1ZQMDBXz28YAY/edit TAG recommendation to TOC: |
|
Project has been given the okay to move to a vote in today's sandbox review |
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 |
|
As part of my vote in favor of this project I would like to call attention to an important consideration for the project's future success in CNCF: Ed has been instrumental in bringing the OpenEBS project into alignment with CNCF expectations of sandbox projects. He has engaged CNCF staff and several community members on direction and next steps for the project towards potential incubation-level maturity. The project's current efforts have been largely shouldered by Ed and a few others. However as with all concerns regarding projects survivability of the lottery factor, it will be paramount to OpenEBS's continued progress that additional community members of OpenEBS step into active leadership roles for the project to more healthfully distribute those efforts beyond a single individual. |
|
/check-vote |
Vote statusSo far Summary
Binding votes (4)
|
| User | Vote | Timestamp |
|---|---|---|
| tamalsaha | In favor | 2024-10-08 18:01:02.0 +00:00:00 |
| chira001 | In favor | 2024-10-08 18:21:32.0 +00:00:00 |
| avishnu | In favor | 2024-10-08 19:12:31.0 +00:00:00 |
| tiagolobocastro | In favor | 2024-10-08 19:17:33.0 +00:00:00 |
| orville-wright | In favor | 2024-10-08 23:50:51.0 +00:00:00 |
|
/check-vote |
|
Votes can only be checked once a day. |
|
/check-vote |
Vote statusSo far Summary
Binding votes (8)
|
| User | Vote | Timestamp |
|---|---|---|
| tamalsaha | In favor | 2024-10-08 18:01:02.0 +00:00:00 |
| chira001 | In favor | 2024-10-08 18:21:32.0 +00:00:00 |
| avishnu | In favor | 2024-10-08 19:12:31.0 +00:00:00 |
| tiagolobocastro | In favor | 2024-10-08 19:17:33.0 +00:00:00 |
| orville-wright | In favor | 2024-10-08 23:50:51.0 +00:00:00 |
| dsharma-dc | In favor | 2024-10-09 5:41:21.0 +00:00:00 |
| croomes | In favor | 2024-10-09 18:30:34.0 +00:00:00 |
| edreed | In favor | 2024-10-09 18:55:18.0 +00:00:00 |
| Johnaius | In favor | 2024-10-09 19:07:36.0 +00:00:00 |
Vote closedThe vote passed! 🎉
Summary
Binding votes (9)
|
| User | Vote | Timestamp |
|---|---|---|
| @tamalsaha | In favor | 2024-10-08 18:01:02.0 +00:00:00 |
| @chira001 | In favor | 2024-10-08 18:21:32.0 +00:00:00 |
| @avishnu | In favor | 2024-10-08 19:12:31.0 +00:00:00 |
| @tiagolobocastro | In favor | 2024-10-08 19:17:33.0 +00:00:00 |
| @orville-wright | In favor | 2024-10-08 23:50:51.0 +00:00:00 |
| @dsharma-dc | In favor | 2024-10-09 5:41:21.0 +00:00:00 |
| @croomes | In favor | 2024-10-09 18:30:34.0 +00:00:00 |
| @edreed | In favor | 2024-10-09 18:55:18.0 +00:00:00 |
| @Johnaius | In favor | 2024-10-09 19:07:36.0 +00:00:00 |
|
Great! I had a question: What do we do next? Is there something the OpenEBS maintainers could do to help? Sorry if there's some doc I missed. Thanks :). |
|
Congrats on being accepted back into Sandbox from Archived! If you have any questions, please don't hesitate to reach out! |
|
With the onboarding issue created, we can go ahead and close this out. :) |
Application contact emails
[email protected], [email protected], [email protected], [email protected]
Also see OpenEBS project leadership Maintainers team
Project Summary
Cloud native storage
Project Description
OpenEBS was accepted as a Sandbox project in 2019, then moved to archive in Feb 2024. For background on why, see OpenEBS - why we were archived. The project team and sponsoring company have made changes in order to ensure the long term sustainability of OpenEBS. We are asking to unarchive the project, and are challenging ourselves to move forward in the CNCF maturity process.
OpenEBS provides enterprise grade block storage for Kubernetes, enabling persistent resilient cloud native storage (storage is managed-from and contained-within a Kubernetes cluster). OpenEBS is popular, with >25,000 new clusters installed every month.
This is a re-application to Sandbox. Project was archived Feb 2024 after TOC vote on 1051. The team has listened to TOC feedback, has made changes , and is now seeking readmission to Sandbox.
Changes include:
Org repo URL (provide if all repos under the org are in scope of the application)
https://github.com/openebs
Project repo URL in scope of application
https://github.com/openebs/openebs
Additional repos in scope of the application
The new OpenEBS project consists of 5 Storage Engines. The strategy is to eventually unify all 5 into 1 platform. There are sub repos & dependencies, 1 sub project & 1 critical external fork dependency. The team took advice from TOC, and advised community, then deprecated, then moved tech-debt of 44 legacy repos to openebs-archive org based on guidance from @caniszczyk and @castrojo. - Our new repo structure is listed below, with engines listed in order of User Adoption:
Note: SPDK patches are available to the community
Website URL
https://openebs.io
https://openebs.io/docs
Roadmap
https://github.com/openebs/openebs/blob/main/ROADMAP.md
Roadmap context
The new project roadmap & strategy is to eventually unify 5 Storage Engines into 1 single Storage platform. This is a major project change compared to the old roadmap, which did not provide enough attention and focus on the 4 Local PV engines. The team acknowledges this lack of focus which created a stale & disappointed community with low contributions.
The team has defined a VISION doc as part of the new GOVERNANCE structure that supports the roadmap and helps guide the Team, the contributors and the community.
Contributing Guide
https://github.com/openebs/community/blob/develop/CONTRIBUTING.md
Code of Conduct (CoC)
https://github.com/openebs/community/blob/develop/CODE_OF_CONDUCT.md
Adopters
https://github.com/openebs/community/blob/develop/ADOPTERS.md
Contributing or Sponsoring Org
https://www.datacore.com/
Maintainers file
https://github.com/openebs/community/blob/develop/MAINTAINERS
IP Policy
Trademark and accounts
Why CNCF?
OpenEBS was accepted as a Sandbox project in 2019, then moved to archive in Feb 2024.
We have re-examined why we want to continue to contribute to CNCF. Here is why:
source platform.
storage for K8s for a wide range of use cases.
guidance to drive innovation, adoption, and growth.
adopters, together we are innovating and enabling the community for the future.
Benefit to the Landscape
Key benefits of OpenEBS are:
Cloud Native 'Fit'
OpenEBS is cloud native storage which enables K8s stateful apps with persistent block storage.
Cloud Native 'Integration'
Kubernetes
Containerd
KubeVirt
Kubernetes
Etcd
NATS
HELM
gRPC
Jaegar
OpenTelemetry
Prometheus
Open Telemetry
Cloud Native Overlap
Longhorn (storage)
CubeFS (storage)
Rook/Ceph (storage)
Similar projects
Longhorn (storage)
CubeFS (storage)
Rook/Ceph (storage)
Landscape
Cloud Native Storage
Business Product or Service to Project separation
The sponsoring company, DataCore offers premium support services to OpenEBS adopters and production users.
The company plans to release a future offering to provide enhanced enterprise management solutions complementing OpenEBS.
The prior commercial offering “openEBS Pro” had trademark issues with Linux Foundation and has been withdrawn.
Project presentations
Prior to project-archiving, OpenEBS has participated with TAG Storage. The Team met once with TAG Storage post archiving in July 2024.
Project champions
Jorge Castro
Chris Aniszczyk
Additional information
OpenEBS production installations
storage provider.
The Team has accepted the feedback and adopted changes recommended by the TOC in February 2024.
While OpenEBS is in Archive, the users are uncertain of the project’s future, and the future of their own software that depends on OpenEBS.
We request TOC to consider OpenEBS for a promotion to Sandbox, the Team commits to work with CNCF guidance to develop and execute a plan to move the project to its next level.
The text was updated successfully, but these errors were encountered: