OK, I’m getting a little impatient with the Free Software Foundation’s work on the GPLv3 and the AGPLv2. This post is what’s getting me all fired up. It expresses quite well my feelings about the GPLv3, the Affero GPL, and the Affero GPLv2, as well as how all those relate to software as a service.
The author makes a great point that many software developers won’t use the GPLv3 to develop web applications because of the fact that the “spirit of the GPL” is lost due to the technical constraints of software distribution and web applications. In a nutshell, you only have to publish and license modifications to GPL software under the GPL if you distribute the original software in any way. Thanks to the magic of the internet, you can easily reap the benefits of GPL software without every distributing it. I’m not saying that is wrong, I’m just saying that it circumvents the purpose of the GPL, rendering it useless to web applications. At this point, open source web applications have the option of licensing under very liberal licenses like the MIT License, or a proprietary license.
The AGPL attempts to fix this with their clause about public access to the software rendered as a service, or something like that. However, the author of the above mentioned blog post makes some very good points:
- The Affero GPL is branded, what’s up with that??
- The Affero GPL is not compatible with the GPLv2, but it is possible that the AGPLv2 is compatible with the GPLv3.
- The AGPL is not OSI approved - that is actually very important!
Again, all this has to do with one post by Brett at the FSF. Its a tantalizing post for sure, but leaves out too many details to be useful. Here is Brett’s post about GPLv3 and Software as a Service.
UPDATE: A day after writing this and the chance to read this article: Novell Says Open Source License Changes Could Kill Microsoft Deal, I understand that the FSF has much bigger fish to fry than the SaaS loophole.
See also: Informed Licensing