Doesn't the GPLv2 state that one is not allowed to release further versions of GPLv2 software under a different license? That pretty much makes the FSF switching future software to the GPLv3 a moot point, since Tivo can keep doing what they're doing with v2 software.
Agreed. Big shot in the foot for the administration to start picking fights with China. The fact that they manufacture everything that the U.S. and others use is the only reason we don't have an embargo with China like we do with Cuba. Money talks.
A government like China's can make people they don't like(e.g., journalists) "disappear" when they really want to. So to me, it doesn't look like they really care about piracy. And why should they? It doesn't really affect their economy...
Do you really need these coders who are disruptive? You should weigh what you would get in keeping them against how much damage they are causing.
If they are excellent coder(s), maybe you could look the other way.
But if they are only OK (or not great), you probably should look for someone else to save yourself some pain.
Doesn't the GPLv2 state that one is not allowed to release further versions of GPLv2 software under a different license? That pretty much makes the FSF switching future software to the GPLv3 a moot point, since Tivo can keep doing what they're doing with v2 software.
My grandfather has dementia and still passed the driving test.
Since France helped America during the American Revolution.
French Revolution, Part 2.
This seems to me like tipical Microsoft schtick. Release first, fix it later.
Agreed. Big shot in the foot for the administration to start picking fights with China. The fact that they manufacture everything that the U.S. and others use is the only reason we don't have an embargo with China like we do with Cuba. Money talks.
A government like China's can make people they don't like(e.g., journalists) "disappear" when they really want to. So to me, it doesn't look like they really care about piracy. And why should they? It doesn't really affect their economy...
ReactOS was frequently accused of being tainted by Windows source. It made the project have to do a long code audit.
Do you really need these coders who are disruptive? You should weigh what you would get in keeping them against how much damage they are causing. If they are excellent coder(s), maybe you could look the other way. But if they are only OK (or not great), you probably should look for someone else to save yourself some pain.
The "wow" ends now!
I've always wanted to do this with a minivan.
They could give a bare kernel, leave out alot of modules, give a disassembled version , or just give an entirely fake version.