R enters the late 2020s with significant new funding and international recognition of its contributions to statistical computing. R Core’s work was recognized in 2026 with the Rousseeuw Prize for Statistics. The Sovereign Tech Fund committed $450,000 to the R Foundation to strengthen R’s sustainability and security, while the Research Software Maintenance Fund is supporting a two-year project focused specifically on expanding the pool of people able to contribute to R. Together, these developments demonstrate substantial institutional support for R’s continued development and long-term sustainability.
During the R Consortium webinar “Sustaining R: Investing in the People, Infrastructure, and Community Behind R”, R Core members Simon Urbanek, Kurt Hornik, and Heather Turner discussed work already underway to strengthen R’s technical foundations and expand the community capable of maintaining them.
The discussion did not present a formal one- or two-year R Core roadmap. But it did identify several clear priorities: reducing technical debt, improving portability and testing, strengthening package infrastructure and software provenance, making R easier to contribute to, and developing the next generation of contributors. Urbanek, Turner, and Hornik each took up one part of that work: the software, the next generation of contributors, and the infrastructure behind both.
Modernizing R’s Technical Foundations
Urbanek focused on keeping R reliable and maintainable through work that often happens behind the scenes. The Sovereign Tech Fund project spans ten milestones across R’s technical foundations, including bug fixes, package infrastructure, numerical work across platforms, provenance, testing, documentation, portability, and legacy code. For him, the common theme is sustainability.
Open source ensures that source code is available, but availability alone does not make a project sustainable. Code must remain maintainable. Knowledge needs to be shared. New maintainers must be able to step in. And increasingly, users need confidence in the provenance and security of the software they install.
Package infrastructure across platforms
One visible piece of that work is R’s binary package infrastructure. Historically, R had separate binary package systems for Windows and macOS. Urbanek explained that the work began by making it possible to provide package binaries across platforms, rather than maintaining separate systems tied to particular operating systems. Different R builds and distributions can then define their own repositories and binary package sources.
Better APIs, documentation, and testing
Another priority is cleaning up and documenting R’s APIs, so the interfaces are understandable to people who did not originally create them. More work is also underway around portability and package testing, including containerizing test environments so the same tests can run across configurations and backend libraries and the results can be compared.
Reducing technical debt
R is more than 30 years old. Some code and libraries embedded in the system date back many years. One current task is deciding what should remain, what should be updated, and what can now be replaced by maintained external libraries, while preserving the stability and backward compatibility on which users depend.
Supporting the Infrastructure Behind R
Hornik focused on the R Foundation’s role in keeping R Core and CRAN running. He described one of its core functions as providing the hardware, software, and services their work requires, much of it invisible to everyday R users.
Email is one example. Infrastructure previously supplied by a university now needs another sustainable home, and the R Foundation is working to address that need. A global open source project cannot assume indefinitely that universities, companies, individual volunteers, or temporary grants will continue supplying critical infrastructure. The Foundation’s work also extends beyond technical systems to outreach, community development, and securing the financial resources needed to sustain the project.
Stability Remains a Design Constraint
Turner emphasized that R Core deliberately works incrementally because users depend on existing R code continuing to work.
“We want to keep things working for people in a predictable way,” Turner said. “We want things to be backwardly compatible, so that your code that you wrote a few years ago still works.”
That has consequences for how quickly R changes.
“Larger things can change, but we tend to work quite incrementally,” she said.
For users in research, industry, and other settings where analyses may need to remain reproducible for years, that conservatism is a feature.
Building the Next Generation of Maintainers
The Research Software Maintenance Fund is supporting a two-year project focused on expanding the pool of people able to contribute to R. At the time of the webinar, Turner said the project was approximately six months underway. It includes mentoring a cohort of expert contributors, making it easier for people to begin contributing, and work on communication and the broader sustainability of the R Foundation.
Turner said the project aims to “strengthen that contributor community and that pool of people that can keep R going into the future.”
That includes R Dev Days, development sprints, the R Dev Guide, contributor infrastructure, and environments that make it easier for a new contributor to build R and begin working with the source.
At a recent three-day sprint at the University of Birmingham, approximately 30 people participated in person, with others joining online. Their work included statistical functions, package installation, translation, documentation, website accessibility, and CRAN-related infrastructure. The event brought together beginners, regular contributors, and experienced R Core members. Part of the objective, Turner explained, is to help participants learn from each other, not simply to complete individual contributions.
Thinking Beyond the Next Grant
The Sovereign Tech Fund and Research Software Maintenance Fund have enabled substantial work. But both are time-limited investments. The longer-term question is how to make the technical and human infrastructure around R sustainable beyond individual grants.
Reflecting on the Rousseeuw Prize, Hornik connected recognition of R’s achievements over the past three decades with the responsibility to sustain the project for decades to come.
“To make sure that R is still up and running and doing well in the next 30 years,” he said.
The work underway is about ensuring that the language remains reliable, its infrastructure remains sustainable, and a new generation of contributors is ready to carry the project forward.
Watch the full discussion and audience Q&A on the R Consortium webinar page.

