Slashdot Mirror

← Back to Stories (view on slashdot.org)

GPL 3 Forking Risks Discussed

Posted by Hemos on from the much-thunder-and-lightning dept.

sebFlyte writes ""I fear a lot of unpleasant forking action when the GPLv3 comes out." The words of Debian maintainer Matthew Palmer. ZDNet has an interesting look at the possibility of forking when GPLv3 emerges, with lots of reassurance from Eben Moglen (the FSF's chief lawyer)."

6 of 356 comments (clear)

  1. Whew by Captain+Nick · · Score: 5, Funny

    At least they aren't GPL spooning.

  2. From the GPL v2 text: by azmaveth · · Score: 5, Informative

    TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

    9. The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.

    Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation.

  3. Re:And from the Linux Kernel "COPYING" file by Anonymous Coward · · Score: 5, Insightful

    That means there will be no GPL v3 as far as Linux is concerned. Linus et al won't get every contributor to the table to agree to a license change. Without that happening, the kernel will have to remain under GPL v2 only. The relicensing of the Mozilla codebase (to the MPL/LGPL/GPL trilicense) has been a tedious process for the Mozilla project, and that is a considerably younger and smaller codebase.

  4. Stop being afraid of Change by ites · · Score: 5, Insightful

    Remember that the version 2 of the GPL dates from June 1991. It is an incredible document, and I agree with Moglen's assertion that it's the basis of a multi-billion dollar industry. Stallman will go down in history as a visionary.

    But after 14 years, GPL/2 is starting to age. Yes, it addresses current problems, but remember that software written and licensed today must still be protected and viable in 15 years' time.

    There is absolutely no point in postponing the introduction of GPL/3. There must be a migration, and there will be a period of overlap.

    But change is not something to fear in itself. It's something to plan and to manage, and in this case, it's essential.

    Last thing: if you followed the FSF's recommendations as to how to use the license, your code would contain this text:

    # This program is free software; you can redistribute it and/or
    # modify it under the terms of the GNU General Public License as
    # published by the Free Software Foundation; either version 2 of
    # the License, or (at your option) any later version.

    Which all my company's GPL software contains.

    Thanks to Moglen, and the FSF for their fantastic work.

    --
    Sig for sale or rent. One previous user. Inquire within.
  5. Not that easy by Anonymous Coward · · Score: 5, Insightful

    If GPL3 mentions anything that is not in GPL2 (ie it places restrictions relating to patent litigation etc) then it cannot be compatible with GPL2.

    The only thing the GPL3 can do and still be compatible with GPL2 is to have fewer restrictions. In which case, what's the point, we already have BSD.

  6. Vaporware issues.. by iamsure · · Score: 5, Insightful

    If they'd stop talking about what it "will be" and "wont be", and put out a draft, they'd have *constructive* discussions instead of guessing!

    Look, seriously, yes, there are grave concerns, and its a hideously important document. However, there is no reason why they cant put v2 into a wiki, add some proposed changes, and start working with the community on modifications.

    This is at least the 10th story that has discussed A DISCUSSION OF WHAT WILL BE IN THE NEW VERSION!

    Its not even 5 pages long. They've already mentioned the high points of areas they want to improve/change (patents, webservices), and everyone is well informed!

    So just get on with it, and stop playing the vaporware game.

    In the meantime, the only GPL-like license that actually closes the web services loophole (the Affero GPL), which is mentioned as a template for the GPLv3, ISNT GPL compatible!

    It would be nice to have a GPLv2 compatible license that closes that loophole, so I'm waiting anxiously for a look at a license that will do it.

    Enough talk - WRITE!

    --
    GPL'd web-based tradewars themed space game