r

Bug reports history review and common actions and patterns. People that contribute and how it might continue to go.

I’ve been doing some analysis on the review submissions of several projects of R. However, till recently I couldn’t analyze the CRAN submission. There was cransays’ package to check package submissions which on the online documentation provided a dashboard which updated each hour.

Comparing rOpenSci review process to the Bioconductor review process. Most important differences are external reviewers and build on external machines as well as a longer review time.

Looking in detail to Bioconductor sumbissions: interactions between bots, reviewers and the community.

Presenting the socialGH package to retrieve information from GitHub.

Exploring the submission process to Bioconductor. What happens, how long does it take, what are the common problems and solutions for new contributors.

Checking quarantine environments

Checking who can be Rweekly.org editor with R

New policy in CRAN With the new policy of a maximum of 20 packages in Imports. Let’s see how many dependencies has each package on CRAN and Bioconductor:

One of the worst thing I experienced is having a bug in a nested call of functions. If it is not simple the problems comes to isolate when and why does it occur.