Release software as GPL (or similar) but allow non
I am trying to figure this out since a few days now and find no way to do this:
I have a software I want to release under the AGPL so the base system "is open-source", but my software has a plugin interface, where external plugins can be loaded at runtime (so no separation which the GPL would allow).
I now what to make it possible to others to develop non-GPL plugins, as I do not like "this part" of the GPL.
Is there a ways to somehow allow this as an exception to the GPL or in any other way?
Or is there a license which has the same copyleft for the code itself but permits linked software to be under a different license?
I already though of releasing the plugin interface under a different license (like LGPL), but to quote a well know CEO: "The GPL is like cancer". This is not possible, as the plugin interface must be GPL, because it is also linked into the (A)GPL'ed main project.
Could I solve this with some kind of "weird" dual-licensing of the plugin interface?
PS: My software is developed using .net 4.5 and C# if that matters anyhow.
您可能希望将API库/程序集发布为LGPL,它允许用户链接它们而不会“污染”他们的软件,因此这些插件没有污点,但仍需要增强API库的发布。
链接地址: http://www.djcxy.com/p/79562.html上一篇: GPL是否也适用于作者?
下一篇: 释放软件为GPL(或类似),但不允许