Roadmap

Most work on Home Assistant needs no plan: a bug fix or an improvement to an integration goes straight to a pull request. Larger work is different. When something spans several repositories, needs design, or touches how people use Home Assistant every day, it is planned on the roadmap of the Open Home Foundation.

The roadmap isn't a list of features with dates. It describes the problems the project wants to solve next, and it's an open call for contributions in those areas. Everything on it happens in public repositories on GitHub, so you can follow along, and join in, at every step.

• Your first roadmap contribution: share a feature request, or add your use case to one that exists.
• From idea to release: the whole path, from a goal of the foundation to a feature request, an opportunity, an epic, tasks, and the release that ships it. With one real example traced end to end.

• The roadmap repository holds the opportunities: the problems the foundation has chosen to work on.
• The project board shows them at a glance.
• Epics break an opportunity into phases of work, with tasks in the repositories where the work happens.
• Roadmap updates are published on the Home Assistant blog, in the roadmap category.

The roadmap decides what gets built. How Home Assistant is built is guarded by the architecture meeting, which sits next to the roadmap: every change to the architecture needs its approval, whether it comes from the roadmap or from a contributor's own idea. How architecture decisions are made explains that side.

• Ideas go to the feature requests, where everyone can vote and discuss.
• Comments on an opportunity go on its issue in the roadmap repository.
• Questions about how something should be built go to the architecture discussions, or the #developers channel on Discord.