I've been in a three different scenarios where I worked for independent companies under the umbrella of a large parent organization. In all 3, the leadership left or was fired, and the remainder of the company was merged into a division of the parent company.
The product quality went to shit in all 3 scenarios. There were different reasons and nuances to them all, but all 3 boiled down to one common factor. Instead of following the desires of the customers, they now had to pigeon-hole those desires into the larger business goals of the parent organization.
They all turned into political battles at the leadership level, low morale at the product level, and decent jobs for the engineers as long as they were happy just doing what they were told. For the customers, everything just stagnated. It took years before all the politics sorted themselves out, people chose whether to stay or go, and you got product leadership running who could balance it all out without the baggage of the merger.
So as a Github customer, this does not have me running for the hills. We won't lose functionality. But we won't gain anything we truly desire either - we'll see new features come out that relate to Microsoft's dreams, not our own. At a strategic level, I'd start telling my teams to be sure not to get vendor-locked to any Github features, and always have a migration plan at least conceptualized so that once we see where it all really goes, we are well prepared to either stay or go depending on exactly what Microsoft does in the next couple years.
The product quality went to shit in all 3 scenarios. There were different reasons and nuances to them all, but all 3 boiled down to one common factor. Instead of following the desires of the customers, they now had to pigeon-hole those desires into the larger business goals of the parent organization.
They all turned into political battles at the leadership level, low morale at the product level, and decent jobs for the engineers as long as they were happy just doing what they were told. For the customers, everything just stagnated. It took years before all the politics sorted themselves out, people chose whether to stay or go, and you got product leadership running who could balance it all out without the baggage of the merger.
So as a Github customer, this does not have me running for the hills. We won't lose functionality. But we won't gain anything we truly desire either - we'll see new features come out that relate to Microsoft's dreams, not our own. At a strategic level, I'd start telling my teams to be sure not to get vendor-locked to any Github features, and always have a migration plan at least conceptualized so that once we see where it all really goes, we are well prepared to either stay or go depending on exactly what Microsoft does in the next couple years.