Closed source plugins using SDK

I want to clarify that closed source plugins using the SDK is OK. If you want to sell your plugins, that's also fine. I haven't sorted out the license yet but I'm going to try and find a suitable one that allows derivative works to do this. If anyone has any suggestions for a suitable license, let me know <img src="{SMILIES_PATH}/icon_smile.gif" alt=":)" title="Smile" />

GPL/GNU?

If a suitable open source license doesn't already existing maybe dual licensing is the solution. Use a standard license like GPL for the C++ source code but then have a second license that only applies to plug-in developers that doesn't require publishing their source code under the GPL but only covers plug-in development so they can't use it to make proprietary fork of Construct without your permission.

Can't we use something like Creative Commons Licensing?

http://creativecommons.org/

Hope that helped, I'm not sure it fits for the application, but you can check it out!

Best,

Joystick

I fear CC is a bit too simple.

snoopbaron

Perhaps a BSD license, with a clause that states, closed source plugins require an endorsement.

With the endorsement granting them the right to use a license relating only to that specific plugin.

So long as that license, the plugin, or any of its derivatives, does not imply any warranty by Construct.

i remember seeing something like this over here

http://www.gnu.org/copyleft/

couldnt you make plugins have no licensing terms? allowing the developper to apply their own terms and distribute them however they please.

I guess "newt" CC it's a bit simplified.

Yes, "QuaziGNRLnose" that seems a good idea,

It's something that reminds me of the licensing that the "VST" plugins standard has and it's available from http://www.steinberg.net/en/company/3rd ... loper.html check it out.

Greets!

Panoz