Grafana, Loki, and Tempo will be relicensed to AGPLv3
1–10 of 578 posts
Re: Grafana, Loki, and Tempo will be relicensed to AGPLv3
#2I can see why they would relicense Grafana this way, but why Loki? It's a fairly immature product that needs the boost of a less restrictive license IMO. I'm worried this will harm the adoption of it compared to the ES ecosystem (OpenSearch in particular) and we won't see it used for anything beyond Grafana.
Re: Grafana, Loki, and Tempo will be relicensed to AGPLv3
#3All of the most important software of our lifetime is going through this relicensing effort as the creators attempt to capture the value of what it enables. This is not some nefarious plan to screw over the community. It's a very measured and thoughtful way to ensure the long term progress and continuity of these projects. If the core companies maintaining them did not do this they would eventually die and these projects would slowly rot. Hopefully over time rather than having everyone choose their own licenses we end up with some form of standardisation.
Re: Grafana, Loki, and Tempo will be relicensed to AGPLv3
#4What 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.
Re: Grafana, Loki, and Tempo will be relicensed to AGPLv3
#5"Amazon Announces Grafana Fork , Promises Amazing Things for the Community" (2021/05/08) [1]
On a more serious note: there is a bit of a trend in the licensing world. Mongo or ElasticSearch changes, or cool new projects like redpanda [2] launching with BSL.
Open source is still a very young business model. One that has provided a tremendous amount of value over the past decades, but we still need to figure out how to build sustainable businesses with it. Be it open core, more restrictive licenses, copyleft, dual licensing, ...
I just really hope that we don't slide back into the world of proprietary closed source. The danger is certainly there, and it will hit smaller companies the most.
Re: Grafana, Loki, and Tempo will be relicensed to AGPLv3
#6What 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?"
Re: Grafana, Loki, and Tempo will be relicensed to AGPLv3
#7I 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, which calls into question whether it's even legally enforceable.[1]
AGPL is somewhat controversial, but the reasoning for AGPL to exist is chiefly to protect the end user's rights, however misguided that may be in your opinion. In this case Grafana presumably retains the copyright to these programs, so presumably they are not beholden to these restrictions in any way. On the other hand, though, it does mean that other providers will have to distribute their patches back to the community, which is pretty much the entire goal of copyleft open source in the first place.
In any case, this is, in my opinion, a lot better than SSPL or the Timescale license.
[1]: https://www.processmechanics.com/2018/10/18/the-server-side-...
edit: wording regarding AGPL was changed, because the claim that considering AGPL as not open source is “somewhat controversial” isn’t quite accurate; it’s more correct to say the license itself is simply controversial.
Re: Grafana, Loki, and Tempo will be relicensed to AGPLv3
#8I can see why they would relicense Grafana this way, but why Loki? It's a fairly immature product that needs the boost of a less restrictive license IMO. I'm worried this will harm the adoption of it compared to the ES ecosystem (OpenSearch in particular) and we won't see it used for anything beyond Grafana.
Popularity can increase rapidly, and if they do it too late, Amazon will screw them just like they did with Elastic.
Re: Grafana, Loki, and Tempo will be relicensed to AGPLv3
#9Even 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.
Re: Grafana, Loki, and Tempo will be relicensed to AGPLv3
#10Hmm. Where does Grafana people stand on what constitutes a "derivative" work? Are my Grafana dashboards derivatives of Grafana, and must now be published? If I embed a Grafana dashboard in my application, is my application now a derivative of Grafana and must be released as AGPLv3?