3 ms·
> Further, only Github has been given this waiver. Anyone else is still held to any requirement of attribution. This convinced me. I can release my code under
by Buttons840 10y ago
> Further, only Github has been given this waiver. Anyone else is still held to any requirement of attribution.
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.
- flukus 10y agoBut some projects don't have the copyright of the original author/s, particularly forked ones.
- notzorbo3 10y agoEven 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.
- vsl 10y agoThat's all fine if your project is a tiny one and you never ever accepted any contribution or used any dependency.