Live data from Hacker News

Microsoft forked MIT licensed repo and changed the copyright [fixed]

github.com

451–460 of 626 posts

Re: Microsoft forked MIT licensed repo and changed the copyright [fixed]

#451

I lead the Microsoft Open Source Programs Office team. I'm sorry this happened. We have merged a pull request that restored the correct LICENSE file and copyright, and are in touch with the upstream author Leśny Rumcajs who emailed us this morning. We'll look to revert the entire commit that our bot made, too, since it updated the README with a boilerplate getting started guide. The bug was caused by a bot that was d…

Thank you for showing up on Christmas to address this. Have a great holiday!

Re: Microsoft forked MIT licensed repo and changed the copyright [fixed]

#452
post #391

What's surprising to me about all the negative reactions Microsoft receives, especially on here, is that from my point of view, they are currently the most open out of all the big companies (Google, Facebook, Apple, etc). I cannot remember a time Apple has admitted to anything or made any effort to have anything that could be considered open, but they do no wrong in most people's eyes, where even a simple mistake by…

Google contributed the enormous k8s to the community, which has thankfully made Microsoft's proprietary Service Fabric mostly go away.

Apple have caught huge flak recently e.g. for the phone-local image scanning software.

Re: Microsoft forked MIT licensed repo and changed the copyright [fixed]

#453
post #348

Earlier quoted context omitted.

Yeah, I think this is an example of addressing a mistake that other companies should take note of. I don’t trust Microsoft-sized corporations as a matter of principle, and I don’t typically give them the benefit of the doubt, but when one of their own engineers explains in human-readable terms what specifically happened—on a holiday, no less—I’m impressed enough to believe him. Some PR flack showing up with vague boi…

Quoted post unavailable.

An engineer who can write straightforwardly is worth 100 PR people in situations like this.

They're not paid like that, but they are worth that.

Re: Microsoft forked MIT licensed repo and changed the copyright [fixed]

#454

Earlier quoted context omitted.

Thanks for explaining. Out of curiosity, does Microsoft have any external-facing GPL-licensed projects? Are there any restrictions to using (i.e. open sourcing something developed internally or forking something from outside MS) GPL-licensed projects? Specifically, would teams be able to get approval to fork GPL repos?

Git for Windows comes to mind. Teams can absolutely get approval for any open source license; however, for a GPL project, we'd have their open source legal team work with them to brief them on the license obligations and requirements, such as publishing code to https://3rdpartysource.microsoft.com/ .

Interesting, so that's specifically for GPL-licensed projects? Or am I misunderstanding and you would have dev teams work with Legal for any open source licensed project?

Re: Microsoft forked MIT licensed repo and changed the copyright [fixed]

#455
post #401

Earlier quoted context omitted.

Do you mind addressing the reason why an employee did exactly what you are claiming the bot did in error? https://github.com/microsoft/cups/commit/8100595a3a3a6d5c7d0... Again, this is a person, not a robot. How does this play into a "software bug"?

Honestly, I'm not sure what happened here. My guess is that they were going through a checklist of what to do when releasing open source changes, and didn't understand what they were doing. A lot of why we've had to put some guardrails in our system has been to point people to guidance and training on open source. I've sent the team that works on this repository an e-mail, but I don't expect to get a response on the…

Thanks for the response. Mistakes happen, human or computer, not the end of the world, and I get it. I was just more curious to know if there is a manual process for this type of forking that was not being vetted via the bot, and to bring another example to your attention.

Re: Microsoft forked MIT licensed repo and changed the copyright [fixed]

#456
post #434

Earlier quoted context omitted.

Note these are thrown-over-the-wall source dumps, with no valuable VCS history, nothing more recent than at least 2 releases ago, and sending a PR will likely only receive crickets (said as someone who recently found an easily patchable bug in dyld, contemplated the idea of opening a PR and was told by an ex-colleague who now works at Apple that my best shot would be through feedbackassistant.apple.com). BTW, those r…

I just got a security bug fixed last month in dyld in one release cycle. Didn't strike me as difficult. I emailed them, and they fixed it. Not much more to add then that. Have you actually tried? Also dyld isn't just some thrown-over the wall code. It's completely designed and built by Apple and is the cornerstone to making the user-space runtime functional.

All the code designed and built by Apple is thrown-over-the-wall. That's old-version-of-source-available, barely open source.

I tried emailing ld64's author about a bug in the past without success. I don't remember how I found their name/address back then, but I sure can't find any names or contact information for dyld right now...

Re: Microsoft forked MIT licensed repo and changed the copyright [fixed]

#457
post #391

What's surprising to me about all the negative reactions Microsoft receives, especially on here, is that from my point of view, they are currently the most open out of all the big companies (Google, Facebook, Apple, etc). I cannot remember a time Apple has admitted to anything or made any effort to have anything that could be considered open, but they do no wrong in most people's eyes, where even a simple mistake by…

what surprises me the most about Microsoft related hate is that, despite the fact that they had (still have pretty much) control over the OS market they never locked their system down or charged people in any capacity. People take it for granted that you can just run what you want on your windows machine but they could have turned it into smartphone style locked down system. Imagine if every app developer in history…

While it's not locked, they're certainly pushing you that way. For example the only built-in installer for VS projects right now essentially gives you a choice of either a plain directory of files, or a nice process to release to the windows store. Want a simple MSI/installer - deal with the pain yourself.

Once you do try to distribute your own app, you need to shell out >$200/yr for code signing certificates which pass the smartscreen filter, otherwise your app will be randomly prevented from running.

And other issues... With every version things get just a tiny bit more inconvenient for out-of-store software releases.

Re: Microsoft forked MIT licensed repo and changed the copyright [fixed]

#458
post #434

Earlier quoted context omitted.

I just got a security bug fixed last month in dyld in one release cycle. Didn't strike me as difficult. I emailed them, and they fixed it. Not much more to add then that. Have you actually tried? Also dyld isn't just some thrown-over the wall code. It's completely designed and built by Apple and is the cornerstone to making the user-space runtime functional.

All the code designed and built by Apple is thrown-over-the-wall. That's old-version-of-source-available, barely open source. I tried emailing ld64's author about a bug in the past without success. I don't remember how I found their name/address back then, but I sure can't find any names or contact information for dyld right now...

What on earth are you talking about? ld64 is a completely different beast than dyld in today's world.

Also, I'm not sure looking for individual points of contact in a large org is the best idea. I emailed security@apple.com. Even if it's not a security bug they will help direct you to the right team.

Again, have you even tried?

Re: Microsoft forked MIT licensed repo and changed the copyright [fixed]

#459
post #411
post #391

What's surprising to me about all the negative reactions Microsoft receives, especially on here, is that from my point of view, they are currently the most open out of all the big companies (Google, Facebook, Apple, etc). I cannot remember a time Apple has admitted to anything or made any effort to have anything that could be considered open, but they do no wrong in most people's eyes, where even a simple mistake by…

Literally half the operating system is open source macOS, they have an entire site dedicated to it. opensource.apple.com. Oh and don't forget googles ridiculous amount of effort poured into Android open-source source tree, just to name one of many. I honestly can't tell if you are trolling here or not.

[deleted]

Re: Microsoft forked MIT licensed repo and changed the copyright [fixed]

#460
post #178

The 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…

Quoted post unavailable.

FS I’m not sure about. Office goes into massive nag mode.

What’s your point?

Post reply on HN