- The Haskell Foundation is eliminating its executive director role and redirecting funds toward direct technical work in 2026.
- The Haskell Foundation is shifting its language from ‘donors’ to ‘members’ — a deliberate move to build partnership and shared ownership.
- Three board directors have departed, with Simon Marlow and Dominik Schrempf elected as replacements.
- A new part-time financial sustainability role will replace the full-time executive director position going forward.
- The Haskell Foundation is eliminating its executive director role and redirecting funds toward direct technical work in 2026.
- The Haskell Foundation is shifting its language from ‘donors’ to ‘members’ — a deliberate move to build partnership and shared ownership.
- Three board directors have departed, with Simon Marlow and Dominik Schrempf elected as replacements.
- A new part-time financial sustainability role will replace the full-time executive director position going forward.
The Haskell Foundation Is Changing How It Operates
The Haskell Foundation is undergoing one of its most significant structural shifts since its founding, and the changes go well beyond a simple leadership transition. In a post published to the official Haskell Discourse forum, board chair Laurent P. René de Cotret announced a series of moves that, taken together, signal a genuine rethink of what a language foundation should actually do — and who it should serve.
At the center of it all is the departure of José, the Foundation’s executive director, who will step down in June 2026. According to de Cotret, José has been the longest-serving executive director the Haskell Foundation has had, and a lot of his most important work happened away from the public eye. “Through personal sacrifices,” de Cotret wrote, “José has allowed the Haskell Foundation to survive some tough times.” That’s a candid acknowledgment that the organization has had its rocky moments — and that keeping it afloat took more than just a job title.
But here’s the thing: the board isn’t rushing to replace him. Instead, they’re using this moment to fundamentally rethink the role itself.
Ditching the Executive Director Model
The Haskell Foundation won’t have a full-time executive director for the foreseeable future. Instead, responsibilities that would have sat with that one person — fundraising, event coordination, community mediation, operational logistics — will be split between the board and a new part-time role focused specifically on financial sustainability.
That’s a pretty big bet. Executive directors in open source foundations typically serve as the connective tissue between technical contributors, corporate sponsors, and the broader community. The Python Software Foundation, the Apache Software Foundation, the Rust Foundation — all of them maintain full-time executive leadership. The Haskell Foundation is essentially saying: we don’t think that model works for us right now.
Whether that’s a pragmatic response to funding constraints or a genuine philosophical shift is probably both. The board’s stated goal is to put the Haskell Foundation’s money where it makes the most visible difference: directly into technical work. The idea is that members — a word chosen carefully, more on that in a moment — should be able to draw a clear line between what they contribute and what gets built or fixed in the Haskell ecosystem.
That’s a harder problem than it sounds. Open source foundations often struggle with exactly this: money goes in, community goodwill is generated, and… something happens? The causal chain between a $5,000 sponsorship and a specific improvement in the toolchain is often murky at best. The Haskell Foundation seems aware of this, and the restructure is at least partly designed to fix it.
Members, Not Donors: A Deliberate Shift in Language
One of the more interesting details in de Cotret’s announcement is the explicit choice to call contributors members rather than donors or sponsors. That might sound like marketing copy, but in the context of open source sustainability, it actually matters.
The donor/sponsor framing positions companies and individuals as patrons — they give money, the foundation does things, and the relationship is largely transactional. The member framing implies agency. It implies that the Haskell Foundation wants contributors to have a voice in what gets built, to feel genuinely invested in outcomes, and to see the ecosystem as something they co-own rather than something they’re subsidizing from a distance.
De Cotret put it plainly: “Rather than merely throwing money over the wall, we want membership to feel engaged in an inspiring shared mission.” That’s a direct acknowledgment that the current model hasn’t fully delivered on that sense of engagement — and an invitation to do it differently.
This kind of language shift is increasingly common across open source infrastructure projects. The Rust Foundation made similar moves when it launched in 2021, emphasizing that corporate members would have structured input into priorities. The trick, as Rust has learned, is that giving members a voice without letting the foundation get pulled in ten directions at once requires real governance discipline. The Haskell Foundation will need to figure that balance out quickly.
A New Technical Committee Takes the Wheel
The structural centerpiece of the 2026 changes is a new Haskell Foundation committee that will direct the bulk of the organization’s financial resources toward a “unified technical vision.” The details of what that vision looks like are still forthcoming — de Cotret promises more concrete updates in the coming weeks and months — but the intent is clear: the Haskell Foundation wants to stop spreading itself thin and start shipping meaningful improvements to the language and its ecosystem.
Haskell has a reputation that’s simultaneously its biggest asset and its biggest obstacle. It’s beloved by a passionate, technically sophisticated community, it’s been quietly influential on the design of languages like Rust and Swift, and it has genuine production users at companies like Meta and Standard Chartered. But it also has a long history of tooling frustrations, onboarding friction, and infrastructure that moves slowly. If the new technical committee can make a credible dent in any of those areas — better documentation, faster GHC builds, more reliable package tooling — it would represent a real step forward.
Critically, the committee will include representation from the Haskell Foundation’s members. That’s the governance piece that ties back to the member-not-donor framing. If it works, it creates a feedback loop where people who fund the foundation also shape its priorities and can see the results of their investment directly in the tools they use every day.
Board Turnover and What It Signals
Alongside the structural changes, the board itself has seen significant turnover. Andres Löh, who served as the former chair, has stepped down along with directors Hazel Weakly and Josh Meredith. De Cotret thanked all three for three years of service.
Coming in are Dominik Schrempf and Simon Marlow. Marlow’s addition in particular is notable — he’s one of the most respected figures in the Haskell world, having spent years at Microsoft Research working on GHC and co-authoring the widely read book Parallel and Concurrent Programming in Haskell. His presence on the board lends the new technical direction some serious credibility. If the Haskell Foundation is going to make bold claims about directing resources toward meaningful technical work, having someone of Marlow’s depth involved is a strong signal that it’s not just talk.
What This Means for Haskell’s Future
The Haskell Foundation is making a calculated wager here. Leaner governance, more direct technical investment, a stronger sense of member ownership — these are the right instincts. The risk is execution. Running a foundation without a full-time executive director is genuinely hard, and the part-time financial sustainability role will need to punch well above its weight class to keep corporate relationships warm and funding flowing.
But if the new committee can deliver visible improvements to the Haskell ecosystem on a consistent basis, it could change the calculus for potential members. Companies that have been lukewarm on sponsoring foundations because they couldn’t see the ROI might find a model where their priorities directly influence a technical roadmap far more appealing. That would be good for Haskell, and honestly, it might be a model worth watching for other niche language communities that have struggled with the traditional foundation playbook.
The Haskell Foundation says to expect more communications soon. Given how much is changing at once, that transparency will be essential — the community will want to know not just what the new structure looks like on paper, but how it performs in practice.
Source: https://discourse.haskell.org/t/haskell-foundation-2026-update/14136
