Problem statement
We currently have "Casita" logos for the Home Assistant, Music Assistant, ESPHome, and Speech-to-Phrase projects, under the Open Home Foundation's branding identity umbrella.
When new projects (e.g., Matter.js, the Device Database, etc) need or are requested to create logos, there isn't a clear policy or list of requirements for identifying which projects require a "Casita" logo, so we can create it and give it its own identity, while maintaining the same branding as the rest.
Community signals
No response
Scope & Boundaries
In scope
- List of requirements that qualify a project as part of the "Casita" brand
- List of projects that must adhere to this policy
Not in scope
- New logos designed for the new projects added to the list
- Any potential redesign for existing projects that already have an Open Home Foundation branded logo
Foreseen solution
No response
Risks & open questions
No response
Appetite
- Small: this first iteration should be what enables subsequent steps related to new designs, etc
Execution issues
No response
Decision log
Problem statement
We currently have "Casita" logos for the Home Assistant, Music Assistant, ESPHome, and Speech-to-Phrase projects, under the Open Home Foundation's branding identity umbrella.
When new projects (e.g., Matter.js, the Device Database, etc) need or are requested to create logos, there isn't a clear policy or list of requirements for identifying which projects require a "Casita" logo, so we can create it and give it its own identity, while maintaining the same branding as the rest.
Community signals
No response
Scope & Boundaries
In scope
Not in scope
Foreseen solution
No response
Risks & open questions
No response
Appetite
Execution issues
No response
Decision log