-
Notifications
You must be signed in to change notification settings - Fork 201
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
Lua script licenses need to be cleared up #638
Comments
Perhaps we could have some kind of catch-all license file somewhere? It would mean that we implicitly require all script contributions to use the same license. |
Sure, that would work. One other thing that should be done, though: everyone who has contributed code should be reached out to, asked to confirm that their contributions can be distributed under GPLv3. It might also be worthwhile to ask if later versions of the GPL can be used, kill two birds with one stone. |
Since I saw this, and maybe to save you some work, all my current and any future contributions can be licensed GPLv3+. |
Ditto; all my past and future contributions are licensed GPLv3. The
Just my ha'penny worth ;) Phoenix... |
Same here. Every bit of code I have contributed can be considered under GPLv3 or later. |
I don't know if this is really necessary legally (but licensing is complicated), since it would generally be assumed that all code is under the same license as the rest of the project unless otherwise stated (the If this is an issue for the lua code, it probably applies to the xml files as well. |
Alright, I've gone through the list of contributors and looked for the ones who contributed to things in the dat directory without indicating a license explicitly, whose contributions are possibly copyrightable (so none of the people who just committed a couple of misspellings). I also sent an email to those who had an email address listed on their GitHub profile. This is the list of people who still need to be contacted (I don't know how to do that, does GitHub have a personal messaging system?): nloewen And this is the list of people who I have already contacted via email: xales |
I received the email. A link to this thread would have been appreciated. I thought all my contributions were gplv3, but I agree to license them as GPLv3. I would probably have ignored the email if I didn't find this thread. @onpon4 github removed messaging ages ago, but if you hi-light them as I did you they should receive an email unless they've changed that in their notification settings I believe. |
Ah, alright, thanks, reynir. :) I got a response to the email I sent to Lukc:
|
Alright, so shouting out to everyone who hasn't been contacted yet: @nloewen And those who haven't responded to the email I sent (yet): @xales Please help resolve this issue by commenting here:
|
Email response from Scaatis:
|
Do I only have to reply in this comment or make some sort of change ? But either way, everytthing i committed is GPL3. |
@PhilmacFLy responded:
The second question I asked was about versions of the GPL later than 3, so that means (if I understand correctly) his contributions can be GPLv3+. |
Just the reply. Thanks! :) |
Yep that was exactly what I meant :) |
Yes and yes |
Yes, "GPLv3 or later" for whatever I've contributed. |
You can attach whichever GPL you want to my contributions. |
Yes to both Havent seen activity here in a while. If those issues that were blocking me On Thu, Aug 11, 2016 at 6:39 AM, rkulhanek notifications@github.com wrote:
|
Yes and yes to both. -Micah On Thu, Aug 11, 2016 at 10:08 AM, AvanWolf notifications@github.com wrote:
Micah Mumper, M.A. |
Yes to both |
@AvanWolf What specific issues prevented you from continuing development of the Thurion? |
All contributions I made to Naev on or before July 10, 2016 are distributable under the conditions of the GNU GPL v3. They are also distributable under any later versions of the GPL, or under any OSI approved license this project moves to in the future. To the best of my knowledge, I have not made any contributions after July 10, 2016 but I started employment on July 11, 2016 and I want to ensure that I don't accidentally relicense something I don't have the rights to. |
Sure, no problem. |
I aree that my contributions can be distributed under GPLv3 and later. |
Yes to both as well. On Fri, Aug 12, 2016 at 3:22 AM, nenau notifications@github.com wrote:
|
My contributions may be distributed under the GNU GPLv3 and any subsequent versions of that license. |
Sorry about the wait. |
Same for me, best! On 12/08/16 23:57, Old T. Man wrote:
|
Same for me: |
I must have missed this when clearing out my (underused, old) Email. My bad. :( I don't really recall adding anything worth copywriting, but if so, then GNU GPLv2 applies to them. |
It looks like this didnt go through, it was jut saved as a draft The engine was missing support for features that they needed in their Furthermore, apparently putting the spritesheets on git was overburdening On Thu, Aug 11, 2016 at 8:24 AM, Ian D. Scott notifications@github.com
|
Putting the sprite sheets on git doesn't exactly overburden it, but the memory footprint caused by using sprite sheets is getting too large, so we need to switch to 3D model rendering. |
@AvanWolf I think the homing weapons (#298) should be fairly simple to implement. I may take a shot at implementing them when I have time. Using 3D models instead of sprite sheets will be necessary for adding many more ships. #511 partially implements it, but still has issues. Among other things, we'll need to actually have all the 3D models, which is a problem for some. @Deiz may have them, but he hasn't been around lately. @Deiz Are you reading this? |
So @bobbens or @BTAxis, how about adding that license notice, probably to the readme? It doesn't need to be anything complicated, just something like "everything in this repository is under at least version 3 of the GNU General Public License (see LICENSE), with the following exceptions: {list of exceptions}". |
I can add it to naev.h as currently done, and also to the (new) Readme.md. However, I am not sure what files are exceptions besides the data stuff, which are tracked separately. |
Just passing by - hunting for information about practical situations where the GPL is interacting with Lua scrip situations and I spotted a glaring issue that will bite you if not resolved: as written here @Lineth specifically licensed their contributions as GPL version 2 ONLY which is not compatible with GPL version 3 (or, at the user's option, any later version)... :
|
Reynir sent me an email response:
The only significant thing about this is that he said he would be okay with newer versions of the GNU GPL as well as version 3 (his original post here only said "GPLv3"). |
These are still uncomfirmed:
Potential issues:
|
Ok, I forgot I contributed, thanks for pinging. Yes and yes to both questions. |
since I saw myself, in the "potential problems" box, and I hope i can make this official here: |
Probably they meant v3, but GPL compatibility isn't needed for artwork (projects mix GPL code with CC artwork all the time). Artwork licenses are actually documented very well under ARTWORK_LICENSES. I think it would be perfectly fine at this point to just put a statement of intent in the readme that all Lua and XML files are GPLv3 unless otherwise noted.
They haven't made any contributions in that time period so that's fine. |
If they're not at least under the GNU GPL v3, they're infringing copyright. But I don't like this situation where none of the Lua files have any sort of license information attached to them. This needs to be addressed somehow. It needs to be made clear that all Lua scripts are licensed under at least version 3 of the GNU GPL. Preverably, every Lua script should have some sort of notice on it.
I was trying to address this with my "copyright" branch, but it was never merged.
The text was updated successfully, but these errors were encountered: