[Incubation] Cozystack Incubation Application #1916
Description
Review Project Moving Level Evaluation
- I have reviewed the TOC's moving level readiness triage guide, ensured the criteria for my project are met before opening this issue, and understand that unmet criteria will result in the project's application being closed.
Cozystack Incubation Application
v1.6
This template provides the project with a framework to inform the TOC of their conformance to the Incubation Level Criteria.
Project Repo(s): $URL
Project Site: $URL
Sub-Projects:
Communication: CNCF Slack, Kubernetes Slack, Telegram, GitHub Discussions
Project points of contacts:
The Cozystack Maintainers
| Maintainer | GitHub Username | Company | Responsibility |
|---|---|---|---|
| Andrei Kvapil | @kvaps | Ænix | Core Maintainer |
| Timur Tukaev | @tym83 | Ænix | Cozystack Website, Marketing, Community Management |
| Kingdon Barrett | @kingdonb | Urmanac | FluxCD and flux-operator |
- (Post Incubation only) Book a meeting with CNCF staff to understand project benefits and event resources.
Incubation Criteria Summary for Cozystack
Application Level Assertion
- This project is currently Sandbox, accepted on 2025/03/02, and applying to Incubation.
- This project is applying to join the CNCF at the Incubation level.
Adoption Assertion
The project has been adopted by the following organizations in a testing and integration or production capacity:
We know that another 10-15 organizations use it but unfortunately we don't know or cannot mention names.
Application Process Principles
Suggested
N/A
Required
- Engage with the domain specific TAG(s) to increase awareness through a presentation or completing a General Technical Review.
- This was completed and occurred on DD-MMM-YYYY, and can be discovered at $LINK.
- All project metadata and resources are vendor-neutral.
Yes. Cozystack is utilizing CNCF provided vendor neutral resources for communication, testing , hosting and governance and Telegram.
- Review and acknowledgement of expectations for Sandbox projects and requirements for moving forward through the CNCF Maturity levels.
- Met during Project's application on 09-Jan-2025.
- Due Diligence Review.
Completion of this due diligence document, resolution of concerns raised, and presented for public comment satisfies the Due Diligence Review criteria.
-
Additional documentation as appropriate for project type, e.g.: installation documentation, end user documentation, reference implementation and/or code samples.
Governance and Maintainers
Note: this section may be augmented by the completion of a Governance Review from the Project Reviews subproject.
Suggested
-
Governance has continuously been iterated upon by the project as a result of their experience applying it, with the governance history demonstrating evolution of maturity alongside the project's maturity evolution.
-
Cozystack project Governance based on best CNCF Project practices and it's still in the process of improvement. Contributor Roles and contributor ladder will change along with changes in the community and the growth of the project. The Project has currently 12 active maintainers and it has received contributions from 40+ contributors who come from 15+ different companies.
-
Clear and discoverable project governance documentation.
-
Governance is up to date with actual project activities, including any meetings, elections, leadership, or approval processes.
Yes, governance repository is kept up to date according to project activities.
- Governance clearly documents vendor-neutrality of project direction.
- Included in code of conduct
-
Document how the project makes decisions on leadership, contribution acceptance, requests to the CNCF, and changes to governance or project goals.
-
Document how role, function-based members, or sub-teams are assigned, onboarded, and removed for specific teams (example: Security Response Committee).
-
Document a complete maintainer lifecycle process (including roles, onboarding, offboarding, and emeritus status).
-
Demonstrate usage of the maintainer lifecycle with outcomes, either through the addition or replacement of maintainers as project events have required.
- If the project has subprojects: subproject leadership, contribution, maturity status documented, including add/remove process.
NA
Required
- Document complete list of current maintainers, including names, contact information, domain of responsibility, and affiliation.
- A number of active maintainers which is appropriate to the size and scope of the project.
7 active maintainers
- Code and Doc ownership in Github and elsewhere matches documented governance roles.
- Document adoption and adherence to the CNCF Code of Conduct or the project's CoC which is based off the CNCF CoC and not in conflict with it.
- CNCF Code of Conduct is cross-linked from other governance documents.
Yes. https://github.com/cozystack/cozystack/blob/main/GOVERNANCE.md, https://github.com/cozystack/cozystack/blob/main/CONTRIBUTING.md, https://github.com/cozystack/cozystack/blob/main/CONTRIBUTOR_LADDER.md.
-
All subprojects, if any, are listed.
Contributors and Community
Note: this section may be augmented by the completion of a Governance Review from the Project Reviews subproject.
Suggested
- Contributor ladder with multiple roles for contributors.
https://github.com/cozystack/cozystack/blob/main/CONTRIBUTOR_LADDER.md
Required
- Clearly defined and discoverable process to submit issues or changes.
https://github.com/cozystack/cozystack/blob/main/CONTRIBUTING.md
- Project must have, and document, at least one public communications channel for users and/or contributors.
In the end of Readme.md
- List and document all project communication channels, including subprojects (mail list/slack/etc.). List any non-public communications channels and what their special purpose is.
CNCF Slack, Kubernetes Slack, Telegram, GitHub Discussions
-
Up-to-date public meeting schedulers and/or integration with CNCF calendar.
-
Documentation of how to contribute, with increasing detail as the project matures.
https://github.com/cozystack/cozystack/blob/main/CONTRIBUTING.md
- Demonstrate contributor activity and recruitment.
Engineering Principles
Suggested
- Roadmap change process is documented.
- History of regular, quality releases.
Required
- Document project goals and objectives that illustrate the project’s differentiation in the Cloud Native landscape as well as outlines how this project fulfills an outstanding need and/or solves a problem differently. This can also be satisfied by completing a General Technical Review.
- If applicable a General Technical Review was completed/updated on DD-MMM-YYYY, and can be discovered at $LINK.
https://cozystack.io/docs/introduction/
- Document what the project does, and why it does it - including viable cloud native use cases. This can also be satisfied by completing a General Technical Review.
https://cozystack.io/docs/introduction/
- Document and maintain a public roadmap or other forward looking planning document or tracking mechanism.
- Document overview of project architecture and software design that demonstrates viable cloud native use cases, as part of the project's documentation. This can also be satisfied by completing a General Technical Review and capturing the output in the project's documentation.
- If applicable a General Technical Review was completed/updated on DD-MMM-YYYY, and can be discovered at $LINK.
https://cozystack.io/docs/guides/, https://cozystack.io/docs/guides/use-cases/
- Document the project's release process.
https://cozystack.io/docs/operations/cluster/upgrade/
Security
Suggested
N/A
Required
Note: this section may be augmented by a joint-assessment performed by TAG Security and Compliance.
- Clearly defined and discoverable process to report security issues.
Don't have yet, just using general process defined in Contributing.md file.
- Enforcing Access Control Rules to secure the code base against attacks (Example: two factor authentication enforcement, and/or use of ACL tools.)
NA
- Document assignment of security response roles and how reports are handled.
Don't have yet, just using general process defined in Contributing.md file.
- Document Security Self-Assessment.
Don't have yet.
- Achieve the Open Source Security Foundation (OpenSSF) Best Practices passing badge.
https://www.bestpractices.dev/en/projects/10177
Ecosystem
Suggested
N/A
Required
- Publicly documented list of adopters, which may indicate their adoption level (dev/trialing, prod, etc.)
- Used in appropriate capacity by at least 3 independent + indirect/direct adopters, (these are not required to be in the publicly documented list of adopters)
https://github.com/cozystack/cozystack/blob/main/ADOPTERS.md
The project provided the TOC with a list of adopters for verification of use of the project at the level expected, i.e. production use for graduation, dev/test for incubation.
- TOC verification of adopters.
Refer to the Adoption portion of this document.
- Clearly documented integrations and/or compatibility with other CNCF projects as well as non-CNCF projects.
There are a lot of CNCF Projects and cloud native projects in our platform underhood https://cozystack.io/docs/guides/platform-stack/
Additional Information
This project very important for gaining digital sovereignity, migration from public clouds to bare metal and for giving local service providers and integrators open and free tollkit for competing with hyperscalers like AWS, GCP, Azure and giant proprietary platforms like OpenShift.