Recently bumped into a license called AGPL. If you don’t know what it is, just by looking at the name you can guess that it’s one from FSF. AGPL is designed to close the “ASP loophole”. What does that mean? If you’re using GPL licensed software, you MUST release the source code if you’re redistributing the software. For example, if you use a GPL licensed library or program in your software projects, when you put your product out there (either sell or give it away free) you must release the source code for your program under the same license. So your program will also be GPL licensed automatically. If not it’s a violation of the GPL licensing terms.
Now, if you use a GPL licensed program in the server side (a CMS such as WordPress for example) to provide a service and you’ve done some modifications to the server side software, then even though it’s GPL licensed you don’t have to release your modifications. In this case you’re not really redistributing the software so you’re alright. This has been referred to as the “ASP loophole”.
So, AGPL is designed to close this “loophole”. Meaning, if you’re using an AGPL licensed program on the server side and you have done some modifications, you MUST release the source code with those modifications.
My view about the AGPL, as with anything GPL, don’t bother.
AGPL seems to be seeing more popularity these days. MongoDB is a project I recently found out to be released under AGPL. We are considering it for project at work too.
I love the fact that there are a good number of alternatives with more business friendly licenses for any given piece of software that comes with a GPL-like license!