feat: ngi_roadmap

[JarbasAl]

Summary by CodeRabbit

• Documentation
  • Published the OpenVoiceOS 2026 roadmap blog post detailing planned releases, architectural enhancements, ecosystem expansions, and upcoming improvements across core functionality, language support, and user interface capabilities.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

📝 Walkthrough

Walkthrough

A new blog post detailing the OpenVoiceOS 2026 roadmap is added, covering release strategy, key technical initiatives including modular core architecture, LLM integration, plugin abstraction, GUI improvements, and dataset expansion, with emphasis on privacy-first, open-source principles and community engagement.

Changes

Cohort / File(s)	Summary
Blog Post Addition _posts/2026-01-10-ngi_roadmap.md	New markdown blog post documenting OpenVoiceOS 2026 roadmap, including release codenames, nine key technical initiatives (modular core, LLM ecosystem, memory abstraction, OVOS Plugin Arena, session-aware GUI, wake word datasets, language/TTS research, third-party server compatibility, UX/tooling), funding acknowledgments, and call-to-action.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A roadmap hops forth, shining bright,
With modular cores and LLMs in flight,
Privacy-first, open, and true,
OpenVoiceOS charts paths anew!
Twenty twenty-six awaits the call,
Community voices will echo through it all! 🌟

Pre-merge checks

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'feat: ngi_roadmap' is vague and uses generic terms without clearly describing the actual change.	Consider a more descriptive title like 'feat: add OpenVoiceOS 2026 roadmap blog post' to better convey what content is being added.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

_posts/2026-01-10-ngi_roadmap.md (2)

30-33: Minor style improvement: Remove redundant phrasing on line 32.

The phrase "Specific details" is redundant; consider simplifying to just "Details" for better conciseness.

🔎 Suggested refinement

-This roadmap reflects current development priorities for 2026 and summarizes work supported by the NGI Zero Commons Fund. It is not a binding commitment or a finalized project plan. The items described here represent active work, ongoing research, and intended directions rather than guaranteed deliverables. Specific details may change as development progresses, community feedback is incorporated, or technical constraints evolve. All implementations remain subject to revision based on practical findings and upstream ecosystem changes.
+This roadmap reflects current development priorities for 2026 and summarizes work supported by the NGI Zero Commons Fund. It is not a binding commitment or a finalized project plan. The items described here represent active work, ongoing research, and intended directions rather than guaranteed deliverables. Details may change as development progresses, community feedback is incorporated, or technical constraints evolve. All implementations remain subject to revision based on practical findings and upstream ecosystem changes.

---

36-50: Minor style suggestion: Tighten verbose phrase on line 44.

The phrase "at a specific point in time" could be shortened to "at a specific point" for better conciseness, though the current phrasing is acceptable for a blog post.

🔎 Suggested refinement

-In 2026, we will introduce **codename releases**, corresponding to stable releases. These will freeze all OVOS package versions at a specific point in time, providing reproducible, production-ready deployments, while the rolling alpha channel continues to support bleeding-edge development.
+In 2026, we will introduce **codename releases**, corresponding to stable releases. These will freeze all OVOS package versions at a specific point, providing reproducible, production-ready deployments, while the rolling alpha channel continues to support bleeding-edge development.

📜 Review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f939d73 and c34cae4.

📒 Files selected for processing (1)

• _posts/2026-01-10-ngi_roadmap.md

🧰 Additional context used

🪛 LanguageTool

_posts/2026-01-10-ngi_roadmap.md

[style] ~32-~32: This phrase is redundant. Consider writing “details”.
Context: ...ns rather than guaranteed deliverables. Specific details may change as development progresses, c...

(SPECIFIC_DETAILS)

---

[style] ~44-~44: This phrase is redundant. Consider writing “point” or “time”.
Context: ...all OVOS package versions at a specific point in time, providing reproducible, production-rea...

(MOMENT_IN_TIME)

---

[style] ~101-~101: To elevate your writing, try using an alternative expression here.
Context: ...ti-device, multi-user deployments. This matters for distributed environments like Hivem...

(MATTERS_RELEVANT)

---

[grammar] ~106-~106: Ensure spelling is correct
Context: ...ts own persona and GUI state. --- ### Pyhtmx GUI Adoption The OVOS community has de...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

🔇 Additional comments (4)

_posts/2026-01-10-ngi_roadmap.md (4)

1-11: Frontmatter looks good. Metadata is complete and properly formatted.

---

152-174: Vision and call-to-action sections are compelling and well-written. The closing effectively reinforces OVOS's mission-driven approach and provides clear ways for community members to contribute.

---

14-26: Introduction is clear and well-structured. Establishes context effectively with references to prior work and funding support. All referenced blog post links are valid.

---

53-150: Key initiatives section is well-structured and comprehensive. Each subsection clearly explains the technical direction with appropriate context and valid references to prior work. All external links (GitHub repositories, blog posts, and HuggingFace collections) are accessible and current.

[j1nx]

A bit technical however all looks fine to me.

Merge away I would say.