Closed dem1995 closed 1 month ago
A different gaming project was informed by the Free Software Foundation that in order for their project to be compliant, the commercial video-game ROM that their project modified needed to be included.
This sounds to me very strange. LGPL is the LESSER GPL, it can be used with proprietary software:
The license allows developers and companies to use and integrate a software component released under the LGPL into their own (even proprietary) software without being required by the terms of a strong copyleft license to release the source code of their own components.
From https://en.wikipedia.org/wiki/GNU_Lesser_General_Public_License
Can I have a link about what are you saying?
My understanding was that the ROMs constituted corresponding application code despite not being distributed with the application, but I was/am pretty confused by this, too, though, given the LGPL's stated purpose (and the fact that seemingly this problem could be removed by just bringing an LGPL project into an LGPL-complying non-LGPL project, then using that secondary project directly). The licensing conversation happened before I joined the community in question, so it's possible something became misconstrued- I've reached out for more clarification on the other end and will let you know when I hear more.
Long time passed, closing here.
Background: I am part of a group working on an open-source (MIT-licensed) project, Archipelago, that adds networking and shared progression to video games. Under the terms of the LGPL, required data to run a program must be released in non-LGPL combined works that link LGPL software.
Problem: A different gaming project was informed by the Free Software Foundation that in order for their project to be compliant, the commercial video-game ROM that their project modified needed to be included. This is obviously not possible, as users need to use their own purchased games for ours and others' projects to remain legal. We are unsure of whether this LGPL ruling applies to our project (or if the licence would hold up in this way in court), but this possible forced noncompliance being the case, we are not eager to include software that might lead to legal issues down the line.
Solution: I am hoping that
frozendict
might be made available to our project or projects in similar positions to our project, to the extent that thefrozendict
developers are comfortable doing so. For example, "we thefrozendict
team, licensefrozendict
for video-game modding projects to usefrozendict
if complying withfrozendict
's licensing in all ways but the redistribution of the video games being modified or the hardware/software required to run those games".Some other solutions to this might be (where the above is #2):
frozendict
team for Archipelago to usefrozendict
if complying withfrozendict
's licensing in all ways but the redistribution of the video games being modified or the hardware/software required to run those gamesfrozendict
team for open-source video-game modding projects to usefrozendict
if complying withfrozendict
's licensing in all ways but the redistribution of the video games being modified or the hardware/software required to run those gamesfrozendict
team for projects to usefrozendict
if complying withfrozendict
's licensing in all ways but the redistribution of video games or hardware/software/data that development members have no control overThank you for your time and consideration of this request, as well as your continued efforts on the
frozendict
library.