IANAL, but the MIT license specifically does not say you have to redistribute with the same copyright owner notice. It says the copyright notice and terms must remain, and that you can sublicense it. It doesn't say you can't change the copyright notice.
Microsoft forked MIT licensed repo and changed the copyright [fixed]
211–220 of 626 posts
Re: Microsoft forked MIT licensed repo and changed the copyright [fixed]
#212Earlier quoted context omitted.
I am not, and have never been a Microsoft employee. You can search online for my name / username to find my open-source contribution history, if you would like. I hope that sufficiently answers your query.
Quoted post unavailable.
Re: Microsoft forked MIT licensed repo and changed the copyright [fixed]
#213The attitude in these threads always boggles my mind. When YOU, your teammates or someone else you know makes a mistake, then it’s just a mistake. But when someone at Microsoft makes a mistake it’s because Microsoft is evil and by extension so is the person who offended. “It’s a big company”, you say. They should have a process! And I’m sad to say, they do/will have a process exactly because of this attitude. Then, e…
1. They made similar mistakes in the past.
2. They didn't fix it for half a year.
3. They can expect strong financial benefits from making these mistakes.
4. They've recently burned a lot of goodwill by deliberately infringing licenses on a large scale when they trained Copilot.
5. They could have easily prevented this kind of mistakes.
My summary would be that Microsoft deserves to be punished for making this mistake. If nothing bad happens now, then we'll have the same discussion again in half a year from now.
Re: Microsoft forked MIT licensed repo and changed the copyright [fixed]
#214The attitude in these threads always boggles my mind. When YOU, your teammates or someone else you know makes a mistake, then it’s just a mistake. But when someone at Microsoft makes a mistake it’s because Microsoft is evil and by extension so is the person who offended. “It’s a big company”, you say. They should have a process! And I’m sad to say, they do/will have a process exactly because of this attitude. Then, e…
This is their process. Very hard to argue these are all mistakes: ippsample (Apache -> MIT) https://github.com/microsoft/ippsample/commit/938bff17c72868... huggingface-transformers (Apache -> MIT): https://github.com/microsoft/huggingface-transformers/commit... health-cards-tests (MIT changed) https://github.com/microsoft/health-cards-tests/commit/5649b... CUPS (Apache -> MIT) https://github.com/microsoft/cups/commit…
It seems the automation is also triggered when Repos are forked into the Microsoft GitHub org which isn't correct behavior.
This isn't a deliberate action. If it were plenty of employees (myself included) would be outraged. I assume it's a bug in the bot - an edge case that was not considered. It is very rare to fork something into the Microsoft GitHub org after all.
I'll pass it along to some people I know.
Re: Microsoft forked MIT licensed repo and changed the copyright [fixed]
#215Earlier quoted context omitted.
It is wrong as a specific statement about GitHub, because regardless of current practice, the legal theory for Copilot applies to any code anywhere, so anything that is publicly accessible would involve the same risk. It's not dependent on use of GitHub even if Microsoft has initially started their because it's easier for them.
So this sense of “wrong” is similar to “correct”. Also, I don’t see how this is true. Code on my website is publicly accessible, but not in the public domain, nor licensed for re-use, unless I say that it is.
Re: Microsoft forked MIT licensed repo and changed the copyright [fixed]
#216The attitude in these threads always boggles my mind. When YOU, your teammates or someone else you know makes a mistake, then it’s just a mistake. But when someone at Microsoft makes a mistake it’s because Microsoft is evil and by extension so is the person who offended. “It’s a big company”, you say. They should have a process! And I’m sad to say, they do/will have a process exactly because of this attitude. Then, e…
A healthy org doesn’t blame individuals, it blames failures in process. Thus Microsoft should own this mistake. Stating it’s the fault of an individual sounds more like your team operates a blame culture. Which, frankly, is a major red flag for a failing organisation.
Re: Microsoft forked MIT licensed repo and changed the copyright [fixed]
#217The attitude in these threads always boggles my mind. When YOU, your teammates or someone else you know makes a mistake, then it’s just a mistake. But when someone at Microsoft makes a mistake it’s because Microsoft is evil and by extension so is the person who offended. “It’s a big company”, you say. They should have a process! And I’m sad to say, they do/will have a process exactly because of this attitude. Then, e…
In my opinion, this gets a strong reaction because: 1. They made similar mistakes in the past. 2. They didn't fix it for half a year. 3. They can expect strong financial benefits from making these mistakes. 4. They've recently burned a lot of goodwill by deliberately infringing licenses on a large scale when they trained Copilot. 5. They could have easily prevented this kind of mistakes. My summary would be that Micr…
Re: Microsoft forked MIT licensed repo and changed the copyright [fixed]
#218Earlier quoted context omitted.
How is running a bot to change copyright notices a /mistake/? > Full disclosure: I work for MS It is difficult to see the reality distortion field you are in from the inside.
I used to work for MS and... it's still easy to see it from the inside lol
My personal conspiracy theory is Teams would have died long ago if not for strong support from the top.
Re: Microsoft forked MIT licensed repo and changed the copyright [fixed]
#219Earlier quoted context omitted.
How is it not intentional? To me it seems very clear that someone designed this bot to specifically alter the LICENSE file so that it matches some sort of predefind Microsoft file. Edit: To give a bit more nuance, I would guess that the actual bot changing the LICENSE files is not a mistake, but working as intended. What could, however, be a mistake is thinking that licenses can be legally overwritten. It wouldn't be…
Because a bot like this could never used on internal libraries that are about to be open sourced?
That's not a bot.
Re: Microsoft forked MIT licensed repo and changed the copyright [fixed]
#220The attitude in these threads always boggles my mind. When YOU, your teammates or someone else you know makes a mistake, then it’s just a mistake. But when someone at Microsoft makes a mistake it’s because Microsoft is evil and by extension so is the person who offended. “It’s a big company”, you say. They should have a process! And I’m sad to say, they do/will have a process exactly because of this attitude. Then, e…