-
Notifications
You must be signed in to change notification settings - Fork 49
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
Add license #77
Comments
Any updates on this? |
The information is from the wiki, and I assume the wiki documentation is under the GNU Free Documentation License because it says "Content is available under GNU Free Documentation License 1.3 unless otherwise noted." at the bottom of the wiki pages. You might want to ask one of the devs to clarify this. As far as I'm concerned, everything I've done on this is public domain, but maybe this legally needs to be under the GNU Free Documentation License too. |
I asked about this wayyyy back (probably a few years by now) on the Discord channel, but didn't get a clear answer... I'd say the save thing to do is to add the GNU License. (Then again there are also references to the FreeBSD license, but they are probably outdated). |
FreeBSD is outdated yeah, nothing remains of those docs. GNU Free Documentation License should be used, considering the amount of data taken straight from the wiki. Also all projects that use it should probably expose the JSON table in some way in order to avoid the GNU Free Documentation license affecting the entire project (cause it's invasive as f*ck) |
What do you mean by "expose the JSON table"? |
Say for love-atom you created the derivative |
The JSON expose table is pretty much solved (https://love2d-community.github.io/love-api/love-api.json). However the question of the license still remains. |
There's the question of the license of the content, but I'm curious about the license of this repo itself. What is the license of the authored code here, the code that scrapes and publishes the API? |
Yeah the license is complicated to solve. LOVE Wiki is licensed under GNU FDL 1.3 which means the whole Lua file in here is subject to that license and it has its own gotchas. Considering that someone also mentioned that the FDL is a viral license, this means the JSON output is also gonna be in FDL too. This also means, for an example, definitions file generated by LuaLS using the JSON file also falls under FDL. The legally questionable part is if the processing program should also fall into FDL. Ideally we'd like to use Creative Commons, however asking contributors to relicense is time consuming, if it's even possible (e.g. controbutions made by deceased person). Core LOVE developers like Sasha and bartbes likely open to relicense it. I also personaly don't mind relicensing my contributions to another license. Again, the issue is contributions by other people which requires their permission (considering the issue I mentioned before), rewritten, or removed. In short, the situation is complicated. |
I understand that licensing the output is a bit difficult. However, do you have any thoughts on the license of the web scraper itself? If somebody wanted to take that part of the repo and republish it, what license would they be able to use? |
I believe the web scraper is only used as building blocks. Nowadays the changes are hand-copied or hand-written from the wiki. You'd probably have to ask the original author of the original scraper script for that, unfortunately. |
In the löve discord, someone brought this issue up since they can't incorporate this into their project since they cannot provide a license for it.
The text was updated successfully, but these errors were encountered: