GPL?
-
I was thinking about it earlier today. I think, as FLHook matures and becomes a large player in how servers work, people should start looking to put an official license on the code. It’d help define the goals of the software and hopefully further its recognition as a great tool.
I suggest GPL because it goes along the mentality of sharing. FLHook wouldn’t be where it is now without sharing, so I thought things should keep going that way. It’d be, in my opinion, a great thing if people had to release whatever modifications they might do on existing source code. I’m sure we would all benefit from the increased sharing we would witness. The GPL is also a very recognized name, it’d give the whole project more credibility and an “official” flavor, I think. Heck, it could even get on SourceForge?
It was just a simple thought I had; sharing is what got us here, sharing should be kept at the very center of FLHook.
-
FLHook is actually already licensed under the GPL (if I’m not mistaken) and has its own Sourceforge page. It just hasn’t been updated at all.
-
Disclaimer: I’m not a copyright lawyer (or any other kind of laywer) so I don’t know what I’m talking about…
The version on source forge claims to be GPL’d but I’m not sure it should be as I don’t know if mc_horst was asked if this license could be applied. From a practical perspective this is probably okay as he released the source to share it and so applying the GPL is probably okay.
I support the idea of releasing flhook-plugin under GPL but there are a few things I think need to be done:
- mc_horst agrees
- wodka agrees
- any other contributors to the current code base agree for their parts (motah I guess?)
- copyright statements added to all files, the readme and the GPL license included in the distribution/
I’d be happy with my contributions (as small as they are) being released under GPL. Currently my plugins are under ‘public domain’ rather than GPL but I have no issue with changing them to GPL.
-
Back in the day when “that guy” brought FLHook to sourceforge, mc_horst was asked if he would be okay with that (also with a GPL license) and he agreed.
So I also chose GPL for the google code repository.Plugins however can have the license they want, since they are a seperate entity.
Not sure if we really need copyright statements in the files etc…