So you support the position that the GPL infects the whole mod but then go around proclaining that we should just surrender all rights to decide what we can do with our mods? I wouldn't mind if it was just the lua stuff, that can be used in any freaking way you want (IMO code this simple is not a creative work because there's only a limited number of approaches which can lead to the goal) but I'd highly object to being forced to release creative works under the GPL because some stupid helper script was GPL. I don't want to surrender my right to tell people making shitty 3rd rate unit mash mods to fuck off and leave my units alone unless I explicitely decide to do so (e.g. Kernel Panic, I don't care). I also want to reserve the right to release my work into the public domain or under a BSD license, all of which I lose if I let any GPL code into my work.jK wrote:why the hell, are guys such selfish? A lot of ppl spend hundreds of hours into the spring engine code and you don't want to make your <12h content public (or only limited) available?
I don't want to ask each time the author, if I can use his model or if I want to modify the texture a bit etc.
Not to forget, how much code you used/read to write/make 'your' gadget/content.
And it isn't that you want to earn money with your work, you only don't want to that other ppl use 'your' work as they want. Imo this is greedy ...
Additionally I cannot grant a specific mod a right to use my work if that mod uses the GPL and I don't want to give a permission to everyone.
Furthermore, I think using anything that you don't hold the copyright to (Gundam, TA) automatically prevents you from GPLing your mod because you cannot attach a license to that IP.
In order to avoid this I can just avoid including things like the gadget handler into my mod, I could just write everything straight into main.lua and not use modules. It will be the same for me, after all I don't need modules when my code is meant for my mod anyway but if I were to allow others to use that lua code they wouldn't have modules and would have to manually separate the features they need, making the code much less reusable.
All of this would have been resolved by using a license designed to be put on modules, i.e. the LGPL.