On Thu, 30 Jan 2020 08:19:08 -0500 Rich Freeman <ri...@gentoo.org> wrote:
> Really the main threat (IMO) is that the code could be de-copylefted. > They could make GPL v4 a copy of the BSD license, and now anything > that was v2+ is effectively BSD and can be used in non-FOSS software > without issue. I guess that isn't any worse than the previous case of > it instead being merged into some other v4 variant that you can access > the source for but prefer to avoid because of something else in the > license, except now you might not see the code at all. Its like we need some sort of statement people can use that says something to the effect of: - GPL versions published after this release may be used, but contingent on the author of this release verifying that newer GPL versions continue the intended spirit of GPL2 The idea that my code might be later under some other terms of license that I've never read is about as bad as somebody updating EULA/TOS without informing anybody it changed. Its *probably* fine, but I'd want to have opportunity to read those before rubber stamping it. As they say: Trust, but Verify. GPL terms changing after an authors death should not really apply retroactively to the dead authors code.
pgppHmDJ7BLMD.pgp
Description: OpenPGP digital signature
