Site icon R-bloggers

Latest rOpenSci News Digest

[This article was first published on rOpenSci - open tools for open science, and kindly contributed to R-bloggers]. (You can report issue about the content on this page here)
Want to share your content on R-bloggers? click here if you have a blog, or here if you don't.

Dear rOpenSci friends, it’s time for our monthly news roundup! Some housekeeping first: We’ve been changing the infrastructure of our newsletter a bit so please update your RSS and JSON feeds to https://ropensci.org/tags/newsletter/index.xml and https://ropensci.org/tags/newsletter/index.json, respectively. You can read this post on our blog. Now let’s dive into the activity at and around rOpenSci!

🔗 rOpenSci HQ

Our R-universe project now has its own page on our website! ???? The R-universe platform is a new umbrella project under which we experiment with various new ideas for improving publication and discovery of research software in R.

Regarding another exciting project of ours… We’ve run the first comm call of our series on the statistical software review project! rOpenSci Statistical Software Testing and Peer Review took place on March 2nd. The video recording (including closed captions) and resources as well as a summary have been posted.

Find out about more events.

🔗 Software ????

🔗 New packages

The following two packages recently became a part of our software suite:

Discover more packages, read more about Software Peer Review.

🔗 New versions

The following twenty-one packages have had an update since the latest newsletter: chlorpromazineR (v0.2.0), crul (v1.1.0), eia (v0.3.7), epubr (v0.6.2), essurvey (v1.0.7), fulltext (v1.7.0), magick (v2.7.0), opencage (v0.2.2), osmextract (v0.2.1), parzer (v0.4.0), pathviewr (v1.0.0), phonfieldwork (v0.0.11), rerddap (v0.7.4), rinat (v0.1.8), rnoaa (v1.3.2), rplos (v1.0.0), tarchetypes (0.1.0), targets (0.2.0), terrainr (v0.3.1), tiler (v0.2.5), webmockr (v0.8.0).

🔗 Software Peer Review

There are eighteen recently closed and active submissions and 2 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

🔗 Other topics

🔗 Tech Notes

🔗 Citations

Below are the citations recently added to our database of 1254 articles, that you can explore on our citations page. We found use of…

Thank you for citing our tools!

🔗 Use cases

Nine use cases of our packages and resources have been reported since the 1st of January.

Explore other use cases and report your own!

🔗 Call for maintainers

There’s no open call for new maintainers at this point but you can refer to our contributing guide for finding ways to get involved! As the maintainer of an rOpenSci package, feel free to contact us on Slack or email info@ropensci.org to get your call for maintainer featured in the next newsletter.

🔗 Package development corner

Some useful tips for R package developers. ????

Do you have some questions around licensing of your R package? The license chapter of the R packages book by Hadley Wickham and Jenny Bryan was recently updated. A less recent but interesting read is Colin Fay’s Licensing R e-book.

Encoding can also be a tricky topic for package developers. Useful resources include Kevin Ushey’s blog post “String encoding and R”, Irene Steves’ blog post “Encoding in R”, searching for encoding in “Writing R Extensions” (e.g. “If the DESCRIPTION file is not entirely in ASCII it should contain an ‘Encoding’ field specifying an encoding. This is used as the encoding of the DESCRIPTION file itself and of the R and NAMESPACE files, and as the default encoding of .Rd files."), some threads of R-package-devel.

Afraid to forget something when you submit your package to CRAN? A check list could help! You can use usethis::use_release_issue(), number one “secret” [of the tidyverse team] for avoiding multiple rounds of review with CRAN. Now, if you want to add your own specific bullet e.g. “Update my brag document” or “Consider writing a tech note for rOpenSci blog”, you can add an unexported release_bullets() function returning a character vector to your package.

release_bullets <- function() {
c(
"Update my brag document.",
"Contact rOpenSci blog editors to schedule a tech note."
)
}

For inspiration you can search the CRAN mirror maintained by R-hub. For more resources around CRAN, see Isabella Velásquez’s post “You CRAN Do It, What CRAN First-Timers Should Know”.

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

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 Twitter account.

To leave a comment for the author, please follow the link and comment on their blog: rOpenSci - open tools for open science.

R-bloggers.com offers daily e-mail updates about R news and tutorials about learning R and many other topics. Click here if you're looking to post or find an R/data-science job.
Want to share your content on R-bloggers? click here if you have a blog, or here if you don't.