Slashdot Mirror
Ask Slashdot: Where Do You Draw the Line On GPL V2 Derived Works and Fees?
First time accepted submitter Shifuimam writes "I downloaded a DOSBox port for Android recently to get back into all the games of my childhood. Turns out that the only free distribution available hasn't been updated in nearly two years, so I looked for alternatives. There are two on Google Play — DOSBox Turbo and "DOSBot". Both charge a fee — DOSBox Turbo is $3.99; DOSBot is $0.99. The developer of DOSBot says on his Google Play entry that he will not release the source code of his application because it's not GPL, even though it's derived from source released under GPL v2 — this is definitely a violation of the license. The developer of DOSBox Turbo is refusing to release the source for his application unless you pay the $3.99 to "buy" a license of it. The same developer explicitly states that the "small" fee (although one might argue that $3.99 is pretty expensive for an OSS Android app) is to cover the cost of development. Unless I'm misreading the text of GPL v2, a fee can only be charged to cover the cost of the distribution of a program or derived work, not the cost of development. And, of course, it doesn't cost the developer anything for someone to log in to Google Play and download their app. In fact, from what I can tell, there's a one-time $25 fee to register for Google Checkout, after which releasing apps is free. Where do you draw the line on this? What do you do in this kind of situation?"
distribute the source on demand to ANYBODY requesting it for the price of materials
Not anybody -- any third party. That's a specific legal term and the specific meaning of the third party is not defined. The GPL v3 clarified it as to mean that the first party (distributor) only has to provide source code to a third party if the third party received a GPL-licensed work from the first party. If it came down to it, a judge and jury would probably use the GPL v3 rules for an ambiguous v2 license dispute.