rOpenSci | rOpenSci News Digest, May 2024

rOpenSci News Digest, May 2024

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

🔗 rOpenSci in the Research Organization Registry

rOpenSci was added to the Research Organization Registry (ROR) in its latest release. The ROR is a global, community-led registry of open persistent identifiers for research organizations. ROR IDs help link and disambiguate metadata about organizations in the scholarly record, much like DOIs and ORCiDs do for manuscripts and researchers. Linked metadata is rOpenSci’s love language ❤️ ! Find us at

🔗 What are the rOpenSci Champions up to now?

Our Champions and mentors have been carrying out various programmed activities. The first stage of the program has a very important training component. This year, we divided the training into technical and community tracks, with several one to two-hour sessions each. Here, you can find the openly available material for each session.

The Technical Track is focused on good software and package development practices:

The Community Track is focused on community-building skills:

Next month, we will complete the training with a workshop on Git and GitHub and another on Event Organization.

🔗 Coworking

Read all about coworking!

Join us for social coworking & office hours monthly on first Tuesdays! Hosted by Steffi LaZerte and various community hosts. Everyone welcome. No RSVP needed. Consult our Events page to find your local time and how to join.

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 package recently became a part of our software suite:

  • dendroNetwork, developed by Ronald Visser: Creating dendrochronological networks based on the similarity between tree-ring series or chronologies. The package includes various functions to compare tree-ring curves building upon the dplR package. The networks can be used to visualise and understand the relations between tree-ring curves. These networks are also very useful to estimate the provenance of wood as described in Visser (2021) DOI:10.5334/jcaa.79 or wood-use within a structure/context/site as described in Visser and Vorst (2022) DOI:10.1163/27723194-bja10014. It is available on CRAN. It has been reviewed by Kaija Gahm and Zachary Gajewski.

Discover more packages, read more about Software Peer Review.

🔗 New versions

The following nine packages have had an update since the last newsletter: comtradr (v1.0.0), dendroNetwork (0.5.4), drake (7.13.10), fellingdater (v1.0.2), melt (v1.11.4), nasapower (v4.2.1), osmextract (v0.5.1), stplanr (v1.2.0), and traits (v0.5.1).

🔗 Software Peer Review

There are thirteen recently closed and active submissions and 7 submissions on hold. Issues are at different stages:

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

🔗 On the blog

🔗 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

Also 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. 👀

🔗 Token now needed for code coverage via codecov and {covr} on GitHub Actions

Test coverage reports are useful when assessing and improving tests of an R package. One can run the covr package locally, or send results to an interface like that provides interactive exploration of the output. It is possible to compute test coverage and send the results to on GitHub Actions, using the r-lib/actions actions.

Now, recently, workflows have started to fail if one did not set a token as an environment variable. How to solve this

🔗 Notes on package repositories

Lluís Revilla Sancho wrote about Packaging R: getting in repositories. We particularly note his two definitions of package repositories: the first one consists in making install.packages() work, the second in adding a layer of checks to packages in the repository. He then added “R-universe is using the first definition but could be used to generate repositories with checks that comply with the second definition.”

🔗 Standardize a DESCRIPTION file in one function call

Do you know about the desc::desc_normalize() function that orders and formats DESCRIPTION fields in a standard way? Once you start using it, there’s no way back.

You can also call it indirectly via usethis::use_tidy_description() that also sets the Encoding field to UTF-8.

🔗 Automated refactoring with xmlparsedata

Refactoring code can be tedious manual work, but it can also be tedious automated work. 😉 Read a post about how to replace all occurrences of a given function call with another one using an XML representation of the code.

🔗 What’s your favorite IDE?

Athanasia Monica Mowinckel wrote an informative post about the IDEs she uses.

🔗 Code review resources

Beside the tidyverse code review guidance, we can now recommend you check out the code review anxiety workbook by Carol Lee and Kristen Foster-Marks, that explains what code review anxiety is, and describes efficient methods to deal with it.

🔗 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.