4 ms·
I don’t understand what exactly Apple’s objection is, given that the original is GPL’d open source and not present on the app store. One person’s “knockoff” is
by layer8 3y ago
I don’t understand what exactly Apple’s objection is, given that the original is GPL’d open source and not present on the app store. One person’s “knockoff” is another person’s fork.
- Retric 3y agoApple doesn’t want the App Store filled with 100,000 copies of the same thing. So they are very strict around how different forks must be because of how low effort these copies are. The rules are simply a pragmatic response to their business goals.
- layer8 3y agoBut there was no alternative present on the app store. Apple also doesn’t define any clear rules here, they seem to decide in a very ad-hoc fashion.
- asddubs 3y agoit's not a fork unless source is available (even if it's a name replace copy-paste job) and other license terms are followed.
- layer8 3y agoTrue, but that’s not the rationale Apple gave here. I would understand if they rejected the app on grounds that it is violating the GPL terms, which would be rather easily fixable by the submitter, and then the app could be reapproved.
- asddubs 3y agoI'm not positive the app store terms are compatible with the AGPL
- Retr0id 3y agoThe source has a GPL license next to it, but there are additional licensing conditions that make it proprietary: > Licensing > The GBA4iOS codebase is distributed under the GNU GPLv2 license. That being said, I explicitly give permission for anyone to use, modify, and distribute my original code for this project without fear of legal consequences — unless you plan to submit your app to Apple’s App Store, in which case written permission from me is explicitly required. (emphasis mine) https://bitbucket.org/rileytestut/gba4ios/src/master/ https://bitbucket.org/rileytestut/gba4ios/src/master/
- lxgr 3y agoThat clause is not compatible with the GPL, to which the author is bound in this case (since he does not own the copyright for all of the emulator cores he's including).
- Retr0id 3y agoIf the GBA4iOS author is infringing the GPL license by including 3rd-party GPLed code in a not-GPL-compatible codebase, does that make their 1st-party code any less proprietary? My non-lawyerly interpretation is that both parties seem in the wrong.
- lxgr 3y ago> does that make their 1st-party code any less proprietary? I believe that is the case, yes. The GPL has a "sticky clause" that attempts to make all code deriving from/including GPL-ed code GPL-licensed itself, without requiring the original author to be the one that enforces this: > Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. I have no idea if this practically works in court, though.
- boomlinde 3y ago"That being said, I explicitly give permission for anyone to use, modify, and distribute my original code for this project without fear of legal consequences — unless you plan to submit your app to Apple’s App Store, in which case written permission from me is explicitly required." Emphasis mine. The author is giving permission to use their original code but doesn't re-license anyone else's code. They're explicitly offering their own code under a dual license.
- axus 3y agoPerhaps it is in Apple's interest to allow additional restrictions on the GPL. They're certainly not required to distribute it.
- lxgr 3y agoHow would Apple "allow additional restrictions on the GPL"? They're not the copyright holder of all GPL-licensed code! I suppose they could try to establish something like a "first/original app wins" clause to prevent distribution of builds of paid-but-GPLed iOS apps, but that feels like it would at least clash heavily with the intent of the GPL.
- axus 3y agoBy removing apps from it's store that don't comply with those restrictions. GPL only applies if Apples distributes. Makes me wonder, if App Store distributes a GPL app which doesn't link to source, is Apple obligated to distribute the source? Seems like they'd have to.
- fweimer 3y agoSome of the dependencies/vendored code are GPL version 3 or later (see e.g. https://bitbucket.org/rileytestut/gba4ios/src/master/emu-ex-plus-alpha/EmuFramework/src/CreditsView.cc https://bitbucket.org/rileytestut/gba4ios/src/master/emu-ex-...). This license may require handing over signing keys in the iOS context (but I have not really analyzed the scope). The project README says it's “distributed under the GNU GPLv2 license”, which isn't helpful, either. Under the usual reading, the GPLv2 is only compatible with the GPLv3 if the GPLv2 licensing declaration comes with the “or later” clause. Of course I don't know if Apple even looked that far.