https://www.gnu.org/software/emacs/manual/html_node/emacs/Co...
So opened - https://github.com/Wilfred/remacs/issues/238
https://www.gnu.org/software/emacs/manual/html_node/emacs/Co...
So opened - https://github.com/Wilfred/remacs/issues/238
God knows how many GPLed lines of code has not been submitted back upstream to them over this minor technicality, and that's such a shame.
I honestly think this is for the FSF to fix, not everyone else.
How many legal disputes have the FSF had recently, in practice, where this turned out crucial?
More specifically: how much have they gained by this vs how many contributions have they lost?
Until proven otherwise, I'd expect them to clearly be in the negative here.
If there was evidence that some third party could enforce GPL compliance on behalf of the copyright holder(s) then maybe the FSF should consider relaxing the requirements.
Do you recall that Sony failed to comply with the GPL when they used LAME? The LAME community wasn't prepared to actually do anything about it. That's the kind of shit that would happen, especially to smaller projects. There are big companies out there that want to use your hard work without compensation and shit all over the GPL. Never forget that.
I'll rather have code which is harder to defend than defense for code I never got.
https://lists.gnu.org/archive/html/emacs-devel/2017-07/msg00...
Copyright assignments allow the FSF to enforce the GPL on Emacs.
I know plenty of people who won't bother on plain principle, and that's both people and code which the FSF is missing out on.
New times. New standards. Get with the program FSF.