-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
License #8
Comments
Heh, yes, this is a little complicated. Some more context:
And more complicated context:
Tricky! |
Apparently this is also the zlib/libpng license, so it should be compatible as well.
Then I think it's a safe assumption that
Well then, I guess that alone settles it. The repo (this one at least) should be then licensed as GPL 3.0 |
Another bonus: The old modules project referenced the GPL in Google Code, but the repo then continued to have LICENSE files referring to MIT/zlib licenses for the individual modules. However amx wasn't included in that repository. I'm not quite sure where the old amx module code was located.
No. Modules are derivatives of the publicsdk (zlib license). The modules do not link to MTA itself and are hence not convered by the GPL.
That's assuming the file was originally GPL licensed. For example, something that's MIT licensed can be relicensed under GPL later on, without affecting old copies. |
Reading very carefully, here's the difference between the publicsdk license and the zlib license. Specifically the phrase "including commercial applications" vs. "excluding commercial applications"... |
Boy... What now then? To be honest I don't feel very comfortable working without a License. The publicsdk is inside the mtasa repository which is GPL 3. The Sockets module seems to be under GPL 3, and the MySQL Module (although old) includes MySQL Community Edition source which also seems to be GPL. These are first party modules made by MTA. This is a time wasting mess... we're just better off assuming the publicsdk is GPL 3 as well, just like these first party modules did... |
I mean I think it's safe to assume the license is this https://www.github.com/multitheftauto/mtasa-blue/tree/master/Shared%2Fpublicsdk%2FLICENSE since that's the actual original source. (The publicsdk folder being in a repo surrounded by GPL doesn't matter because the publicsdk folder has its own license) |
I noticed this repo and mtasa-resources don't have a license. I was looking to add a file from AMXModX, which is GPL 3.0. (namely a slightly old version of format.cpp, which is used by SA-MP to format strings in custom versions of the
printf
andformat
. The natives provided byamx_ConsoleInit
are not actually used). mtasa-blue is GPL 3.0, so my assumption is that everything here also is GPL 3.0, but I'm not 100% if that's the case. It would be ideal to specify the license ASAP to avoid any problems if we want to use external stuff.On the other hand, AMX/Pawn uses the "zLib/libpng" license which is very permissive (and therefore GPL compatible), so no problems on that regard.
As a side note, I realized SA-MP violates GPL because it doesn't publicly provide the source of this file!
The text was updated successfully, but these errors were encountered: