3 ms·
It's completely possible to take a piece of GPLv2 or v3 software, make extensive changes, and provide it only as a web service without ever being required to ma
by scblock 2y ago
It's completely possible to take a piece of GPLv2 or v3 software, make extensive changes, and provide it only as a web service without ever being required to make those changes available to the community. AGPL solves for that important case, where if you use AGPL software to provide a service and make changes, in addition to providing the service you must also make your changes available to the community.
But I think I misunderstood your point, you were focused on the GPLv3 itself. Which I don't think prohibits running on any computer as you say.
- johnea 2y agoYou're correct that I was refering to GPL s/w being able to run on "consumer devices". But to your first point: I'm not a lawyer (thankfully), but my interpretation of GPL: that the s/w source must be published if the s/w is "distributed", would require the source of SaaSS s/w to be published, since the "service" is distributing that s/w. Is that not correct?
- lcnPylGDnU4H9OF 2y ago> the "service" is distributing that s/w If it's running on their machine, they're not distributing it; users don't actually receive the software to run themselves and are instead making requests to a server that is running the software. (Client software would be different, of course.) I am also not a lawyer so perhaps take with a grain of salt.