I learned LimeSurvey is GPL 2. But how about the code that works with LimeSurvey or changes things on it?
If I publish a plugin for LimeSurvey or code sniplets to put into questions, what license must I publish it under?

If it is a plugin and you want to distribute it and it would not work without LimeSurvey (= code dependency) then it needs to be under GPL2 or later, or any other compatible license.

If it is a separate application and maybe only uses the LimeSurvey database then you can use whatever you like.

thank you. So that's a combined work then.
And if it's just javascript that goes into a question?

c_schmitz wrote:

If it is a plugin and you want to distribute it and it would not work without LimeSurvey (= code dependency) then it needs to be under GPL2 or later, or any other compatible license.
 

I'm not sure about this, there are discussion about WordPress template NOT GPL

See make.wordpress.org/themes/2015/08/15/themes-should-be-100-gpl/

In my opinion : you can create Plugin with a private license. You just need to don't copy/paste existing plugin licensed under GPL OR more restricted license (AGPL for mine, i like to have a more restricted free license (always contribute to original)).
 

Templates are usually not alot of code, so yeah, I can understand that view/exception.

to make it even more complicated, if I modify things that come from bootstrap for instance, which is licensed under MIT, I am not bound to MIT, but as I intended it to be running in LimeSurvey, am I bound to GPLv2?

c_schmitz wrote:

Templates are usually not alot of code, so yeah, I can understand that view/exception.
 

But for plugins, you can create a plugin for scratch too.

Using init and $this->getEvent didn't move code to GPL in my opinion.

You can disallow promotion of non GPL compatible licence plugin.
Bit then : what for Offline surveys Android app ?
I have a plugin from an official limesurvey partner with obfuscate code and without GPL license too : are you OK with that ?

> Using init a d $this->getEvent didn't move code to GPL in my opinion.

Sure, but only if the rest of the plugin code does not use any other core functions and re-implement all necessary logic by itself.

code obfuscation violates GPLv2 significantly as it makes it harder to read and modify:
www.gnu.org/licenses/old-licenses/gpl-2.0.html

The source code for a work means the preferred form of the work for making modifications to it.

yjeanrenaud wrote:

code obfuscation violates GPLv2 significantly as it makes it harder to read and modify:

 

I know that,

It's more a question to Carsten
Did selling not free plugin are allowed by LimeSurvey official Partners (on www.limesurvey.com/ )