-
Notifications
You must be signed in to change notification settings - Fork 135
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
GPL license potentially problematic for App Store distribution #2
Comments
Perhaps an explicit exemption as suggested here would work: (Again, I am not a lawyer) |
A quick search yield more sources that concur:
While I am not a lawyer (IANAL) either, it does seem like a weird choice of license. While GPL does have good intentions, it's incredibly restrictive of its compatibility with other open source licenses. It was good for major projects such as *NIX systems. But in an open source community where Apache 2.0 and MIT becoming more ubiquitous, it tends to add more restrictions than actual freedom to use the source code. To quote from opentrace-community/opentrace-cloud-functions#2:
IMO, we shouldn't be forcing other people to comply to GPL. This may hinder adoption and cause potential users to look for a different solution. Instead, we should provide increased flexibility by using a more open license (preferably MIT as it's the least restrictive, widely used, and one of the most compatible license) and then encouraging people to contribute back to the main project. |
How do you explain this so? |
I am not a lawyer, but the GPL license could potentially be problematic for App Store distribution.
An old link about the issue: https://www.fsf.org/news/2010-05-app-store-compliance
I'm not sure if anything has changed since then, but the basic issue of restricting distribution still appears to hold.
The text was updated successfully, but these errors were encountered: