[Incubation] HAMi Incubation Application #1775
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.
$PROJECT 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): https://github.com/Project-HAMi/HAMi
Project Site: https://project-hami.io/
Sub-Projects: https://github.com/Project-HAMi/HAMi-core, https://github.com/Project-HAMi/volcano-vgpu-device-plugin, https://github.com/Project-HAMi/HAMi-WebUI
Communication: https://cloud-native.slack.com/archives/C07T10BU4R2
Project points of contacts:
| Full Name | Github | |
|---|---|---|
| LiMengxuan | [email protected] | archlitchi |
| ZhangXiao | [email protected] | wawa0210 |
- (Post Incubation only) Book a meeting with CNCF staff to understand project benefits and event resources.
Incubation Criteria Summary for $PROJECT
Application Level Assertion
- This project is currently Sandbox, accepted on 2024-08-21, 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:
*
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 14-MAY-2024, and can be discovered at https://youtu.be/SwdEoQYkMsE, the corresponding domain specific TAG is TAG-Runtime
- TAG provides insight/recommendation of the project in the context of the landscape
HAMi is adopted in CNCF landscape in
https://landscape.cncf.io/?item=orchestration-management--scheduling-orchestration--hami
- All project metadata and resources are vendor-neutral.
- Review and acknowledgement of expectations for Sandbox projects and requirements for moving forward through the CNCF Maturity levels.
- Met during Project's application on 2025/07/11.
- 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.
This can be seen in project website
Governance and Maintainers
Note: this section may be augmented by the completion of a Governance Review from TAG Contributor Strategy.
Suggested
- Clear and discoverable project governance documentation.
https://github.com/Project-HAMi/community/blob/main/governance.md
- 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.
Yes, we have iterated governance over the last year, the detailed can be seen in the commit history of community repository
here
- Governance is up to date with actual project activities, including any meetings, elections, leadership, or approval processes.
The governance document is here:
https://github.com/Project-HAMi/community/blob/main/governance.md#meetings
The decisions made according to governance is here:
https://github.com/Project-HAMi/community/issues?q=is%3Aissue%20state%3Aclosed
- Governance clearly documents vendor-neutrality of project direction.
- Document how the project makes decisions on leadership, contribution acceptance, requests to the CNCF, and changes to governance or project goals.
The decision on maintainer membership is held by maintainer meeting, meeting notes is listed as follows:
https://docs.google.com/document/d/1mRUhNm3spCdRLcxFBuCYNfwQJqSO9RwXi82IHF6M4Xk/edit?tab=t.0#heading=h.g61sgp7w0d0c
The assignment of reviewer, approver, change to governance, project goals, etc is held in weekly meeting, meeting agenda is shown here:
https://docs.google.com/document/d/1YC6hco03_oXbF9IOUPJ29VWEddmITIKIfSmBX8JtGBw/edit?tab=t.0#heading=h.g61sgp7w0d0c
- Document how role, function-based members, or sub-teams are assigned, onboarded, and removed for specific teams (example: Security Response Committee).
Currently, we don't have other sub-teams except maintainer team, so project maintainers is responsible for all roles of this project and sub-projects.
https://github.com/Project-HAMi/community/blob/main/community-membership.md
- Document a complete maintainer lifecycle process (including roles, onboarding, offboarding, and emeritus status).
https://github.com/Project-HAMi/community/blob/add_sub_projects/community-membership.md#maintainer
- Demonstrate usage of the maintainer lifecycle with outcomes, either through the addition or replacement of maintainers as project events have required.
This can be seen in maintainer group notes:
https://docs.google.com/document/d/1mRUhNm3spCdRLcxFBuCYNfwQJqSO9RwXi82IHF6M4Xk/edit?tab=t.0#heading=h.g61sgp7w0d0c
- If the project has subprojects: subproject leadership, contribution, maturity status documented, including add/remove process.
The subprojects contribution and leadership is shown in community-membership:
Required
- Document complete list of current maintainers, including names, contact information, domain of responsibility, and affiliation.
https://github.com/Project-HAMi/HAMi/blob/master/MAINTAINERS.md
- A number of active maintainers which is appropriate to the size and scope of the project.
https://github.com/Project-HAMi/HAMi/blob/master/MAINTAINERS.md
- Code and Doc ownership in Github and elsewhere matches documented governance roles.
- Document adoption of the CNCF Code of Conduct
https://github.com/Project-HAMi/community/blob/main/CODE-OF-CONDUCT.md
- CNCF Code of Conduct is cross-linked from other governance documents.
- All subprojects, if any, are listed.
https://github.com/Project-HAMi/HAMi-core
https://github.com/Project-HAMi/volcano-vgpu-device-plugin
https://github.com/Project-HAMi/HAMi-WebUI
Contributors and Community
Note: this section may be augmented by the completion of a Governance Review from TAG Contributor Strategy.
Suggested
- Contributor ladder with multiple roles for contributors.
https://github.com/Project-HAMi/community/blob/main/contributing.md
Required
- Clearly defined and discoverable process to submit issues or changes.
https://github.com/Project-HAMi/HAMi/issues/new/choose
- Project must have, and document, at least one public communications channel for users and/or contributors.
yes, we have weekly meeting, and slacks and wechat groups
https://github.com/Project-HAMi/HAMi/blob/master/README.md#meeting--contact
- 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.
2 wechat groups (hami vgpu discussion group 1, members:500), (hami vgpu discussion group 2,members 151)
slack(https://cloud-native.slack.com/archives/C07T10BU4R2)
- Up-to-date public meeting schedulers and/or integration with CNCF calendar.
https://github.com/Project-HAMi/HAMi/blob/master/README.md#meeting--contact
- Documentation of how to contribute, with increasing detail as the project matures.
https://github.com/Project-HAMi/community/blob/main/contributing.md
- Demonstrate contributor activity and recruitment.
Engineering Principles
Suggested
- Roadmap change process is documented.
- History of regular, quality releases.
https://github.com/Project-HAMi/HAMi/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.
- 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.
- 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.
- Document the project's release process.
Security
Note: this section may be augmented by a joint-assessment performed by TAG Security.
Suggested
N/A
Required
- Clearly defined and discoverable process to report security issues.
https://github.com/Project-HAMi/HAMi/security/policy
- Enforcing Access Control Rules to secure the code base against attacks (Example: two factor authentication enforcement, and/or use of ACL tools.)
- Document assignment of security response roles and how reports are handled.
https://github.com/Project-HAMi/HAMi/security/policy
- Document Security Self-Assessment.
- Achieve the Open Source Security Foundation (OpenSSF) Best Practices passing badge.
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://project-hami.io/adopters
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.
Full list of adopters can be found here: https://project-hami.io/adopters
- TOC verification of adopters.
Prepedu: https://www.cncf.io/case-studies/prep-edu/
Daocloud: https://www.cncf.io/case-studies/daocloud/
SF Express: https://www.cncf.io/case-studies/sf-technology/
Nio inc: share their experience with HAMi in KCD HangZhou 2025
Ke Holdings inc: case-study in progress, Adopter Interview Questionnaire submitted
Refer to the Adoption portion of this document.
- Clearly documented integrations and/or compatibility with other CNCF projects as well as non-CNCF projects.
With volcano: https://github.com/volcano-sh/volcano/blob/master/docs/user-guide/how_to_use_gpu_sharing.md
With koorindator: https://koordinator.sh/docs/user-manuals/device-scheduling-gpu-share-with-hami