ROS 2 Grow with evidence, not with hype
Once the lab has something verified to show, this phase shares it, listens to what real people run into, and fixes the friction they report. Growth here means more people reaching a working first run, not a bigger number on a badge.
A loop, not a launch
Publishing is where the loop starts, not where it ends. Each lap uses what people actually report, and the roadmap plans to repeat it every quarter.
Publish, listen, fix, measure
Illustration · sequence onlyThe marker shows order only. It does not show that a video, post or review exists yet.
The two issues in this phase
#21 Demo, articles and community ↗
Publish a demonstration video and two technical posts, and seek ROS and Kubernetes educator reviews. Then triage new issues and improve installation using actual user reports.
Completion gate: useful technical content and documented engagement metrics.
#22 Naming, links and redirects ↗
The repository now lives at ros2-kubernetes-lab. The issue stays open until old and new links, citations, badges, docs and packages are audited and the redirects are verified.
Completion gate: old and new links, citations, badges, docs and packages audited.
How the lab will measure
The table copies the roadmap's own wording (section 7). "Not measured" means exactly that: the lab has no number yet, and none is shown here. Targets are planning goals, not predictions.
| Measure | Status today | Review | Target |
|---|---|---|---|
| Stars | 6 on 2026-10-10 | Monthly | 25 / 75 / 150 / 300, and an aspiration of 600 |
| Successful fresh-install validations | Not measured | Per release | At least one verified supported path before launch |
| Verified cross-node ROS messages | Not measured on the current checkout | Per pull request or release | A repeatable PASS on the supported profile |
| GitHub unique visitors and clones | Needs Insights access | Monthly | Record a baseline, then improve |
| External contributors | Not assessed | Monthly | Record a baseline and welcome the first outside pull request |
| Search impressions and documentation visits | No docs analytics baseline | Monthly after launch | Record, then improve |
| Reproduced benchmark experiments | Modern validated runs not assessed Historical artifacts exist | Per release | Three independently repeatable cases |
The one dated baseline
Audited on 10 October 2026: 6 stars, 2 forks, 0 releases. Source: docs/ROADMAP-2026.md, section 7. These are not current counts.
Stars are an imperfect signal
A star does not show that anyone ran the lab. The roadmap treats successful first runs, outside contributors, documented reuse and reproducible results as better signs, and says to measure feedback quality too. Stars are never incentivised.
How to help
- Pick a small task and comment that you would like to work on it.
- When a supported quickstart exists, try it and report exactly where it failed or confused you.
- If you teach ROS 2 or Kubernetes, review a tutorial and tell us what a student would stumble on.
- Fixing a broken link or an unclear sentence counts as a real contribution.
Start with a good first issue
Documentation and static-check tasks do not need a 30 GB Vagrant cluster.