You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -74,7 +73,7 @@ This milestone crystallizes the near-term roadmap items into a cohesive theme: e
74
73
75
74
### Community Health
76
75
77
-
-**Adopters program** — Populate ADOPTERS.md with confirmed production users; define maturity tiers (install-mission vs. production deployment)
76
+
-**Adopters program** — Populate ADOPTERS.MD with confirmed production users; define maturity tiers (install-mission vs. production deployment)
78
77
-**Contributor onboarding** — Establish PR triage SLA, define `ai-needs-human` escalation path, and publish contributor guide update; see `docs/plans/PR-TRIAGE-SLA.md`
79
78
-**Adoption metrics** — Replace all `TBD` fields in `docs/adoption-metrics.md` with real measurements before any CNCF application
80
79
@@ -111,7 +110,7 @@ See **v0.4 — AI-Native Observability** milestone above for the full near-term
111
110
112
111
## Mid-Term (Q3–Q4 2026)
113
112
114
-
-**Stellar subsystem GA** — Graduate the Stellar persistent AI runtime from alpha to GA: finalize CRD versioning (v1 stability), complete Mission Operator test coverage, publish upgrade path documentation, and achieve at least one confirmed non-demo deployment. GA criteria tracked in [#17757](https://github.com/kubestellar/console/issues/17757). **Handler-layer test coverage ≥80% on `pkg/api/handlers/stellar/` is an explicit GA gate** — tracked in [#18535](https://github.com/kubestellar/console/issues/18535). Stellar GA is the strategic milestone that moves Console from a dashboard to a production AI operations runtime.
113
+
-**Stellar subsystem GA** — Graduate the Stellar persistent AI runtime from alpha to GA: finalize CRD versioning (v1 stability), complete Mission Operator test coverage, publish upgrade path documentation, and achieve at least one confirmed non-demo deployment. GA criteria tracked in [#17757](https://github.com/kubestellar/console/issues/17757). Stellar GA is the strategic milestone that moves Console from a dashboard to a production AI operations runtime.
115
114
-**GitOps integration milestone** — First-class Flux + Argo CD support with observability parity, declarative Console configuration, and Mission Control deep links; see `docs/plans/GITOPS-INTEGRATION-RFC.md`
116
115
-**Multi-tenant RBAC** — Role-based access control for teams sharing a Console instance, with namespace-scoped permissions
117
116
-**Plugin architecture** — Extensible card and mission system allowing third-party developers to build custom dashboard components; see `docs/plans/PLUGIN-ARCHITECTURE-RFC.md` (RFC to be authored — tracked in [#17760](https://github.com/kubestellar/console/issues/17760))
@@ -157,65 +156,71 @@ We welcome community input on priorities:
157
156
## Strategic Health — June 2026
158
157
159
158
> Status snapshot filed by the strategist agent (ACMM L6). Updated when material risks to roadmap delivery are identified.
160
-
> **Last updated:** 2026-06-16 (pass 13)
161
-
162
-
### Community Momentum — Positive Signals 🌱
163
-
164
-
Three external contributors opened substantial PRs on 2026-06-13. **Two merged on 2026-06-16:**
|#18373|@AdeshDeshmukh| test: missions pure functions unit tests (M) | ⏳ Open — awaiting `/lgtm`|
171
-
172
-
This is the first time two XXL+ external PRs have landed in the same 24-hour window. @bmvinay7's semantic search contribution (`pkg/kb/rag/`) is the most architecturally significant community contribution to date — a production-quality in-process retrieval engine.
173
-
174
-
**Action required:** Review and `/lgtm` PR #18373 (@AdeshDeshmukh) to complete the three-contributor set and reinforce the community flywheel. See [#18534](https://github.com/kubestellar/console/issues/18534).
159
+
> **Last updated:** 2026-06-20 (01:06 AM EDT, pass 15)
| Stellar subsystem — GA criteria partially defined; handler coverage gate now explicit | 🟡 Medium |#17757, #18535| In progress |
190
-
| CNCF incubation tracker on `hold`| 🟡 Medium |#4072| Blocked pending audit + adopters |
191
-
|~~Three community PRs prow-gated on same day~~|~~🔴 Critical~~|~~#18385~~| ✅ Two of three merged 2026-06-16 |
165
+
| Coverage suite 100% collapse — all 12 shards failing for 3+ days; v0.3 "91% coverage" claim unsupportable | 🔴 Critical |#19158#19257| Requires immediate fix; every day deepens v0.3 credibility debt |
166
+
| Feature vacuum: zero open PRs + Q3 starts July 1 (11 days) — v0.4 delivery now critical risk | 🔴 Critical |#19257| v0.4 feature captain needed; llm-d/Drasi/kagent work has not started |
**Human contributor ratio: ~10%** (2 distinct external contributors, 2 PRs of 20 merged in last 10 days). Improved from 0% in prior periods; target is ≥10% sustained.
199
+
198
200
### v0.4 Delivery Prerequisites
199
201
200
202
Before v0.4 ("AI-Native Observability") can ship on-schedule (Q3 2026), ordered by urgency:
201
203
202
-
1.**Enable GitHub branch protection on `main`** (#18355) — [Configure here](https://github.com/kubestellar/console/settings/branch_protection_rules). Require status checks: `build`, `lint`, `go-test`. Policy files in `.github/` are advisory and cannot block merges.
203
-
2.**Merge @AdeshDeshmukh PR #18373** (#18534) — `/lgtm` the final community PR from the June 13 wave. This completes a 3-contributor set and signals the community is welcome.
204
-
3.**File CNCF security audit** (#18207) — Q2 deadline has passed; file at `github.com/cncf/toc/issues` now to secure Q3 slot.
205
-
4.**Triage coverage suite 39% failure rate** (#18533) — The v0.3 "91% coverage" milestone claim requires a stable test infrastructure to be credible.
206
-
5.**Enforce Stellar handler coverage gate** (#18535) — Add `pkg/api/handlers/stellar/` coverage floor to CI before Stellar GA is tagged.
207
-
6.**v0.4 feature kickoff** — Q3 starts July 1 (~15 days). Designate a feature captain; llm-d monitoring (#18031) is Tier 1 per the scoping doc.
204
+
1.**Fix coverage suite** — Assign and resolve #19158 immediately. All 12 test shards have been failing for 3+ days. v0.3's "91% coverage" ROADMAP claim requires a functioning test infrastructure.
205
+
2.**Enable GitHub branch protection on `main`** (#18355) — [Configure here](https://github.com/kubestellar/console/settings/branch_protection_rules). Require status checks: `build`, `lint`, `go-test`. Policy files in `.github/` are advisory and cannot block merges. This is a 5-minute task.
206
+
3.**Designate v0.4 feature captain** (#18974) — Q3 starts July 1 (11 days). Feature work for llm-d, Drasi, and kagent has not started. Without an owner, v0.4 will ship as a scanner/automation release rather than an AI-Native Observability milestone.
207
+
4.**File CNCF security audit** (#18207) — Q2 deadline passed 39 days ago. File at `github.com/cncf/toc/issues`. Three security findings in May (CSP, ValidateKubeContext, SSRF IsMulticast) all now fixed, which strengthens the audit narrative.
208
+
5.**Triage Auto-QA backlog** (#19256) — 4 issues (#18599, #18598, #19077, #19161) need a human decision (accept/defer/close). ~30 minutes total.
209
+
6.**Tag ≥20 issues `good-first-issue`** (#18973 closed, #18785 open) — Hacktoberfest 2026 signups begin September; tagging before Q3 end maximizes project discoverability.
0 commit comments