openebs / community Goto Github PK

Author a NEW Governance doc doc for the OpenEBS project that structures the governance system that the new Unified project (5 unified repos) will operate under.

• The current Governance structure was not designed for this new project structure
• Our objective to to achieve a higher quality and more vibrant community focus that meets the CNCF community standard and CNCF governance guidelines.
• We fell out of compliance with our old governance structure, due to the complexity of our project (i.e. too many repos and projects with different governance, contributing guidelines per repo/project). We have now fixed this issue with a SINGLE UNIFIED GOVERNANCE doc for all 5 repos in the Parent OpenEBS project org.

We believe that our new governance structure & system sets the project on a better more balanced governance operating mode.

We need to make a decision on what happening with the new OpenEBS as a new project as we reapply for CNCF for SANBOX.

We need to mentally get beyond the mindset that its just the OLD project getting back into CNCF. I'm not convinced that this is how CNCF TOC will view it. I believe that they will review our application on the merits that its a NEW application.

• Yes there is a complexities to our status and applications...
  • all of our IP and Trademarks and repo have already been transfer into CNCF ownership
  • so technically we are half-way in and half-way out of the door
  • But its unclear if we have any rights to to re-use anything as part of our application... which includes the project logo

Current plan is to edit the main Readme.md doc in the parent repo of each of the main Data-Engines that are targeted to be archived.
Link to the main parent issue and announcement.

For the main OpenEBS Legacy PROJECTs designated to be a Migrated project; we will make an announcement and update the project README.md files that... "this project and all associated sub-repos has been depreciated and migrated out the OpenEBS Parent ORG".

When project team made decision to re-apply to CNCF, we recognized we needed to archive a number of repos, plus revise the project governance for the project. We "turned off" the existing governance procedures, to make these changes.

Turn on governance procedures (after two week comment period)

The new project structure allows for 1 single instance of the Maintainers file that governs the entire project and all sub-projects.
The structure was advised by Jorge Castro (CNCF Developer Relations). It allows the projects maintainer status to remain clean, healthy, clear and very current as there are can be no stale instances of Maintainers files floating around... and there is 1 clear well known location of where to keep the list if Maintainers current.

RawFile LocalPV is a similar but more flexible, yet more complex.. derivation of the LocalPV-Hostpath Data-Engine.

1. RawFile is officially classified by the CNCF project rules as a sub-project within the OpenEBS project.
2. RawFile was conceived, designed and is maintained by a community that operates independently and in concert with the OpenEBS community.
3. OpenEBS and RawFile co-exist in a symbiotic project/product engineering relationship for the benefit of both projects.
4. RawFile is very complimentary to OpenEBS and is designed to integrate tightly with OpenEBS. RawFile provides additional value to OpenEBS, to the community, to OpenEBS users and to CNCF.
5. The current maintainers (at the time that we began the CNCF assisted project restructuring initiative (started on 2 Feb 2024) are:
   Mehran Kholdi
   Kiran Mova

@avishnu had a meeting with Mehran where he acknowledges the following:
Project needs to be more active w.r.t. contributions, he's willing to commit more time to the project.
Project needs a roadmap and he has ideas that he'd like to share with us CI needs to be stabilized

@edrob999
Which REPO are you referring to here?

• OSS ?
• Archive ?

Please provide a detailed description *here...

MAINTAINERS file change vote ‼️

This vote proposes adding 2 new Special Maintainers to the openEBS project.

These candidates are the existing maintainers within the openEBS project's. Local PV RAWFile sub-project and OpenEBS parent project.

1. RAWfile is officially classified by the CNCF project rules as a sub-project within the openEBS project.
2. RAWfile was conceived, designed and is maintained by a community that operates independently and in concert with the openEBS community.
3. openEBS and RAWfile co-exist in a symbiotic project/product engineering relationship for the benefit of both projects.
4. As a sub-project within openEBS, RAWfile cannot exist (by-itself) as an independent member of CNCF, or a CNCF certified project (by itself). RAWfile's membership and status in CNCF and within the CNCF Landscape is inherited from openEBS.
5. RAWfile is very complimentary to openEBS and is designed to integrate tightly with openEBS. RAWfile provides additional value to openEBS, to the community, to openEBS users and to CNCF.
6. The current maintainers (at the time that we began the CNCF assisted project restructuring initiative (started on 2 Feb 2024) are:
   • Mehran Kholdi
   • Kiran Mova

Proposal for vote (RAWfile):

• It is proposed that @kmova and @semekh be added to new openEBS MAINTAINERS file as SPECIAL MAINTAINERS
• In their capacity as SPECIAL MAINTAINERS they will have FULL authority to manage the RAWfile project as MAINTAINERS
• Their MAINTAINER status of the RAWfile project shall be unchanged and EQUAL to what it was prior to the CNCF assisted project restructuring initiative (started on 2 Feb 2024)
• Both maintainers will have FULL authority to Raise and approve PR's against certain repos (as agreed by the openEBS MAINTAINERS)
• While existing as a sub-project with the openEBS parent project; the RAWfile project does not maintain its own separate individual MAINTAINERS file. This is in accordance with the new openEBS structural changes as per CNCF project guidelines.

Note: Since the openEBS project status is Archive, this vote is governed by the new openEBS governance structure (not the Legacy Sandbox governance structure that is no longer is valid).

Vote ‼️

Design the structure of the new OpenEBS OSS project that contains 4 Data-Engines in 1 product.

• LocalPV-Hostpath
• LocalPV-LVM
• LocalPV-ZFS
• Mayastor

Take into account the Helm installation process and user experience for net-new installs as well as migrations from old versions and upgrades..

Author an public announcement that is similar to the main GitHub product restructuring announcement but is targeted top post on Slack. The wording should be simplified and refined with less details. Slack has 1500+ active daily users, and get far more daily exposure so we need to be sensitive with the wording.

Once Reviewed and approved, Publish announcement on SLACK.

The CNCF Sandbox and Incubation application forms are live GitHub Webform.

Sandbox is here: https://github.com/cncf/sandbox/issues/new?assignees=&labels=New&projects=&template=application.yml&title=%5BSandbox%5D+%3CProject+Name%3E?assignees=&labels=New&projects=&template=application.yml&title=%5BSandbox%5D+%3CProject+Name%3E

Incubation is her: (TBD)

We should familiarize ourselves with it and begin preparing & collecting data to fil in each field.

SANDBOX
CNCF TOC provided guidance as to how they will review Sandbox applications.
See it here: https://github.com/cncf/sandbox#how-applications-are-reviewed

The current CNCF Sandbox Application GitHub Project Board is here: https://github.com/orgs/cncf/projects/14

As of today, there are 54 projects in the queue. I have started doing some analysis on them.

11 projects are currently in HOLD status

These projects have been given explicit feedback by TOC as to why they have not been APPROVED

• 5 have been postponed and asked to reapply in 6 ~ 12 months
• 5 have been DECLINED and REJECTED
• 1 has been advised to MERGE with a CNCF project and become a sub-project of the parent
• The above 11 project experienced an average waiting time of 4 months from making the application to getting an Decision

25 new Projects (separate to the ones on HOLD) have passed through the entire process in 2023 / 2024

• 18 have been voted on an APPROVED
• 6 have been DECLINED and/or REJECTED

A single contributing (or contributors) document that applies to all repos in the GitHub openEBS organization

Review all open ISUSES existing across the unified 4 Data-Engines repos

• LocalPV-Hostpath
• LocalPV-LVM
• LocalPV-ZFS
• Mayastor
• LocalPV-Rawfile (still being considered as part of the new OpenEBS core project)

Migrate each issue up to a new location at the parent org.

We need to make a decision on what CNCF Project LEVEL we are going to re-apply at.

Chris Anascsyk has advised us that we can re-apply as either of these, but we MUST meet to criteria.

OpenEBS has centralized project files + policies to openebs/community.

1. Plz remove these files from OpenEBS/OpenEBS (since they are now in community)
   ADOPTERS.MD

2. Plz change GOVERNANCE.md to read:
   For Governance, see OpenEBS Umbrella Governance

3. Plz change CODE_OF_CONDUCT.md to read:
   For code of conduct, see OpenEBS Umbrella Code of Conduct

4. Plz change CONTRIBUTING.md to read:
   To learn about contributing to this repo, see the OpenEBS Umbrella Contributor's Guide

We need to provide Data Migration guidance and support to all community users of all OpenEBS sub-projects that are going to be Archived, EOL & made Read-Only.

We need a table that lists...

• All EOL/Archive Projects by name and repo destination
• Makes a 1 or 2 recommendations
• Provides links to the recommendation project
• Declares how many users will be affected by this action
• In some (hopefully many) cases we will recommend that users migrate to the new OpenEBS Standard (either Replicated or Non-Replicated Data-Engine).

In some cases we will be recommending users migrate to a known CNCF project.
We should calculate how many users (for each recommended project) we are sending their way, and advice those projects. As well as make a PSA announcement on Issue #1051 and Issue #3701 that a cohort of affected OpenEBS new users may be heading in that project's direction.

There are 129 BLOGS docs that exists in the website.

Source location is here: https://github.com/openebs/website/tree/main/website/src/blogs

We need to review every one for...

1. Age
2. relevance
3. usefulness
4. can it be recycled and used in the new site
5. Should we keep it and update it
6. Should it be deleted

Assuming that it will take a minim of 30 mins per doc to review and make a decision (this is reasonable IMHO).

• that's 3,900 mins = 65 hours of work effort

Physically migration all target archive repos our of current openebs org and into the new openebs-archive org.
Currently we have identified 47 repos for archival.

Tag some of the archive repos as ARCHIVE (Read-Only) mode.

orville-wright
on Feb 23 (edited)
Parent issue create and is here: openebs/openebs#3701

RichiH first commenter is here: cncf/toc#1051 (comment)

CNCF Master vote proposal issue is here: cncf/toc#1051

What was posted by @avishnu ...

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 cncf/toc#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.

This task refers to the parent Home Page README file for the new OpenEBS-Archive ORG.

@edrob999 - please add a detailed description here...

• I discovered that I do not understand what the TITLE description is trying to define
• What REPO is this referring to?
• Which README is thig referring to?