It is dangerous to allow project templates to have a copyleft license. Any project that uses it could be argued as a derivative work. For this behavior in your application it should be explicitly disallowed or at minimum a red dialog.
There are multiple problems here. First, there's the unsupported claim that the AGPL is somehow incompatible with being production-ready, which seems obviously false. But more seriously, there's the proposition that GitHub should crack down on this project, which I find to be absolutely bizarre.
The person who opened that issue also made some other claims, like that a more permissive license would allow the project to reach a broader audience. That's undoubtedly true, but I'm going to go out on a limb and say that the author of the project is probably well aware of that and chose an appropriate license based on their own goals.
5 comments
[ 0.18 ms ] story [ 19.6 ms ] threadyikes
I suppose it's good that these people actually bother to read the license and intend to respect it.
The person who opened that issue also made some other claims, like that a more permissive license would allow the project to reach a broader audience. That's undoubtedly true, but I'm going to go out on a limb and say that the author of the project is probably well aware of that and chose an appropriate license based on their own goals.
If you do not agree to the license terms, do not use the project template.
Or, you could contact the project template author and ask if they are willing to sell a commercially-licensed copy to you.