4 ms·
How is it debated whether AGPL is open source? Who says it isn't?
by josephcsible 6y ago
How is it debated whether AGPL is open source? Who says it isn't?
- jchw 6y agoIt seems like this one sentence of my message has become the focal point of it, which was not the intent. However, I corrected it to be more close to the truth, which is to say that it is merely controversial, not necessarily that its status as an open source license is debatable.
- zokier 6y agohttps://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495721 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495721 might be good background reading
- clankyclanker 6y agoThe FTP masters’ message (from 14 years ago!) is pretty convincing: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495721#17 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495721#17 The follow on questions on that thread seem to be fairly hypothetical handwringing, and something I’d expect the FSF to submit an amicus brief, giving their fairly reasonable FAQ answers, if it ever did show up in court. Given that the GPLv3 (and its derivative, the AGPLv3) allow for up to thirty days to remedy shortcomings, your source code being unavailable for a few hours while GitHub is down seems like a non issue.
- zokier 6y agoSure, I think its mostly settled now. But it definitely was debated at the time.
- sneak 6y agoI feel that the AGPL actually reduces the software freedom in a misguided attempt to close the ASP "loophole", as if offering an API from a private fork is something to be prevented. I am a proponent of software freedom, and resultantly I view the AGPL as nonfree.
- josephcsible 6y agoWhat's your definition of software freedom exactly?
- sneak 6y agoIf I download some open source free software, and modify it so it does something differently on my computer, simply running "systemctl start httpd" should not potentially bring down the machinery of state copyright enforcement against me for not publishing my private patches. Freedom includes freedom to have privacy. Not distributing any software, my privacy should not be violated. Running an ASP off a private fork is not "loophole", any more than, say, using free software to make missiles or killing machines. I feel like the AGPL is just anticapitalist fist-shaking.
- pritambaral 6y ago> Freedom includes freedom to have privacy. You have that. The AGPL provides rights to _users_ of your software; that's it, no one else. If _you don't provide_ the modified software to someone, they can't demand your private patches. No one can "bring down the machinery of state copyright enforcement" against you, unless you interact with them first and provide them your modified software and they use it. And even when you do that — when you provide your software to someone — they still can't demand that you "publish" your private patches. Only that you give to _them_ the modified software under the same rights that you received the original software. Only to _them_, not the public. No publishing required. _They_ are free to publish the software they received, of course, as were you when you first received the original software; but you aren't obligated to publish it. ---- The only difference between AGPL and GPL is that the definition of what constitutes "distribution" of software is extended. The AGPL changes only "distribution" and nothing else in the GPL.
- sneak 6y agoYeah, and running a business on my own computer by providing API services to someone is not distribution of software. Running an API business shouldn't force me to distribute anything to anyone.