Adds new plugin [rejuvenate/lovelace-horizon-card]

[edwardtfn]

A Home Assistant Dashboard Card available through the Home Assistant Community Store and inspired by Google Weather.

Lovelace Horizon Card is a fork of the original home-assistant-sun-card project by @AitorDB to continue the great work and distribute the responsibility of supporting and advancing the project among a team of people.

Checklist

• I've read the publishing documentation.
• I've added the HACS action to my repository.
• [N/A] (For integrations only) I've added the hassfest action to my repository.
• The actions are passing without any disabled checks in my repository.
• I've added a link to the action run on my repository below in the links section.
• I've created a new release of the repository after the validation actions were run successfully.

Links

Link to current release: https://github.com/rejuvenate/lovelace-horizon-card/releases/tag/v0.9.0
Link to successful HACS action (without the ignore key): https://github.com/rejuvenate/lovelace-horizon-card/actions/runs/4724341351
Link to successful hassfest action (if integration): <N/A>

[ThomDietrich]

Hey all,
is anything stopping this PR we can offer support with? The user base of the project is already quite big (89 stars on GitHub) and a place in the default repo would certainly make onboarding a lot easier for people.

[TheFes]

The PRs are reviewed in order of last change, where the PR which has changed longest ago is reviewed first. So every change to the PR will but it back on the list.

So to speed up the process, it's required to stop making changes to it :)

[ludeeus]

https://github.com/rejuvenate/lovelace-horizon-card/commits?author=edwardtfn
https://hacs.xyz/docs/publish/include

Only the owner of the repository or a major contributor to it can submit a PR to have it included as a default.

[edwardtfn]

This is so frustrating!
😩

[ThomDietrich]

Dear @ludeeus,
sorry we missed this part of the guidelines. @edwardtfn is an active part of the community and had our okay to go ahead with the PR.

Anyhow, I have just created #1958. I am a major contributor and owner of the organization under which this plugin is released.

The repository already has 130 stars on GitHub. Could you please prioritize it's merge, based on the fact that we already waited three months for #1808 ? Thank you.

[gucki]

@ludeeus It seems like hacs needs more maintainers if such a simple addition needs several weeks/ months to get merged. This is no complaint, just a serious question. And if so, what about putting this in the README.md? Thanks.