4 posts / 0 new
Last post
ForumImport
Offline
Last seen: 9 years 11 months ago
Joined: 09/22/2009 - 18:47
GPL License (K-3D and Plugins)

This message was originally posted by giantjupiter on 12/26/2007 23:27:59
Hi,
K-3D is released under GPL, how about the plugins? Let’s say we develop a new plugin, do we have to release it under GPL.
http://www.k-3d.org/wiki/Plugin_Design
This link mentions the issue, as it says \"...distributors can ship binary plugins to users...\"
Does it mean the newly developed plugin can be release under a non-GPL license, and keep close-sourced. Please confirm.
Is there any chance the K-3D being released under a license other than the GPL.

ForumImport
Offline
Last seen: 9 years 11 months ago
Joined: 09/22/2009 - 18:47
GPL License (K-3D and Plugins)

This message was originally posted by joa on 12/27/2007 04:47:13
Hi GiantJupiter!
Lets see if i can help you:
> K-3D is released under GPL, how about the plugins? Let’s say we develop a new plugin, do we have to release it under GPL.
> ...
> This link mentions the issue, as it says \"...distributors can ship binary plugins to users...\"
What this means is that there is no need to compile the plugins. It isn’t talking about the license.
I don’t know if you can distribute your plugin separately and closed source. I would say you can’t, because in that case the K-3D license ought to be LGPL and is GPL. And you would be linking against the k3dsdk. (i will confirm this anyway)
> Is there any chance the K-3D being released under a license other than the GPL.
In fact the project leader should change the License (and all the contributors should also), but I don’t think he (and all the contributors) would agree.
Closing the source is not on the spirit of the community, so my question would be:
¿Is it really necessary to be closed source?
Maybe you can open source part of your code. Make an open source plugin for connecting K-3D to your product. (a separate program)
Maybe if you have a too good product you can make a fundraising and set a threshold for releasing the source. If the fundraising gets its limit, the project is reviewed and the money is delivered.
There is another option also. If you have not many users (but they are going to pay well) you don’t have to release the code to the public, just to your users.
Cheers!
Joaquín
------------------
The K-3D Team has just created a Announce mailing to keep users informed.
https://lists.sourceforge.net/lists/listinfo/k3d-announce
Feel free to subscribe.

ForumImport
Offline
Last seen: 9 years 11 months ago
Joined: 09/22/2009 - 18:47
GPL License (K-3D and Plugins)

This message was originally posted by Daniel S. Matthews on 12/28/2007 11:22:37
A plugin is a separate piece of code therefore it can have it’s own license if you are distributing it yourself. i.e. it would not be in the code hosted on sf.net. You can \"roll you own\" K-3D distribution so long as the terms of the license are met for the open source part of your project. For example you have some exotic functionality that is not of interest to the general user base but you wish to provide it, using your own preexisting code, leveraging K-3D as a framework.
If you need any clarification, ask https://sourceforge.net/users/tshead/ as Tim has the final word on such matters.

ForumImport
Offline
Last seen: 9 years 11 months ago
Joined: 09/22/2009 - 18:47
GPL License (K-3D and Plugins)

This message was originally posted by Timothy M. Shead on 12/28/2007 17:08:41
All K-3D plugins must link with the K-3D SDK library, which is licensed using the GPL. That means that *all* plugins are derived works, which *must* be licensed using the GPL. This is by design, and will not change.
If you wish to create a plugin for internal use within your company, you’re free to do so:
http://www.fsf.org/licensing/licenses/gpl-faq.html#GPLRequireSourcePoste...
... however any other distribution of a plugin requires that you abide by the terms of the GPL.
Regards,
Tim Shead

Log in or register to post comments