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.
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.
We are pleased to announce the release of our new Code of Conduct. rOpenSci’s community is our best asset and it’s important that we put strong mechanisms in place before we have to act on a report. As before, our Code applies equally to members of the rOpenSci team and to anyone from the community at large participating in in-person or online activities.
In late November 2018, we ran the third annual rOpenSci ozunconf. This is the sibling rOpenSci unconference, held in Australia. We ran the first ozunconf in Brisbane in 2016, and the second in Melbourne in 2017. Photos taken by Ajay from Fotoholics As usual, before the unconf, we started discussion on GitHub issue threads,and the excitement was building with the number of issues.
I never really thought I would write an R package. I use R pretty casually. Then, this year, I was invited to participate during the last week of the Analytical Paleobiology short course, an intensive month-long experience in quantitative paleontology. I was thrilled to be invited.
