Slashdot Mirror


NewsForge 'Previews' GPL3

Meltr writes: "NewsForge has an interesting sneak preview of the 3rd version of the GNU Public License. Among other things, RMS will make V3 more business friendly and will close the ASP loophole in V2. Check it out here." Now, take things with a grain of salt - RMS [?] doesn't feel comfortable calling this even a "draft" so there's much work still to be done. But's a good article, and interesting to see what's happening.

6 of 195 comments (clear)

  1. Re:Versioning by Bruce+Perens · · Score: 4
    The FSF actually has a board and an administrative director. People like Miguel of GNOME fame are on the board. This issue is covered.

    Thanks

    Bruce

  2. Any questions about the ASP and linking issues? by Bruce+Perens · · Score: 4
    I'm not RMS, and not even an FSF official, but I've been working on this issue on my own for a year or more. If anyone wants to leave questions about it here, I'll answer them later today, and pass them on to RMS.

    Thanks

    Bruce

  3. My code is my property. by Convergence · · Score: 5

    Under current law, my code is my property. Thus, you have no right to distribute it without me allowing it. In order to let you distribute MY code, I exact a price on you. You must distribute your changes to my code. Instead, I could have required you to pay me $10 per copy and required that you give nobody else redistribution rights.

    Both of these are capitalistic. Each option exacts a price on you. One is measured in dollars, another is measured in requirements. You aren't obligated to do either of them, but then again, if you don't, you're not allowed to distribute MY code.

    This isn't communist. I'm not forcing you to give anything away. You have no right to force ME to give MY things away to you to do whatever you wish, just as I have no right to force Oracle to give me their source code.

    Just because GPL software is distributed with full source code doesn't mean it's public domain. If you want source code that has no restrictions on it, write it yourself, or use public domain. Otherwise, live with the restrictions other people put on their source code. Whether they be monetary renumeration (Oracle/Windows/Office/Kai C++/Mathematica/Matlab), or requirements that you must allow your changes to be redistributable under the terms of the GPL (emacs/gcc/linux kernel/tinyfugue).

    There's no coercion going on. Your code and your changes are your own. You can distribute them however you wish. What you CANNOT do is distribute MY source code.

  4. GPL doesn't Force by nuggz · · Score: 4

    You overlook that you CHOOSE the GPL.
    All licenses force everyone but the owner to follow certain conditions.
    If you don't like the GPL, don't use it.
    I don't like the MS EULA, I don't use it.

  5. Re:Communism and GPL by Omnifarious · · Score: 4

    Once you tell anybody your idea or show anybody your work, you've already given it away, and can't prevent them from giving it to anyone else. That's just the way it is. No matter how many attempts you make to erect societal walls to keep it from happening, it will, and short of totalitarianism, you can't do anything at all about it.

    I would prefer that this fundamental truth be realized, and people start basing their actions on it. It's much more healthy and sane than continually trying to make everybody conform to a set of rules that just aren't the way things are.

    Likening GPL to communism and BSD to socialism is quite flawed. Communism and socialism are both about physical property. Neither a copyright, nor a patent are physical property. Both are mere societal conventions we follow in the hopes of achieving certain ends.

    The fact that these conventions have largely come at no cost to society from ignoring what the real laws are is an accident of history. Those costs now loom large, and it's time to revisit our conventions and decide what would better further our goals.

  6. Re:closing the ASP loop hole by Eric+Sharkey · · Score: 5

    The ASP loophole exists because the ASP provider never distributes a copy of the application to the user. In general, copyright law covers the creation and distribution of copies of works, but for certain kinds of works, there is also a restriction on perfomance of the work.

    Take for example the play "Cats". Cats as literary work is copyrighted. You can't make copies of the script and sell them unless you're licensed to do so by the copyright holder. However, you also can't put on an independent production of the play and charge admission, even though the audience would not be actually receiving a copy of Cats, they would be perceiving a performance of it. That's controlled by copyright law.

    What RMS is trying to do is to equate ASP to a performance of the software. It's a good analogy. The consumer never gets a true copy of the work, but they perceive all that is important about it. If ASP can be equated with a performance, then it can be controlled within the existing framework of U.S. copyright law.