This is nothing new. Provide a permissive license and expecting everything to be returned to you is contradictory to the very license you've chose. Forking happens all the time, usually around licensing or management issues. So aside from the little dust storm we've seen recently regarding the wifi driver and the copyright clause I don't see how this is news.
The GPL and BSD type licenses coexist perfectly, so long as both parties take the time to understand each other. Which is mostly the way it's happened
The point is that we have the GPL camp and we have the BSD camp. The GPL camp takes code from the BSD camp and the BSD camp is not able to merge those changes back into BSD code. The issue here is not that this is a license violation; it is not. BSD people, like me, want other people to use our code. The complaint here is about the hypocrisy of the GPL camp, who claim that they don't want anyone to use their code without giving back the changes, but then turn around and do just that to the BSD people's code
The GPL camp takes code from the BSD camp and the BSD camp is not able to merge those changes back into BSD code.
And that's the inherant problem with the BSD license, people can mod your code and not give it back to you.
The complaint here is about the hypocrisy of the GPL camp, who claim that they don't want anyone to use their code without giving back the changes, but then turn around and do just that to the BSD people's code.
There's no hypocrisy in that. Anyone can use the changes that where GPL'
There's no hypocrisy in that. Anyone can use the changes that where GPL'd, but you just have to adhere to the GPL license for those changes. The hyprocisy is the BSD camp saying "be free to use our code any way you want" and when people take them up on the offer, they complain.
You guys are confused. BSD code does make it into proprietary products, but you do not get to omit the fact that there's BSD code in it. We see it all the time: "Copyright The Regents of the University of California (etc.)..." So, you do not get to strip the license, although you can use and produce binaries with it. That's the issue: you can't strip the license. By removing the BSD license, the linux people are obliterating the license. As Theo says, licenses are granted to you.
For fucks sake, it's forking... (Score:5, Informative)
The GPL and BSD type licenses coexist perfectly, so long as both parties take the time to understand each other. Which is mostly the way it's happened
This is not the point (Score:5, Insightful)
Re: (Score:3, Informative)
And that's the inherant problem with the BSD license, people can mod your code and not give it back to you.
The complaint here is about the hypocrisy of the GPL camp, who claim that they don't want anyone to use their code without giving back the changes, but then turn around and do just that to the BSD people's code.
There's no hypocrisy in that. Anyone can use the changes that where GPL'
Ball of confusion (Score:3, Interesting)
You guys are confused. BSD code does make it into proprietary products, but you do not get to omit the fact that there's BSD code in it. We see it all the time: "Copyright The Regents of the University of California (etc.)..."
So, you do not get to strip the license, although you can use and produce binaries with it.
That's the issue: you can't strip the license. By removing the BSD license, the linux people are obliterating the license. As Theo says, licenses are granted to you.