GPLv2 Vs. GPLv3

chessweb writes "Here is a rather enlightening article by Richard Stallman on the reasons for moving to GPLv3 that puts the previous TiVo post into the right context." From the article: "One major danger that GPLv3 will block is tivoization. Tivoization means computers (called 'appliances') contain GPL-covered software that you can't change, because the appliance shuts down if it detects modified software... The manufacturers of these computers take advantage of the freedom that free software provides, but they don't let you do likewise... GPLv3 ensures you are free to remove the handcuffs. It doesn't forbid DRM, or any kind of feature. It places no limits on the substantive functionality you can add to a program, or remove from it. Rather, it makes sure that you are just as free to remove nasty features as the distributor of your copy was to add them."

Comments

Re:The GPL: Intellectual Theft

[wellingtonsteve]

Support for my statement above: GPL on Qikipedia From the link:
Non-GPL'd and non-free software can be developed with GPL'd tools The program must be GPL only if it includes GPL source code or it is linked with a GPL library. For example, using gcc to compile proprietary software is allowed.

Re:The "ASP loophole"?

[bheer]

ASP loophole = the fact that the GPL doesn't cover programs you use over a network.

As an AC reply noted (thanks, AC!), there's something called the Affero GPL, and you can (if I'm reading the draft right, I could be wrong) distribute GPL3 code under the Affero GPL. If you do that then anyone installing the program on a network (e.g. a web server) will have to make the source available to its users.