4 ms·
That's fair - although I can't imagine letting someone rename my project and deciding to collaborate on it together while still trying to retain my own copyrigh
by TallGuyShort 11y ago
That's fair - although I can't imagine letting someone rename my project and deciding to collaborate on it together while still trying to retain my own copyright notice on files. I hope we hear the other side of the story. My point is just that the MIT license itself isn't necessarily the issue here.
- icebraining 11y agoThat's fair - although I can't imagine letting someone rename my project and deciding to collaborate on it together while still trying to retain my own copyright notice on files. I don't understand, why not? That's in fact what usually happens; projects usually have a list of contributors, providing attribution. For example: https://www.kernel.org/pub/linux/kernel/CREDITS https://www.kernel.org/pub/linux/kernel/CREDITS
- TallGuyShort 11y agoThe collaboration model of the Linux kernel is not remotely what I think the context describes. But like I said - perhaps reality is different - I still hope to hear the other side.
- charles2013 11y agothis hn comment links to a github comment (from the other side) that was deleted by the usurper: https://news.ycombinator.com/item?id=10273780 https://news.ycombinator.com/item?id=10273780
- TallGuyShort 11y agoThanks. There's this too: https://github.com/derekstavis/diary-of-a-stolen-repository/commit/e58087908f2e84a998c2ebe4ffcf36d2f8193fe4 https://github.com/derekstavis/diary-of-a-stolen-repository/...