Skip to content

Comment on Relicensing Dolphin: The long road to GPLv2+parent

Comments

they _could_ do so.

They already wrote legalese that says that they can't do so. This isn't merely an empty promise: it's already encoded into the text of the license. If a later version of the license is radically different and not in spirit of the GPL or imposes upon authors obligations that earlier versions of the GPL do not, then the current version of the GPL already says that later version would be invalid.

Would the anti-TiVoization wording in the GPLv3 count as "obligations that earlier versions of the GPL do not [impose]", and if so, does that mean that the GPLv3 is invalid?

The obligations are upon the authors and copyright holders. So, for example, a later version can't remove the no warranty clause, because that would burden the authors with providing warranties.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.