News for hackers. Stuff that matters.
Re:Announcing .NET Foundation Open Membership by ocdtrekkie on Tuesday December 04, 2018 @02:50PM (#18603025)
I just want to point out that you will not need to pray to God to get a PR accepted in a Microsoft repo if their docs team is any indication. They are nearly aggressively professional at handling GitHub issues. Minor mentions of confusions I've had on docs.microsoft.com were zealously assigned, pursued, and fixed, and the PRs I submitted to the code samples there were approved within a day or two.
Re:Announcing .NET Foundation Open Membership by GordonS on Tuesday December 04, 2018 @06:43PM (#18604543)
I've had the same experience with docs, but the polar opposite with .NET Core FX and ASP.NET Core - seems any new features need to be discussed by committee, and can take several months or even years before they will then say "OK, send a PR", even for features that there is demand for.

Even for bugfixes, I've been really dissapointed in their responses - they call any change in behaviour a 'regression', and won't accept fixes, even if the behaviour they want to preserve only exists as a side effect of the bug, and nobody could possibly want in any case!

I write this as a .NET fanboi, but my negative experience of trying to contribute to Microsoft's OSS projects has been left me dissolutioned.

Re:Announcing .NET Foundation Open Membership by setquk on Tuesday December 04, 2018 @04:55PM (#18603927)
Versus the whole "we don't want telemetry on by default" argument which the response was "fuck off" then they shipped packages for Debian that the "disable the telemetry" environment variable didn't work on...
Re:Announcing .NET Foundation Open Membership by SaltyBackendGuy on Tuesday December 04, 2018 @03:03PM (#18603138)
I've had the opposite experience about a year ago with their Node.js PowerBI repo. Although, they deprecated that SDK within a few months after, so it's possible it was more of a resource issue.