Unclear Licensing
Elzair opened this issue · 4 comments
I don't know what are the legal implications of the previous license. As
far as I am concerned you can do whatever you want with my code.
On Aug 9, 2016 3:34 PM, "Philip Woods" notifications@github.com wrote:
What is the LICENSE on this? Is it GPL, or is it BUILDLIC
http://svn.eduke32.com/eduke32/polymer/eduke32/build/buildlic.txt—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#48, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABKbkO4ju9rgHcutMr9gHanrnJ4_igaFks5qeQBbgaJpZM4Jgl2B
.
Thanks!
First of all: I'm not a lawyer.
I think the engine code (Engine/src) comes from Ken Silverman and is BUILDLIC but the game code (Game/src) was published by 3D Realms under GPL. As far as I know the final compiled binaries are therefore non-distributable (in theory).
As far as I am concerned you can do whatever you want with my code.
That would apply to code generated by yourself like Engine/src/network.c I guess. I think it would be still good to have an exact license or disclaimer for those files. MIT (my personal favorite), WTFPL or Unlicense might be good candidates.
I know this issue is 2 years old at this point, but the point stands that it is probably good to put a root level license on the repo to clarify the various licenses at play here. I'd open a PR but I don't feel I have enough of a handle on it to even take a stab at it.
Neovim does a prettty good job calling out previous licenses and then licenses future work.
I think the engine code (Engine/src) comes from Ken Silverman and is BUILDLIC but the game code (Game/src) was published by 3D Realms under GPL. As far as I know the final compiled binaries are therefore non-distributable (in theory).
One of things I would add to http://fabiensanglard.net/duke3d/code_legacy.php is impact of the BUILDLIC license. It's a bespoke license that breaks compatibility with other widely accepted free software licenses.