Slashdot Mirror
Should the GPL be Used as a Click-Wrap?
swillden asks: "I've come across an increasing number of GPL programs lately that display an EULA-style click-wrap agreement during installation. While not exactly wrong, this seems like a bad idea to me, since it perpetuates the idea that you must agree to some arbitrary set of conditions in order to install and use a piece of software. In this case the conditions are very liberal (there are none, really), but still it reinforces the notion that you can't install a package unless you agree. The FSF says that such click-wrapping is neither required nor forbidden but it seems like a bad idea to promote the click-wrap meme, even if the license is user-friendly. Does Slashdot have strong thoughts on this matter?"
Click-wrap of GPL is one thing. Forcing you to click "agree" to install is another.
Display the license, fine. Don't write "by using this software you agree..." just "this software is distributed under the following conditions". And allow clicking "forward" without any prerequisites.
Anagram("United States of America") == "Dine out, taste a Mac, fries"
Most users may not even know about the GPL. They just downloaded that CD ripping software or audio software or game off of Sourceforge because it was free as in beer.
Even if these users don't usually redistribute or modify and redistribute, if they are made aware of the GPL they might favor or even seek out GPL software over freeware or shareware software in the future because they feel good about the using software that shows this respect to them.
However, it can be done incorrectly. For example, users should not have to click an "I Agree" button in order to use GPLd software because the GPL does impose any restrictions on use.
No one seems to have mentioned the LARGE CAPITOL LETTER SECTION of the GPL that tells you that the author disclaims responsitibility from any damage caused by the program, etc.
Given the choice between inserting the GPL into the EULA section of commonly used installer software, or opening themselves up to huge potential liability, I can't blame software distributors for weaseling out and going with the status quo.
Of course, this isn't a binary choice. You're perfectly free to excerpt the disclaimer and display just that. Indeed, the example offered for people adding the GPL to their program is quite short. The GPL's "How to apply" section specifically suggests showing this short message when your program starts. For reference, here's the suggestion. It's short enough that mroe people will read it, it clearly warns that users get no warranty and provide directions on how to see the full disclaimer. It also tells users of their free software rights, and gives directions on learning about that as well.
(Obviously you're supposed to change the "show w" and "show c" to something else if appropriate, say "Select Help > Warranty" and "Select Help > License".)
Search 2010 Gen Con events