5 ms·
Well, the EFF has a long list of the things they hate about Apple's licenses. The FSF pretty much sees eye-to-eye with them, so that seems like a good starting
by Natsu 16y ago
Well, the EFF has a long list of the things they hate about Apple's licenses. The FSF pretty much sees eye-to-eye with them, so that seems like a good starting place. Here's the link:
http://www.eff.org/deeplinks/2010/03/iphone-developer-program-license-agreement-all http://www.eff.org/deeplinks/2010/03/iphone-developer-progra...
After reading that, my best guess for the GPL violation would be Section 7.2, which "makes it clear that any applications developed using Apple's SDK may only be publicly distributed through the App Store."
But the worst part for Apple, I would think, is the review. Even though it's not their fault that some developer submitted an infringing application, they approved it. IANAL, though, so I don't know exactly what Apple is on the hook for. My guess would be that Apple will pull the application and blame the developer, but I don't know where it'll go from there. It really seems like they're more interested in Apple than the developer, after all.
- yummyfajitas 16y agoIANAL, though, so I don't know exactly what Apple is on the hook for. The GPL applies to anyone who distributes a GPL product. Apple is the distributor.
- sigzero 16y agoI am not sure that is going to fly though. Apple is the conduit in this case. The developer is still the distributor and has chosen to do so through the store.
- DrSprout 16y agoFarmer : producer. Walmart : distributor. Car manufacturer : producer. Car dealership : distributor. Software developer : producer. Apple App Store : distributor.
- sigzero 16y agoI don't think that scenario holds for the actual "license" and it would just make the GPL suck that much more if you try to hold Apple to something like that.
- chc 16y agoYou're really ignoring the obvious facts in favor of arguments over tiny minutiae. The App Store is a store. Not a conduit, not a dumb pipe, a store. Apple maintains it, Apple choses what to stock there, Apple specifies the terms of purchase and Apple makes a profit off each item it sells there. The developer just gives Apple his app to put in its store. Analogously to this case, if my local store doesn't refrigerate its milk properly, I don't sue the dairy farmer. Apple's App Store is a store in exactly the same sense.
- ahoyhere 16y agoYour analogy fails miserably. If your grocery store fails to refrigerate otherwise perfectly good milk, the analogy to the App Store would be that Apple injected GPL code into the app. No, if Nabisco violates a copyright agreement with the box design of some cookies, and your grocery store sells them (unknowingly), the grocery store is not at fault.
- chc 16y agoThe developer did not place any illegal restrictions on the app. Those are all imposed by Apple's store.
- jacobian 16y agoHm. It would seem that similar logic would apply to, say, an ISP which "distributes" GPL produces over its pipes and applies additional restrictions via its EULA. This sort of "if you touch GPL in any way" reading isn't a very positive one for copyright in general, and I think it'd be a pretty bad faith argument to make. I think, then, that the FSF's argument must be a more nuanced one; but like pierrefar I can't quite suss out what, exactly, they object to. The App Store obvious violates the spirit of the GPL in about a dozen ways, but it's unclear to me how the app store violates the letter of the GPL.
- DrSprout 16y agoDid you read the root post in this thread? Apple is distributing GPL code, and therefore Apple is responsible for providing source. Cut and dry, cannot get any simpler. If you distribute binaries compiled from GPL source, you are required to distribute source. Apple is not distributing source, case closed. Furthermore, the App store license forbids end-users from redistributing binaries, which again, is a cut and dry violation of the GPL, since it not only says the opposite, but that you must allow them to distribute binaries and source. This isn't an "if you touch GPL in any way" problem. It's a "if you give someone something under the GPL, you must follow the GPL." Apple is not a dumb pipe. They are hosting the software.
- jacobian 16y agoDid you read the root post in this thread? Why do you need to do this? I'm trying to honestly engage with the ideas presented here, and what's clear to you isn't clear at all to me. Why do you assume I'm operating in bad faith? Apple is not a dumb pipe. They are hosting the software. Clearly, and clearly it's an important difference. But I'm not so sure where the legal line is drawn. What about SourceForge? They have a EULA, right? Have they carefully written one that's compatible with the GPL? Or what about language package hosts like RubyGems, PyPI, or CPAN? Do they need to be careful about any terms and conditions to avoid violating GPL'd apps placed on their repositories? I'm not a lawyer -- are you? -- and I certainly don't claim to be an expert here. But even if you think I'm an idiot the fact is I actually know quite a good deal about copyright and software licensing, and I still don't see what the FSF's particular legal argument is. And I do want to understand their argument, especially as it applies to other types of "app stores" that might distribute open source code on behalf of other users.