June 18, 2020
A semi-monthly summary of the rOpenSci Newsletter including software reviews, packages on CRAN, use cases, posts from staff and community, and events. April 27 to June 8, 2020
rOpenSci HQ
The rOpenSci team, together with ten expert community members, put together a post: When Field or Lab Work is not an Option - Leveraging Open Data Resources for Remote Research. We highlighted examples of how specific collections of packages are being used right now in fields as varied as archaeology and climate science and compiled a table of > 100 rOpenSci packages for access to open data.
Software Peer Review
Software peer review is accepting submissions again, after a pause to reduce the load on reviewers and editors in light of the COVID-19 crisis.
Consider submitting your package or volunteering to review. If you want to be a reviewer fill out this short form, and we’ll ping you when there’s a submission that fits in your area of expertise.
On the Blog
From the community
From the rOpenSci team
-
When Field or Lab Work is not an Option - Leveraging Open Data Resources for Remote Research - by The rOpenSci Team, Brooke Anderson, Robin Lovelace, Ben Marwick, Ben Raymond, Anton Van de Putte, Louise Slater, Sam Zipper, Ilaria Prosdocimi, Sam Albers, Claudia Vitolo
-
Superior svg graphics rendering in R, and why it matters Tech Note - Jeroen Ooms
-
Miscellaneous Wisdom about R Markdown & Hugo Gained from Work on our Website Tech Note - Maëlle Salmon
-
Highlights of Hugo Code Highlighting Tech Note - Maëlle Salmon
-
A Roundup of R Tools for Handling BibTeX Tech Note including discussion of rOpenSci packages RefManageR, bib2df, and handlr - Maëlle Salmon
-
2 Months in 2 Minutes - rOpenSci News, April 2020 - Stefanie Butland
Use Cases
-
69 published works cited or used rOpenSci software (listed in individual newsletters)
-
9 use cases for our packages or resources were posted in our discussion forum Look for bomrang, clifro, crul, drake, magick, piggyback, rnaturalearth, tidyhydat, tradestatistics
Have you used an rOpenSci package? Share your use case and we’ll tweet about it.
In the News
Why You Should Document Your Tests, by Hynek Schlawack
- Scott says “I for one, only sometimes include comments in my tests, but perhaps they should be documented better?” Do you comment or document your tests? This blog post is about Python, but the ideas apply to any language.
Call For Maintainers
Part of our mission is making sustainable software users can rely on. Sometimes software maintainers need to give up maintenance due to a variety of circumstances. When that happens we try to find new maintainers. Check out our guidance for taking over maintenance of a package.
rflybase is in need of a new maintainer. Email Scott if you’re interested.
Keep up with rOpenSci
We create a newsletter every two weeks. You can subscribe via rss feed in XML or JSON or via our one-way mailing list.
Follow @rOpenSci on Twitter.
Find out how you can contribute to rOpenSci as a user or developer.
