Slashdot Mirror


Explaining the GPL to Non-Lawyers?

peddrenth asks: "Software licenses are, we keep saying, difficult to read. The public clicks OK without reading, either implicitly trusting or mistrusting us the software authors. There have been calls recently for companies to clean-up the license, to bullet, section, and colour their licenses, to remove THE UPPERCASE and to draw charts and graphs to explain the license. Anyone who's had to read a 3-page document in a 3"x1" textbox knows how useful this would be. The GPL is one of the most important licenses in the world, and appears on thousands of products. Everything from windows programs to operating systems to people's artwork requires understanding and acceptance of the GNU GPL. Should we, the free software community, take the first step in this effort, and show the world what an easy-to-read license looks like? Would it be useful if long textual software licenses stood out like a sore thumb amongst the cool, pretty, and clear free licenses?" Many may think the GPL Preamble to be clear enough, and this may be true. However there are a lot of people out there that would like to read the entire license so that they know exactly what they may be getting into, before they agree to it. This usually implies being able reading the actual license, and not just the preamble.

"Should we use such a comparison to show the public how they're being manipulated by terms in a EULA they don't read or understand, and encourage other license-writers to include the graphs and tables themselves, showing the public what a license really means?

What would be your ideal license, what poster would you draw to explain the GPL to a child, a PHB, or an artist? Would you stick with the text, or can you think of anything better?"

jamie interjects: The root of the problem is that "intellectual property" is a kludge of a natural human understanding of property rights. Useful, but a kludge. You have to invent many oddball concepts to keep up the pretense that ideas are property. The GPL is a kludge (strict and precise licensing terms) implemented on top of a kludge (copyright law) and, in English or in code, there is no short and simple way to describe complex things.

3 of 399 comments (clear)

  1. Free The United States Of Amerika @ +2; High @ by Anonymous Coward · · Score: 0, Offtopic

    Lame stories are posted to Slashdot about science
    while Biker Gangs On Turf Warpath.

    I wonder if John Ashcroft will call them as material witnesses or
    Donald Rumsfeld will call in the Special Forces.

    Thanks in advance.

    Woot

    My complaint about John Ashcroft

    May I be cynical for a bit? I hope you don't mind,
    but with Ashcroft's latest barrage of
    malodorous notions, I can't resist the urge to make a
    few cynical comments. To get right
    down to it, some of the facts I'm about
    to present may seem shocking. This
    they certainly are. However, it's time that a few
    facts had a chance to slip through the fusillade of hype.
    What's my problem, then? Allow me to present it
    in the form of a question: Where are the people
    who are willing to stand up and acknowledge
    that Ashcroft, in his infinite wisdom, has decided
    to destroy the natural beauty of our parks and forests?
    On the surface, it would seem to have something to do
    with the way that his whole approach is repugnant.
    But upon further investigation, one will find that
    by allowing Ashcroft to put mephitic thoughts in our
    children's minds, we are allowing him to play puppet master.
    As for the lies and exaggerations, Ashcroft's
    epigrams are rife with contradictions
    and difficulties; they're entirely maladroit,
    meet no objective criteria, and are unsuited
    for a supposedly educated population.
    And as if that weren't enough, if Ashcroft is going to
    obstruct important things, then he should at least have
    the self-respect to remind himself of a few things: First, a
    true enemy is better than a false friend. And
    second, many people respond to his debauched vituperations
    in much the same way that they respond to television
    dramas. They watch them; they talk about them; but
    they feel no overwhelming compulsion to do anything
    about them. That's why I insist we pronounce the truth
    and renounce the lies.

    Even people who consider themselves scornful
    foolhardy-types generally agree that Ashcroft's slurs
    symbolize lawlessness, violence, and misguided rebellion
    -- extreme liberty for a few, even if the rest of us
    lose more than a little freedom. One might conclude
    that Ashcroft is incapable of writing a letter without using
    such phrases as "crapulous pop psychologists", "loquacious
    exhibitionists", "oppressive personae non gratae", or
    some combination thereof. Alternatively, one might conclude
    that Ashcroft has a different view of reality from the rest of us.
    In either case, if you're not part of the solution,
    then you're part of the problem. His historical record of
    fickle pleas is clearer than the muddled pronouncements
    of his apple-polishers for a variety of reasons. For
    instance, the worst sorts of inconsiderate Neanderthals there
    are must be treated with political justice, not with
    civil justice, as they are sincerely not real citizens. Let me
    rephrase that: I wonder if he really believes the
    things he says. He knows they're not true, doesn't he?
    A complete answer to that question would
    take more space than I can afford, so I'll have to give
    you a simplified answer. For starters, if
    we let him cause riots in the streets, then greed,
    corruption, and tribalism will characterize the government.
    Oppressive measures will be directed against citizens.
    And lies and deceit will be the stock and trade of the
    media and educational institutions.

    Even Ashcroft's bedfellows couldn't deal with the full impact of
    Ashcroft's refrains. That's why they created "Ashcroft-ism," which is
    just a garrulous excuse to force square
    pegs into round holes. He plans to drag everything
    that is truly great into the gutter. He has instructed
    his votaries not to discuss this or even admit to his
    plan's existence. Obviously, Ashcroft knows he has
    something to hide. Most of you reading this letter
    have your hearts in the right place. Now
    follow your hearts with actions. I have traveled the length and
    breadth of this country and talked with the best people. I can
    therefore assure you that Ashcroft's artifices cannot stand on
    their own merit. That's why they're dependent on elaborate
    artifices and explanatory stories to convince us that Ashcroft's
    warnings can give us deeper insights into the nature of
    reality. We can and we must protect ourselves by any means
    necessary against the unrestrained bestiality
    of stupid, quasi-macabre paper-pushers. And that's the honest truth.

  2. Forget the license, what about the code? by electricmonk · · Score: 0, Offtopic
    Sure, it can be problematic when one cannot understand or sometimes even read their software license, but there are greater problems afoot in the open source movement.

    The primary problem is the absolute unreadability of most of the code. Now, I don't mean to flame or troll or anything like that, but there are a lot of parts of the Linux kernel (especially those written in assembler) that are difficult to read and understand. Why can't the Linux kernel maintainers write these illegible functions in a clearer, more concise language like Perl?

    Speaking of Perl, there is a lot of awfully illegible code written with this language as well. Take Slashcode, for instance. Have you ever tried to read Slashcode, let alone make improvements to it? I have, and let me tell you, it ain't pretty. This kind of illegibility led me to dump a Perl-based site altogether in favor of something better-documented and more legible, such as (regrettably) ASP.NET.

    The point of my little tirade here is simply thus: you defeat the purpose of opening your source when no one else can make heads or tails of it. Furthermoree, you are only shooting yourself in the foot when you try to audit the code, since you won't be able to use the "many eyes make every bug shallow" model to fix things (a concept first posited in Eric Raymond's masterpiece The Cathedral and the Bizarre). So please, comment your code, people, and code legibly.

    --
    Friends don't let friends use multiple inheritance.
  3. Forget the GPL by Anonymous Coward · · Score: 1, Offtopic

    Whenever i try to explain the GPL to anyone, the chief problem i have is getting them to understand what "source code" is!

    Once i can explain what source code is, the GPL becomes effortless to explain. But that first step is hard. So here's my question:

    How do you explain the concept of "Source code" to non-programmers in a way that you can be certain they understand what you're saying and aren't just nodding in an "okay.. i don't get it , but go on anyway" fashion?