Our 1-hour Call on Reproducible Research with R will include three speakers and 20 minutes for Q & A.
Ben Marwick will introduce you to a research compendium, which accompanies, enhances, or is a scientific publication providing data, code, and documentation for reproducing a scientific workflow.
From Karthik Ram you will learn about holepunch, an R package that will take any GitHub repo with R scripts and R markdown files and quickly turn it in into a free, live RStudio server where anyone can run your code!
...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. Search the schedule for details.
Wednesday, July 10
Julia Stewart Lowndes Keynote! R for better science in less time
...rOpenSci HQ 👨🏽💻👩🏼💻 🏗️
Software Peer Review ✔
6 community-contributed packages passed software peer review
Consider submitting your package or volunteering to review.
...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?
Our guest speakers will include:
The call will be moderated by Melina Vidoni, an associate editor for rOpenSci software peer review. There will be 20 minutes for Q & A following the presentations.
...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. Increasing maintainers increases the so-called bus factor. A lower number of maintainers means fewer people have to get hit by a bus to then have no maintainers.
...