Except it's not the FSF blocking the work, it's UC Berkeley blocking the work. The FSF's copyright assignment policy is very important.https://twitter.com/RichFelker/status/783482575633408001 …
...is stuck permanently maintaining a fork/patches out-of-tree. The code is effectively license-incompatible with upstream.
-
-
For GCC and binutils, a reasonable compromise would be to drop the assignment requirement for target support code.
-
For example if I wanted to forward-port the ARM FDPIC work ST did to modern GCC & upstream it, I'd have to worry about assignment.
-
If anything fell through, all my work would then be a waste. All despite the code already being GPL'd...
-
...where the whole point of GPL is supposed to be that the code is permanently free and others can pick up abandoned work.
-
I fully understand your position, and the flaws in assignment. But assignmnet has been positive, too.
-
Do you have any examples of concrete benefits that have come out of requiring assignment, not already achieved by "or later"?
-
the tivoization stuff is an example of this. "Or later" is for the user. In order to move to 3+, we needed assignment.
-
Nonsense. If a whole work is licensed under 2+, you can make a derivative licensed under 3+. GPL allows that.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.