Slashdot Mirror
Linus Loves GPL, But Hates GPL Lawsuits (cio.com)
Long-time Slashdot reader sfcrazy writes: During LinuxCon, Torvalds was full of praise for GNU GPL: "The GPL ensures that nobody is ever going to take advantage of your code. It will remain free and nobody can take that away from you. I think that's a big deal for community management... FSF [Free Software Foundation] and I don't have a loving relationship, but I love GPL v2. I really think the license has been one of the defining factors in the success of Linux because it enforced that you have to give back, which meant that the fragmentation has never been something that has been viable from a technical standpoint."
And he thinks the BSD license is bad for everyone: "Over the years, I've become convinced that the BSD license is great for code you don't care about," Torvalds said.
But Linus also addressed the issue of enforcing the GPL on the Linux foundation mailing list when someone proposed a discussion of it at Linuxcon. "I think the whole GPL enforcement issue is absolutely something that should be discussed, but it should be discussed with the working title 'Lawyers: poisonous to openness, poisonous to community, poisonous to projects'... quite apart from the risk of loss in a court, the real risk is something that happens whether you win or lose, and in fact whether you go to court or just threaten: the loss of community, and in particular exactly the kind of community that can (and does) help. You lose your friends."
And he thinks the BSD license is bad for everyone: "Over the years, I've become convinced that the BSD license is great for code you don't care about," Torvalds said.
But Linus also addressed the issue of enforcing the GPL on the Linux foundation mailing list when someone proposed a discussion of it at Linuxcon. "I think the whole GPL enforcement issue is absolutely something that should be discussed, but it should be discussed with the working title 'Lawyers: poisonous to openness, poisonous to community, poisonous to projects'... quite apart from the risk of loss in a court, the real risk is something that happens whether you win or lose, and in fact whether you go to court or just threaten: the loss of community, and in particular exactly the kind of community that can (and does) help. You lose your friends."
I have always preferred permissive licenses like MIT and BSD. However, Linus has created the world's most successful open-source software, so perhaps it's worth considering how the license has helped shape the software and its supporting community.
All my liberal friends think I'm a conservative, all my conservative friends think I'm a liberal.
I think if you want to build an empire around your projects, that BSD is probably not the best way to go. It's too easy for anyone to setup a business and overshadow your contributions. (it's why the wine project switch to GPL)
I tend to use ISC, MIT, or BSD myself. But I'm not looking to be the be in charge of the next Linux, GIMP, GTK, etc.
“Common sense is not so common.” — Voltaire
then soon every greedy capitalist in the software industry would be scalping code and using it in their products and selling it for top dollar and without releasing the source code, people like microsoft, apple, google, oracle, etc... they would all be raping your code for profits if the threat of litigation did not hang over their heads
Politics is Treachery, Religion is Brainwashing
The only restriction the GPL imposes is to prevent you to take away freedom. Thus, the GPL is only "non-free" to those who want to restrict or remove freedom.
Well there is one exception of course, its compatibility with other copyleft licenses. See the whole ZFS license debacle. But that's a negative side effect, and not what the GPL was designed for (however precisely what the CDDL was designed for, but thats a different story).
[...] You can't have freedom if there's a "but only if..." attached to it, [...]
I'm free to swing my fist, but only if I don't hit you.
Now, based on this example, please explain again what kind of freedom you are looking for that has no "but only if ..." attached to it.
The point of the GPL is to make the code free, not the coders. When starting, you're free to choose the GPL or not, and thus the GPL never revokes that initial freedom from you. GPL code can never be reverted to a less free state, whereas code under other licenses, such as BSD, can.
You can lead a horse to water, but you can't make it dissolve.
... unless you can, and do, enforce it.
Lots of entities would share their code in that circumstance because its in their best interests to do so. But a lot MORE companies (especially companies running Linux on all kinds of embedded hardware like routers and phones and tablets and such) wouldn't share if they didn't have to because its in THEIR best interests NOT to share their code.
Me personally, I think there should be MORE enforcement (via lawsuits if talking directly to the company that is violating the license doesn't work) of the GPL against companies who use the Linux kernel and dont share their code when legally required to.
Plenty of companies violate the GPL on the Linux kernel and many companies are well known as repeat offenders (taking months or even longer to release the source code corresponding to a new device or a new firmware update, releasing code that is incomplete or wont compile, releasing code that doesn't match the binaries or otherwise not properly following the GPL)
They aren't. They are concerned about derivative works of THEIR OWN code, concerns that they are legally entitled to have by virtue of having the copyright on the code that they wrote. The fact that a derivative work might have your own code in it is entirely superfluous, if it is a derivative work then you still need the original copyright holder's permission to do something with it. The GPL outlines the terms necessary to receive such permission. Nothing more, and nothing less.
File under 'M' for 'Manic ranting'
The freedom of the people who receive those modifications is affected. And if those people want features and bug fixes, your freedom to provide it for them is diminished because you don't know if it's your code or the proprietary code that needs to change and how to change it.
It's completely okay to not care about flow on effects, but please admit you're not thinking about the big picture.
Those who do not learn from commit history are doomed to regress it.
Actually, it only directly implies that people who use BSD licensing think less about derivative works from their code than people who use the GPL. This is perfectly fine, but since derivative works would typically contain substantial portions of the original code, by extension, the lack of care about derivative works of their ccde thereby reduces to a lack of care about their own code, from that perspective.
File under 'M' for 'Manic ranting'
If I was building a Tivo today I'd probably start with a BSD license. It's what Sony did with the PlayStation 4.
Having actually seen that done, both with Linux and FreeBSD (as operating systems in routers), I can tell you a) that I would choose Linux every time and that b) the reason is the license and the lawyers.
For the first year or so you will be concentrating on adding features. Making things you probably benefit from keeping private. With Linux you make these in user space which might occasionally make things more difficult. You will eventually want to add some low level functionality and add it to the kernel.
At the point you start low level work, if you used a BSD licensed kernel, there will be a discussion between lawyers and management and likely you end up keeping your functionality private a) because you can and b) because your competition might use it otherwise. If you have a GPL licensed kernel, you will likely decide to publish and push upstream a) because the license pushes you to and b) because even if your competition uses it you will get the benefit back.
After some time, if you don't contribute upstream, you will find that you have incompatibilities with new software versions and you will stick to a stable version. Eventually you will stop benefiting from the evolution of the upstream software. Long term this is a nightmare for the developers. You lose a tiny bit by being "forced" to contribute back. You actually gain a huge amount back from the community because they continue working on your software.
This has happened often; commercial derivatives of BSD operating systems either fork completely or die. 386BSD, JunOS, OSX, IPSO etc. etc. It's very hard to do long term commercial contributions into a complex BSD environment because technically you are giving away shareholder value with no visible recompense.
"Some people love the BSD license. Some people love the proprietary licenses. I understand that. If you want to make a program and you want to feed your kids, it makes a lot of sense to have a proprietary license and sell binaries. I think it makes less sense today, but I really understand the argument. I don't want to judge. I'm just giving my view on licensing."
Elen sìla lùmenn' omentielvo