Commit graph

4 commits

Author SHA1 Message Date
Alexander A. Klimov
3c8ed68cc6 Upgrade license from GPLv2 to GPLv2+
This was easy because only README.md and doc/01-About.md were redacted manually, everything else via:
git ls-files -z |xargs -0 perl -pi -e 's/Icinga GmbH \| GPLv2/Icinga GmbH | GPLv2+/'

This is legal because we have only merged PRs with label:cla/signed or made by Icinga staff:
https://github.com/Icinga/icingadb-web/pulls?page=1&q=is%3Apr+is%3Aclosed+-label%3Acla%2Fsigned+-author%3Anilmerg

This has no risk for us in people distributing their own version under GPLv3 only.
After all, we won't take their patches anyway, unless they sign our CLA.

This is the cleanest solution for having e.g. these in one address space:

* Icinga Web, GPLv2+
* K8s Web, AGPLv3
* Thirdparty, some LGPLv3 and Apache-2.0

Apropos, K8s Web is even v3-licensed on purpose, to have a stronger protection against cloud ops.
2025-11-21 13:31:24 +01:00
Johannes Meyer
f2da48219c tests: Enhance command transport tests 2025-11-12 15:15:10 +01:00
Johannes Meyer
a0bb146790 test: Command transmission fallback handling
refs #950
2024-03-26 17:05:32 +01:00
Johannes Meyer
8a57ca7850 Introduce monitoring's perfdata tests here 2023-01-19 11:04:17 +01:00