Leadership in open source projects
This is the second part of the previous post about concepts around open source/free software.
Since last book, I also read Uncurled which recommended “The Making and maintenance of open source software” (I will short it to MMOSS) and “Producing Open Source Software” (POSS), which provide first hand experiences about how those maintainers handled different projects.
Writing a thesis with bookdown
Tips and leasons learned while writing a PhD thesis with bookdown.
Concepts around open source/free software
This post is to lay out some concepts I picked up after reading “The Making and maintenance of open source software”. Having these concepts in mind might help me on my contributions to R and OSS in general.
Creating an RSS feed for r-bloggers for my blogdown
To avoid post with incorrect XML on full content you can limit the post served on the pages.
Reasons why packages are archived on CRAN
Most frequent reason is due to the package not fixed on time, followed by depending on packages archived and policy violation.
Bugs in R
Bug reports history review and common actions and patterns. People that contribute and how it might continue to go.
CRAN review
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.
rOpenSci submissions
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.
Bioconductor submissions: reviews
Looking in detail to Bioconductor sumbissions: interactions between bots, reviewers and the community.
Social activities on GitHub
Presenting the socialGH package to retrieve information from GitHub.