Three members of the rOpenSci team - Scott Chamberlain, Jenny Bryan, and Rich FitzJohn - as well as many community members will give talks at useR!2019. Many other package authors, maintainers, reviewers and unconf participants will be there too. Don’t hesitate to ask them about rOpenSci packages, software peer review, community, or just say hello if you’re looking for a friendly face. We’ve listed their talks for you.

rOpenSci’s community is increasingly international and multilingual. While we have operated primarily in English, we now receive submissions of packages from authors whose primary language is not. As we expand our community in this way, we want to learn from the experience of other organizations. How can we manage our peer-review process and open-source projects to be welcoming to non-native English speakers?

Software is maintained by people. While software can in theory live on indefinitely, to do so requires people. People change jobs, move locations, retire, and unfortunately die sometimes. When a software maintainer can no longer maintain a package, what happens to the software? Because of the fragility of people in software, in an ideal world a piece of software should have as many maintainers as possible.

[From algorithms to the bench]{style=“color: #666666; font-family: "arial"; font-size: 15pt; vertical-align: baseline; white-space: pre-wrap;”} [Text-mining holds the promise of helping researchers to overcome information overload. It is a familiar premise: an avalanche of scientific knowledge is being produced and shared.

We’ve been following rOpenSci’s work for a long time, and we use several packages on a daily basis for our scientific projects, especially taxize to clean species names, rredlist to extract species IUCN statuses or [treeio](many probs with this post) to work with phylogenetic trees.rOpensci is a perfect incarnation of a vibrant and diverse community where people learn and develop new ideas, especially regarding scientific packages.We’ve also

Introduction ramlegacy is a new R package to download, cache and read in all the different versions of the RAM Legacy Stock Assessment Database, a public database containing stock assessment results of commercially exploited marine populations from around the world.

Stefanie Butland, rOpenSci Community Manager Some things are just irresistible to a community manager – PhD student Hugo Gruson’s recent tweets definitely fall into that category.

“Security” can be a daunting, scary, and (frankly) quite often a very boring topic. BUT!, we promise that this Community Call on May 7th will be informative, engaging, and enlightening (or, at least not boring)! Applying security best practices is essential not only for developers or sensitive data storage but also for the everyday R user installing R packages, contributing to open source, working with APIs or remote servers.

Our next Community Call, on March 27th, aims to help people learn about using rOpenSci’s R packages to access and analyze taxonomy and biodiversity data, and to recognize the breadth and depth of their applications. We also aim to learn from the discussion how we might improve these tools.

There seem to be a lot of ways to write about your R package, and rather than haveto decide on what to focus on I thought I’d write a little bit about everything.To begin with I thought it best to describe what problem rdhs tries to solve,why it was developed and how I came to be involved in this project.