For day 3 of project recaps from this year’s unconf, here is an overview of the next five projects. Stay tuned for the last recap tomorrow. (Full set of project recaps: recap 1, recap 2, recap 3, recap 4.) In the spirit of exploration and experimentation at rOpenSci unconferences, these projects are not necessarily finished products or in scope for rOpenSci packages. Let’s dive into today’s 5 projects in focus!

As part of our series summarizing all projects from this year’s unconf I’m excited to dive into all the security related offerings from this year. (Full set of project recaps: recap 1, recap 2, recap 3, recap 4.) In the spirit of exploration and experimentation at rOpenSci unconferences, these projects are not necessarily finished products or in scope for rOpenSci packages.

After Stefanie’s recap of unconf18, this week the blog will feature brief summaries of projects developed at the event: each day 4 to 5 projects will be highlighted. (Full set of project recaps: recap 1, recap 2, recap 3, recap 4) In the following weeks, a handful of groups will share more thorough posts about their work.

We held our 5th annual unconference in Seattle, May 21-22, 2018 at Microsoft’s Reactor space. Researchers, students, postdocs and faculty, R software users and developers, and open data enthusiasts from academia, industry, government, and non-profits came together for two days to hack on projects they dreamed up and for an opportunity to meet and work together in person.

R package test suites that include HTTP requests are dependent on an internet connection being up, the internet connection speed, changing behavior of the remote server, as well as changing response formats/data from a remote server. We ideally want to test functionality of our package relative to some known data that isn’t intermittently unavailable or changing.

taxize was seven years old this last Saturday! What is taxize? taxize is designed around making working with taxonomic names easier - abstracting away the details of what each of 20 or so taxonomic data sources require for a given use case.

The drake R package is not only a reproducible research solution, but also a serious high-performance computing engine. The package website introduces drake, and this technical note draws from the guides on high-performance computing and timing in the drake manual. You can help! Some of these features are brand new, and others are newly refactored.

Phylogenetic trees are commonly used to present evolutionary relationships of species. Newick is the de facto format in phylogenetic for representing tree(s). Nexus format incorporates Newick tree text with related information organized into separated units known as blocks. For the R community, we have ape and phylobase packages to import trees from Newick and Nexus formats.

Icons in R Icons can be added to your R Markdown documents using short prefixes which identify the font’s library. fa: Font Awesome ai: Academicons ii: ionicons For example, `r icon::fa("rocket")` can be used to add the rocket icon from Font Awesome. This interface is convenient if you are familiar with the icon you want, or if you are dynamically selecting your icon.

Our onboarding processensures that packages contributed by the community undergo atransparent, constructive, non adversarial and open review process.Before even submitting my first R package to rOpenSci onboarding systemin December 2015, I spent a fair amount of time reading through previousissue threads in order to assess whether onboarding was a friendly placefor me: a newbie, very motivated to learn more but a newbie nonetheless.I soon got