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
Event: Career Paths for U.S. Federal Data Scientists
rOpenSci and Openscapes are lucky to have as members many U.S. federal employees who enrich our work and community. In a time of great uncertainty for so many government workers, we want to support our members who are considering their next career steps.
Join us on Tuesday, May 6 at 8:30PM EDT for a discussion and networking event for and with current and former U.S. federal government data scientists.
More information.
rOpenSci Champions Program 2025 In Spanish: Apply before April 30th!
Reminder: The call for applications to be part of the new cohort of our 2025 Program is open until April 30th! For the first time it will be in Spanish.
Find out more in our call for applications. It will be open until Wednesday, April 30, 2025.
rOpenSci in the News
Our community manager Yanina Bellini Saibene was also interviewed in Nature, for the article “Which programming language should I use? A guide for early-career researchers”
“The user community is also a key consideration — Saibene says that’s one of the things she loves most about R. The language’s large, welcoming and engaged user community means that tools are developed and updated frequently; that local user groups exist around the world; and that tutorials and other resources are available in many spoken languages, including her native Spanish.”
Our executive director Noam Ross was interviewed for the Nature article “Stay safe from online hate with these five tips”. For more on this topic, we recommend this 2021 paper by Danielle Smalls and Greg Wilson: “Ten quick tips for staying safe online”.
More Languages, More Access: Discover rOpenSci in Spanish
We’re excited to share that our website has more content than ever available in Spanish! We started with our Dev Guide and some of our blog posts. Now you’ll also find key pages, information about projects and programs, documentation, and community resources in Spanish. This milestone reflects our ongoing commitment to making open science more inclusive and accessible to Spanish-speaking communities worldwide. We are grateful to all the community members who contribute to our translation and localization efforts.
Coworking
Read all about coworking!
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 packages
The following two packages recently became a part of our software suite:
-
gtexr, developed by Alasdair Warwick together with Benjamin Zuckerman, Abraham Olvera-Barrios, Chuin Ying Ung, and Robert Luben: A convenient R interface to the Genotype-Tissue Expression (GTEx) Portal API. The GTEx project is a comprehensive public resource for studying tissue-specific gene expression and regulation in human tissues. Through systematic analysis of RNA sequencing data from 54 non-diseased tissue sites across nearly 1000 individuals, GTEx provides crucial insights into the relationship between genetic variation and gene expression. This data is accessible through the GTEx Portal API enabling programmatic access to human gene expression data. For more information on the API, see https://gtexportal.org/api/v2/redoc. It is available on CRAN. It has been reviewed by Zhian N. Kamvar and Ernest Guevarra.
-
c3dr, developed by Simon Nolte: A wrapper for the ‘EZC3D’ library to work with C3D motion capture data. It has been reviewed by Aymeric Stamm and July Pilowsky.
Discover more packages, read more about Software Peer Review.
New versions
The following sixteen packages have had an update since the last newsletter: butterfly (1.1.2
), c3dr (v0.1.1
), FedData (v4.3.0
), git2r (v0.36.2
), gtexr (v0.2.0
), ijtiff (v3.1.3
), nodbi (v0.12.0
), osmapiR (v0.2.3
), osmextract (v0.5.3
), pangoling (v1.0.3
), rb3 (v0.0.12
), stplanr (overlapping_segments_in_overline
), tarchetypes (0.13.0
), targets (1.11.2
), waywiser (v0.6.3
), and weatherOz (v2.0.1
).
Software Peer Review
There are twelve recently closed and active submissions and 5 submissions on hold. Issues are at different stages:
Find out more about Software Peer Review and how to get involved.
On the blog
Software Review

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 tips for R package developers. 👀
Eleven quick tips for writing a Bioconductor package
If you are planning to publish your package with Bioconductor, do not miss this paper by Charlotte Soneson and collaborators.
Dump all package information into one file for LLMs
With the rdocdump package by Egor Kotov, you can generate a single file containing the source code, documentation and vignettes of an R package. You can then use the file for ingestion into a Large Language Model (LLM).
plumber2
If you use the plumber package to publish your code as an API, you’ll be interested in its successor, plumber2 by Thomas Lin Pedersen.
Use a nested folder structure for your package
If you dream of using nested folders for storing the R code of an package, try out the experimental dir package by Antoine Fabri.
Minimal type guessing
Did you know about minty, an R package by Chung-hong Chan that shares the type inferencing and parsing tools used by the original readr package prior to 2021? It can be handy for your parsing needs.
Visualising R Package Risk Assessments using Litmus
An interesting post and dashboard by Pedro Silva, Astrid Radermacher & Colin Gillespie to assess the risk of packages.
CI: Pin the R version if using renv
A good tip by Christophe Dervieux in our Slack workspace: If you use renv to freeze dependencies in continuous integration, you should pin the R version to what’s been used to build the renv’s lockfile. This lets you update (and check) everything at once: the R versions and package versions.
Last words
Thanks for reading! If you want to get involved with rOpenSci, check out our Contributing Guide that can help direct you to the right place, whether you want to make code contributions, non-code contributions, or contribute in other ways like sharing use cases. You can also support our work through donations.
If you haven’t subscribed to our newsletter yet, you can do so via a form. Until it’s time for our next newsletter, you can keep in touch with us via our website and Mastodon account.
Related