News for hackers. Stuff that matters.
Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by pavon on Tuesday April 20, 2021 @05:53PM (#26882330)
The only difference between GPL3 and AGPL3 is what constitutes distribution. With GPL3 you have to provide source to anyone you provide binaries. With AGPL3 you also have to provide source to anyone who uses the software remotely (eg a web app). Everything else, including the scope of what must be included in the source (modifications, linked software, but not software that talks over IPC, etc), is identical between GPL3 and AGPL3.

More specifically, the only difference between GPL and AGPL is section 13 (and the preamble summary). The rest of the license is word-for-word identical (save for the name). https://www.gnu.org/licenses/agpl-3.0.en.html#section13

Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by LukeShu on Tuesday April 20, 2021 @06:19PM (#26882623)
To expand on that, you have to offer to provide the source to "all users interacting with it remotely through a computer network". If you're using Grafana for monitoring your SaaSS app, then your users aren't interacting with Grafana, so you're fine.
Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by Paul-ish on Tuesday April 20, 2021 @07:28PM (#26883362)
If your SaaSS app surfaces a few small things from Grafana to the user, do you only have to open source the glue code, or the entire SaaSS application?
Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3 by lmm on Wednesday April 21, 2021 @01:20AM (#26885693)
The entire application, to the extent that it's a single work under copyright law. If your app is a "mere aggregation" of e.g. grafana administration and other-service-administration components then maybe not.