View the roadmap
OSSM Project Roadmap
View milestones, planned features, and development progress on GitHub Projects.
Roadmap scope includes hardware, firmware, and documentation work for OSSM. Timelines are targets and may shift based on testing feedback, safety reviews, and community input.
How we prioritize
- Safety, reliability, and usability improvements come first
- Community impact and number of affected users
- Effort required versus value delivered
- Dependency order (what must ship before something else)
Contribute to the roadmap
There are several ways to help shape what we build next:- Suggest features β open a GitHub issue describing your idea and why it matters
- Vote on priorities β react to existing issues to show community interest
- Join quarterly planning β comment on relevant issues or reach out to the maintainers to participate in roadmap discussions
1
Check existing issues and projects
Search the OSSM repositories and project boards to avoid duplicates. If a related issue exists, add your use case or a thumbs-up reaction.
You should see your reaction counted or your comment posted on the existing issue.
2
Open a well-scoped feature request
Create a new GitHub issue with:
- Problem statement and the outcome you want
- Who it helps (e.g., builders, new users, advanced tinkerers)
- Proposed approach (optional) and alternatives considered
- Risks, safety considerations, and testing ideas
3
Tag and follow
Add helpful labels (e.g., feature, firmware, hardware, docs). Link any related discussions. Subscribe to the issue to receive updates as it moves through the project board.
When triaged, your issue will appear in the appropriate project column with an assignee or status label.
Stay informed
- Watch the OSSM repositories and project boards on GitHub for updates
- Join community discussions during quarterly planning
- Follow release notes and firmware updates when new milestones ship
Flash OSSM firmware
Update to the latest firmware and verify fixes or new features.
Device support (RADR)
See current and planned device compatibility evaluated across 2025β2026.
What does βquarterlyβ mean here?
What does βquarterlyβ mean here?
We target roadmap reviews and updates at the start of each quarter. Dates may shift to accommodate testing cycles, supply chain changes, or significant community feedback.
How are breaking changes handled?
How are breaking changes handled?
Changes with safety or compatibility impact are called out in release notes and documentation with migration guidance. We strive to provide deprecation periods whenever feasible.
Where do I start contributing?
Where do I start contributing?
Look for issues labeled βgood first issueβ and βhelp wantedβ. These are curated to be approachable and come with clearer acceptance criteria.

