Amid drama at .NET Foundation, Microsoft's De Icaza reveals it was meant to be like GNOME Foundation

Which it isn't, as illustrated by exec director of the F# Foundation


The troubled .NET Foundation was intended to "borrow as much as possible from the GNOME Foundation," according to Miguel de Icaza, co-founder of GNOME and now at Microsoft, who was involved in its original design.

De Icaza's remarks were triggered by a post from Reed Copsey, president of earth science research company C Tech and executive director of the F# Foundation.

F# is a .NET language, but has its own foundation. The F# Software Foundation (FSSF) began in 2014 (the same year the .NET Foundation was founded) after F# inventor Don Syme "met in a café in Cambridge" with researcher Tomas Petricek and software architect Phil Trelford, and was originally an informal organisation, according to Syme's paper on F# history. It was modelled "along the lines of the Python Software Foundation."

In 2016 the FSSF was incorporated as a non-profit with guidance from Copsey, and now maintains the F# repositories.

Commenting on the current issues at the .NET Foundation, Copsey said in the post: "As things stand today, I find myself unable to honestly recommend anybody put time or effort into the Foundation, or recommend joining as a member."

He said there "seems to be a large disconnect between the governance of the Foundation and the public opinion of the Foundation's purpose."

Copsey said that the "independence of the Foundation is disingenuous," because of the special privileges assigned to Microsoft and its veto over any significant change.

Copsey also believes that the governing documents for the foundation are lacking, insofar as they are available for scrutiny. The bylaws refer to a membership policy but "this 'Membership Policy' is not available publicly, which means there is no way for people to have a formal knowledge of member rights, responsibilities, etc," he said, and "lack of clarity abounds."

The leadership responsibilities are also unclear, he said. The bylaws state: "The officers of the Foundation shall consist of a President, one or more Vice Presidents, a Secretary, and a Treasurer," but who holds these positions (other than Treasurer) is not known, and the page listing the Board of Directors states that "the board completely runs the .NET Foundation."

Copsey said: "A non-profit Board should not 'run the foundation'. The purpose of the Board of Directors in a non-profit is normally about governance, not management."

Copsey insisted that he wants the foundation to succeed and has recommendations for the board. One of these concerns whether it intends to be a independent organisation, in which case the bylaws must be changed, requiring agreement from Microsoft.

"Non-profits thrive when their members are empowered," he said. The position of executive director is vacant following the resignation of Microsoft's Claire Novotny, and the new appointment should be "somebody with experience in non-profit management and governance," he said.

Responding to this post, De Icaza said that the .NET Foundation's design borrowed from the GNOME Foundation, but added that "the major areas where it differed you identified clearly: the permanent [Microsoft] seat and the veto power. The latter is intended to prevent a scenario where the assets of the foundation were relicensed under a license like the GPL (I think there are reasons why this couldn't happen, and also I think it doesn't matter in practice, as a fork can achieve the same), but this was the rationale for it."

According to De Icaza, the open-sourcing of .NET including the formation of the foundation was "a major concession from Microsoft" so it may have been a matter of going as far as the company would accept.

He added: "I was exhausted at the end of this process, and did not run for the first reformed .NET board and didn't have a chance to communicate to the new board the design, beyond 'it is like gnome'."

If the .NET Foundation were performing well, the issue of governance would likely be under less scrutiny, but the current circumstances have exposed these issues that existed from its earliest days.

Board members Rob Prouse, Mattias Karlsson, and Javier Lozano have also commented and promised to take Copsey's remarks seriously. "You bring up excellent and addressable points. The current Board is hard at work reviewing these and other items," said Lozano.

That said, these are non-Microsoft board members and we have not yet heard much from the company (de Icaza aside) regarding the current crisis. If Microsoft does support meaningful reform, it is possible that the outcome will be beneficial rather than harmful to the .NET ecosystem. ®

Similar topics


Other stories you might like

  • Prisons transcribe private phone calls with inmates using speech-to-text AI

    Plus: A drug designed by machine learning algorithms to treat liver disease reaches human clinical trials and more

    In brief Prisons around the US are installing AI speech-to-text models to automatically transcribe conversations with inmates during their phone calls.

    A series of contracts and emails from eight different states revealed how Verus, an AI application developed by LEO Technologies and based on a speech-to-text system offered by Amazon, was used to eavesdrop on prisoners’ phone calls.

    In a sales pitch, LEO’s CEO James Sexton told officials working for a jail in Cook County, Illinois, that one of its customers in Calhoun County, Alabama, uses the software to protect prisons from getting sued, according to an investigation by the Thomson Reuters Foundation.

    Continue reading
  • Battlefield 2042: Please don't be the death knell of the franchise, please don't be the death knell of the franchise

    Another terrible launch, but DICE is already working on improvements

    The RPG Greetings, traveller, and welcome back to The Register Plays Games, our monthly gaming column. Since the last edition on New World, we hit level cap and the "endgame". Around this time, item duping exploits became rife and every attempt Amazon Games made to fix it just broke something else. The post-level 60 "watermark" system for gear drops is also infuriating and tedious, but not something we were able to address in the column. So bear these things in mind if you were ever tempted. On that note, it's time to look at another newly released shit show – Battlefield 2042.

    I wanted to love Battlefield 2042, I really did. After the bum note of the first-person shooter (FPS) franchise's return to Second World War theatres with Battlefield V (2018), I stupidly assumed the next entry from EA-owned Swedish developer DICE would be a return to form. I was wrong.

    The multiplayer military FPS market is dominated by two forces: Activision's Call of Duty (COD) series and EA's Battlefield. Fans of each franchise are loyal to the point of zealotry with little crossover between player bases. Here's where I stand: COD jumped the shark with Modern Warfare 2 in 2009. It's flip-flopped from WW2 to present-day combat and back again, tried sci-fi, and even the Battle Royale trend with the free-to-play Call of Duty: Warzone (2020), which has been thoroughly ruined by hackers and developer inaction.

    Continue reading
  • American diplomats' iPhones reportedly compromised by NSO Group intrusion software

    Reuters claims nine State Department employees outside the US had their devices hacked

    The Apple iPhones of at least nine US State Department officials were compromised by an unidentified entity using NSO Group's Pegasus spyware, according to a report published Friday by Reuters.

    NSO Group in an email to The Register said it has blocked an unnamed customers' access to its system upon receiving an inquiry about the incident but has yet to confirm whether its software was involved.

    "Once the inquiry was received, and before any investigation under our compliance policy, we have decided to immediately terminate relevant customers’ access to the system, due to the severity of the allegations," an NSO spokesperson told The Register in an email. "To this point, we haven’t received any information nor the phone numbers, nor any indication that NSO’s tools were used in this case."

    Continue reading

Biting the hand that feeds IT © 1998–2021