Re:New GitHub Terms of Service require removing many open-so...
by flukus on Thursday March 02, 2017 @12:06AM
(#13771562)
But some projects don't have the copyright of the original author/s, particularly forked ones.
Re:New GitHub Terms of Service require removing many open-so...
by notzorbo3 on Thursday March 02, 2017 @03:59AM
(#13772688)
Even worse, if you've ever accepted a patch or pull request and didn't get copyright transferred to you, then that code is still owned by the author of the patch, and you'll need their permission too.
edit: I don't think forked repos are much of a problem. They're already on Github, so they already accepted the ToS. if they didn't, that's not your problem as a forkee. Unless the code was forked before this new ToS. Copyright is so messy.
This convinced me.
I can release my code under GPL, and then sell it to someone else under different terms. It's my code, and I have copyright. I don't have to give the same permissions to everyone.
Likewise, just because I give Github certain permissions doesn't mean I have given the same permission to everyone else.