Re:GPL, copyleft use declining faster than ever
by _delirium on Saturday April 21, 2012 @02:25PM
(#3872507)
I agree on the name, yeah, and I was also surprised by Opa. My assumption in infrastructure-code cases like that (not sure if actually true with Opa) is that they want to leave the door open to a dual-licensing solution, so if Opa ends up being a killer technology, the AGPL poison-pills it enough for commercial customers that they'll be able to sell paid licenses.
Not sure what a cleaner alternative would be in that case. Perhaps just state that explicitly? "You can use the free version of Opa to build open-source webapps [define appropriately], but need a commercial license if your app is not open-source."
As with all of these GPL-style licences, there's a lot more risk if you're not an all-GPL house, and quite modest risk if you're intending to GPL your code anyway. But the AGPL is different because it can affect not just developers building on the code for redistribution but also those who are just using it internally.
I can understand why they did that, in the context of network-enabled services, but nothing in the AGPL seems to restrict the implications to only that context. As the example above demonstrates, people do use it for other things with potentially profound implications that aren't obvious to anyone who knows about the much more common GPL and LGPL but doesn't realise why AGPL is fundamentally different. For that reason alone, I don't think the AGPL should have used a similar name.