The role of Microsoft’s .NET Foundation, set up for the governance and support of open-source .NET and related projects, has been questioned by a former board member who resigned in frustration. Here’s an excerpt from The Register’s report: Rodney Littles II is a software engineer at Megsoft Consulting and core maintainer of an open-source project, ReactiveUI, which is a .NET Foundation project. The .NET Foundation was formed in 2014 and describes itself as “an independent, non-profit organization established to support an innovative, commercially friendly, open-source ecosystem around the .NET platform.” Littles joined the .NET Foundation board in August 2020. In his campaign pitch he spoke of a “serious disconnect in the .NET ecosystem” in that Microsoft promotes .NET open source but that the community around it is not healthy. “Maintainers of .NET OSS that Microsoft wants to help thrive are still in rough shape,” he said. The sustainability of open-source projects was a key concern, as was expanding the .NET open-source ecosystem.
Littles resigned from the .NET Foundation board ahead of its elections in September. He intended to say nothing in public about it, but changed his mind when the foundation posted that “we wish him all the best as he refocuses on his personal life.” Concerned friends contacted him, resulting in this post, where he explains some of the background to his resignation and said: “I am fine. No issue in my personal life took me away from the board.” According to Littles’ post, “the .NET Foundation was not concerned about its membership” and “hasn’t been transparent with the community about anything.” He asked the foundation: “Are you here to enforce Microsoft’s will on .NET Open Source, or are you here to help foster and promote a healthy community?” He added: “The scoreboard doesn’t look good for the latter… I watched Microsoft kill an Open Source Project, while my friends in the community demanded the Foundation say something, I felt powerless to do anything. It was clear the reasons I joined the Foundation weren’t important.”
We asked Littles about his experience of being on the board. He joined, he told us, with the awareness that the previous board “was not a fully functioning board… it didn’t seem coherent, it didn’t seem that it was a board moving towards a goal. They put up the maturity model which I had a very big issue with.” Project Maturity was a pilot including “maturity profiles,” designed to improve software quality. The project was abandoned shortly after its introduction after community members complained that it was over-reaching, with board member Ben Adams acknowledging that “we didn’t then open this discussion up to all projects, to find out if it was acceptable to them, or if there was a better way. This was wrong.” Littles told us: “My problem with the maturity model was it seemed too Microsoft bureaucratic… member projects would have to provide a service level agreement for consumers of those libraries… it was elitist and exclusionary. I felt the model should have been more about how do we open up a path for a small open-source library to go from a one-person labour of love to a library that the community can depend on? I felt the focus was more on overseeing and dictating versus nurturing and helping.”
Microsoft engaged in some strange behavior with regard to its WinGet project, finding out all the details of an existing open-source project called AppGet by dangling the prospect of a job at Microsoft for its creator, but then in effect killing that open-source project though borrowing many of its ideas. Littles was more than disappointed. “The foundation, which is supposed to be the champion for open source, said nothing,” Littles told us. “The foundation remained silent and to me, that was extremely loud… that is what made me wake up and realize the foundation doesn’t care about the community or incidents like this… the community was in outrage behind this and the Foundation that’s supposed to be Microsoft’s open source arm said nothing.” AppGet was not a .NET Foundation project, but Little felt that “if you’re here for open source, you cannot be exclusionary, you cannot say it’s not a foundation project so we don’t care.”
Read more of this story at Slashdot.