[HEALTH]: Oxia - Onboarding Deadline Approaching (10+ Months)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Quiet
- Domain
- documentation
Research direction
Start with the linked onboarding issue #408 and review the remaining checklist items and recent maintainer updates. Follow the listed CNCF next steps to identify blockers and support needs; done means the onboarding status, maintainer response, and TOC decision are recorded.
Written by the indexing model from the issue text.
Description
Purpose of This Issue
This Project Health Issue has been filed to ascertain the current activity and health of the project so the TOC may identify the appropriate support and guidance for the project to return to an optimal state of health or determination of archival.
It is intended to initiate a public discussion to seek understanding and define a path forward. Perceptions or commentary counter to this are not constructive for the project or the community.
Should maintainers have sensitive, confidential, or private factors and concerns that influence or affect the project, they are encouraged to contact the TOC or TOC Staff directly via Slack, or email.
Project name
Oxia
Project On-boarding issue
https://github.com/cncf/sandbox/issues/408
Concern
This sandbox project has been in the onboarding process for 10+ months and is approaching the automatic archival deadline. The project has not completed the required onboarding tasks within the expected timeframe.
Potential Indicators:
- Lack of active maintainer engagement
- Insufficient resources to complete onboarding requirements
- Project may no longer be actively maintained
- Need for additional support or guidance from CNCF staff
Timeline:
- Current Status: 10+ months in onboarding process
- Archival Deadline: 12 months from onboarding issue creation
- Time Remaining: ~2 month(s)
Onboarding Issue: #408
Automated Detection: This health issue was automatically created by the CNCF onboarding progress monitoring system when the project reached the 10-month milestone, as part of proactive intervention before automatic archival.
Recent Activity:
Please review the onboarding issue for the current status of completion checklist items and any recent maintainer updates.
Prior engagement
This is an automated health check triggered by the onboarding progress monitoring system.
Prior to this health issue:
- 3 months: Automated reminder with
onboarding/incompletelabel - 6 months: Automated alert with
onboarding/stalelabel + TOC/projects team notification - 9 months: Automated warning with
onboarding/warninglabel + TOC/projects team notification - 10 months: This health issue created with
onboarding/approaching-archivallabel
No direct TOC engagement has been initiated for this specific onboarding delay beyond automated monitoring.
Additional Information
About the Automated Monitor:
The CNCF onboarding progress monitor automatically tracks sandbox project onboarding progress and creates health issues for projects that have been in the onboarding process for 10+ months. This ensures timely TOC awareness and intervention opportunity before automatic archival occurs at the 12-month mark.
Suggested Next Steps for TOC:
- Review the onboarding issue to assess current completion status
- Contact project maintainers to understand any blockers or challenges
- Determine if the project requires additional CNCF staff support
- Evaluate if a deadline extension is warranted based on circumstances
- Provide specific guidance for completing remaining onboarding tasks
- Assess project's continued alignment with sandbox requirements
Automated Actions Already Taken:
- Progressive labels applied at 3, 6, 9, and 10-month milestones
- Automated comments with reminders at each milestone
- TOC/projects team tagged at 6 and 9-month marks
- Weekly warnings scheduled to begin at 11 months
- Daily warnings scheduled for the final week before archival
If No Action Taken:
- 11 months: Weekly warnings will be posted (weeks 1-3), then daily warnings (week 4)
- 12 months: Project will be automatically archived, onboarding issue closed, and this health issue updated
This health issue was automatically created by the CNCF Sandbox Onboarding Progress Monitor. For questions about this automation, please contact CNCF staff or open an issue in the sandbox repository.
- Dominant language
- HTML
- Stars
- 1.9k
- Forks
- 730
- Avg merge
- 5h 5m
- Merged PRs (30d)
- 9
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 9 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 tag/infrastructure 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 14 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
-
Difficulty 1/5 1-3 hours Newbie friendliness 82/100
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 76/100
logto-io/logto#9837 · 1 comment ·
Maintainers usually reply within 1 day
-
area:docs area:i18n documentation priority:low size:S
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
[GOOD FIRST ISSUE] Add Scaladoc to Llm4sHttpClient's request methods and the HttpResponse extensionsOpendocumentation good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
area:integration enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 74/100