Skip to content
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

Open
wojas opened this issue Apr 10, 2020 · 3 comments
Open

GPL license potentially problematic for App Store distribution #2

wojas opened this issue Apr 10, 2020 · 3 comments

Comments

@wojas
Copy link

wojas commented Apr 10, 2020

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.

@wojas
Copy link
Author

wojas commented Apr 10, 2020

Perhaps an explicit exemption as suggested here would work:
https://opensource.stackexchange.com/questions/8674/gpl-with-license-exception-for-ios

(Again, I am not a lawyer)

@achrinza
Copy link

achrinza commented Apr 10, 2020

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:

  • Switch to a more open license (Apache 2.0 or MIT)?

    GPL 3.0 can make it difficult for certain users (or other projects) to adopt the project. This can be due to restricted IPs or policies.

    • While Apache 2.0-licensed code can be used in a GPL v3.0-licensed projects, the other way is not possible.

    • Many projects (notwithstanding Linux and alike using GPL v2.0) use Apache 2.0 or MIT

    • Apache 2.0 (or even better, MIT) is more compatible with other licenses.

    • Case in point, Twitter Bootstrap had to re-license to MIT to support Drupal's GPL license.

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.

@M-Rick
Copy link

M-Rick commented Jun 18, 2020

How do you explain this so?
https://en.wikipedia.org/wiki/List_of_free_and_open-source_iOS_applications
There are quite a lot of softwares under the GPL license v2 and v3 in the App Store.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants