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 Code of Conduct update
We are pleased to announce the release of a new version of our Code of Conduct.
Based on the feedback of our community we added greater detail about acceptable and unacceptable behaviors in online settings and we have the first translation of the text to Spanish.
We thank Megan Carter for serving as independent community member until June, 2022 and welcome back Kara Woo to serve on this role. Yanina Bellini Saibene joins the committee as the new rOpenSci Community Manager.
You can read all the details in our blog post.
The following three packages recently became a part of our software suite:
datefixR, developed by Nathan Constantine-Cooke: There are many different formats dates are commonly represented with: the order of day, month, or year can differ, different separators (“-“, “/”, or whitespace) can be used, months can be numerical, names, or abbreviations and year given as two digits or four. datefixR takes dates in all these different formats and converts them to Rs built-in date class. If datefixR cannot standardize a date, such as because it is too malformed, then the user is told which date cannot be standardized and the corresponding ID for the row. datefixR’ also allows the imputation of missing days and months with user-controlled behavior. It is available on CRAN. It has been reviewed by Kaique dos S. Alves, and Al-Ahmadgaid B. Asaad.
epair, developed by G.L. Orozco-Mulfinger together with Madyline Lawrence, and Owais Gilani: Aid the user in making queries to the EPA API site found at https://aqs.epa.gov/aqsweb/documents/data_api. This package combines API calling methods from various web scraping packages with specific strings to retrieve data from the EPA API. It also contains easy to use loaded variables that help a user navigate services offered by the API and aid the user in determining the appropriate way to make a an API call.
readODS, developed by Chung-hong Chan together with Gerrit-Jan Schutten, and Thomas J. Leeper: Read ODS (OpenDocument Spreadsheet) into R as data frame. Also support writing data frame into ODS file. It is available on CRAN. It has been reviewed by Emma Mendelsohn, and Adam H. Sparks.
The following eight packages have had an update since the last newsletter: datefixR (
v1.0.0), dittodb (
v0.1.4), EDIutils (
v1.0.1), jagstargets (
1.0.3), lingtypology (
v1.1.9), restez (
v2.0.0), rtweet (
v1.0.2), and tidyqpcr (
Software Peer Review
There are fifteen recently closed and active submissions and 2 submissions on hold. Issues are at different stages:
Two at ‘6/approved’:
Three at ‘4/review(s)-in-awaiting-changes’:
Four at ‘3/reviewer(s)-assigned’:
Two at ‘2/seeking-reviewer(s)’:
Three at ‘1/editor-checks’:
Find out more about Software Peer Review and how to get involved.
On the blog
- rOpenSci Code of Conduct Update by Yanina Bellini Saibene, Mark Padgham, and Kara Woo. Update on Code of Conduct 2022.
Evaluating GitHub Activity for Contributors by Maëlle Salmon. How to evaluate the activity of a GitHub repository as an user or potential contributor. This post was discussed on the R Weekly Highlights podcast.
Upgrading rtweet by Lluís Revilla Sancho. Update from rtweet 0.7.0 to 1.0.2.
Call for maintainers
We’re looking for a new maintainer, or a new maintainer team, for each of the following packages:
If you’re interested, please comment in the issues or email
For more info, see
Package development corner
Some useful tips for R package developers. 👀
Say you cloned a repository and are now getting ready to debug it.
How do you make sure you have all its development dependencies installed?
Easy to remember and to type, and it works!
Update to CRAN NEWS.md parsing
R itself – if all goes well a
NEWS.mdfile that is correct for pkgdown will be correct for R too. You can follow the debugging steps recommended by Henrik Bengtsson to find what’s wrong in your
How to handle CRAN checks with
In some cases CRAN might run checks without installing the Suggested dependencies. How to ensure your vignettes still “work”, that is to say, that R CMD check will not produce any error or warning?
- pre-build your vignettes;
- make them pkgdown articles instead (no vignette, no vignette error!);
- execute code conditionally based on the availability of packages, with knitr
evalchunk option for instance.
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.