Slashdot Mirror


RMS Explains GPLv3 Draft 3

H4x0r Jim Duggan writes "A transcript is now online of a talk Richard Stallman gave in Brussels earlier this week about the discussion draft 3 of GPLv3. Among other things, he explained how it will address the Novell-MS deal, from Novell's point of view and from Microsoft's, and he explained how the tivoisation clause was narrowed to make it more acceptable in the hope that it will be used by more people. After the talk he also gave an interview, and yesterday, draft 2 of LGPLv3 was released."

1 of 139 comments (clear)

  1. Compatibility with patent-nullification licenses by Kadin2048 · · Score: 4, Interesting

    My biggest question is whether GPL3 will be compatible with the many existing "GPL-esque" free licenses [1], which are currently GPL-incompatible, because they contain patent-nullification clauses?

    There is a lot of software out there being developed under licenses which aren't compatible with the GPL, because the GPL doesn't allow patent nullification clauses -- this is dangerous, because the purpose of these clauses is to keep someone from slipping code into a major project that they have a patent for, and then torpedoing the whole thing later on when it's crept into wider use. I don't know if this issue just wasn't foreseen when GPL2 was written up, but I can't think of a more pressing issue at the moment.

    Yeah, "Tivo-ization" and web services may keep some software out of the hands of the public, but they're not nearly as downright dangerous as submarine patents are.

    [1] Examples: IBM Public License 1.0, Common Public License 1.0, Apache License v2, or any of the other licenses where the FSF cheerfully comments "We don't think those patent termination cases are inherently a bad idea, but nonetheless they are incompatible with the GNU GPL."

    --
    "Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."