4 ms·
Many people find the AGPL to be a nonfree license, myself included.
by sneak 4y ago
Many people find the AGPL to be a nonfree license, myself included.
- ebiester 4y agoWhat isn't free about it? As a corporation, I might not want to use it in conjunction with my code, but that's the point. You are free to do what you want, but you in turn must share your code. Or you engage with the owner to make a financial arrangement for a separate license.
- sneak 4y agoIn short: It prohibits you from not sharing your code based on whether or not the ethernet cable is or is not plugged in to your machine. This is like nonfree usage restrictions on otherwise free software, like the famous (if unenforceable) “can not be used for evil” license clause.
- bawolff 4y agoRight but which freedom does that restrict that's not in the spirit of the gpl? I.e. the gpl prohibits you not sharing code if you distribute the binary. What is the philosophical underpinning of "sharing binary" not being a restriction but "ethernet" being a restriction. The evil thing is not similar because you are discriminating against a field of endevour (similar to licenses that say educational use only, non-commercial only or non-military only). It seems to be a very different type of restriction.
- em-bee 4y agothat's not right. in my understanding the intention of the AGPL is to share code with users of a program, even if the users didn't get a copy of the program. therefore the AGPL shouldn't force you to share code if the program runs on a server. but it should force you to share code if the program can be accessed by a user. this may even apply to running something like a kiosk device where users interact with a program on a device they don't own.
- the_gipsy 4y ago> whether or not the ethernet cable is or is not plugged in to your machine That's not even remotely near what it is.
- at-fates-hands 4y ago>> As a corporation, I might not want to use it in conjunction with my code, but that's the point. I've worked for several large corporations and were in the throes of a major project. Using an Open Source tool would've cut a lot of our dev times by many hours. Three out of three times, all three team leads and managers said "no" to using open source. We had to build several large components from scratch, which did lead to extended development timelines, a ton of working late at night and several "crunch" weekends. Their rationale? They didn't want to have to maintain a piece of software that was open source. The resounding opinion was it was "dangerous" and not safe - because someone could check in a malicious piece of code and that could end up in our very large, enterprise application when we needed to update it. Nobody wanted to be on the hook if that ever happened. In the end, it seemed like it was more about upper management types playing CYA instead of trying to put out a solid product.
- LtWorf 4y agoI don't think there is any computer currently in use with 0 open source on it.
- Mordisquitos 4y agoAm I mistaken in believing the only additional requirement of the AGPL is, in layman's terms, that if you operate the software as a paid service you must also release the source code of any changes that you apply to it? If that is the case, I don't see how the AGPL qualitatively infringes on any "freedoms" that the GPL doesn't already restrict: you must keep derivatives free. Of course one may argue that the GPL is nonfree when compared to BSD/MIT style licences, in which case fair enough.
- greenshackle2 4y agoThe justification usually given for AGPL is to prevent other companies from running paid SaaS without sharing their modifications. The actual terms is that any user who interacts with the software over the network must be able to download the sources. It doesn't say anything about whether the service is paid or free. I think the argument of FOSS people who don't like it would be something like, as a user, just running the software on my machine can potentially create a legal obligation to set up source distribution, if, like, I forgot to block a port.
- Mordisquitos 4y agoAh, I was unaware that it applied regardless of it being a paid service or not. I imagine that would be somewhat analogous to distributing binaries of modified GPL software for free without providing the sources. In any case, does the AGPL requirement to provide sources apply even if you are running an unmodified version? In other words, would merely pointing to the original repository not be enough? Regarding the risk of accidental legal obligations, I suppose it depends on the details and technical wording of the licence. If the requirement broadly covers any use of the software on the machine (e.g. some backend service that happens to help your public webserver to stay online) I can see the discomfort, especially if one must explicitly provide or link to unmodified sources too. On the other hand though, if the requirement is limited to actual provision of the software's functionality to 3rd parties, I would argue that if someone accidentally provides it due to forgetting to block a port then they have much bigger problems than the AGPL.
- josephcsible 4y agoDo you mean you believe it doesn't comply with the Free Software Definition and/or Open Source Definition, or that you believe it does but that it's nonfree anyway (or in other words, that you disagree with those definitions)?
- enriquto 4y ago> Many people find the AGPL to be a nonfree license, myself included. I don't understand this stance. From the point of view of the user, the AGPL offers the same freedoms as the regular GPL. If you use the program, you have the right to see and edit its source code, regardless if the program runs on your own computer or on another computer. How can anybody call this feature "nonfree" is beyond me.
- hnfong 4y agoAGPL basically says you can't use the program to provide an online service unless you $(sacrifice your first-born.) Granted, the license only asks you to publicize your modifications, but in software that's basically your "first-born".
- detaro 4y agoNot really, the vast majority of users of these kinds of software run it unmodified, the valuable stuff is around it. (If that weren't the case, MongoDB hadn't come up with their own "give us everything!" license because AGPL was too "weak")
- hnfong 4y agoOne of the important definitions of Free (capital F) software is the freedom to modify it without restrictions. If you're just talking about the freedom to run things unmodified, basically every software you can download online without paying is "free", and obviously AGPL fits that bill for the uncapitalized "free" software. But that's not what we're talking about here, right?
- detaro 4y agoIf the freedoms is your angle: And a large point of the GPL family of licenses is to make you publish your changes so your users can run and further modify it, and AGPL is a logical extension to that for a world in which users rely on software they don't personally run. So that their important freedom of being able to run and modify software they rely on is preserved. If you get to keep your changes, your users are deprived. The situation is funny that AGPL is widely derided as both being to weak and being to strong.
- LtWorf 4y agoMany people believe all sorts of absurd things with no evidence. Do you have evidence?