Seems like a sensible choice - one of the things that as cause me to look askance at some of the anti-serverisation (urgh) licenses has been companies trying to bespoke something when the AGPL has always been right there to solve the problem they're trying to tackle.
Grafana, Loki, and Tempo will be relicensed to AGPLv3
11–20 of 578 posts
Re: Grafana, Loki, and Tempo will be relicensed to AGPLv3
#12I don't want to weigh in here with a huge value judgement on whether this is the right decision. However, I do want to say that what they're saying regarding SSPL vs AGPL is totally right. One of the biggest sticking points with SSPL is that it's not even really plausibly open source, and it tries to create restrictions that implicate software that is not even "linked" with the program that is licensed under it, whic…
Who I earth would argue that AGPL isn't open source? The kind of people who think open source = free lunch I suppose. It's probably the most open source licence there is.
Re: Grafana, Loki, and Tempo will be relicensed to AGPLv3
#13Okay, so they go out of their way to avoid answering how this actually affects people, so I'll ask here: If a company uses grafana internally, this should have no effect, right? And then the next step: If a company did offer grafana-based dashboards to customers but wasn't actually modifying grafana, what if anything does this do?
Re: Grafana, Loki, and Tempo will be relicensed to AGPLv3
#14What is the biggest fork of Granafa I can use that is non-share-alike? Edited: Oh, I can't say this... I leave it up for posterity and a note to myself then. http://www.paulgraham.com/say.html
Is there a specific conflict like ZFS-on-Linux that you want to avoid, or are you just asking "how can I most benefit from other people's work without letting anyone else benefit from mine?"
Exactly. This is the ZFS-on-Linux situation.
I prefer to keep all my code as much as possible mit and I share them on Github. This is my mode of operation.
Grafana makes me unable to use MIT for that use.
Re: Grafana, Loki, and Tempo will be relicensed to AGPLv3
#15Sorry for my ignorance, what does this license mean? I find licenses a little bit difficult to understand.
Re: Grafana, Loki, and Tempo will be relicensed to AGPLv3
#16Even though we use Grafana only internally and there would be no problem with AGPLv3 in theory I see big meetings with legal coming up which might result in us not being able to use it anymore. I could image that its the same with other corporations. In the end that might hurt the popularity of Grafana quite a lot.
There should be no problem with it even if you use it externally. It's about time companies stopped seeing open source as freely exploitable. Every company that uses open source software should be obliged to contribute, or pay for proprietary software.
Re: Grafana, Loki, and Tempo will be relicensed to AGPLv3
#17Even though we use Grafana only internally and there would be no problem with AGPLv3 in theory I see big meetings with legal coming up which might result in us not being able to use it anymore. I could image that its the same with other corporations. In the end that might hurt the popularity of Grafana quite a lot.
Would you consider paying for a licence to use it?
Re: Grafana, Loki, and Tempo will be relicensed to AGPLv3
#18Earlier quoted context omitted.
Is there a specific conflict like ZFS-on-Linux that you want to avoid, or are you just asking "how can I most benefit from other people's work without letting anyone else benefit from mine?"
Exactly. This is the ZFS-on-Linux situation. I prefer to keep all my code as much as possible mit and I share them on Github. This is my mode of operation. Grafana makes me unable to use MIT for that use.
>keep all my code
Huh? Grafana isn't your code, it's someone else's code that you'd be using. Unless I misinterpreted, and you are a Grafana contributor. If you are, you could dual license your contributions under AGPL and MIT, if you wanted.
Re: Grafana, Loki, and Tempo will be relicensed to AGPLv3
#19Looks like there were two blog posts. This QA session with the CEO is also interesting.
https://grafana.com/blog/2021/04/20/qa-with-our-ceo-on-relic...
Re: Grafana, Loki, and Tempo will be relicensed to AGPLv3
#20Okay, so they go out of their way to avoid answering how this actually affects people, so I'll ask here: If a company uses grafana internally, this should have no effect, right? And then the next step: If a company did offer grafana-based dashboards to customers but wasn't actually modifying grafana, what if anything does this do?
Presumably - offering dashboards to users, would count as distribution to those users (internal or otherwise). Unmodified Grafana like has/will get a link to source code/license - that would likely cover you - although if Grafana goes away (or becomes closed source) - you might have to offer a copy of the source code on request?