You might think this is a valid clause to include, and like its effects, and that's fine (though a close reading of that AGPL clause reveals a myriad of problems; it's extremely poorly thought-out and I find it unlikely that it would survive in court if properly challenged, with many workarounds possible, or causing problems for normal usage, depending on interpretation). But it doesn't change the fact that, suddenly, it makes it into an EULA, since it imposes a condition on usage, not distribution.
The GPL and other Free Software licenses strictly give you rights. You have no right to copy software by default under copyright. Those licenses give you the right to do so, subject to certain conditions.
The AGPL removes rights. It removes the right to use (not distribute) the software as you wish if you do not follow certain conditions (that you don't modify it without making those modifications available to remote users who are otherwise not receiving a copy of the program anyway, and not invoking copyright).
Linux distributions should be including the AGPL as a click-through license when users request to install such software from the repositories. In the current status quo, users are required to abide by terms they haven't been required to read, and might accidentally violate the license by doing something that is otherwise legal, such as editing a script in /usr that is part of such an app and exposing it over the Internet.
It's not a requirement on users anymore than the GPL requiring you to distribute corresponding source on CDs was a requirement on users. Morally and legally, the distribution medium does not make a difference. When you make the software available over the network you are no longer the user -- the users of the software over the network are the users. When you convey the software over the network you are a network operator and a distributor. Being a network operator and a distributor imposes obligations upon you.
It is not a EULA. The AGPL even says, in the same section that the GPL says (to wit, section 9) that you don't need to accept it in order to be granted its rights.
If I give you a CD with nginx, I'm distributing it.
If I send you a .tar.gz with nginx, I'm distributing it.
If I bring up nginx on a server, put some HTML files in the webroot, and give you a URL to it, I am not distributing nginx. I am merely using nginx, and offering you a service using nginx. I am not offering nginx itself. I am distributing my HTML website, and I am merely using nginx for it.
Cases 1 and 2 invoke copyright. Case 3 does not. In the absence of a license, you are not allowed to do 1 nor 2, but you are allowed to do 3. I can give you software I created, say nothing whatsoever about its license (which means, implicitly, "all rights reserved"), and international copyright law says you can not do 1 nor 2, but you can do 3.
The GPL, BSD, and other free software copyright licenses say you can do 1 or 2, under certain conditions.
The AGPL, and other EULAs, says you can NOT do 3, unless you meet certain conditions (other EULAs may, for example, limit the number of users, which would be typical for typical proprietary software server EULAs; the AGPL limits how you can serve the software, in that you must provide source changes to users of the service).
Therefore, the GPL and BSD strictly grant rights (to copy). The AGPL both grants rights to copy and restricts rights to use. It is therefore not a copyright license, but a contract, an EULA, a click-through usage agreement. And anyone who treats it as a copyright license (i.e. users are not expected to care) is doing a disservice to their users, because they are, in fact, not allowed to use the software without abiding by that contract (license).
If nginx were AGPL-licensed (thankfully it isn't), and I made a change to the source for personal use, then the AGPL would require me to stick a download link to that modified source in the footer of every website served using that copy of nginx, even if I am not serving the nginx binary itself.
The GPL is already perfectly suited to cover distributing software on the internet, as tarballs or whatever. The GPLv2 had some outdated provisions referencing a "medium" and written offers (e.g. the CD story), and the GPLv3 already covered that by saying you can just send the source via the same medium as the binary, e.g. from a network server.
The AGPL is a very different beast, and it has nothing to do with updating the GPL to allow for network transmission of the source, as you seem to imply.
Have an example: I run a Nextcloud instance for personal use. It is AGPL-licensed. Thankfully I have not made any changes to the code. However, if I touch a single php file in my /var/www/nextcloud (other than config files - hopefully, the AGPL is too vague to say for sure), that means I now need to figure out how to package and distribute that change to literally every visitor to my instance, which could be anyone on the internet (even if they just hit the login page). This is NOT possible with a purely copyright license. And my distribution did not warn me about it (like they did for proprietary software EULAs, which require an explicit ack), because they erroneously believe that the AGPL is not an EULA, because the FSF wrote it.
Does this make sense now?
It is an copyright offence to perform any of the following acts without permission of the owner:
Copy the work.
Rent, lend or issue copies of the work to the public.
Perform, broadcast or show the work in public.
*Adapt the work.*
A person who take a copyrighted software and adapts it into a online service need to get adaptation permission from the author. If the work is given out under a AGPL license then that license is proof of permission as long as the person follow the terms, just as with any other copyright license.You do not need permissions from a copyright license unless the action a person does falls within the scope of copyright. If a person don't copy, rent, lend, issue copies, perform, broadcast, show, or adapt the work, then the AGPL conditions are irrelevant because the user do not need permission in the first place. An EULA or contract however is not limited in this way and can restrict usage of a program outside the scope of copyright.
While it is true that copyright protects the right to create derivative works, that is, in practice, usually applied to creating such derivative works and distributing them. Otherwise, scribbling with a pen on a book you bought would be a copyright violation.
Similarly, while technically running a program requires copying it into memory (and thus requires a license), no court in this day and age is likely to rule that running software which was acquired legally, but which does not come with a license to run it, is a copyright violation.
The memory issue has been well discussed and handled in the past. The law has an explicit exception made with this in mind where legal owners of the software has a right to both copy and adapt software if it is an essential step towards utilization of the program. licensees however does not have this right and are restricted to the terms under the license. Naturally this is designed more towards the world of proprietary software where such distinction is more clear.
The AGPL attempts to control any changes made to the code, not just, say, a substantial refactoring or reworking. So in principle a one-line patch is sufficient to trigger AGPL clause 13.
People add links to the source code because it's much less work than responding to emails. It's entirely voluntary. Users have a right to the source code of AGPL software you make accessible to them and you can satisfy that constraint any way you see fit.
> your modified version must prominently offer all users interacting with it remotely through a computer network [...] an opportunity to receive the Corresponding Source of your version by providing access to the Corresponding Source from a network server at no charge [...]
An email does not cut it. It has to be a direct link to the source, or some kind of equivalent mechanism to directly download it from a server. Merely providing you the opportunity to ask a human for it does not cut it (an email bot might, but that'd be dumb).
Does it make sense now?
In fact, courts have repeatedly ruled that the output of software (i.e. the packets nginx sends over the network, but which aren't its own code) is not covered by the software's copyright itself.
If I lend you my phone, in the absence of more restrictive EULAs, and excluding media (which is reproduced verbatim by the phone), you are free to use any software on it without being subject to the copyright of said software.
Does it make sense now?
Does it make sense now?
Yet, the copyright law is what the AGPL is trying to wield as its basis.
It does not seem valid. Has anyone tested it in court?
I don't think that copyright can assert use restrictions. You cannot say that someone is not authorized to have a copy of something if they do not use it in such and such a way.
It's exactly like a "license" written in the flap of a book which says that you must read only the even-numbered pages. If you read any odd-numbered page, then you are breaching the license under which you're permitted to have a copy, and must destroy the book.
I would cheerfully deploy a modified AGPL program and not reveal the code to anyone. Nothing would happen at all.
I'm surprised Google are so allergic to the AGPL. If it came down to it, they could crush this bullshit in court like swatting a mosquito.
You're grasping at straws here. There's provisions based on copyright, and then there's everything else. Redefining users to exclude the person running the server and implying that means the person running the server loses all rights under the Free Software definition is ludicrous.
Once you serve to other users, though, they also become users of nginx. In this regard, you have an upstream/downstream relationship between you and the other users of nginx that you've made users by giving them access over the network.
You are still free to use nginx for your military website or your online shop or whatever. Your usage of nginx has not been restricted for any purpose.
By granting network accesss to our hypothetically AGPLed nginx, though, you now have an AGPL obligation to provide a link to the source code of nginx, in case you modified that source yourself. This isn't taking any rights away from you -- indeed, the AGPL is only granting you rights. You wouldn't have the right to even serve nginx to other users or to modify its source code if it weren't for the AGPL.
None of this is substantially different from the GPL except for the method of interaction with the software.
Note that a shrink-wrap end-user license agreement from Adobe also doesn't take away your rights; it only grants you rights.
At least, according to copyright rhetoric.
Merely receiving a license-free piece of software (i.e. "all rights reserved") with no strings attached gives you a certain set of default rights (i.e. anything not in violation of copyright), such as to run it for any purpose. EULAs like a shrink-wrap agreement from Adobe, or the AGPL, then attempt to remove some of those rights.
Though, sure, you can look at it from the point of view that in the absence of a license at all, nobody would've been able to distribute the software to you in the first place, and therefore you'd have had no rights as a result.
If you have this opinion of the AGPL, then you should also have it about the GPL, since the only difference between the two is section 13 of both of them (seriously, just diff them) which says that conveying over a network also triggers copyleft. This is just a modernisation of plain ol' copyleft from the days when conveying was mostly done on physical media instead of over a network. If some day we discover a way to distribute software over neither a network nor physical medium (I can't imagine what that could be... quantum entanglement?), then the definition of "conveying" should be updated to reflect the new technology.
The GPL has long been considered open source by OSI and free software by the FSF. You are free to use the software however you want -- you're just not free to deny this freedom to your users or clients, with neither the GPL nor the AGPL.