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.
It’s about the workflow for project templates. If there were a warning when creating or cloning that is one thing. But a folder structure, config files for tools, potentially requires the whole project to be a derivative?
It is dangerous to allow project templates to have a copyright license. Any project that uses it will be a derivative work. For this behavior in your application it should be explicitly disallowed or at minimum a red dialog.
Comments
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.
How is that dangerous? Isn't it a good thing, because it stops rug pulls?
It’s about the workflow for project templates. If there were a warning when creating or cloning that is one thing. But a folder structure, config files for tools, potentially requires the whole project to be a derivative?
It is dangerous to allow project templates to have a copyright license. Any project that uses it will be a derivative work. For this behavior in your application it should be explicitly disallowed or at minimum a red dialog.