rOpenSci | rOpenSci News Digest, May 2026

rOpenSci News Digest, May 2026

Dear rOpenSci friends, it’s time for our monthly news roundup! You can read this post on our blog. Now let’s dive into the activity at and around rOpenSci!

🔗 rOpenSci HQ

🔗 15 Years of rOpenSci, and we’re just getting started 🎉

This year we celebrate 15 years of rOpenSci! First up we have a coworking session followed by a couple casual virtual community celebrations. Please join us! Read more in our blog post about these upcoming events.

Also exciting is that this blog post about our 15 year anniversary was featured in the R Weekly Highlights podcast hosted by Eric Nantz and Mike Thomas.

🔗 Champions Program update

The rOpenSci Champions Program is currently running two very active cohorts, with many activities happening across the program, and everything is on track!

The 2025–2026 cohort is wrapping up their projects and outreach activities, with several Champions presenting their work at events such as R/Pharma, useR!, Posit, and LatinR 2026. We also recently held a cohort meeting bringing together Champions and mentors from the 2025–2026 cohort and one meeting for mentors only, to share mentoring tips and tricks.

Meanwhile, the 2026–2027 cohort has started their training activities, including three weekly training workshops for Champions and a mentor training workshop. Mentors and Champions have also had their first meetings together to get to know each other and begin planning their collaboration.

Stay tuned to our events page for Champions outreach activities and to our blog to learn more about Champions’ projects.

🔗 May is Maintainer Month

Open source software doesn’t sustain itself. Behind every R package, there is at least one person who responds to issues, reviews pull requests, keeps up with dependency changes, and makes sure everything still works.

We joined the #MaintainerMonth celebration with a month-long series of rOpenSci’s maintainer spotlights: 36 maintainers from 15 countries across 4 continents, maintaining more than 50 packages that together serve thousands of researchers and data practitioners around the world.

Follow our social media (Mastodon and LinkedIn) and the official hashtag (#MaintainerMonth) to learn more about the maintainers who support open source software. Thank you to those who agreed to participate and to all the maintainers in our community.

🔗 Software-Review update

This month saw a slight policy shift in the way editors handle new software review submissions, assisted by an internal update to our bot system. Previously, our rotating Editor-in-Chief (EiC) was solely responsible for initial decisions on whether to proceed with submissions. Once a decision was reached, a handling editor took over, and generally guided each submission through to approval. However, recent increases in submissions have been too much for one EiC to handle. Submissions will now be passed on more quickly to handling editors who will then make initial scope and fit decisions.

As part of this change, the EiC can now ask the bot to “ping editors”. Editors will receive an email alerting them of this new submission and can then decide whether to take it on as editor. Each time an editor clicks on a link in the email, the EiC will receive an email notification, and once an editor is assigned, all links will be automatically deactivated.

For anybody interested in how to develop an email alert system like this, please contact us and we’ll have happy to share what we learnt along the way. Full code is in this R file.

🔗 Social media cards for R-universe

When posting about your package or universe on social media, you can get a pretty social media card featuring important information about (respectively):

  • the package such as its maintainer, its keywords, its URL, its version, its number of stars, etc.
  • the universe such as its number of packages and contributors, etc.

More information in the R-universe documentation.

🔗 Coworking

Read all about coworking!

  • Tuesday June 2nd 2026, 14:00 Europe Central (12:00 UTC) “15 years with rOpenSci”, with Steffi LaZerte and cohost Noam Ross.
    • Explore rOpenSci projects
    • Do a deep dive into the rOpenSci blog history
    • Meet rOpenSci’s Executive Director, Noam Ross, and discuss how rOpenSci has evolved over the last 15 years.
  • Tuesday July 7nd 2026, 09:00 Americas Pacific (16:00 UTC) “Debugging in R”, with Yanina Bellini Saibene and cohost Shannon Pileggi.
    • Read up on debugging in R
    • Meet community host, Shannon Pileggi, and discuss tips and tricks for debugging in R.

And remember, you can always cowork independently on work related to R, work on packages that tend to be neglected, or work on what ever you need to get done!

🔗 Software 📦

🔗 New versions

The following ten packages have had an update since the last newsletter: cffr (v1.4.0), gutenbergr (v0.5.1), dataset (0.4.4), sofa (v0.4.1), saperlipopette (v1.0.0), medrxivr (snapshot), textreuse (v1.0.1), EDIutils (v2.1.0), rsi (v0.3.3), and UCSCXenaTools (v1.7.0).

The writexl package has a new maintainer, Bill Denney. NLMR is now maintained by Jakub Nowosad.

🔗 Software Peer Review

There are eighteen recently closed and active submissions and 4 submissions on hold. Issues are at different stages:

Find out more about Software Peer Review and how to get involved.

🔗 On the blog

Retro pixel-art graphic celebrating rOpenSci's 15th anniversary. The text 'rOpenSci' appears at the top in pixel font, flanked by three pixel-art balloons. A browser window frames the central message: '15 YEARS / TRANSFORMING OPEN SCIENCE' in bold pixel letters, overlaid on the rOpenSci geometric network pattern. A pixel badge reads 'OMG'. A pixel folder and sparkle icons complete the design.

🔗 Calls for contributions

🔗 Calls for maintainers

If you’re interested in maintaining any of the R packages below, you might enjoy reading our blog post What Does It Mean to Maintain a Package?.

🔗 Calls for contributions

Refer to our help wanted page – before opening a PR, we recommend asking in the issue whether help is still needed.

🔗 Package development corner

Some useful information for R package developers. 👀

🔗 devtools’ install functions now officially deprecated

The devtools::install_ functions like devtools::install_github() have now been officially deprecated in favor of pak. The manual page contains a migration guide. Time to update older READMEs!

🔗 New Git commands!

New in Git: git history! Thanks to Hugo Gruson for bringing this to our attention.

Imagine…

😰 Oops, that old commit’s message had a typo! 😌 git history reword

😰 Oops, that old commit is too big! 😌 git history split (to split it into two commits)

Git release notes; Git docs.

🔗 roxygen2 8.0.0

A new version of roxygen2 hit CRAN. Among the highlights are improvements for R6, S7, inheritance, and better documentation of roxygen2 itself, including the vignette on extending roxygen2 with your own tags and roclets. Release announcement.

🔗 Comment DESCRIPTION files

Have you noticed this line in the release notes of R 4.6.0?

read.dcf() now recognizes lines starting with # as comment lines. By Dirk Eddelbuettel, Laurent Gatto and Hugo Gruson.

This means it’s becoming possible to add comments to DESCRIPTION files, for instance to note why you added a given dependency.

🔗 {cross} R package for running code with different package versions

Have you ever used Git worktree to load several R package versions at once (in different sessions), for instance to create a benchmark? Davis Vaughan made such endeavors much smoother with his cross R package. cross uses Git worktree under the hood to install different package versions in temporary libraries and then runs R code with these different versions. Furthermore, it has a user-friendly interface!

For example, to compare the released version of vctrs to the developement version on GitHub, you could run the following.

cross::bench_versions(pkgs = c("vctrs", "r-lib/vctrs"), {
  library(vctrs)
  x <- c(1, NA, 2, 3, NA)
  bench::mark(missing = vec_detect_missing(x))
})

🔗 On attribution with a footnote

James Balamuta wrote two thoughtful posts on a tricky situation and its resolution. TL;DR James’ work on portable R was used in another repository with only minimal acknowledgement through a footnote in a comment. However, those involved came together to work out a resolution through meaningful conversation.

🔗 Last words

Thanks for reading! If you want to get involved with rOpenSci, check out our Contributing Guide. This guide will help direct you to the right place, whether you want to make code contributions, non-code contributions, or contribute in other ways such as through sharing use cases. You can also support our work through donations.

If you haven’t subscribed to our newsletter yet, you can do so though our signup form. Until it’s time for our next newsletter, you can keep in touch with us through our website, Mastodon, or LinkedIn. See you soon!