: slides; : recording; : materials; : blog post(s).
At rOpenSci, packages contributed by the community undergo a transparent, constructive, non adversarial and open review process. In this talk I’ll briefly present how our peer-review system is built upon empathy, communication, documentation and automation.
“Develop an R package”, they said… What does this even mean? In this session with a live demo, we shall demystify the creation of an R package. R packages are mostly well-organized folders, and there are automatic tools to help. Let’s dive into the wonders of usethis! We shall also see why to create a package (or not). We shall furthermore explain how to improve your R package and your own package development skills.
Apprendre à programmer, quelle bonne idée ! Et que d’efforts à venir… En effet, même une fois passé·e au-delà de “Bonjour Monde”, vous continuerez régulièrement à avoir des problèmes… Triste constat ? Non, car vous apprendrez aussi à devenir un·e praticien·ne résilient·e ! Dans cette présentation ancrée dans mon expérience avec le langage de programmation R, je vous donnerai quelques pistes pour mieux gérer votre portefeuille de savoir, et pour vous tirer des mauvais pas avec brio ou au moins pas trop de souci.
Summary from rOpenSci website: Software peer-review involves coordinating and tracking many moving parts: software submissions, testing and diagnostics, assignment of editors and reviewers, and logging the progression of submissions through revisions and acceptance. On this call we will discuss how rOpenSci has worked with The Journal of Open Source Software to extend JOSS’s approach of chatops-driven publishing into a new GitHub chat-bot that manages our editorial process: assigning tasks, tagging issues, running tests on software submissions, and returning reports to reviewers and editors, logging reviews in an external (Airtable) database, all from the comfort of a GitHub issue comment.