Slashdot Mirror
Linus on GPL3 In Forbes
musicon writes "In an interview via e-mail with Forbes, Torvalds discusses GPLv3, digital rights management and sharks with laser beams. From the article: 'I'm sure changes will be made [to GPLv3]. The fact that the FSF and I have some fundamentally different views of what the GPLv2 was all about makes me worry that we won't find a good agreement on the next version.'"
sudo apt-get install sharks-with-lasers_kernel_module
"Something's wrong with you...and I hope we never do meet again." - Deftones When Girls Telephone Boys
First off, please forgive my ignorance, but is it really *that* important for Linus to decide to move Linux from the GPLv2 to the GPLv3? Just because version 3 of the license becomes available does not automatically invalidate the version 2 license does it? Why is this such a hot button issue?
For the most part, I completely agree with Torvalds on his points--and I can't say I'm at all surprised to see Stallman and the FSF take this direction with version 3. Simply put: they are "zealots" for lack of a better term. For them, free software is less about open source and open development and more about a form of political agenda.
Now I'm not trying to bash Stallman or the FSF, they have made some wonderful contributions to the community. But let's call a spade a spade here and look at what GPLv3 is about: attempting to hide attempts to restrict developers under the guise of being an update to the world's most popular open source license. For all of the FSF's talk against bad copyright policy and software restrictions, this license introduces their own set as if to say, "we don't like their way; so you should definitely do it our way instead."
Too much politics and agenda and not enough open source development.
Torvalds Explains Dislike For GPLv3
Linus Says No GPLv3 for the Linux Kernel
I see a GPL that prevents companies from using DRM (which wasn't around for v2) to get around GPL requirements. Basically those same requirements that we liked from v2.
If Linus is fine with TiVo's method of coopting the kernel and making it for all practical purposes unmodifiable, that's his business. But lots of other people have contributed code to free software and are not.
PS: this is how I understand it so far. My opinion is subject to revision
My turnips listen for the soft cry of your love
Firefox is only on workstations -- headless servers typically won't have a web browser; my company's certainly don't. I was thinking gcc would be a better candidate: Not only is it installed on a strong majority of Linux-based systems, but also on a large number of traditional Unix systems elsewhere.
I wonder if Linus even has the real authority to unilaterly switch to an alternative license. I don't think so. By his own admission he is not a deep thinker about the philosophical (he says polical) part of the job. Many of his colleagues are. Any change would have to be accepted by the core kernel developers. If not a fork is all but inevitable (GNU/Linux anyone?). My guess is he will talk like this from time to time but will be under pressure to maintain the status quo.
an ill wind that blows no good
If I understand it right, and I prolly don't, you can install any modified version whatsoever on your sharks. Your obligations re: making keys available etc. do not kick in until you distribute the modified version. i.e. if you're a shark salesman rather than a mad scientist.
Is that right?
My turnips listen for the soft cry of your love
Due to the public outcry GPLv4 will no longer include sharks with laser beams. They have been replaced with Sea Bass. Extremely ill-tempered sea bass.
Suppose a vendor creates a distro, Blue Hat. It's designed for platform P but P is made to require binaries signed by Blue Hat, it won't run anything else. Now Blue Hat releases a body of source code and claims to have complied with GPL v.2.
Now has Blue Hat complied with GPL v.2? No one outside Blue Hat can know. The only way to verify that some source corresponds to the binary you're running is to compile it and run the result. If you can't do that without a key, and Blue Hat won't give you a suitable key, they could violate GPL with impunity.
It doesn't require that BH give up their ultimate private key, just one sufficient to sign source. This is all that GPL 3 requires in regard to DRM and keys.