Cleanup LICENSE.txt file

[wborn]

There are a lot of details in the license file that do not apply to this repository. This also allows for GitHub recognizing the license and show "AGPL-3.0 license" in the about section and repositories list.

[richturner]

@pierrekil I'd imagine we still want OpenRemote license here, maybe talk with @wborn about incompatibilities

[wborn]

If you want to add additional license details you can use multiple license files. That way it is still possible for GitHub to detect the license and show it in about and repository lists.

See for example: https://github.com/wborn/multiple-licenses

---

---

---

---

[pierrekil]

@pierrekil I'd imagine we still want OpenRemote license here, maybe talk with @wborn about incompatibilities

Yes, still same license

[wborn]

I found some popular projects using AGPL-3.0 that also use the LICENSE file as-is. They document in either the README or other files their copyright text as well as details about files in their repositories that have other licenses, see:

• https://github.com/grafana/grafana
• https://github.com/mastodon/mastodon
• https://github.com/nextcloud/server
• https://github.com/rustdesk/rustdesk

[pierrekil]

Let's follow

• https://github.com/grafana/grafana

• LICENSE.MD with standard GNU Affero General Public License v3.0 license text, so GitHub recognises it
• Add License header at bottom ot README: OpenRemote Service ML Forceast is distributed under AGPL-3.0-only. For Apache-2.0 exceptions, see LICENSING.md.
• LICENSING.MD with all APACHE 2.0 licenses and references, same as https://github.com/grafana/grafana/blob/main/LICENSING.md

Keep same as in openremote repo:

• Contributors.txt (for this repo)
• Security.md

[wborn]

OpenRemote Service ML Forceast is distributed under AGPL-3.0-only.

According to our license headers it is AGPL-3.0-or-later:

This program is free software: you can redistribute it and/or modify
it under the terms of the GNU Affero General Public License as
published by the Free Software Foundation, either version 3 of the
License, or (at your option) any later version.

For Apache-2.0 exceptions, see LICENSING.md.

There are no Apache 2 licensed files in this repository so I haven't added this file.

Contributors.txt (for this repo)

We decided to remove this file because this information is part of the Git repository details, see also:

• Fix license header issues and improve tooling openremote#1403
• Add Spotless Gradle plugin configuration and apply it openremote#1441

[pierrekil]

Are we using other libraries with AGPLv3?

[wborn]

Are we using other libraries with AGPLv3?

Not that I know of but it currently is all manual work to keep track of dependencies and their licenses.

Automating the generation of an overview of all dependencies and their licenses, along with creating a Software Bill of Materials (SBOM), can be beneficial. This will also help ensure compliance with the EU Cyber Resilience Act (CRA) once it takes effect.

See: https://fossa.com/blog/sbom-requirements-cra-cyber-resilience-act

[richturner]

Looks like source code is not using our standard OpenRemote copyright header but maybe that needs to be handled in a separate PR.

[wborn]

Looks like source code is not using our standard OpenRemote copyright header but maybe that needs to be handled in a separate PR.

It's similar to the headers in openremote/openremote#1441.

[richturner]

Looks like source code is not using our standard OpenRemote copyright header but maybe that needs to be handled in a separate PR.

It's similar to the headers in openremote/openremote#1441.

Will ask @dominiquekleeven to address separately