You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are deprecation warnings in the Home Assistant logs caused by Dwains Lovelace Dashboard since the 2025.1 version, as noted in Issue #847. Additional details about the issue have been provided in this comment.
To address this, clarification on the project’s licensing and contribution process would help ensure that fixes are submitted in alignment with the project’s guidelines. The project is licensed under CC BY-NC-ND 4.0 with additional custom terms (see README, lines 63–64). This raises some questions about the process for making contributions, as creating pull requests often involves committing changes to public forks on GitHub, which may intersect with the license’s restrictions (see discussion).
The following questions aim to clarify the process for contributors:
Does the current licensing model permit contributions such as bug fixes or compatibility updates?
What guidelines should contributors follow when preparing pull requests?
Are there specific provisions for addressing compatibility issues with newer Home Assistant versions?
Providing guidance on these points would help ensure that contributors can participate effectively while respecting the project’s licensing terms.
The text was updated successfully, but these errors were encountered:
There are deprecation warnings in the Home Assistant logs caused by Dwains Lovelace Dashboard since the 2025.1 version, as noted in Issue #847. Additional details about the issue have been provided in this comment.
To address this, clarification on the project’s licensing and contribution process would help ensure that fixes are submitted in alignment with the project’s guidelines. The project is licensed under CC BY-NC-ND 4.0 with additional custom terms (see README, lines 63–64). This raises some questions about the process for making contributions, as creating pull requests often involves committing changes to public forks on GitHub, which may intersect with the license’s restrictions (see discussion).
The following questions aim to clarify the process for contributors:
Providing guidance on these points would help ensure that contributors can participate effectively while respecting the project’s licensing terms.
The text was updated successfully, but these errors were encountered: