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."

19 of 361 comments (clear)

  1. 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 El+Cubano · · Score: 4, Informative

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

      No kidding. Check this out (from vmscan.c in the Linux kernel):

      /*
      * linux/mm/vmscan.c
      *
      * Copyright (C) 1991, 1992, 1993, 1994 Linus Torvalds
      *
      * Swap reorganised 29.12.95, Stephen Tweedie.
      * kswapd added: 7.1.96 sct
      * Removed kswapd_ctl limits, and swap out as many pages as needed
      * to bring the system back to freepages.high: 2.4.97, Rik van Riel.
      * Zone aware kswapd started 02/00, Kanoj Sarcar (kanoj@sgi.com).
      * Multiqueue VM started 5.8.00, Rik van Riel.
      */

      Any doubts about whose the copyright is?

    2. Re:Stupid stupid article by sharkey · · Score: 5, Funny
      Any doubts about whose the copyright is?

      SCO's?

      --

      --
      "Outlook not so good." That magic 8-ball knows everything! I'll ask about Exchange Server next.
    3. Re:Stupid stupid article by compm375 · · Score: 3, Interesting

      One problem. What if someone else releases a derivative work under the GPL. That person makes a comment copyrighting the code. Then an evil third-party comes along and violates GPL by using some of the code. The code is in both versions, which are copyrighted by the GPL, so whose code is it? It looks obvious, that the first author does, but what if there aren't comments on every single line saying who write what? It might be impossible to find where each part of the code started. Even if you did know who wrote each line, how would the ownership of the code be split up?

    4. 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.

  2. 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...
  3. Tell that to Harald Welte by Anonymous Coward · · Score: 3, Informative

    He has been enforcing GPL for over a year now with impressive results.

    This guy does not know what he is talking about.

  4. This is why... by Jimmy_B · · Score: 3, Informative

    This isn't a real problem. The basic issue is that only the copyright holder has standing to litigate copyright violations. But it's never really ambiguous who the copyright holder is. The FSF recommends that free software developers assign their copyrights to the FSF, so that they can deal with violations. Many individual projects require all contributors to assign their copyrights to a consortium, to the project leader, or something similar. There are some projects with copyright held jointly by many developers, but there's almost always someone who you can point to and say "this person/organization holds copyright over the majority of the code". And even if it's not immediately obvious from the license who the copyright holder is, that doesn't matter in court; not knowing who has standing to prosecute is no defense.

    Also, notice that "Richard Stallman, the founder of the Free Software Foundation and the author of the GPL, was unable to comment in time for this article." A brief interview with RMS would surely have cleared this up as a non-issue.

  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. Re:In other news... by unixbugs · · Score: 3, Interesting

    These things are an entity of greed, something in which the GPL was not founded. IMHO the GPL is an agreement between the user and the developer to maintain the inegrity of the code, and to further its existence and usefulness. This, by nature, is in effect the opposite of that which defines conventional means of protecting ideas and property.

    Developing open source software for public use is not something attributed to those who would benefit from doing so arbitrarily, it is something attributed to those who would better the world around them no matter what they are doing.

    The true meaning behind the division we see is far deeper than what can and cannot be enforceable. The problem we are facing has resolution in the re-thinking of laws and governing institutions over our daily lives. The GPL is not something which can be negotiated or changed to make the individual able to wave in the air in a courtroom, it is a doctrine to which can be added for the need of expanding an idealistic medium of communication between the individual and the masses.

    --
    You are about to give someone a piece of your mind, something which you can ill afford...
  7. 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?

  8. The author is the copyright owner by Pedrito · · Score: 3, Informative

    This is pretty stupid. The author of a work is the copyright owner in perpetuity unless they assign ownership to someone else. If there are multiple authors then the authors as a group own the copyright. This is the way copyright has always worked.

    A work is technically, and legally, copyright upon creation by the author. You don't have to register something with the US Copyright Office for it to be protected. The point of registering with the Copyright Office is to provide an official registration so that if you are legally challenged, it's likely the first person to register is the owner. But it's nothing more than a measure of protection.

    If I create a work and you register the copyright in your name, the burden of proof falls to me to prove that I created it first. But if I can do that, then legally I'm protected and you are not.

    So putting your name on it does nothing for it. If you want to protect it, go to the Copyright Office web site, download the form, fill it out, and send it in with you $30. That's the best protection you can have.

    1. Re:The author is the copyright owner by iCEBaLM · · Score: 3, Informative

      People own copyright on their own code unless they specifically assign it to someone else. A owns his code, B owns his code. C's code is illegal and C is in a world of hurt because he committed infringement and is liable for the damages. A and B could strip out C's code once they found out and no harm can come to them.

      IANAL.

  9. Re:whats in a name by vondo · · Score: 3, Funny

    Yeah, google is a publicly owned company. Where are my shares, dammit?

  10. 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.

  11. The GPL is clear enough - beware not to spread FUD by Pope+Raymond+Lama · · Score: 4, Interesting

    On the other hand, the GPL is just clear enough, that anyone reading it knows when he is in wrong doing.

    That is why there are so few trials involving the GPL in court: violators tend to make agreements before it even gets there.

    It happened just last month around here: on a list I subscribe too tehre are some lawyers who suypport Free Software. One of the members of the list noted that one program a large internet provider offered for free (beer) download for its subscribers was actually a renamed and closed GPLed Software. We on the list had the same doubt as the article proposes: in name of whom should we send a letter to the violators? The developers of said program were all from abroad - they might not even get interested in getting involved. Moreover, for the local lawyers to be able to legaly represent the foreigner developers, there would be quite a lot of bureaucratic entanglements.

    So, on the list, we decided just to send a lawyer letter pointing that their software was violating the GPL - said lawyer was representing no one in particular. Ok, it took some phone calls besides the letter, but in no much time, they complied and released the source code for downloading, as required by the license.

    So, IMHO, IANAL, ETC, even when a case actually gets into trial, a single developer, with no more than a few dozen lines of code, involved in the proccess is more than enough for the wrongdoing to get characterized.

    --
    -><- no .sig is good sig.
  12. What an idiot! by ucblockhead · · Score: 3, Informative
    You'd think a lawyer would have been smart enough to read this.

    Quote:

    Whichever license you plan to use, the process involves adding two elements to each source file of your program: a copyright notice (such as "Copyright 1999 Linda Jones"), and a statement of copying permission, saying that the program is distributed under the terms of the GNU General Public License (or the Lesser GPL).

    A quick perusal of any GPL'd software in the world would have shown how full of shit the guy was.

    --
    The cake is a pie
  13. Yes you can. by jd · · Score: 3, Interesting
    It's just that the worse you want the stuff to be, the more you have to pay them to stop laughing long enough to write it.


    The FSF owns (a) the licence, and (b) all code assigned to it. (This is why they do strongly suggest assigning rights to it, to avoid any lack of understanding or willful stupidity on the part of lawyers or corporate execs.)


    Any individual programmer owns all GPLed code that they write, provided they have not assigned the rights to the FSF.


    Personally, I don't see the problem. Well, actually, I do. The problem is that a lot of lawyers get paid to find problems and create them when they aren't there to be found.


    The French only pay doctors when people are well, which means that doctors there do a great deal to prevent illness, rather than profit off it. Maybe US corporate lawyers should be paid on a similar basis - by how many legal tangles they DON'T get into, which seems a better indicator of when they are doing their job.

    --
    It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
    1. Re:Yes you can. by Arker · · Score: 3, Informative

      Correction - the FSF doesn't urge people to assign copyright to them on anything and everything, as you imply. They require copyright assignments on official FSF projects, of course, but there are many other Free Software projects they neither have nor want copyright on.

      The stuff about french doctors doesn't seem to contribute to your post, and sounds a bit suspect, too.

      --
      =-=-=-=-=-=-=-=-=-=-=-=-=-=-
      Friends don't let friends enable ecmascript.