[scanner] docs: add ROADMAP.md governance sections#19318
Conversation
|
Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits. 📝 Please follow instructions in the contributing guide to update your commits with the DCO Full details of the Developer Certificate of Origin can be found at developercertificate.org. The list of commits missing DCO signoff:
DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
✅ Deploy Preview for kubestellarconsole canceled.
|
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
👋 Hey @clubanderson — thanks for opening this PR!
This is an automated message. |
|
🐝 Hi @clubanderson! I'm Trusted users — org members and contributors with write access — can mention Automation may take a moment to start, and follow-up happens through workflow activity rather than chat replies. |
There was a problem hiding this comment.
Pull request overview
This PR replaces the placeholder ROADMAP.md with a substantive project roadmap that includes the governance structure required by the Auto-QA governance checks (near-term, mid-term, long-term, and non-goals) and explicitly references 2026 milestones for CNCF compliance readiness.
Changes:
- Adds a structured 2026 roadmap with Near-Term (Q3 2026), Mid-Term (Q4 2026–Q1 2027), Long-Term (2027+), and Non-Goals / Out of Scope sections.
- Introduces additional roadmap context including completed milestones, community input channels, and a strategic health snapshot.
- Notes: build/lint are validated by CI on the PR in this repository.
|
|
||
| ### Community Health | ||
|
|
||
| - **Adopters program** — Populate ADOPTERS.MD with confirmed production users; define maturity tiers (install-mission vs. production deployment) |
|
|
||
| - **Adopters program** — Populate ADOPTERS.MD with confirmed production users; define maturity tiers (install-mission vs. production deployment) | ||
| - **Contributor onboarding** — Establish PR triage SLA, define `ai-needs-human` escalation path, and publish contributor guide update; see `docs/plans/PR-TRIAGE-SLA.md` | ||
| - **Adoption metrics** — Replace all `TBD` fields in `docs/adoption-metrics.md` with real measurements before any CNCF application |
|
Thank you for your contribution! Your PR has been merged. Check out what's new:
Stay connected: Slack #kubestellar-dev | Multi-Cluster Survey |
|
Post-merge build verification passed ✅ Both Go and frontend builds compiled successfully against merge commit |
Restores current strategic health status (overwritten by scanner's governance PR #19318 which reverted to the June 12 snapshot): - v0.4 T-10 days still #1 critical risk - Coverage collapse ✅ resolved Jun 20 - ROADMAP governance sections ✅ added by #19318 - All resolved risks struck through with date/context - Adoption Readiness table fully current Signed-off-by: clubanderson <407614+clubanderson@users.noreply.github.com>
…(restore post-#19318) Restores current strategic health status (overwritten by scanner's governance PR #19318 which reverted to the June 12 snapshot): - v0.4 T-10 days still #1 critical risk - Coverage collapse ✅ resolved Jun 20 - ROADMAP governance sections ✅ added by #19318 - All resolved risks struck through with date/context - Adoption Readiness table fully current Signed-off-by: clubanderson <407614+clubanderson@users.noreply.github.com>
Fixes #19315
Adds standard governance sections required for CNCF compliance:
Ensures 2026 milestones are clearly referenced.