๐ข R Project Sprint 2026
๐ข University of Birmingham / Remote
๐
Tue 1 - Thu 3 Sept
โจ Travel funding available โจ
Apply by Friday 8 May to join this free event to collaborate on contributions to #RStats.
https://contributor.r-project.org/r-project-sprint-2026
The latest issue of @rweekly is now live!
https://rweekly.org/2026-W14.html
Highlights:
- ๐ Introducing ggauto: automating better charts by @nrennie
- ๐ค Adding Alt Text in Quarto with Claude Code by @stephenturner.us
- โ Using science to find the best decaf by @gdeejay.bsky.social
As always, thanks for your contributions - keep them coming! Add your R blog to our RSS feed list, or submit a PR on GitHub linking to a post
"The Untold Story of R" - Youtube Video by CodeSource
Interesting to have to show to folks who wonder what all this "R" stuff is about.
Caveat: this is obviously an AI production, with weird package name pronounciation, and it swings into a lot of "Spicy" topics
https://www.youtube.com/watch?si=29bE-YvuKeQj8WJE&v=FjSPm1PB6Y0&feature=youtu.be

A nod of appreciation to the `pak` library for R.
I don't use #RStats much anymore (because #Julia), but just wanted to test something that required installing devtools--and of course my current system was missing some of the system libraries that devtools depends on. `install.packages` makes it difficult to figure out what's missing, but `pak` provides much better documentation, including of missing dependencies.
The goal of pak is to make package installation faster and more reliable. In particular, it performs all HTTP operations in parallel, so metadata resolution and package downloads are fast. Metadata and package files are cached on the local disk as well. pak has a dependency solver, so it finds version conflicts before performing the installation. This version of pak supports CRAN, Bioconductor and GitHub packages as well.