To read all comments associated with this story, please click here.
Actually they can. Anyone can take GPLv2 or later code and relicense it as "GPLv2 only" or "GPLv3 only" or "GPLv3 or later" or even "GPLv4". It's at the *user's* discretion (read the license). Now they can't relicense copies that they don't possess, so if Novell decides to fork the current Samba as "GPLv2 or later" or even "GPLv2 only" they could do so. But they couldn't take any updated code from the Samba team without going GPLv3.
"Anyone can take GPLv2 or later code and relicense it as "GPLv2 only" or "GPLv3 only" or "GPLv3 or later" or even "GPLv4". It's at the *user's* discretion (read the license)."
Hmmm, no. You can't relicense the code, only the original copyright holder can.
If the code is licensed "v2 or later", *you* can choose to follow the terms of version 2, 3, 4, etc., but when you redistribute the code, the people that receive it *must* receive the right to do the *same*. If you redistribute the code as "v3 or later", you are limiting the rights of the recipients by preventing them from choosing to follow v2's terms.







Member since:
2006-01-03
There's something that I don't get... Does the samba team require all contributors to assign copyright to them (just like most GNU projects require contributors to assign copyright to the FSF)?
If they don't, then they can't actually change the licence without permission from everyone that made a contribution, however small, because they (implicitly) licensed their code as "v2 or later" and not "v3 or later".