Reasons to upgrade your code to GPL version 3 from GPLv2

Richard M Stallman the person who gave us the GPL version 2 licence on which Linux kernel and scores of programs are based on has written a very informative piece citing the pertinent reasons that one should consider moving ones code from GPL version 2 to the GPL version 3 when it is finally released.

Some of the points he makes in the article are as follows :

• There is no problem in having GPLv3-covered and GPLv2-covered programs side by side in an operating system. For example if Bash and GCC move to GPLv3, while Linux remains under GPLv2, there is no conflict.
• GPLv3 will block tivoization which allows embedded consumer appliances to contain GPLed code which the end user is not allowed to change. But GPLv3 tolerates tivoization for products that are almost exclusively meant for businesses and organizations.
• GPLv3 doesn't forbid DRM (Digital Restrictions Management) but under GPLv3, the end user will have the power to remove the DRM if he so chooses to.
• GPLv3 comes down strongly on software patents. So it provides for explicit patent protection of the users from the program's contributors and redistributors. Which means a person or company using a GPLv3 program is never going to get sued because the program infringes on some software patents.
• Other features of GPLv3 include better internationalization, gentler termination, support for BitTorrent, and compatibility with the Apache license.
  

Ultimately GPLv3 licence even after it is finally released some time this year will be an ongoing process and might lead to GPLv4 if and when new threats to Freedom are encountered.

You can read the full article written by Richard.M.Stallman at the fsf.org website.