Incompetent workers, it's that simple really. MS assigns college degrees to projects, those college degrees understand very little about software, much less the culture of repository ownership and open source relationships. Too many employees, not enough experience heading them.
Microsoft and orgs like it are too big, you cannot trust a massive machine to be efficient, there's little incentive for proper management.
Au Contraire. From the bylaws posted publicly so far, it seems, they aren't truly independent of each other.
Microsoft is the "Founding Member" of the .NET Foundation. They are entitled to appoint an Exec. Director (ED) and the board has no say in this matter (The current ED is the person who forced a commit on a member project). The ED's tenure has no expiry other than when Microsoft feels the need to change (or they leave). All other board members are elected for a set term.
Lastly, the ED can block any board resolution; aka, the elected board needs Microsoft's blessing to do literally anything.
I have not. I am not a foundation project maintainer or have had any direct interactions with the foundation. My understanding mostly comes from following the community.
But this is what Rodney Littles is quoted as having said in his interview with The Register
> From Littles' perspective, though, the .NET Foundation is insufficiently independent from Microsoft, does too little to help its member projects, and lacks a strong sense of mission or purpose.
This is definitely not the case. The .Net Foundation is not staffed by Microsoft, nor is it owned by Microsoft. It’s an entirely distinct entity though I believe some board members work for Microsoft.
That’s where the poor & questionable transparency comes in, they try to market it as independent but it was formed and funded by Microsoft with the Executive Director whose performing all the objectionable actions an MS employee who is also the only person that is able to approve all material changes made to the foundation whose position can only be filled by the founding member who is Microsoft, in effect they are the silent hand making all the power moves to its member projects without their consent, wishes or even a courtesy notification. Then to try downplay the bad PR you had the MS VP Director with no visible ties to the foundation willing to jump on a call to disgruntled members so they can downplay their MS foundation employees actions behind close doors.
Microsoft and orgs like it are too big, you cannot trust a massive machine to be efficient, there's little incentive for proper management.