lzybkr is a developer on the poweshell team, and who I would guess is reacting according to standard operating procedure. Then jpsnover, who is a Technical Fellow (a senior position) gets involved and makes the call to start the RFC process. This seems like a reasonable escalation process to me. lzybkr may well not have the authority to commit to an investigation/fix.
They don't even have an obligation to consider outside PRs, let alone provide a reason. It's rather a stretch to say people who want to change the behavior of PowerShell are their main customers.
Depends what main customers you are thinking off. For this product in particular, it seems these users might be potential customers of powershell. Each product has it's own main customers.
> I think MSFT needs to try harder at their customer service. Their first response from a human was hard rejection response
All open source projects (on github and everywhere else) that require a contributor agreement do the same thing (e.g. Android). They usually have bots that auto close pull requests when the person hasn't signed the agreement first.
It's an unfortunate but necessary requirement for some projects. There's no malice, just bureaucracy.
He wasn't talking about the attribution bot (which did not actually reject the change). He was talking about the first human response from lzybkr, which was a "no, it's a breaking change".
They are people that work at company's that have the option of buying Microsoft products that will discourage coworkers from buying Microsoft products...
lzybkr wrote "We are rejecting this PR as it introduces "Unacceptable Changes", see our breaking change contract."
It is not, "let's investigate it where what the problem is and get back to you some feedback.".