4 ms·
ok so my github project created 17 days ago with unlicense I recently checked in a change to the file LICENSE and then today I reverted it: https://github.com/
by andrewfromx 6y ago
ok so my github project created 17 days ago with unlicense I recently checked in a change to the file LICENSE and then today I reverted it:
https://github.com/andrewarrow/base9/commit/f920f311b1b0afe863e340303f9b95bdeae74584 https://github.com/andrewarrow/base9/commit/f920f311b1b0afe8...
but if I CAN go mit now, surely I have to rename my project and make a new repo? If I continue in repo as is, years go by, can't someone argue the change to MIT didn't have the legal authority to remove it from the public domain?
- dragonwriter 6y ago> but if I CAN go mit now, surely I have to rename my project and make a new repo? No. > If I continue in repo as is, years go by, can't someone argue the change to MIT didn't have the legal authority to remove it from the public domain? To the extent the Unlicense is valid in the jurisdiction whose law would apply, they would certainly have the right to use any material previously released under that license under its terms. That doesn’t obligate you to continue hosting it with that license, or to use a different project name for a derivative you distribute with a more recent license, or even notify that you ever had some part of it offered under the Unlicense. It may prevent you from distributing exactly the same content with a copyright claim, so its probably best to make the license change with a substantive code change.
- andrewfromx 6y agook, makes sense, but there does seem to be some gray area with how substantial the code change has to be. And when I start a new repo, I'm going to stop using unlicense. I feel like I was tricked.