On one hand that’s fair, but on the other hand Microsoft is the biggest name in software development and ffmpeg is a volunteer gig, this is probably a problem the megacorp can handle.

They offered a one time gift in the thousands of dollars. They were planning to do that anyway.

the FFmpeg version is currently used in a highly visible product in Microsoft. We have customers experience issues with Caption during Teams Live Event.

This seems like a “you” problem, Microsoft, and since you employ thousands of programmers with the experience to solve your problem and commit the change back to the FOSS project, I think this is also very easily a “you” solution as well.

You either learn to work within a system or you build your own system. Guess where the money is.

At the end of the day, following your own coding preferences isn’t the fun part of the job. The fun part of the job is looking back and saying “hey, I did that.”

I think Copilot would get a lot more takers if it looked like this. https://xkcd.com/1838

But a few lines later:

Although we’ll be hosting the repository on GitHub, our contribution workflow will remain unchanged and we will not be accepting Pull Requests at this time

So I don’t know if you meant that the focus of the change wasn’t GH or that they weren’t using GH at all, but it seems like the latter is untrue.

TS is open-source, so if they do I’m certain that there will be a fork available within moments.