Earlier quoted context omitted.
It doesn’t matter that it was an accident; it’s still a serious issue that needs to be corrected and deserves an upvote. It’s also quite curious, and I appreciate hearing about the incident. Incidents don’t need to be malicious to be newsworthy or intriguing.
Quoted post unavailable.
Microsoft forked MIT licensed repo and changed the copyright [fixed]
31–40 of 626 posts
Re: Microsoft forked MIT licensed repo and changed the copyright [fixed]
#32So you can't do that? I do it all the time when I fork something.
EDIT: also if there are any forks of your project, you should ask people who forked it to restore the original copyright notice as well. If the original copyright holder sees your name instead of theirs, they'll know who to sue.
Re: Microsoft forked MIT licensed repo and changed the copyright [fixed]
#33Quoted post unavailable.
Intentional, manual or not, projects are now attributed to Microsoft when they should not.
Re: Microsoft forked MIT licensed repo and changed the copyright [fixed]
#34Earlier quoted context omitted.
It doesn’t matter that it was an accident; it’s still a serious issue that needs to be corrected and deserves an upvote. It’s also quite curious, and I appreciate hearing about the incident. Incidents don’t need to be malicious to be newsworthy or intriguing.
Quoted post unavailable.
How often have we seen closed accounts getting resolved after complaining about it on HN/Twitter/Etc.
I’m not saying tha to how it should be, just what it’s become.
Re: Microsoft forked MIT licensed repo and changed the copyright [fixed]
#35Earlier quoted context omitted.
It doesn’t matter that it was an accident; it’s still a serious issue that needs to be corrected and deserves an upvote. It’s also quite curious, and I appreciate hearing about the incident. Incidents don’t need to be malicious to be newsworthy or intriguing.
Quoted post unavailable.
Re: Microsoft forked MIT licensed repo and changed the copyright [fixed]
#36So you can't do that? I do it all the time when I fork something.
Re: Microsoft forked MIT licensed repo and changed the copyright [fixed]
#37What is the point of using all caps? For me it makes legal texts like these really annoying to read. I'm not a native English speaker, is that really correct English writing? Aren't there clear rules when to use capitalization? Like, at the beginning of sentences. Feels like they are abusing the language.
Can they just lower case the paragraphs, to make things more convenient to read? Or does that change the legal meaning? For me it would feel like they would stop screaming :-)
Re: Microsoft forked MIT licensed repo and changed the copyright [fixed]
#38Original author could send a DMCA, or they could simply enjoy Christmas and assume a ticket will undo this sometime in January.
Re: Microsoft forked MIT licensed repo and changed the copyright [fixed]
#39Earlier quoted context omitted.
It doesn’t matter that it was an accident; it’s still a serious issue that needs to be corrected and deserves an upvote. It’s also quite curious, and I appreciate hearing about the incident. Incidents don’t need to be malicious to be newsworthy or intriguing.
Quoted post unavailable.
It's the latter action that's being addressed here.
Re: Microsoft forked MIT licensed repo and changed the copyright [fixed]
#40Earlier quoted context omitted.
It doesn’t matter that it was an accident; it’s still a serious issue that needs to be corrected and deserves an upvote. It’s also quite curious, and I appreciate hearing about the incident. Incidents don’t need to be malicious to be newsworthy or intriguing.
Quoted post unavailable.
e.g.: Anyone remembering AppGet? [0][1]
[0]: https://www.theverge.com/2020/5/28/21272964/microsoft-winget...
[1]: https://www.theverge.com/2020/6/2/21277863/microsoft-winget-...