[29J]

The GPL is pre-web so has a bug allowing web programmers to use a GPL'ed program in their web service without having to give their users the web service's source code. The AGPL fixes that bug so that such web programmers will need to give their users the web service's source code. Therefore the AGPL constrains licensees more and frees their users more.

[keepamovin]

I see, thank you! In your opinion what's the right license for this situation?

[orra]

I don't want to be overly dramatic. Your current license is decent. But the AGPLv3 is better: it fixes what is essentially a loophole in the GPL (the "ASP loophole", as described by the other user here).

From your perspective, you might find it even easier to sell your paid licences to companies and governments, if you use the AGPLv3. There's little downside to switching, because the AGPLv3 is still open source, and has similar compatibility with other open source licenses.

You've already released this under GPLv3, but you can switch going forward.

[keepamovin]

True. Alright, I think the reasons for us to stick with GPL are not as compelling as I first thought. I've updated my view. We will switch to AGPL. :)

On govs, unfortunately, but I still think it's a benefit: governments can simply use it without purchasing a commercial license or using GPL, under the Polyform Noncommercial. They can definitely purchase support, deployments, and customizations tho.