Re: Kernel developers' position on GPLv3
Posted Sep 23, 2006 12:21 UTC (Sat) by jeroen
In reply to: Re: Kernel developers' position on GPLv3
Parent article: Kernel developers' position on GPLv3
GPLv3 doesn't force anyone anything as much as the GPLv2 does. If you don't like the terms, you don't have to use the software. Write your own software. But I don't want that people use the software I write for things I don't like, such as using it a tivo-like system.
That DRM is a tool is correct, but the GPLv3 doesn't go against DRM. It goes against companies who sell DRM systems without giving users the keys to modify the software on the system. That's an use of DRM that I consider evil. And of course I would like to prevent people doing that with my software.
And how many iteration did the linking clause in the GPLv2 have? We don't know, because AFAIK the drafts were never public. Maybe there have been ten or twenty. Does that make it a bad clause? I don't think so. Linux also needed several rewrites of the packet filtering framework to get it right. Does that make packet filtering a bad thing? I don't think os. The fact that something is hard to get right isn't an argument for not doing it.
The linking clause is also not tailored to the many moral viewpoints that exist, if you listen to the BSD camp. Is that a reason to remove the linking clause of the GPL?
If you would actually think about the hypothetical situation of the GPLv2 not yet existing and then evaluating the GPLv2 according to the same criteria as being done here on the GPLv3, the result would be that GPLv2 is a bad license too. It tries to dictate morals on other people (the moral of that you should give users the freedom to hack their software), there exists many moral viewpoints about it and it is hard to get right.
to post comments)