Hacker News new | ask | show | jobs
by kmeisthax 1029 days ago
RMS also changed GPLv3 to specifically forbid exactly the kind of lawsuit being threatened in the commit message.
2 comments

Sure - I think there's a hair to be split here where we could argue that weaponizing anti-circumvention logic in GPLv2 is generally in the spirit of the GPL as a whole, but then also say they in GPLv3 we decided to remove it because while it's in the spirit, it's too dangerous, and net-better for user freedom if using GPLv3 software doesn't carry the risk of accidentally tripping up anti-circumvention laws.
I get the impression that GPLv2 is (perhaps unintentionally) in the spirit of open source, whereas GPLv3 is in the spirit of Free Software. Thus Linus's famous "I just want the code" rant.
GPLv2 was created by and for the free software movement. The notion that it is somehow more aligned with a depoliticized, whitewashed ancestor of that movement than it is with the real deal is absurd.
It's absurd, but true. I do think it's unintentional, but due to historical reasons GPLv2 doesn't prevent tivoization, which is more aligned with open source than with free software.

Again, I'm not discussing what the intentions were, nor what the practical effects used to be 20 years ago, I'm referring to it's position today.

Suppose a hypothetical that GPLv2 never existed and that the GPLv3 was written in 1990, then someone came along today and wrote a variant of GPLv3 that specifically permitted tivoization and firmware blobs; surely such a license would be seen as moving from open-source to free software.

Link to Linus' rant please?
I am less familiar with the lawsuit sections of GPLv3; would you mind pointing to the relevant sections?
GPLv3 has the following clause:

>3. Protecting Users' Legal Rights From Anti-Circumvention Law.

>No covered work shall be deemed part of an effective technological measure under any applicable law fulfilling obligations under article 11 of the WIPO copyright treaty adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention of such measures.

>When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures.