Particularly with how they interact on GitHub now, it's quite impressive. I've reported issues for docs.microsoft.com, participated in discussions on Visual Basic development, etc. and while there's still definitely that corporate veil to some degree, they're extremely responsive, they're very active in responding to requests and discussing fixes.
I generally now hope that whatever Microsoft thing I'm dealing with somewhere ends up linking to GitHub, because everyone on the side of the company that's working with GitHub is pretty on point.
Which is what gives me some hope that they could manage this acquisition right: They're already doing GitHub the way GitHub should be done.
Even when it leads from GH to internal email chains, they're really good about keeping those on the GH issue in the loop... often from only parallel issues.
Issue filed in node sql driver... azure tech notices the issue, raises to sql team... sql team dev starts replying and working to resolve... recommends patch to upstream project in github... issue resolved.
Oracle would NEVER do something like that. It was actually very impressive, and that's just my one anecdote, and I've seen many others.
I generally now hope that whatever Microsoft thing I'm dealing with somewhere ends up linking to GitHub, because everyone on the side of the company that's working with GitHub is pretty on point.
Which is what gives me some hope that they could manage this acquisition right: They're already doing GitHub the way GitHub should be done.