4 ms·
How does the choice for AGPL influence third-party consumers of governments deployments the citizenlab platform? I understand this license closes the network lo
by wrnr 6y ago
How does the choice for AGPL influence third-party consumers of governments deployments the citizenlab platform? I understand this license closes the network loophole in GPL by forcing all calling code to be released under the AGPL, so I be interested to know if I can call apis and download data of my government website without sharing it or talking to citizenlab. Maybe I am a little paranoid but this feels like a big brain play, or some just sloppy oversight.
[EDIT] Clarification.
- Mathnerd314 6y agoThe loophole is someone hosting a modified instance without publishing their source code changes. I don't think it affects data or APIs at all.
- wrnr 6y agoOh so I can basically do a SaaS and as long as I don't change the codebase without charing the changes its ok
- webmobdev 6y agoYes. If you don't change the code base to modify or add a new feature, there is nothing to share. If you add to, or modify any of the existing features of the web application, you are obliged to share the code for the same under AGPL, on request.
- kjeetgill 6y agoI don't think it's as simple as the parent says, but I don't know better either. Talk to a lawayer.
- eeZah7Ux 6y ago> forcing all calling code to be released under the AGPL No. If you modify an AGPL network service you have to share the changes. If you call the API from a client you have no obligations.