Slashdot Mirror


Palm Sued Over Palm Pre GPL Violation

zaxl writes "Palm is being sued by Artifex Software over the PDF viewer in Palm's Pre smartphone, which may violate the GNU GPL. Artifex alleges that Palm has copied Artifex's PDF rendering engine, called muPDF, and integrated it into the Palm Pre's PDF viewer application without the proper licensing conditions. The entire application must be licensed under the GPL if muPDF is part of the application. It seems more and more cell phones are shipping with open source code, but in a closed manner."

13 of 374 comments (clear)

  1. Settlement is probably inevitable... by Chysn · · Score: 4, Interesting

    ...since Palm mentions muPDF in their documentation, and they don't have a commercial license for it. Anyone in the software industry, anyone using libraries they didn't write, should understand that there's a difference between "open source" and "public domain."

    --
    --I'm so big, my sig has its own sig.
    -- See?
    1. Re:Settlement is probably inevitable... by MichaelSmith · · Score: 3, Interesting

      Maybe a palm pre owner should just ask for the source code. They may get it.

    2. Re:Settlement is probably inevitable... by Daniel_Staal · · Score: 3, Interesting

      The pre actually ships with a fair amount of code on it: It's based on a Linux system, after all. Hook it up as a USB drive, and there will be a folder with a copy of the GPL and the full code for much of the OS.

      If Palm actually shipped this without the right licensing, I'll bet it's an oversight. I'm betting the first Palm knew of this was when the lawsuit reached them.

      --
      'Sensible' is a curse word.
    3. Re:Settlement is probably inevitable... by Achromatic1978 · · Score: 3, Interesting
      Douglas Adams once posited in The Deeper Meaning Of Liff that the shortest measurable duration of time in the universe was "the time elapsed between the light turning green, and the driver behind you blowing his horn". I now beg to differ. It's the time between someone claiming a GPL violation, and the Open Source hordes clamboring for someone's head, regardless of merit.

      the violation is obvious

      No evidence of code out there.... and the app doesn't exist in a vacuum.

      If fact, it's quite clear what the problem is: violation.

      http://opensource.palm.com/1.3.1/index.html would disagree with you.

      I'd agree, it is quite clear what the problem is. But it's not a GPL violation...

    4. Re:Settlement is probably inevitable... by martin-boundary · · Score: 3, Interesting

      if Palm is dynamically linking rather than statically linking the software and isn't modifying the GPL software, they have a legitimate argument as to whether or not they have to comply with the more onerous licensing terms. Meaning that they don't have to license their application as GPL.

      Incorrect. If they statically link or dynamically link, they *must* license as GPL. What you're probably thinking of is if the libraries that they link to (dynamically or statically) happen to be LGPL, then they would have a choice. But if one of the libraries is GPL, then they have to show the complete source for each executable which links to it.

      It would be a bullshit license if they required that code that uses dynamic linking had to be GPLed as well.

      The GPL is not a bullshit license, it's very well thought out so that bullshit companies who just want to leach someone else's code can't do it.

  2. How hard is it? by Darkness404 · · Score: 3, Interesting

    How hard is it to just release a totally OSS version of your OS with all applications and stuff there and let people modify it and put it on your phone? I really don't see the point of trying to complicate things by closing the OSS. Release everything for free and you can take a lot more free code and not having to worry about paying lots of money when you are caught.

    --
    Taxation is legalized theft, no more, no less.
    1. Re:How hard is it? by bendodge · · Score: 3, Interesting

      The truth is in the middle. No, a truly open phone isn't going to wreck anything. But the carriers won't sell it, because that would endanger their nickle-and-dime model. They do NOT want people to see them as just a mobile ISP.

      Yeah, a handset maker could sell them directly to the customer, but that market is simply too small. Almost everybody leases their phone directly from the carrier. What we need is an Android-type device running on a WiMAX network that realizes it's just a dumb pipe...then we'll get some progress.

      --
      The government can't save you.
    2. Re:How hard is it? by Sentry360 · · Score: 5, Interesting

      Just got my N900 the other day... and the way this phone integrates with Skype is a thing of beauty. With WiFi + 3G and I have slim to no reason to use any minutes. You are right though.... carriers are afraid of this.. and I can see why... because who's going to pay $70 a month for lackluster internet service... while the whole arbitrary minutes to $ value is a good way to make a lot of money. Thus I had to order my phone from Dell... and T-Mobile gives you the same deals as a contract with no contract if you don't want any phone subsidies. I think all communications companies need to realize they're all going to be ISPs in the future, and the only thing they'll be able to charge for is how much bandwidth they deliver. I also think that T-Mobile starting to realize that... seeing as how they offer a $40 data-only plan... to which I'm considering switching eventually.... after I see how this Skype thing plays out over time...

  3. Re:Another example of Not Really Free by caseih · · Score: 3, Interesting

    Yeah the "industry" would love all open source code to be BSD so they can use it with impunity. Honestly let's stop this FUD. It's simply not true. Code under the GPL is no different from code under any other license. If you don't use it in compliance with the license then you are in a copyright violation situation, and the law allows financial remedies for such a case. The fact that it is GPL is irrelevant to this. Also the summary is incorrect. Palm is in a copyright violation now and have three choices: 1. remove the GPL code, 2. license the code under a different arrangement, and 3. License their derivative product as GPL.

    Why are you upset when copyright holders exercise their rights under the law to prevent a company from knowingly or unknowingly rip them off? How would BSD help this situation? Because the GPL actually has teeth we're starting to see the tip of the ice berg as far as willful license violations go. It's impossible to judge how much code is being used illegally in proprietary products. We're not talking GPL either. Any license. Microsoft code, code from some other source.

    Do liberty and capitalism allow one the right to violate copyrights? The GPL exists to protect the rights and freedoms of the developers and the end users while allowing free redistribution of code. I know of no other license that does this so effectively. In my opinion, if all open source code was BSD, there really would be no open source community or ecosystem. Like Adam Smith said, sometimes you have to balance self-interest with self-interest. The BSD doesn't do that really well. Certainly there is zero incentive for a company to release code under the BSD if it's just going to be used directly against them. The GPL allows companies to foster communities and promote development, while maintaining a level playing field for all the players.

  4. Re:Palm Mentions mupdf on the phone by thedarknite · · Score: 5, Interesting

    Further to your comment, I pulled down the source code from Palm (http://opensource.palm.com/1.3.1/index.html) and compared it to the the earliest source I could find on Artifex's site. Palm is using an earlier version (02-Mar-2008) of the muPDF source which is licensed under GPLv2. Artifex's available source(01-Jul-2009) is GPLv3.

    IIRC GPLv2 allows Palm to distribute the application as they are doing.

    --
    A game has objectives and is competitive, anything else is just play
  5. Re:Well by hairyfeet · · Score: 3, Interesting

    Which brings up a question I have had on my mind for quite awhile now since all these companies started getting sued for GPL violations, that nobody has really been able to answer: What is wrong with BSD? Is it broken, code sucks, bloated beyond repair, what?

    Because it seems like from a business standpoint, especially after RMS wrote the "TiVo clause" into GPL V3, that the business world would just avoid anything GPL altogether, and stick with BSD code that won't come back to bite them in the ass. After all it worked for Apple and MSFT, so what is wrong with BSD? There has to be SOME reason why these companies keep snatching GPL and dealing with possible lawsuits when you can do whatever you want with BSD and all is golden, so what is it?

    --
    ACs don't waste your time replying, your posts are never seen by me.
  6. Re:Palm Mentions mupdf on the phone by dovgr · · Score: 3, Interesting

    If you look at the Artifex license page (http://www.artifex.com/indexlicense.htm) you will actually see that they have a very strange interpretation of the GPL. They basically claim that you can't bundle Ghostscript together with non-GPL programs, or install it with the same installer. If they used the same legal advice for writing their licensing terms as they have used for filing the lawsuit, then it might turn up in the end that the whole case has no merit...

  7. Re:I'm confused by GreatBunzinni · · Score: 4, Interesting

    You seem to be confused. If we can talk about a copyright law consensus on slashdot, that consensus would be that copyright is there to benefit the authors but it should not be used as a weapon to hinder any social, cultural and educational use of any copyrighted work. That, oddly enough, is the premises where the french copyright tradition is built upon. That is the reason why commercial distribution of an unauthorized copy of a copyrighted work is frowned upon (i.e., piracy) but if you can (or at least should) be able to freely access copyrighted works without the need for an authorization of the copyright owner if it's strictly for personal use and your distribution does not have any meaningful and measurable impact on the commercial distribution. It's straight forward and it has been the norm in an awful lot of countries, at least until the US started to force it's version of copyright law onto the world.

    --
    Slashdot, fix your code or at least hire someone who is competent at it to do it for you.