Slashdot Mirror


OpenOffice.Org Now Under LGPLv3

I Don't Believe in Imaginary Property writes "Sun has moved OpenOffice.org to the LGPLv3 license. In his blog Sun's Simon Phipps cites worry over software patents as being one of their main reasons for this move: 'Upgrading to the LGPLv3 brings important new protections to the OpenOffice.org community, most notably through the new language concerning software patents. You may know that I am personally an opponent of software patents, and that Sun has already taken steps in this area with a patent non-assert covenant for ODF. But the most important protection for developers comes from creating mutual patent grants between developers. LGPLv3 does this.'"

24 of 107 comments (clear)

  1. Software by sm62704 · · Score: 5, Insightful

    You may know that I am personally an opponent of software patents

    Software is the only thing you can have both a patent AND a copyright on.

    --
    mcgrew's razor: Never attribute to stupidity that which can be explained by greedy self-interest
    1. Re:Software by aerthling · · Score: 2, Informative

      Don't patents apply to the method and copyright to the implementation?

    2. Re:Software by Anonymous Coward · · Score: 2, Interesting

      The idea is patented. The very specific implementation (the code) is copyrighted.
      The patent on the idea will eventually expire. The exact specific code used in their specific implementation will remain copyrighted longer.

      Imagine someone long ago patented the idea of the book when they wrote the first one and copyrighted it. The patent on the idea of books would long ago have expired, but each individual book can still be copyrighted for a certain period of time.

    3. Re:Software by sayfawa · · Score: 4, Interesting

      Unfortunately, plots of books and movies are also being patented by people like this.

      --
      Free the Quark 3 from asymptotic confinement! Bring your charm! Don't get down! All colours and flavours welcome!
    4. Re:Software by sm62704 · · Score: 4, Insightful

      Those people belong in prison.

      --
      mcgrew's razor: Never attribute to stupidity that which can be explained by greedy self-interest
    5. Re:Software by skoch · · Score: 2, Informative

      > Software is the only thing you can have both a patent AND a copyright on.

      This is not true, Mechanical components have patents on the idea, and copyrights on the drawings of the machine that implement the idea. Software is the same way, patents on the idea, but copyrights on the source code and executables.

      That does not make software patents a good idea however.

  2. Ah, the LGPL, the "sane" GPL by BadAnalogyGuy · · Score: 5, Funny

    The LGPL is in no way "lesser" than its hideously deformed cousin the GPL. Where the second one takes and takes, the first one gives and gives. It promotes community through sharing rather than through vigorously tilting at windmills.

    If the LGPL were a presidential candidate, it would be Barack Obama -- "Yes we can." The GPL would be Ron Paul -- "We need the gold standard and protectionist trade."

    1. Re:Ah, the LGPL, the "sane" GPL by Anonymous Coward · · Score: 3, Funny

      I guess there is a reason you are "BadAnalogyGuy"

    2. Re:Ah, the LGPL, the "sane" GPL by Anonymous Coward · · Score: 5, Funny

      Never before in Slashdot history have you so completely earned your screenname. I salute you, sir.

    3. Re:Ah, the LGPL, the "sane" GPL by BadAnalogyGuy · · Score: 3, Informative

      Because it takes as payment the entire work of someone who relies on the supposedly "free" software.

      The LGPL only requires such payment if changes are made directly to the LGPL'd work itself.

    4. Re:Ah, the LGPL, the "sane" GPL by webmaster404 · · Score: 4, Insightful

      So wait... How does that work? Chances are if someone relies on free software outside of free software projects (such as Debian, Mozilla, Ubuntu, Open Office, etc.) they work as a business and use free software to get the job done. Most of the time that software never leaves the company so the company could say that it will provide the source to anyone who requests it (being nobody) the company is in no way obligated to publish the modifications they made. They just can't prevent someone who has the source from uploading it to a server and having people download it.

      --
      There is no "disagree" moderation, and troll, flamebait and overrated are not valid substitutes
    5. Re:Ah, the LGPL, the "sane" GPL by Knuckles · · Score: 2, Insightful

      Because it takes as payment the entire work of someone who relies on the supposedly "free" software.

      How so?

      Entire work: you mean that, e.g., the entire product portfolio of IBM becomes copylefted as soon as they use GPl'ed software in one of their products?
      supposedly "free": you mean that the GPL changes its clauses after you incorporated GPL'ed code into your product?

      --
      "When I first heard Daydream Nation it quite frankly scared the living shit out of me." -- Matthew Stearns
    6. Re:Ah, the LGPL, the "sane" GPL by kdemetter · · Score: 2, Informative

      It depends on how you look at it :

      In GPL , anything that is derived from that code , must also be published under GPL .
      So all code use must be GPL .

      Lesser GPL changes this , in that it allows the LGPL'ed software to be linked with non GPL'ed software ( ie it can use non gpl libraries)

      This means that , if OpenOffice remains pure PGL , then there's a problem if someone wants to extends OpenOffice with properietary libraries . This problem doesn't present itself with LPGL.

      Off course , there's a danger that the proprietary code becomes a main part of the application , making it basically a proprietary application.

  3. Sun's lawyers "get it" by davecb · · Score: 4, Insightful

    I've always claimed that whenever Sun wrote a strange license, it was because their lawyers told them to.

    You may recollect a small war between Sun and MS over the MS effort to "embrace and extend" Java.

    I suspect we'll see more GPL3 and LGPS3 as it is shown in practice to provide the same patent potection as CDDL.

    --dave

    --
    davecb@spamcop.net
  4. Re:Market Fragmentation by AvitarX · · Score: 2, Interesting

    It would be nice if people stuck to LGPL 2+, GPL 2+, Old X11/New BSD or multi-licenses that included them. This would allow for compatibility for the most part. Other licenses that are compatible but not multi-license are OK too, but really should just be one of those IMO (based solely on momentum, not quality).

    CC is not a Free or Open license (as it is used for the most part anyway). So I think your post is just further muddying the waters.

    --
    Wow, sent an e-mail as suggested when clicking on "use classic" banner, and got a fast response that addressed my msg
  5. Re:Market Fragmentation by mdwh2 · · Score: 4, Insightful

    But the fragmentation of licensing agreements (LGPL, GPL, CC, CC2.5, ETC) is just going to confuse people

    Different licences for different purposes. And remember that before these licences came along, individuals would often release software under their own (often poorly worded) licences, or sometimes not at all. Sometimes the licences are ambiguous, or the authors feel compelled to add in all sorts of arbitrary restrictions (I guess that's their right, but it's annoying when there's no logical reason). Indeed some people still do that. When I see something that's licenced under "GPL" or "CC", I know exactly what I'm getting, and don't have to worry if I can or can't do something, or if even though it's advertised supposedly "free" I'm going to download it and find it's crippleware, trialware, or has all sorts of licence restrictions.

    Recently I was looking for free graphics to use for writing games, and I came across one from years ago that had some licence saying it was free, but only for Windows because he wanted to be the one to "port" it to another platform. Huh? I thought, why should the graphics need to be changed for a different platform? Thankfully I then found a later version of the graphics which he'd sensibly released under CC.

    I'm not sure that comparing to Linux distributions makes sense. You might as well complain that having thousands of pieces of software available is "confusing", and this is comparable to Linux distributions. If people just choose the first licence they come across because the rest are too confusing, that's fine.

  6. Re:Great ... now what about ZFS? by zdzichu · · Score: 3, Insightful

    Let it go... Sun released ZFS on open source license. It already got integrated in few systems. Open source != GPL. Free software != GPL.
    We, linux guys, want ZFS features. But we are not center of the universe. Let's just wait for btrfs to mature and Daniel Phillip's ddlink to take off.

    --
    :wq
  7. Right, because MS has a single EULA by SmallFurryCreature · · Score: 4, Insightful

    Oh wait, no MS has several, off the top of my head, the OS, directX, media player. Office offcourse as well, but that is a seperate product. Does IE still come with one? Silverlight?

    In fact most windows software comes with a EULA all written differently.

    So you claim that people have no problem understanding all these different EULA's but would be confused by the far simpler opensources licences of which only about a dozen are in actuall use?

    Bad troll, no cookie for you! This is 2008, we expect more nowadays. Go on, mention soundcard drivers, why don't you.

    --

    MMO Quests are like orgasms:

    You may solo them, I prefer them in a group.

  8. Re:Market Fragmentation by JustinOpinion · · Score: 4, Insightful

    remember that before these licences came along, individuals would often release software under their own (often poorly worded) licences ... When I see something that's licenced under "GPL" or "CC", I know exactly what I'm getting, and don't have to worry if I can or can't do something Furthermore, it's worth noting that when it comes to proprietary software, the licensing landscape is very confused and inhomogeneous. Each software package has its own custom EULA. Though they often share similar features (e.g. "no liability"), there are often all kinds of ridiculous clauses buried among the boilerplate legalese. Volume license agreements are no better: you have to be very careful when selecting them (are we talking per-user? per-installation? per-processor? per-active-instance?).

    As you point out, at least with open-source licenses, there are only a handful of major ones that cover the vast majority of software. Once you know about them, you can very quickly know how much control you'll have over the code, and can confidently download/install/use/modify as required.

    There is no proprietary equivalent to this kind of well-organized and relatively homogeneous licensing landscape. (Of course not! Having "named" proprietary licenses would make it too easy for a customer to compare different product licenses and select the less onerous ones.)
  9. About that patent non-assert covenant by harlows_monkeys · · Score: 2, Informative

    That patent non-assert covenant is almost identical (and the differences are in the parts that aren't important) to Microsoft's patent no- assert covenant for its XML formats. Many have said that the latter is unacceptable for use with free software. It's also interesting to compare those two non-assert covenants against the one IBM provides for their patents that cover OpenOffice, and for Microsoft's OSP. I've made a little page that lists all four of these non-assertion covenants, side-by-side, with corresponding sections highlighted in matching colors.

    1. Re:About that patent non-assert covenant by HiThere · · Score: 2, Insightful

      I rarely read MS EULAs, because I never use MS products. But I've read one of the patent non-assert agreements on a proposed OOXML standard. ("A", because they've continued to shift the proposal, and because they reserve the right to continue to change it after it gets approved, presuming that it does.)

      The non-assert agreement only guaranteed that the patents would not be asserted against fully conforming implementations. But the specifications of the standard (at that time) were such that nobody, including MS, could actually build a fully conforming implementation. (Including such wonderful statements as "split the text layout in the same way that Word 95 did."(paraphrase. I'm *NOT* going to read that mess of garbage again!). Also the non-assert agreement named a particular version of the specifications to which it applied. Which didn't imply in any way that if some security fix was mandatory, that it would be legal to apply that fix.

      Additionally, I have reasonable grounds based on past history of actions, for trusting Sun to not act maliciously towards folk who were not acting maliciously toward them. The case for MS is rather different.

      Additionally the GPL3 and LGPL3 have been verified by lawyers that I trust to have good intentions. This is not true of ANY license offered by MS. Several of them have been roundly denounced by legal experts that I give reasonable credence to. "Nearly unconscionable" is a phrase that pops to mind.

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    2. Re:About that patent non-assert covenant by WebMink · · Score: 5, Informative

      That patent non-assert covenant is almost identical ... to Microsoft's patent no- assert covenant

      That's because Microsoft based their document on Sun's. I know that because the author of the Sun covenant is a colleague, because it was released at least a year before Microsoft copied it and because, after I pointed this out, Microsoft credited Sun for the original document.

      (and the differences are in the parts that aren't important)

      I disagree, and I have explained why before on my blog. Sun's covenant is intended to empower open source developers, and Microsoft has altered the parts that make that happen. Most notably, Sun's covenant grants all patents, Microsoft's is limited to "necessary claims". That is a very major difference since it means open source developers cannot be sure they have actually been given cover by Microsoft's covenant whereas they can be certain they have by Sun's. It is deeply regerttable that Microsoft added essential claims language in this way. For those who don't follow links, I also find the conformance requirements and the patent peace asymmetry poor in Microsoft's document.

      Many have said that the latter is unacceptable for use with free software.

      Indeed, and I am among them. However, your implication that the same applies to Sun's covenant is incorrect.

  10. Re:I'm happy but... by htd2 · · Score: 5, Insightful

    Yawn, Solaris is probably the most capable server OS on the planet and it contains a number of technologies that even the most passionate Linux advocate would give their eye teeth to have in Linux. dtrace, ZFS, SMF etc etc.

    Sun also developed Java still the most widely used application development and deployment platform for enterprise applications. It is also the largest single platform for Mobile Phones, way ahead of Symbian, Windows Mobile etc.

    They have also developed the only credible alternative to MS's cash cow Office.

    Not bad for a company apparently rubbish at Software development.

  11. Linus needs to reconsider GPL V3 by FreeUser · · Score: 2, Interesting

    No, but Linux==GPL. Sun could release ZFS under a Linux-compatible license without affecting anything else (they could triple-license it).

    The only reason Sun isn't releasing ZFS under the GPL or a GPL-compatible license is to prevent Linux from using it. And that tells you that Sun is lying when they are saying that they are supporting Linux; they are trying to hurt Linux and replace it with their shit.


    While I think you have a point, and I share (to a degree) your suspicion with regards to Sun's motivations, I would point out that Linus brought this upon himself in no small part as a result of "not trusting" the Free Software Foundation (or Richard Stallman personally, I suppose), and not licensing the Linux kernel under the GPL V2 "or any later version." As a direct result of this, it is impossible for Sun to release their product under a Linux kernel compatible license that also protects them from Software patent claims, as the GPL V3 and Sun's own open source licenses do.

    I have been a Linux advocate since the mid nineteen-nineties, and remain so today, but Linus' stubbornness on the licensing issue may well have condemned Linux to the annals of history sooner than it otherwise might have been. Sun may be trying the accelerate this, but in point of fact, I supsect it will be Linux's incompatibility with GPL V3, V4, V5... that will push it away from the center of the Free Software and Open Source world in the coming decades, far more than any political maneuverings by Sun, Microsoft, SCO, or anyone else.

    Why does this matter, when we're talking timeframes greater than any software's life cycle? Because free software, unlike proprietary products, tends to change, morph, fork, and become incorporated into new products. Emacs has reinvented itself numerous times. So too has the Linux kernel and a dozen other free software projects. But now, as the legal copyright/patent landscape changes and much of the world is forced to move to protective licenses such as GPL V3 as a matter of self-preservation, Linux will be left out. More and more code will be license-incompatible with the kernel, which over time may well become an insurmountable problem. There is no reason that fragments of Linux code wouldn't have been included in an operating system in 2050 ... perhaps one calling itself Linux ... except that it will be license incompatible, and the GPL V2 so hopelessly outdated with current law and legal precedents as to be nearly useless.

    It is this kind of entropy that the Free Software Foundation's recommendation of "GPL V or any later version" was designed to address. Unfortunately, Linux doesn't have that option, so instead (most ironically) it will likely be a bit of FreeBSD, or perhaps GNU Hurd code, that we see floating around in the codebase of whatever free OS we're running forty-odd years from now, and much of that will be down to licensing as much as technical merit.

    --
    The Future of Human Evolution: Autonomy