-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Which is the correct license? #2071
Comments
The GPL in the installer is from when Qt was licensed under GPLv2 - so the combination of Mumble and Qt would have to be GPL licensed. Now, Qt is under LGPL 2.1/3. For other GPL'd software, we have a license exception (I.e. ZeroC Ice) We should be able to ship Mumble's BSD license along with a trail of all third party licensing to make the licensing situation as seen through the installer a bit less confusing. So: Mumble's source is under a BSD license. I don't believe we have GPL'd dependencies that force the final Mumble distribution to be distributed under the terms of the GPL anymore. |
@mkrautz We should drop that page from the installer in any case. The GPL doesn't require it and it might scare people off even when with mumble the restrictions of the GPL on the installer are pretty much meaningless (we'll still have to put a license somewhere obviously). That being said it makes my brain hurt even trying to figure out what the binary distribution is licensed under.
|
Update: We don't have a license exception for Ice. I took a closer look at the license. |
I agree with @hacst, we should drop the license page from the installer. |
Is this actually a blocker? What's our todo here? Just remove the page? Looking at the installer I see it installing license files for speex etc. which have not been touched in a while. Is this redundant with our license dialog or actually required and must be updated? |
In https://github.com/mumble-voip/mumble/blob/master/LICENSE , the license of mumble looks like new BSD license, but the installer shows GPLv2 as the Mumble's EULA.Which is the correct license?
The text was updated successfully, but these errors were encountered: