[LEVEL CHANGE] HAMi move from Sandbox to Incubation
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Domain
- release
Research direction
Review the project moving levels PR linked in the issue and identify the HAMi entry in Devstats. Update its maturity level from Sandbox to Incubating, then confirm the Devstats change and complete the remaining checklist item.
Written by the indexing model from the issue text.
Description
Project Moving Levels Checklist
This template outlines the administrative steps required when a project moves from one maturity level to another (e.g., Sandbox to Incubating, Incubating to Graduated).
- Project Name: HAMi
- New Maturity Level: Incubating
- Project moving levels PR: https://github.com/cncf/toc/pull/2198
Administrative Checklist
- TOC vote passed https://github.com/cncf/toc/issues/1775
- Moving levels PR merged
- Email Formation team to move the project's level in PCC.
- Ensure the project is in Google Group mailing lists [email protected]
- Update the project's level and maintainer list in the aggregated CNCF maintainer list. https://github.com/cncf/foundation/pull/1446
- Move the project to its new level on the CNCF Landscape. https://github.com/cncf/landscape/pull/4896
- Move the project to the new level in Clomonitor https://github.com/cncf/clomonitor/pull/1915
- Move the project to the new level in Devstats
- Move artwork in cncf/artwork https://github.com/cncf/artwork/pull/665
- Move project in maintainer spreadsheet
- Sent email to CNCF PR team for marketing the change
- Run CNCF Calendar update automation
- Update website footer
- Dominant language
- HTML
- Stars
- 1.9k
- Forks
- 728
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 10
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from cncf/toc
-
fix(generator): correct struct tag for subproject_leads in Leadership structPossibly taken @Tharun-Varshan-S claimed this 2 days ago. Openneeds-group needs-kind needs-triage
Difficulty 1/5 Under an hour Newbie friendliness 25/100
Maintainers usually reply within 1 day
-
kind/review needs-triage review/health toc
Difficulty 5/5 Over a week Newbie friendliness 5/100
Maintainers usually reply within 1 day
-
kind/initiative needs-group needs-triage
Difficulty 5/5 Over a week Newbie friendliness 18/100
Maintainers usually reply within 1 day
-
[Initiative]: Telco AI NativePossibly taken @kashifest claimed this 7 days ago. Openkind/initiative tag/infrastructure triage/valid
Difficulty 5/5 Over a week Newbie friendliness 20/100
cncf/toc#2314 · 14 comments · 2 reactions · 1 assignee ·
Maintainers usually reply within 1 day
-
kind/initiative needs-group needs-triage
Difficulty 5/5 Over a week Newbie friendliness 30/100
Maintainers usually reply within 1 day
Similar issues
-
ci(release): escape workflow commands in check_release_scan_evidence.py's top-level error outputOpenci-cd from-review-extraction python security severity:should-fix
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
LearningCircuit/local-deep-research#7453 ·
Maintainers usually reply within 2 days
-
Dev
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
ankidroid/Anki-Android#22555 ·
Maintainers usually reply within 1 day
-
release
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
area: release lane: free-agent roadmap size: S type: task
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
arminazimi/evergreen#311 ·
Maintainers usually reply within 1 day
-
bug p2 triaged
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
getpaseo/paseo#7032 · 1 comment ·
Maintainers usually reply within 1 day