Slashdot Mirror


GPL Hard to Enforce?

the-dark-kangaroo writes "The GPL may be difficult to enforce due to a lack of clarity over who owns the copyright to the software, according to a legal expert. Lucie Guibault, an assistant professor of intellectual-property law at the Institute for Information Law in Amsterdam, said at the Holland Open Software Conference in Amsterdam, that the GPL should clarify who is the author of the software to ensure that open source software distributed under this licence receives legal protection."

12 of 361 comments (clear)

  1. Comment removed by account_deleted · · Score: 2, Insightful

    Comment removed based on user account deletion

  2. Stupid stupid article by interiot · · Score: 4, Insightful
    The copyright of the actual text of the GPL is owned by the Free Software Foundation, but the author owns the copyright to the GPL-licensed software. Authors that wish to release their software under the GPL are advised to include a line in the source code stating "Copyright © [name of author]".

    If the author of GPL-licensed product discovers that a company has not adhered to the terms and conditions of the free software licence, the individual may find it difficult to argue his case in court as the defending party could argue that the copyright appears to belong to the Free Software Foundation, according to Guibault.

    "The only name that appears on the licence is the Free Software Foundation -- they appear to be the licensor," she said.

    Seriously, you can't pay someone to come up with schlock this bad.

    1. Re:Stupid stupid article by Phexro · · Score: 3, Insightful

      Actually, the authors own the copyright to their individual contributions, e.g. Rik van Riel has copyright to the code for the kswapd_ctl changes.

      Simply being the last to contribute to something doesn't mean that you gain the copyright over the rest of the code.

      The only even semi-legit issue here is that because the code is/may be copyrighted by many people, it becomes hard to sort out who owns what in a particular file. Revision control takes care of that, since you can see the precise changes made by each individual. It may be harder to sort out older (pre-BitKeeper) code, since I don't think the original patches exist anymore, just the aggregate changes from version N to N+1.

  3. Enforceable? by unixbugs · · Score: 3, Insightful

    We'll see what is enforceable and what isn't when these big companies that are dumping money in to open source development feel like they have something to protect from each other.

    --
    You are about to give someone a piece of your mind, something which you can ill afford...
  4. Re:It's pretty simple... by eurleif · · Score: 2, Insightful

    They own the copyright to their patches, but not to the thing they're patching. Just like the renter of an apartment owns the microwave oven they bought, but not the apartment they put it in.

  5. Sigh, more morons reported on Slashdot by QuantumG · · Score: 4, Insightful
    Everytime random lawyer X says something about Open Source without doing a trivial amount of fact checking it gets reported on Slashdot. Braindead news. If Lucie Guibault, assistant professor of intellectual-property law at the Institute for Information Law in Amsterdam had bothered to go read "How to use the GPL or LGPL" she would have noted that the way to use the GPL is to state ON YOUR SOURCE CODE that it is copyright to you and that it is released under the TERMS OF THE GPL. Obviously if you don't do this you're not releasing your source code under the GPL, but in that case you're giving your source code out under NO LICENSE which means that others have NO RIGHTS to reuse the code.

    Then to point out the even greater boneheadedness of this story, let's say that EvilMegaCorp went to court and said "oh, we didn't think you owned this copyright, we thought the FSF did" and the judge agreed, the FSF would be in court the next day saying "no, we didn't write it, we wrote the license, but if you'd like to name us as the author of the software we'll gladly defend the copyright on it."

    So STFU and get back to teaching students how to swindle.

    --
    How we know is more important than what we know.
  6. Assistant professors can be wrong by gvc · · Score: 3, Insightful

    I have exclusive copyright for my work, unless I transfer it in a written "instrument of conveyance."

    An infringer might claim that I have no standing, but could not possibly make that case as there is no instrument of conveyance, and I and FSF would both testify that I had not tranferred ownership.

    Since when was uncertainty as to the owner a defence? If I rip off your bicycle (to use the stupid IP as physical property analogy), am I less guilty because I thought I was ripping off somebody else's?

  7. Lucky eh? by OverflowingBitBucket · · Score: 3, Insightful

    Seems like his 'enforcement' has relied on the good nature of the 'violators'.

    A quick glance didnt point out any legal findings in real court, so its all just a lot of hot air.

    The GPL doesnt stand up.

    Lucky all these companies caved in then isn't it? I mean, you'd expect multiple companies to cave in to the demands to fight off the terrifying threat of an individual with a baseless case, right?

    Just because it didn't make it to court doesn't mean the case is without merit. In fact quite the opposite. The GPL violators caving before court suggests that they figured there was a good chance they wouldn't win.

  8. Re:It's pretty simple... by Husgaard · · Score: 2, Insightful
    Each contributor to a FOSS project owns his own copyrights, unless he assigns them to the project.

    When the patch has been applied to the project he is legally one of the copyright holders of the project, unless he has assigned his copyright elsewhere.

  9. Re:The Problem as I See It. by wes33 · · Score: 2, Insightful

    Joe Hacker's code is still copyright Joe Hacker. When did he assign away his copyright? Not by using the GPL. Of course, it might be hard for Joe Hacker to find out where is code has ended up ... but that's life on the globe of corporate scumbags we call Earth.

  10. Re:The Problem as I See It. by Anonymous Coward · · Score: 1, Insightful

    Jack N Box downloads the code, modifies it to modification.cc and posts it as GPL material.

    Jack has to leave the original copyright notice on the code, or he violates the GPL by distributing the modifications.

    Company X downloads modification.cc code uses it to make a propritary product and claims all ownership of the work, ignoring the terms of the GPL.

    If SCO can sue IBM because they *thought* they could convince people that source code was copied from SCO, how much more do you thinks the courts will go for the fact that the exact same code is demonstratably open and owned by Joe Hacker, even if it doesn't say so?

    For instance, what prevents Company X from just skipping the Jack N Box completely and pretending to find the code laying out in the public domain somewhere with no copyright notice or GPL license? Obviously, the (exact) similarity between the original source and Company X's will prove otherwise, which probably happens quite a lot in normal copyright cases. The judges will laugh them off the face of the earth.

  11. The article may have a point! by Per+Abrahamsen · · Score: 2, Insightful

    Yes, as a zillion high rated comment already point out, there is no legal doubt that the author own the code. And a "copyright year name" statement is not needed, but anyway encouraged and common (the article actually also state that).

    However, the article is about damages, not ownership. If it is unclear to the defendant who the opposing legal party was, it may reduce the chance or size of damages awarded. At least in Holland. No question though, the defendant will be forced to stop the illegal distribution.

    Stopping the illegal distribution is what is most important to us, but a lawyer is usually paid to extract as many money as possible, so his point of view is obviously different.