2 ms·
This is a very professional and level headed response by the VS Code team. I hope people reference this in the future to learn how to handle and respond openly
by mey 7y ago
This is a very professional and level headed response by the VS Code team. I hope people reference this in the future to learn how to handle and respond openly to divisive issues.
- snazz 7y agoYou're being downvoted, but I agree that Microsoft did the best they possibly could have in this situation: getting the off-topic (and potentially offensive on their own) threads and comments on the issue tracker out of view, making the Santa hat a configurable choice, and still maintaining a decent standard of transparency.
- NewsAware 7y agoI would personally love to add a response along the lines of "professional yes, but they should have..." regarding their stance, but no - you are right. This is an exceptionally professional response and the discussion regarding PC, wokeness etc belongs elsewhere.
- Aqua 7y agoThis is not a divisive issue, the account that raised the issue is most likely fake, the person behind it intended to trigger and divide people and they succeeded at that. The world is no paradise, you will never satisfy everyone nor should you try to. Microsoft's response is cringeworthy.
- mey 7y agoBy us being here, that so many people objected to the removal of an easter egg in a developer channel release, to me, indicates there is a serious schism. I expect people are using this as a proxy for concerns about PC culture and "the war on christmas". This written description of what happened, and how the team is handling what happened going forward is transparent and respectful, that is what I am attempting to comment on.
- temac 7y agoThis is a professional reaction to a shitty situation they created mostly themselves. The proper even more professional thing to do would have been to not react to the initial troll in the first place.
- sdinsn 7y agoI disagree. This wasn't a divisive issue, this was ONE troll who raised an issue. MSFT should have simply said "No" to this troll. It's also worth mentioning that the original issue violated Code of Conduct as well, but for some reason MSFT only applied the Code to posts following it.