The rOpenSci Blog

Community call on Enhancing Software Peer Review with GitHub Automation, help wanted issues, new packages and package news

• newsletter

A major difference between r-universe and static repositories like CRAN and BioConductor is continuous deployment: packages in r-universe are continuously built in CI and immediately deployed to our package server. This package server stores binaries and metadata in a database, which enables us to dynamically query and expose all the package data through APIs, dashboards, feeds, etc. Based on some suggestions from twitter users, we have added support for RSS feeds of package updates

• r-universe
• rss
• feeds
• tech notes

cffr, a package for creating valid CITATION.cff files using the metadata of any R package.

• cffr
• citations
• codemeta
• community
• cran
• github
• metadata
• packages
• R
• Software Peer Review
• zenodo

When GitHub announced support for CITATION.cff files I though of creating a package that would assist R developers in this matter. I was already using codemetar for most of my packages, so I was familiar with the creation of these kind of metadata files. I borrowed some ideas from codemetar, although I decided to create most of my code from scratch (I enjoy challenging myself, and there is no better way of learning)....

• cffr
• CI
• community
• GitHub Actions
• r-universe
• tech notes
• testing
• testthat

Updates in version 0.7.0 of the online book 'rOpenSci Packages: Development, Maintenance, and Peer Review rOpenSci Packages: Development, Maintenance, and Peer Review'

• Software Peer Review
• dev guide