Thursday, February 26, 2026 From rOpenSci (https://ropensci.org/blog/2026/02/26/news-february-2026/). Except where otherwise noted, content on this site is licensed under the CC-BY license.
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!
The Champions Program call closed on February 23, and the response was fantastic. We received 81 Champion and 14 Mentor applications from 23 countries, with 74% of applicants proposing to develop a new package. We’re now kicking off the selection process, starting with mentors so they can support the evaluation of Champion proposals. Confirmation emails have already been sent to all applicants. Thank you to everyone who applied!
We published an initial blog post about planned updates to our policies and practices for use of generative AI tools in rOpenSci packages. This follows recent policy updates at both the Journal of Open Source Software and pyOpenSci. We are seeking feedback on the blog post, and on the policy changes proposed there, via this decidated GitHub issue. The blog explains our intention to permit the use of generative AI tools throughout package development, and during the review process. Our policies aim to maintain our culture of openness and transparency, and we have already started informally asking submitting authors about any use of generative AI tools.
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!
Last year we published a blog post on an organization-level dashboard for all rOpenSci packages and community contributors. We have now developed the orgmetricsDashboard repository to enable anybody to deploy their own organizational dashboard directly from their R-Universe repository. The only input needed is an R-Universe “packages.json” file, and you can deploy either via GitHub actions, or a local Docker workflow. Try it out!
The following two packages recently became a part of our software suite:
Athlytics, developed by Zhiang He: An open-source computational framework for longitudinal analysis of exercise physiology metrics using local Strava data exports. Designed for personal analysis and sports science applications, this package provides standardized functions to calculate and visualize key physiological indicators including Acute:Chronic Workload Ratio (ACWR), Efficiency Factor (EF), and training load metrics. It has been reviewed by Eunseop Kim and Simon Nolte.
orgmetrics, developed by Mark Padgham: Metrics for your GitHub organization. Call one function to generate an interactive dashboard displaying the state of your organization.
Discover more packages, read more about Software Peer Review.
The following thirteen packages have had an update since the last newsletter: dittodb (v0.1.11), targets (1.12.0), RSelenium (v1.7.10), Athlytics (v1.0.4), pkgstats (v0.2.2), osmapiR (v0.2.5), dbparser (v2.2.1), taxize (v0.10.1), rangr (v1.0.9), wikitaxa (v0.5.0), mantis (v1.0.2), tarchetypes (0.14.0), and tidyhydat (1.0.0).
Post on dfms release: Releasing dfms 1.0: Fast and Feature-Rich Estimation of Dynamic Factor Models in R.
There are seventeen recently closed and active submissions and 4 submissions on hold. Issues are at different stages:
One at ‘6/approved’:
Two at ‘5/awaiting-reviewer(s)-response’:
suwo, Access Nature Media Repositories Through R. Submitted by Marcelo Araya-Salas.
pkgmatch, Find R Packages Matching Either Descriptions or Other R Packages. Submitted by mark padgham.
One at ‘4/review(s)-in-awaiting-changes’:
Seven at ‘3/reviewer(s)-assigned’:
priorsense, Prior Diagnostics and Sensitivity Analysis. Submitted by Noa Kallioinen. (Stats).
logolink, An Interface for Running NetLogo Simulations. Submitted by Daniel Vartanian.
ActiGlobe, Wearable Recording Processor for Time Shift Adjustment and Data Analysis. Submitted by C. William Yao.
ernest, A Toolkit for Nested Sampling. Submitted by Kyle Dewsnap. (Stats).
rcrisp, Automate the Delineation of Urban River Spaces. Submitted by Claudiu Forgaci. (Stats).
reviser, Tools for Studying Revision Properties in Real-Time Time Series Vintages. Submitted by Marc Burri.
priorsense, Prior Diagnostics and Sensitivity Analysis. Submitted by Noa Kallioinen. (Stats).
Six at ‘1/editor-checks’:
nycOpenData, Convenient Access to NYC Open Data API Endpoints. Submitted by Christian Martinez.
pvEBayes, Empirical Bayes Methods for Pharmacovigilance. Submitted by Yihao Tan. (Stats).
RAQSAPI, A Simple Interface to the US EPA Air Quality System Data Mart API. Submitted by mccroweyclinton-EPA.
RAMEN, RAMEN: Regional Association of Methylome variability with the Exposome and geNome. Submitted by Erick Navarro-Delgado.
fcmconfr, Fuzzy Cognitive Map Analysis in R. Submitted by benroston. (Stats).
coevolve, Fit Bayesian Generalized Dynamic Phylogenetic Models using Stan. Submitted by Scott Claessens. (Stats).
Find out more about Software Peer Review and how to get involved.
Announcing New Statistical Software Peer Review Editors: Natalia da Silva and Andrew Heiss by Natalia da Silva, Andrew Heiss, and Yanina Bellini Saibene. Introducing two new editors for rOpenSci statistical software peer review.
Software Review in the Era of AI: What We Are Testing at rOpenSci by Mark Padgham, Noam Ross, Maëlle Salmon, Yanina Bellini Saibene, Mauro Lepore, Emily Riederer, Jouni Helske, and Francisco Rodriguez-Sanchez. rOpenSci is testing preliminary policies on the use of generative AI tools, with proposed updates to documentation and procedures for authors submitting software for review, for editors, and for reviewers.
Paleontology R Packages to Benefit from Software Sustainability Institute Grant by Will Gearty and The Palaeoverse Team. A grant from the Software Sustainability Institute will go towards improving the sustainability and maintainability of R packages used in paleontological research.
Our forum is closed but our community is not! by The rOpenSci Team. Why we’re closing our forum, how to keep participating in our community.
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?.
NLMR, R package to simulate neutral landscape models. Issue for volunteering.
landscapetools, R package for some of the less-glamorous tasks involved in landscape analysis. Issue for volunteering.
hddtools, Tools to discover hydrological data, accessing catalogues and databases from various data providers. Issue for volunteering.
qualtRics, download Qualtrics survey data. Issue for volunteering.
photosearcher, searches Flickr for photographs and metadata. Issue for volunteering.
Refer to our help wanted page – before opening a PR, we recommend asking in the issue whether help is still needed.
Some useful tips for R package developers. 👀
The R Foundation answered a Call for Evidence from the EU about open-source, after asking for examples of the added value of R in the public or private sectors. You can read the full response of the R Foundation, including a discussion of useful ideas for the future of R and open-source in general.
Athanasia Monika Mowinckel wrote a post on sitrep functions: functions that help the user check their setup and provide them with useful diagnostics. The blog post includes two examples.
The jarl CLI by Etienne Bacher “finds inefficient, hard-to-read, and suspicious patterns of R code across dozens of files and thousands of lines of code in milliseconds”. Read about the new features in jarl 0.4.0, like the ability to find “unreachable code”.
Henrik Bengtsson released futurize that allows you to parallelize execution with minimal changes to code, by simply adding a call to futurize(): y <- lapply(x, fcn) |> futurize().
Scott Shambaugh, an open-source maintainer, wrote about his being targeted by an AI agent after closing a PR for an issue that was intended for human newbies. Initial blog post: “An AI Agent Published a Hit Piece on Me”, Updated.
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.
