Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3
by sneak on Tuesday April 20, 2021 @07:52PM
(#26883559)
That's a very simplistic and, I think inaccurate view of the matter.
My customers, for example, to whom I provide service, are not infringed upon in any way because I use private forks of GPL software in the provision of my services.
Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3
by LambdaComplex on Tuesday April 20, 2021 @08:28PM
(#26883861)
> My customers, for example, to whom I provide service, are not infringed upon in any way
The issue is that I—and, more importantly, your customers—must simply take your word for it, since we're unable to confirm or deny it for ourselves if you don't make the source available.
When dealing with large corporations, taking such statements at face value is pretty foolish.
Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3
by throwaway2037 on Tuesday April 20, 2021 @10:06PM
(#26884609)
This is an interesting point. The original question was what if my database was AGPL, and it's source code was modified. If this database was used as part of a public (cloud-based) web-app, how could end users ever know there is a custom database? You are right: It seems likely that less ethical orgs would just lie and say they use the database unmodified. Thus avoiding the obligation to publish their database modifications as required by AGPL.
Re:Grafana, Loki, and Tempo will be relicensed to AGPLv3
by CRConrad on Tuesday April 20, 2021 @08:37PM
(#26883943)
They will be when you go out of business and disappear, and they can't compile that same service to run on their own replacement server because you've withheld the source to your modification.
You might not want to admit to yourself that your business model is based on infringing on the freedoms of these users of GPL software, but that's exactly what it is.
To the detriment of the users of that service--which are the people that the FSF aims to protect.