#Custom integrations
1 messages · Page 1 of 1 (latest)
Cc @haughty roost
I'm not that big of a fan though, as we advertise our own integrations as community maintained
I agree with @solar socket , the core Integrations are also community maintained. And that's sometimes not communicated clearly enough. often people who support HA with their cloud subscription (which is really a good thing),then feel entitled towards integration maintainers, just because they are paying "customers". You can recognize that misunderstanding for example when core integrations are called "official" integrations, while custom integrations are community integrations, although they are both community integrations.
I don't think it was the idea to change custom integrations to community integrations. It was just meant so change custom cards (as in frontend cards) to community cards.
yeah, that makes a bit more sense, as frontend is mainly sponsored by OHF
Maintained is a better word I'd say
Yeah it all stemmed from this conversation: #1351536906437005313 message
Cards/badges/dashboards/views but not integrations
Honestly probably need a better word for them all. Community sounds like someone else made them when in fact you can copy your own code in. This isnt a super good example though
I'll probably revert some of these changes too https://github.com/home-assistant/frontend/pull/51368/changes
cc @deep cypress @mild stratus
https://github.com/home-assistant/frontend/pull/51440
Integration translations revert pr
Forgot the common naming across all custom things
One day i want to flip it around. Official ones and "no label" other ones
I would agree not to do a rename now
With this revert we also need to revert the core PRs, shall I create revert PRs for the core changes?
(android also)