Closed dkastl closed 3 years ago
Yes, we can switch to AGPL
license. The only thing is the strictness of AGPL
makes certain companies completely prohibit the use of the code. And, it is somewhat less compatible with other licenses.
However, the GNU project recommends using AGPL
for any project involving Network Interaction. It also allows the developers to mix code under AGPL
and GPL-v3
licenses in projects, and that somewhat reduces the compatibility issue.
Shall we switch to AGPL
, then? It would be good to change this now, as it is generally hard to change licenses in the later stages of a project.
Right, AGPL is the most restrictive choice. And it can cause heated debates ;-)
You can see it from three perspectives: the service provider, the service user and the project developers.
For a service provider AGPL can be a reason to ignore the project. But on the other hand it also makes it less attractive for those who are not willing to contribute improvements back.
For the user of the service AGPL is a win, because it ensures that there is no vendor lock-in and full transparency.
For the developers it's hard to say: there are advantages and disadvantages. I would say that the main reason not to go with AGPL could be a conflict with other licenses that we want to make use of.
I haven't used AGPL for a project yet, but I have the feeling that this one would be a suitable one. For those, who have a problem with AGPL, it would be also fine to offer a commercial license.
I think it's always easier later to change the license to a more permissive one than the opposite way.
Looks good! Changing the license to AGPL.
Currently the license is set to
GPL-v3
, but we could try to be more strict withAGPL
. Any thoughts?GPL-v3
is relatively weak when it's about web services.