Hacker News new | ask | show | jobs
by Smithalicious 2454 days ago
I take issue with the "promote ... the best use of copyleft (GPL version 3-or-later)" here. The GPL is a controversial license by itself, though it's the de facto copyleft license and reasonable to promote it, but the GPLv3-vs-GPLv2 debate is alive and well and I don't want GitHub to "promote" either of them as "the best".
2 comments

Were you ever affected by the GPL3 vs GPL2 license? I am just wondering who is affected(not everybody makes kernels and drivers)
Any MacOS user who has to put up with having bash-from-2006 as the default shell has been affected by GPL2 vs GPL3.
Correction: any MacOS user is affected by Apple's decision not to update bash.
...due to changes in v3 which Apple sees as incompatible with their business model. That is an effect of v3. By your logic v3 never affects anyone because there's always a human decision behind whether or not to adopt it or to integrate software which does.
Yes my large tech company has a blanket ban on us using GPLv3 (it's possible to get some exceptions but a pain in the arse), but no problem with GPLv2
Readline is distributed only under GPLv3 nowadays. I worked on some software licensed only under GPLv2, where some authors are no longer available. GPLv2 and GPLv3 aren't compatible.
Thanks for you response but I am not understanding, you wanted to copy paste some code from a GPL2 project into a GPL3 one ?
He probably wanted to link the Readline library into his GPL2 program, which according to the owner of the library (the FSF) is not permitted and might have led to his employer's getting sued by the FSF for copyright infringement or at least to his employer's lawyers getting scared, then badmouthing him to management.
TL;DR on GPLv3-vs-GPLv2: the v3 adds a protection against hardware lock-ins. It doesn't come up in 95% of the cases. But the license is different, so a debate can be started.