<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>rOpenSci - open tools for open science</title><link>https://ropensci.org/</link><description>Recent content on rOpenSci - open tools for open science</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 02 Apr 2026 11:59:17 +0200</lastBuildDate><atom:link href="https://ropensci.org/index.xml" rel="self" type="application/rss+xml"/><item><title>Rencontres R 2026 - Nantes</title><link>https://ropensci.org/events/rr2026/</link><pubDate>Thu, 18 Jun 2026 17:00:00 +0000</pubDate><guid>https://ropensci.org/events/rr2026/</guid><description>
&lt;p&gt;&lt;a href="https://rr2026.sciencesconf.org/?lang=fr"&gt;Rencontres R 2026&lt;/a&gt; will take place in Nantes, France, June 16-18, 2026.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Maëlle will be presenting her keynote talk &amp;ldquo;Plongée dans l&amp;rsquo;écosystème R&amp;rdquo;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Maëlle will be the teaching assistant for Christophe Dervieux&amp;rsquo;s tutorial &amp;ldquo;PDF sans frictions : Typst dans vos projets Quarto&amp;rdquo;.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>Software Sustainability and Community Management</title><link>https://ropensci.org/events/r-medicine-2026-keynote/</link><pubDate>Thu, 07 May 2026 16:15:00 +0000</pubDate><guid>https://ropensci.org/events/r-medicine-2026-keynote/</guid><description>
&lt;p&gt;&lt;a href="https://rconsortium.github.io/RMedicine_website/"&gt;R/Medicine 2026&lt;/a&gt; will happen May 4-8, 2026.&lt;/p&gt;
&lt;p&gt;Yanina Bellini Saibene will deliver a keynote on Thursday May 7th, 11:15AM–12:15PM ET.&lt;/p&gt;
&lt;p&gt;Sustainable software depends as much on people and practices as it does on code. In this talk, she will draw on her experience leading and supporting R communities to show how intentional community management contributes to long-term software sustainability. Using concrete examples, she will highlight how communities of practice help distribute maintenance, grow skills, and support inclusive, resilient software ecosystems across research and open source.&lt;/p&gt;</description></item><item><title>Social Coworking and Office Hours - Code Review with rOpenSci</title><link>https://ropensci.org/events/coworking-2026-05/</link><pubDate>Tue, 05 May 2026 03:00:00 +0000</pubDate><guid>https://ropensci.org/events/coworking-2026-05/</guid><description>
&lt;p&gt;&lt;strong&gt;Join us for 2 hours Tuesday May 05, 09:00 Australia Western (01:00 UTC) for
&lt;a href="https://ropensci.org/blog/2023/06/21/coworking/"&gt;Social Coworking + Office Hours&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This month we&amp;rsquo;re focusing on the theme &lt;strong&gt;Code Review with rOpenSci&lt;/strong&gt;
with community host &lt;strong&gt;Liz Hare&lt;/strong&gt;, rOpenSci Champion and Software Reviewer,
Dog Genetics Researcher, and accessibility advocate.&lt;/p&gt;
&lt;p&gt;Come for the full 2 hrs or only as long as you need!&lt;/p&gt;
&lt;h3&gt;
Cowork
&lt;/h3&gt;&lt;ul&gt;
&lt;li&gt;Explore resources for Code Review&lt;/li&gt;
&lt;li&gt;Sign up to volunteer to do &lt;a href="https://airtable.com/app8dssb6a7PG6Vwj/shrnfDI2S9uuyxtDw"&gt;software peer-review&lt;/a&gt; at rOpenSci&lt;/li&gt;
&lt;li&gt;Cowork independently on something related to R&lt;/li&gt;
&lt;li&gt;Cowork on whatever you need to get done!&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;
Socialize/Network
&lt;/h3&gt;&lt;ul&gt;
&lt;li&gt;Meet community host, &lt;strong&gt;Liz Hare&lt;/strong&gt;, and discuss Code Review with rOpenSci and which resources are available.&lt;/li&gt;
&lt;li&gt;Meet other R users and rOpenSci staff in Zoom&lt;/li&gt;
&lt;li&gt;Get answers to your questions: Ask hosts or coworkers&lt;/li&gt;
&lt;li&gt;Discuss your work, best practices, or get advice and resources&lt;/li&gt;
&lt;li&gt;Answer other coworkers&amp;rsquo; questions!&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;We host &lt;a href="https://ropensci.org/blog/2023/06/21/coworking/"&gt;Social Coworking + Office Hours&lt;/a&gt;
on the first Tuesday of each month, alternating among timezones to
accommodate different parts of the world.&lt;/p&gt;</description></item><item><title>Social Coworking and Office Hours - Getting to know the CSID Network</title><link>https://ropensci.org/events/coworking-2026-04/</link><pubDate>Tue, 07 Apr 2026 18:00:00 +0000</pubDate><guid>https://ropensci.org/events/coworking-2026-04/</guid><description>
&lt;p&gt;&lt;strong&gt;Join us for 2 hours Tuesday April 07, 09:00 Americas Pacific (16:00 UTC) for
&lt;a href="https://ropensci.org/blog/2023/06/21/coworking/"&gt;Social Coworking + Office Hours&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This month we&amp;rsquo;re focusing on the theme &lt;strong&gt;Getting to know the Climate Sensitive Infectious Disease (CSID) Network&lt;/strong&gt;
with community hosts &lt;strong&gt;Irene Ramos&lt;/strong&gt; and &lt;strong&gt;Adamu Saleh Saidu&lt;/strong&gt;. Irene is curious about the intersection of open science, data, and sustainability, and is the Head of Membership for the CSID Network. Adamu is a reader in Epidemiology at University of Maiduguri, One Health activist with experience in public health, epidemiology and modelling of infectious diseases, and on the CSID Network Membership Committee.&lt;/p&gt;</description></item><item><title>A Better R Programming Experience Thanks to Tree-sitter</title><link>https://ropensci.org/blog/2026/04/02/tree-sitter-overview/</link><pubDate>Thu, 02 Apr 2026 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2026/04/02/tree-sitter-overview/</guid><description>
&lt;p&gt;A little bit less than two years ago, building on work by Jim Hester and Kevin Ushey, Davis Vaughan completed a very impactful JavaScript file for the R community: an R grammar for the Tree-sitter parsing generator. He even got a round of applause for it during a talk at the useR! 2024 conference! So, did he get cheered for&amp;hellip; grammatical rules in a &lt;a href="https://github.com/r-lib/tree-sitter-r/blob/next/grammar.js"&gt;JavaScript file&lt;/a&gt;? &amp;#x1f605;&lt;/p&gt;
&lt;p&gt;No, the audience was excited about the &lt;em&gt;improved developer experience for R&lt;/em&gt; that this file unlocked. R tooling around Tree-sitter is how you get&lt;/p&gt;</description></item><item><title>rOpenSci News Digest, March 2026</title><link>https://ropensci.org/blog/2026/03/30/news-mars-2026/</link><pubDate>Mon, 30 Mar 2026 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2026/03/30/news-mars-2026/</guid><description>
&lt;!-- Before sending DELETE THE INDEX_CACHE and re-knit! --&gt;
&lt;p&gt;Dear rOpenSci friends, it&amp;rsquo;s time for our monthly news roundup! &lt;!-- blabla --&gt; You can read this post &lt;a href="https://ropensci.org/blog/2026/03/30/news-mars-2026"&gt;on our blog&lt;/a&gt;. Now let&amp;rsquo;s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;h3&gt;
rOpenSci Dev Guide 1.0.0: Trilingual and Improved
&lt;/h3&gt;&lt;p&gt;rOpenSci Software Peer Review&amp;rsquo;s guidance is gathered in an online book that keeps improving! It is now available in &lt;a href="https://devguide.ropensci.org/"&gt;English&lt;/a&gt;, &lt;a href="https://devguide.ropensci.org/es/index.es.html"&gt;Spanish&lt;/a&gt; and &lt;a href="https://devguide.ropensci.org/pt/index.pt.html"&gt;Portuguese&lt;/a&gt;. Read more in the &lt;a href="https://ropensci.org/blog/2026/03/02/devguide-1.0.0/"&gt;release announcement&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Code Peer Review in practice: how we review code in open projects</title><link>https://ropensci.org/events/rse-argentina-code-review-2026/</link><pubDate>Thu, 26 Mar 2026 22:00:00 +0000</pubDate><guid>https://ropensci.org/events/rse-argentina-code-review-2026/</guid><description>
&lt;p&gt;First RSE Argentina meetup of the year! Yanina Bellini Saibene will lead a talk on code peer review in practice: how we review code in open projects.&lt;/p&gt;
&lt;p&gt;Event in Spanish. Free online event – registration required: &lt;a href="https://luma.com/7xzkl5qh"&gt;https://luma.com/7xzkl5qh&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Open Science and Reproducible Research: The rOpenSci Experience and Perspective</title><link>https://ropensci.org/events/nutriverse-commcall-2026/</link><pubDate>Wed, 18 Mar 2026 15:00:00 +0000</pubDate><guid>https://ropensci.org/events/nutriverse-commcall-2026/</guid><description>
&lt;p&gt;Noam Ross will be chatting on all things open science and reproducible research based on his many years of experience as a community member and now a community leader not just of rOpenSci but of the wider open science movement.&lt;/p&gt;
&lt;p&gt;More details: &lt;a href="https://nutriverse.io/community-calls/2026-03-18-community-call.html"&gt;https://nutriverse.io/community-calls/2026-03-18-community-call.html&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Breaking Release of the patentsview R Package</title><link>https://ropensci.org/blog/2026/03/10/patentsview-breaking-release/</link><pubDate>Tue, 10 Mar 2026 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2026/03/10/patentsview-breaking-release/</guid><description>
&lt;p&gt;The &lt;a href="http://docs.ropensci.org/patentsview/"&gt;patentsview&lt;/a&gt; R package was created by Chris Baker to simplify interactions with the
PatentsView API as announced in Chris&amp;rsquo;
&lt;a href="https://ropensci.org/blog/2017/09/19/patentsview/"&gt;blog post&lt;/a&gt;
in 2017. The API can be queried for data from US patents granted since 1976 as well as
patent applications since 2001 (not all going on to become granted patents).&lt;br&gt;
As shown in the package&amp;rsquo;s vignettes, location data can be mapped, charts of
assignees can be created etc. using other R packages, only limited by the
developer&amp;rsquo;s imagination.&lt;/p&gt;</description></item><item><title>Social Coworking and Office Hours - rOpenSci Editors</title><link>https://ropensci.org/events/coworking-2026-03/</link><pubDate>Tue, 03 Mar 2026 15:00:00 +0000</pubDate><guid>https://ropensci.org/events/coworking-2026-03/</guid><description>
&lt;p&gt;&lt;strong&gt;Join us for 2 hours Tuesday March 03, 14:00 Europe Central (13:00 UTC) for
&lt;a href="https://ropensci.org/blog/2023/06/21/coworking/"&gt;Social Coworking + Office Hours&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This month we&amp;rsquo;re focusing on the theme &lt;strong&gt;rOpenSci Editors&lt;/strong&gt;
with cohost &lt;strong&gt;Mark Padgham&lt;/strong&gt;, rOpenSci Software Review Lead and passionate open science and open data advocate!&lt;/p&gt;
&lt;p&gt;Come for the full 2 hrs or only as long as you need!&lt;/p&gt;
&lt;h3&gt;
Cowork
&lt;/h3&gt;&lt;ul&gt;
&lt;li&gt;Learn more about &lt;a href="https://ropensci.org/software-review/"&gt;rOpenSci Software Peer Review&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Cowork independently on something related to R&lt;/li&gt;
&lt;li&gt;Cowork on whatever you need to get done!&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;
Socialize/Network
&lt;/h3&gt;&lt;ul&gt;
&lt;li&gt;Meet cohost, &lt;strong&gt;Mark Padgham&lt;/strong&gt;, and discuss what it&amp;rsquo;s like being an Editor for rOpenSci Software Peer Review.&lt;/li&gt;
&lt;li&gt;Meet other R users and rOpenSci staff in Zoom&lt;/li&gt;
&lt;li&gt;Discuss your work, best practices, or get advice and resources&lt;/li&gt;
&lt;li&gt;Ask and answer questions with the hosts and other coworkers&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;We host &lt;a href="https://ropensci.org/blog/2023/06/21/coworking/"&gt;Social Coworking + Office Hours&lt;/a&gt;
on the first Tuesday of each month, alternating among timezones to
accommodate different parts of the world.&lt;/p&gt;</description></item><item><title>rOpenSci Dev Guide 1.0.0: Trilingual and Improved</title><link>https://ropensci.org/blog/2026/03/02/devguide-1.0.0/</link><pubDate>Mon, 02 Mar 2026 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2026/03/02/devguide-1.0.0/</guid><description><i><a href="https://ropensci.org/es/blog/2026/03/02/r_open_sci_dev_guide_1_0_0_triling%C3%BCe_y_mejorada/">Read it in: Español</a>.</i><i><a href="https://ropensci.org/pt/blog/2026/03/02/guia_de_desenvolvimento_da_r_open_sci_1_0_0_tril%C3%ADngue_e_aprimorado/">Read it in: Português</a>.</i>
&lt;p&gt;rOpenSci Software Peer Review&amp;rsquo;s guidance is gathered in an &lt;a href="https://devguide.ropensci.org/booknews"&gt;online book&lt;/a&gt; that keeps improving!
This blog post summarises what&amp;rsquo;s new in our Dev Guide 1.0.0, with all changes listed in the &lt;a href="https://devguide.ropensci.org/booknews.html"&gt;changelog&lt;/a&gt;.&lt;/p&gt;
&lt;h2&gt;
Now available in Portuguese!
&lt;/h2&gt;&lt;p&gt;Our guide is now trilingual (&lt;a href="https://devguide.ropensci.org/index.html"&gt;English&lt;/a&gt;, &lt;a href="https://devguide.ropensci.org/es/index.es.html"&gt;Spanish&lt;/a&gt;, &lt;a href="https://devguide.ropensci.org/pt/index.pt"&gt;Portuguese&lt;/a&gt;)!&lt;/p&gt;
&lt;p&gt;Find more about the awesome Portuguese translation project, initiated and powered by our Lusophone members in our &lt;a href="https://ropensci.org/blog/2025/11/25/translation-devguide-pt/"&gt;blog post&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;The translation project and ongoing multilingual maintenance uses our &lt;a href="https://docs.ropensci.org/babelquarto/"&gt;babelquarto package&lt;/a&gt; to render multilingual Quarto books and websites.
It was recently &lt;a href="https://github.com/ropensci/software-review/issues/720"&gt;peer-reviewed&lt;/a&gt; by Ella Kaye and João Granja-Correia.&lt;/p&gt;</description></item><item><title>rOpenSci News Digest, February 2026</title><link>https://ropensci.org/blog/2026/02/26/news-february-2026/</link><pubDate>Thu, 26 Feb 2026 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2026/02/26/news-february-2026/</guid><description>
&lt;!-- Before sending DELETE THE INDEX_CACHE and re-knit! --&gt;
&lt;p&gt;Dear rOpenSci friends, it&amp;rsquo;s time for our monthly news roundup! &lt;!-- blabla --&gt; You can read this post &lt;a href="https://ropensci.org/blog/2026/02/26/news-february-2026"&gt;on our blog&lt;/a&gt;. Now let&amp;rsquo;s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;h3&gt;
Strong Engagement in the Champions Program Call
&lt;/h3&gt;&lt;p&gt;The Champions Program call closed on February 23, and the response &lt;em&gt;was fantastic&lt;/em&gt;. We received &lt;strong&gt;81 Champion&lt;/strong&gt; and &lt;strong&gt;14 Mentor applications&lt;/strong&gt; from &lt;strong&gt;23 countries&lt;/strong&gt;, with &lt;strong&gt;74%&lt;/strong&gt; of applicants proposing to develop a &lt;strong&gt;new package&lt;/strong&gt;. We&amp;rsquo;re now kicking off the selection process, starting with mentors so they can support the evaluation of Champion proposals. Confirmation emails have already been sent to all applicants. Thank you to everyone who applied!&lt;/p&gt;</description></item><item><title>Software Review in the Era of AI: What We Are Testing at rOpenSci</title><link>https://ropensci.org/blog/2026/02/26/ropensci-ai-policy/</link><pubDate>Thu, 26 Feb 2026 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2026/02/26/ropensci-ai-policy/</guid><description>
&lt;p&gt;The advent of large language models (LLMs) and generative AI tools has changed the nature of software development and of software review.
These developments are complex, challenging, and controversial, but require action to maintain and grow rOpenSci&amp;rsquo;s programs and community.
In response, we are starting with a preliminary set of policies to clarify our expectations for use of generative AI tools by authors, reviewers, and editors in software peer-review.
This blog post describes the challenges ahead and initial changes we are making.&lt;/p&gt;</description></item><item><title>Our forum is closed but our community is not!</title><link>https://ropensci.org/blog/2026/02/23/forum-closing/</link><pubDate>Mon, 23 Feb 2026 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2026/02/23/forum-closing/</guid><description>
&lt;p&gt;As of this week, we are closing our forum at &lt;code&gt;discuss.ropensci.org&lt;/code&gt;.
The forum has become largely inactive in recent years, so we are consolidating our conversations to our other online spaces to reduce maintenance and moderation burden.&lt;/p&gt;
&lt;p&gt;We&amp;rsquo;re not putting our community building aside or behind a wall! We remain committed to our &lt;a href="https://ropensci.org/blog/2025/02/05/no-science-without-deia/"&gt;values&lt;/a&gt; and to maintaining an open community.
We&amp;rsquo;ve migrated the most active part of the forum, the use cases collection, to our &lt;a href="https://ropensci.org/usecases"&gt;website&lt;/a&gt;, and we will continue to collect them via &lt;a href="https://github.com/orgs/ropensci/discussions/categories/use-cases"&gt;GitHub discussions&lt;/a&gt;.
Don&amp;rsquo;t forget that there are still many other ways to be part of the &lt;a href="https://contributing.ropensci.org/"&gt;rOpenSci Community&lt;/a&gt;:&lt;/p&gt;</description></item><item><title>Clinica de Aplicación para el Programa de Campeon(e|a)s de rOpenSci</title><link>https://ropensci.org/events/clinica-champions-2026/</link><pubDate>Thu, 05 Feb 2026 18:00:00 +0000</pubDate><guid>https://ropensci.org/events/clinica-champions-2026/</guid><description>
&lt;p&gt;&lt;strong&gt;Sumate a esta clinica de aplicaciones durante 2 horas el jueves, 5 de febrero, 13:00 UTC-3 (Argentina, Uruguay) / 16:00 UTC&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;Este mes tenemos una sesión especial que funciona como una Clínica de Aplicación para
el Programa Campeon(e|a)s con nuestra &lt;em&gt;community manager&lt;/em&gt;, &lt;strong&gt;Yanina Bellini Saibene&lt;/strong&gt;,
como co-anfitriona.&lt;/p&gt;
&lt;p&gt;¡Ven a las 2 horas completas o sólo el tiempo que necesites!&lt;/p&gt;
&lt;h3&gt;
Trabaja en comunidad en tu aplicación para el Programa de Campeones
&lt;/h3&gt;&lt;ul&gt;
&lt;li&gt;Prepara tu solicitud para el Programa de Campeones&lt;/li&gt;
&lt;li&gt;Conoce a la co-anfitriona &lt;strong&gt;Yanina Bellini Saibene&lt;/strong&gt; para charlar sobre el Programa de Campeones
&lt;ul&gt;
&lt;li&gt;¿Tienes preguntas sobre el programa?&lt;/li&gt;
&lt;li&gt;¿Quieres más detalles sobre ser campeon-a o mentor-a?&lt;/li&gt;
&lt;li&gt;¿Tienes preguntas específicas sobre la solicitud?&lt;/li&gt;
&lt;li&gt;¿Necesitas ideas y comentarios sobre tu solicitud antes de presentarla?&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Participa en esta sesión para plantear sus preguntas directamente al equipo de rOpenSci. ¡Siéntete libre de unirte al evento en cualquier momento que quieras durante las dos horas!&lt;/p&gt;</description></item><item><title>Paleontology R Packages to Benefit from Software Sustainability Institute Grant</title><link>https://ropensci.org/blog/2026/02/05/palaeoverse-ssi-grant/</link><pubDate>Thu, 05 Feb 2026 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2026/02/05/palaeoverse-ssi-grant/</guid><description>
&lt;p&gt;&lt;a href="https://palaeoverse.org/"&gt;Palaeoverse&lt;/a&gt;, a grassroots organization that develops R packages for paleontology, has been &lt;a href="https://www.software.ac.uk/rsmf-round-1-projects"&gt;awarded a Large Grant&lt;/a&gt; from the &lt;a href="https://www.software.ac.uk/"&gt;Software Sustainability Institute&lt;/a&gt;, via the &lt;a href="https://www.software.ac.uk/programmes/research-software-maintenance-fund"&gt;Research Software Maintenance Fund&lt;/a&gt;, for the project &amp;lsquo;Converting Users to Contributors: Enabling Sustainable Maintenance and Development of Palaeoverse&amp;rsquo;.
This funding will support efforts to improve the sustainability and maintainability of several key R packages used in paleontological research.&lt;/p&gt;
&lt;figure class="pull-left"&gt;&lt;img src="https://ropensci.org/blog/2026/02/05/palaeoverse-ssi-grant/palaeoverse.png"
alt="The Palaeoverse logo"&gt;
&lt;/figure&gt;
&lt;h2&gt;
Welcome to Palaeoverse
&lt;/h2&gt;&lt;p&gt;&lt;a href="https://palaeoverse.org/"&gt;Palaeoverse&lt;/a&gt; is an initiative aiming to unite the paleontological community through shared resources, agreed standards, and a collective commitment to improving reproducibility in paleontological research.
The project began in 2022 when a group of early-career researchers, including myself, recognized a common challenge: many of us were independently developing similar programmatic workflows for cleaning and preparing paleontological data due to a lack of standardized tools and protocols, leading to duplicated work that was difficult to reproduce.
In response, we came together to develop the &lt;a href="https://palaeoverse.palaeoverse.org/"&gt;palaeoverse R package&lt;/a&gt;—a toolkit designed to streamline data preparation and exploration in paleontological research.
Since then, Palaeoverse has evolved into a formally organized initiative with a growing scope.
We maintain multiple &lt;a href="https://github.com/palaeoverse"&gt;R packages&lt;/a&gt;, curate &lt;a href="https://palaeoverse.org/external"&gt;resources&lt;/a&gt;, host &lt;a href="https://www.youtube.com/@ThePalaeoverse"&gt;lectures&lt;/a&gt;, and run &lt;a href="https://workshop.palaeoverse.org/"&gt;training workshops&lt;/a&gt;.
These resources have been developed entirely through the &lt;a href="https://palaeoverse.org/#about-us"&gt;current team&lt;/a&gt;’s voluntary efforts.&lt;/p&gt;</description></item><item><title>Social Coworking and Office Hours - Share your Positron setup!</title><link>https://ropensci.org/events/coworking-2026-02/</link><pubDate>Tue, 03 Feb 2026 03:00:00 +0000</pubDate><guid>https://ropensci.org/events/coworking-2026-02/</guid><description>
&lt;p&gt;&lt;strong&gt;Join us for 2 hours Tuesday February 03, 09:00 Australia Western (01:00 UTC) for
&lt;a href="https://ropensci.org/blog/2023/06/21/coworking/"&gt;Social Coworking + Office Hours&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This month&amp;rsquo;s theme is &lt;strong&gt;Share your Positron setup&lt;/strong&gt;
with community host &lt;strong&gt;Noam Ross&lt;/strong&gt;, rOpenSci Executive Director, Software Peer-Review Editor, and Positron convert.&lt;/p&gt;
&lt;p&gt;Come for the full 2 hrs or only as long as you need!&lt;/p&gt;
&lt;h3&gt;
Cowork
&lt;/h3&gt;&lt;ul&gt;
&lt;li&gt;Setup Positron and explore extensions and custom settings&lt;/li&gt;
&lt;li&gt;Cowork independently on something related to R&lt;/li&gt;
&lt;li&gt;Cowork on whatever you need to get done!&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;
Socialize/Network
&lt;/h3&gt;&lt;ul&gt;
&lt;li&gt;Meet community host, &lt;strong&gt;Noam Ross&lt;/strong&gt;, share how you have set up Positron for your workflow and learn from others&lt;/li&gt;
&lt;li&gt;Meet other R users and rOpenSci staff in Zoom&lt;/li&gt;
&lt;li&gt;Discuss your work, best practices, or get advice and resources&lt;/li&gt;
&lt;li&gt;Ask and answer questions with the hosts and other coworkers&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;We host &lt;a href="https://ropensci.org/blog/2023/06/21/coworking/"&gt;Social Coworking + Office Hours&lt;/a&gt;
on the first Tuesday of each month, alternating among timezones to
accommodate different parts of the world.&lt;/p&gt;</description></item><item><title>Announcing New Statistical Software Peer Review Editors: Natalia da Silva and Andrew Heiss</title><link>https://ropensci.org/blog/2026/02/03/editors2025/</link><pubDate>Tue, 03 Feb 2026 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2026/02/03/editors2025/</guid><description>
&lt;p&gt;At rOpenSci we’re continually grateful for the support and engagement of our community who help make our open-source ecosystem stronger, more inclusive, and more collaborative. The &lt;a href="https://ropensci.org/software-review/"&gt;software peer review program&lt;/a&gt; is one of the best examples of this: bringing together people from diverse expertise and backgrounds to improve the quality, reproducibility, and usability of scientific software across the R ecosystem.&lt;/p&gt;
&lt;p&gt;Today we’re excited to welcome &lt;em&gt;Natalia da Silva&lt;/em&gt; and &lt;em&gt;Andrew Heiss&lt;/em&gt; as new editors for our Statistical Software Peer Review team. Their expertise and dedication will help grow and sustain this important program, ensuring that statistical software reviews maintain high standards and continue to improve in quality and impact.&lt;/p&gt;</description></item><item><title>rOpenSci News Digest, January 2026</title><link>https://ropensci.org/blog/2026/01/29/news-january-2026/</link><pubDate>Thu, 29 Jan 2026 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2026/01/29/news-january-2026/</guid><description>
&lt;!-- Before sending DELETE THE INDEX_CACHE and re-knit! --&gt;
&lt;p&gt;Dear rOpenSci friends, it&amp;rsquo;s time for our monthly news roundup! &lt;!-- blabla --&gt; You can read this post &lt;a href="https://ropensci.org/blog/2026/01/29/news-january-2026"&gt;on our blog&lt;/a&gt;. Now let&amp;rsquo;s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;h3&gt;
Open call for the rOpenSci Champions Program 2026!
&lt;/h3&gt;&lt;p&gt;We are pleased to announce the opening of a new call for applications for the &lt;strong&gt;rOpenSci Champions Program in Spanish&lt;/strong&gt;, which will begin in 2026. We are accepting applications for both the roles of &lt;strong&gt;Champion&lt;/strong&gt; as well as &lt;strong&gt;Mentor&lt;/strong&gt;. The application deadline is &lt;strong&gt;February 20, 2026&lt;/strong&gt;.&lt;/p&gt;</description></item><item><title>How to Recruit a New Maintainer for Your Package</title><link>https://ropensci.org/blog/2026/01/27/new-maintainer/</link><pubDate>Tue, 27 Jan 2026 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2026/01/27/new-maintainer/</guid><description><i><a href="https://ropensci.org/es/blog/2026/01/27/new-maintainer/">Read it in: Español</a>.</i>
&lt;p&gt;Maintaining an open source package is rewarding work, but it&amp;rsquo;s also a &lt;a href="https://ropensci.org/blog/2023/02/07/what-does-it-mean-to-maintain-a-package/"&gt;&lt;strong&gt;lot&lt;/strong&gt; of work&lt;/a&gt;.
Life and careers change, interests shift, and sometimes you simply don&amp;rsquo;t have the time or energy to keep working on your R package (and that&amp;rsquo;s okay!&lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt;).
When that happens, one of the most responsible things you can do for package users, &lt;em&gt;and&lt;/em&gt; for yourself, is to &lt;strong&gt;proactively look for a new maintainer or co-maintainer.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&amp;lsquo;How do I recruit a new maintainer?&amp;rsquo; is a question we hear a lot at rOpenSci.
Over the years, we&amp;rsquo;ve supported rOpenSci&amp;rsquo;s package authors through this transition, helping them connect with potential maintainers, clarify expectations around the role, and make handovers smoother and more sustainable.&lt;/p&gt;</description></item><item><title>Open Source Viernes</title><link>https://ropensci.org/events/open-source-viernes/</link><pubDate>Fri, 23 Jan 2026 15:30:00 +0000</pubDate><guid>https://ropensci.org/events/open-source-viernes/</guid><description>
&lt;p&gt;¡Acompáñanos en Open Source Friday para descubrir el Programa de Campeon(a|e)s de rOpenSci, una iniciativa que fortalece comunidades de ciencia abierta y software de investigación en América Latina! Yanina Bellini Saibene, GitHub Star y Community Manager de rOpenSci, nos contará sobre la convocatoria 2026–2027, cómo participar, y el impacto de este programa en el desarrollo de herramientas abiertas con R, mentorías, formación técnica, y liderazgo local. Si te interesa la ciencia abierta, los datos abiertos y el software libre, ¡no te pierdas esta transmisión!&lt;/p&gt;</description></item><item><title>Closing The Loop with Our 2025 Wrap-up</title><link>https://ropensci.org/blog/2026/01/22/yearinreview2025/</link><pubDate>Thu, 22 Jan 2026 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2026/01/22/yearinreview2025/</guid><description>
&lt;p&gt;At the beginning of 2025, we outlined our goals for the year, our &lt;a href="https://ropensci.org/blog/2025/01/22/year-in-review-2024/"&gt;2024 Highlights&lt;/a&gt;. As the year started, our work took place in a far more challenging global context than many of us anticipated. Across many countries, science and research faced funding cuts, layoffs, and attacks on diversity, equity, accessibility, and inclusion. These conditions reshaped timelines and capacities for institutions and for the people doing the work, but also reinforced why community-driven, open, and care-centered spaces matter.&lt;/p&gt;</description></item><item><title>Introducing distionary for Building and Probing Distributions</title><link>https://ropensci.org/blog/2026/01/20/introducing-distionary/</link><pubDate>Tue, 20 Jan 2026 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2026/01/20/introducing-distionary/</guid><description>
&lt;p&gt;After passing through rOpenSci peer review, the &lt;a href="https://docs.ropensci.org/distionary/"&gt;distionary&lt;/a&gt; package is now newly available on CRAN.
It allows you to make probability distributions quickly – either from a few inputs or from its built-in library – and then probe them in detail.&lt;/p&gt;
&lt;p&gt;These distributions form the building blocks that piece together advanced statistical models with the wider &lt;a href="https://probaverse.com"&gt;probaverse&lt;/a&gt; ecosystem, which is built to release modelers from low-level coding so production pipelines stay human-friendly.
Right now, the other probaverse packages are &lt;a href="https://distplyr.probaverse.com"&gt;distplyr&lt;/a&gt;, allowing you to morph distributions into new forms, and &lt;a href="https://famish.probaverse.com"&gt;famish&lt;/a&gt;, allowing you to tune distributions to data.
Developed with risk analysis use cases like climate and insurance in mind, the same tools translate smoothly to simulations, teaching, and other applied settings.&lt;/p&gt;</description></item><item><title>Social Coworking and Office Hours - Let it go!</title><link>https://ropensci.org/events/coworking-2026-01/</link><pubDate>Tue, 13 Jan 2026 19:00:00 +0000</pubDate><guid>https://ropensci.org/events/coworking-2026-01/</guid><description>
&lt;p&gt;&lt;strong&gt;Join us for 2 hours Tuesday January 13, 09:00 Americas Pacific (17:00 UTC) for
&lt;a href="https://ropensci.org/blog/2023/06/21/coworking/"&gt;Social Coworking + Office Hours&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This month we&amp;rsquo;re focusing on the theme &lt;strong&gt;Let it go!&lt;/strong&gt;
with community host &lt;strong&gt;Yanina Bellini Saibene&lt;/strong&gt;, rOpenSci community manager and ruthless unsubscriber of Newsletters and Slack workspaces 😆.&lt;/p&gt;
&lt;p&gt;Come for the full 2 hrs or only as long as you need!&lt;/p&gt;
&lt;h3&gt;
Cowork
&lt;/h3&gt;&lt;ul&gt;
&lt;li&gt;Spend some time reviewing the forums, Slack workspaces, Newsletters, RSS feeds (etc. etc.) you&amp;rsquo;re subscribed to&lt;/li&gt;
&lt;li&gt;Unsubscribe to all you no longer need (Let it go!)&lt;/li&gt;
&lt;li&gt;Cowork independently on something related to R&lt;/li&gt;
&lt;li&gt;Cowork on whatever you need to get done!&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;
Socialize/Network
&lt;/h3&gt;&lt;ul&gt;
&lt;li&gt;Meet community host, &lt;strong&gt;Yanina Bellini Saibene&lt;/strong&gt;, and discuss strategies for this New Year decluttering of your digital (or perhaps not-so-digital) life.&lt;/li&gt;
&lt;li&gt;Meet other R users and rOpenSci staff in Zoom&lt;/li&gt;
&lt;li&gt;Discuss your work, best practices, or get advice and resources&lt;/li&gt;
&lt;li&gt;Ask and answer questions with the hosts and other coworkers&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;We host &lt;a href="https://ropensci.org/blog/2023/06/21/coworking/"&gt;Social Coworking + Office Hours&lt;/a&gt;
on the first Tuesday of each month, alternating among timezones to
accommodate different parts of the world.&lt;/p&gt;</description></item><item><title>Open call for the rOpenSci Champions Program 2026!</title><link>https://ropensci.org/blog/2026/01/12/programchamps2026/</link><pubDate>Mon, 12 Jan 2026 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2026/01/12/programchamps2026/</guid><description><i><a href="https://ropensci.org/es/blog/2026/01/12/programachamps2026/">Read it in: Español</a>.</i>
&lt;p&gt;We are pleased to announce the opening of a new call for applications for the &lt;strong&gt;rOpenSci Champions Program in Spanish&lt;/strong&gt;, which will begin in 2026. We will be accepting applications beginning in &lt;strong&gt;January 12, 2026&lt;/strong&gt; and until &lt;strong&gt;February 20, 2026&lt;/strong&gt; for both the roles of &lt;strong&gt;Champion&lt;/strong&gt; as well as &lt;strong&gt;Mentor&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;As in the previous cohort, the 2026 program will be developed &lt;strong&gt;entirely in Spanish&lt;/strong&gt; and will have a &lt;strong&gt;regional focus on Latin America&lt;/strong&gt; with the objective of further strengthening the research and open science software in this region.&lt;/p&gt;</description></item><item><title>rOpenSci Code of Conduct Annual Review</title><link>https://ropensci.org/blog/2026/01/07/conduct2025/</link><pubDate>Wed, 07 Jan 2026 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2026/01/07/conduct2025/</guid><description><i><a href="https://ropensci.org/es/blog/2026/01/07/conducta2025/">Read it in: Español</a>.</i>
&lt;p&gt;rOpenSci’s activities and spaces are supported by a &lt;a href="https://ropensci.org/code-of-conduct/"&gt;Code of Conduct&lt;/a&gt;
that applies to all people participating in the rOpenSci community,
including rOpenSci staff and leadership.
It applies to all modes of interaction including GitHub project repositories,
the rOpenSci discussion forum, Slack, Community Calls, Co-working and social sessions, training and mentoring sessions,
and in person at rOpenSci-hosted events, including affiliated social gatherings.
Our Code of Conduct is developed and enforced by a committee including rOpenSci staff and an independent community member.&lt;/p&gt;</description></item><item><title>rOpenSci 2025 Code of Conduct Transparency Report</title><link>https://ropensci.org/blog/2026/01/06/transparencycoc2025/</link><pubDate>Tue, 06 Jan 2026 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2026/01/06/transparencycoc2025/</guid><description><i><a href="https://ropensci.org/es/blog/2026/01/06/transparenciacoc2025/">Read it in: Español</a>.</i>
&lt;h2&gt;
Maintaining Community Trust and Safety
&lt;/h2&gt;&lt;p&gt;The rOpenSci community is supported by our &lt;a href="https://ropensci.org/code-of-conduct"&gt;Code of Conduct&lt;/a&gt;
with a clear description of unacceptable behaviors,
instructions on how to make a report,
and information on how reports are handled.&lt;/p&gt;
&lt;p&gt;We, the Code of Conduct Committee,
are responsible for receiving, investigating, deciding,
enforcing and reporting on all reports of potential violations of our Code.
We are committed to transparency with our community while upholding the privacy
of people who experience or report incidents.&lt;/p&gt;</description></item><item><title>Testing the R-universe build workflow from your own GitHub repository</title><link>https://ropensci.org/blog/2026/01/03/r-universe-workflows/</link><pubDate>Sat, 03 Jan 2026 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2026/01/03/r-universe-workflows/</guid><description>
&lt;p&gt;We refactored the R-universe CI workflows to make it possible to run the exact same workflow from your own GitHub repository. This allows you to test or debug the build and check process on your R package, exactly as it will happen on R-universe, but without actually deploying to &lt;a href="https://r-universe.dev"&gt;https://r-universe.dev&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;The instructions on &lt;a href="https://github.com/r-universe-org/workflows"&gt;r-universe-org/workflows&lt;/a&gt; explain how it works: simply create a file &lt;code&gt;/.github/workflows/r-universe-test.yml&lt;/code&gt; in your R package git repo with the following config:&lt;/p&gt;</description></item><item><title>rOpenSci News Digest, December 2025</title><link>https://ropensci.org/blog/2025/12/18/news-december-2025/</link><pubDate>Thu, 18 Dec 2025 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2025/12/18/news-december-2025/</guid><description>
&lt;!-- Before sending DELETE THE INDEX_CACHE and re-knit! --&gt;
&lt;p&gt;Dear rOpenSci friends, it&amp;rsquo;s time for our monthly news roundup! &lt;!-- blabla --&gt; You can read this post &lt;a href="https://ropensci.org/blog/2025/12/18/news-december-2025"&gt;on our blog&lt;/a&gt;. Now let&amp;rsquo;s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;h3&gt;
rOpenSci at LatinR
&lt;/h3&gt;&lt;p&gt;We proudly continued supporting LatinR as a community partner in 2025. Here we share a list of resources and recordings for the &lt;a href="https://ropensci.org/training/"&gt;tutorials&lt;/a&gt; and &lt;a href="https://ropensci.org/talks/"&gt;talks&lt;/a&gt; delivered by our staff and community memebers at LatinR. Discover more on the &lt;a href="https://www.youtube.com/@LatinR"&gt;LatinR YouTube channel&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Code Hosting Options Beyond GitHub</title><link>https://ropensci.org/blog/2025/12/17/beyond-github/</link><pubDate>Wed, 17 Dec 2025 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2025/12/17/beyond-github/</guid><description>
&lt;p&gt;rOpenSci makes heavy use of GitHub for our projects and services, including &lt;a href="https://github.com/ropensci/software-review/issues?q=sort%3Aupdated-desc%20is%3Aissue%20state%3Aclosed"&gt;software peer-review&lt;/a&gt;.
GitHub is by far the most widely used git or code-hosting platform, and the combination of its popularity and freemium services have made it central to open-source and R communities.
However, for a variety of reasons, some of our community members or potential members may prefer or need to use other platforms.
These reasons may include concerns about being forced into &lt;a href="https://www.techspot.com/news/109040-microsoft-ai-push-tightens-grip-github-after-ceo.html"&gt;Microsoft&amp;rsquo;s AI division&lt;/a&gt;, a desire to support platforms with &lt;a href="https://ziglang.org/news/migrating-from-github-to-codeberg/"&gt;different ownership or business models&lt;/a&gt;, which are based in other countries, or a general desire to support alternatives to avoid the risk of hegemony.&lt;/p&gt;</description></item><item><title>Better Code, Without Any Effort, Without Even AI</title><link>https://ropensci.org/blog/2025/12/15/better-code/</link><pubDate>Mon, 15 Dec 2025 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2025/12/15/better-code/</guid><description>
&lt;p&gt;We are experiencing a programming revolution, with the democratization of artificial intelligence, &lt;em&gt;but&lt;/em&gt; also with the creation and improvement of more traditional software tools to improve your code: local, free, deterministic.&lt;/p&gt;
&lt;p&gt;In this post, we will introduce you to&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&amp;#x1f4e6; &lt;a href="https://lintr.r-lib.org/"&gt;lintr&lt;/a&gt;, by &lt;a href="https://lintr.r-lib.org/authors.html"&gt;Michael Chirico and many others&lt;/a&gt;, an R package that detects many ways to improve your code;&lt;/li&gt;
&lt;li&gt;&amp;#x1f4bb;$ &lt;a href="https://posit-dev.github.io/air/"&gt;Air&lt;/a&gt;, by Lionel Henry and Davis Vaughan, a fast CLI (command-line interface) for formatting R code automatically and almost instantly;&lt;/li&gt;
&lt;li&gt;&amp;#x1f4bb;$ &lt;a href="https://jarl.etiennebacher.com/"&gt;jarl&lt;/a&gt;, by Etienne Bacher, another fast CLI (command-line interface) tool to find and automatically fix lints;&lt;/li&gt;
&lt;li&gt;&amp;#x1f4e6; &lt;a href="https://flir.etiennebacher.com/"&gt;flir&lt;/a&gt;, by Etienne Bacher, an R package to efficiently rewrite patterns of code, either built-in ones or custom ones.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;With these four wonderful tools, you can effortlessly improve your code, your colleagues&amp;rsquo; code&amp;hellip; and even code proposed by AI. With a bit more effort, you might even internalize best practice and write better code from the get go in the future!&lt;/p&gt;</description></item><item><title>How to Assess Usage of your Package</title><link>https://ropensci.org/blog/2025/12/11/package-usage/</link><pubDate>Thu, 11 Dec 2025 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2025/12/11/package-usage/</guid><description>
&lt;p&gt;As a package maintainer, you might want to get some numbers or impressions on the usage of your package for various reasons: getting some confirmation that your work is useful, prioritizing development on specific features of your software, helping justify a request for funding. Don&amp;rsquo;t get your hopes too high: there is no perfect solution nor measure. However, we will share some useful information sources in this post &amp;ndash; many of them already used and displayed by &lt;a href="https://ropensci.org/r-universe"&gt;R-Universe&lt;/a&gt;!&lt;/p&gt;</description></item><item><title>LatinR &lt;- Latinamerican Conference About the Use of R in R&amp;D 2025</title><link>https://ropensci.org/events/latinr-2025/</link><pubDate>Fri, 05 Dec 2025 15:00:00 +0000</pubDate><guid>https://ropensci.org/events/latinr-2025/</guid><description>
&lt;h3&gt;
LatinR 2025 Conference and Tutorials – Registration Open!
&lt;/h3&gt;&lt;p&gt;We’re proud to once again join LatinR as a community partner this year, continuing our commitment to fostering collaboration and open science across Latin America. &lt;a href="https://www.eventbrite.com.ar/e/1939670499679"&gt;Register for the free LatinR 2025 Conference&lt;/a&gt;&lt;/p&gt;
&lt;h2&gt;
Keynotes
&lt;/h2&gt;&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href="https://ropensci.org/author/heather-turner/"&gt;Heather Turner&lt;/a&gt;: &lt;strong&gt;Lowering Barriers to Contributing to R&lt;/strong&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Stephanie Zimmer: &lt;strong&gt;Transforming a team to open-source first.&lt;/strong&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;TRACE-LAC Team. &lt;strong&gt;Lo invisible del código abierto: Lecciones desde el proyecto TRACE-LAC / Epiverso para conectar el desarrollo de software con la salud pública&lt;/strong&gt;&lt;/p&gt;</description></item><item><title>Social Coworking and Office Hours - Getting to know The Carpentries</title><link>https://ropensci.org/events/coworking-2025-12/</link><pubDate>Tue, 02 Dec 2025 15:00:00 +0000</pubDate><guid>https://ropensci.org/events/coworking-2025-12/</guid><description>
&lt;p&gt;&lt;strong&gt;Join us for 2 hours Tuesday December 02, 14:00 Europe Central (13:00 UTC) for
&lt;a href="https://ropensci.org/blog/2023/06/21/coworking/"&gt;Social Coworking + Office Hours&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This month we&amp;rsquo;re focusing on the theme &lt;strong&gt;Getting to know The Carpentries&lt;/strong&gt;
with community host &lt;strong&gt;Angelique Trusler&lt;/strong&gt;. Angelique is passionate about equitable access to data science education and is the Associate Director of Community at The Carpentries.&lt;/p&gt;
&lt;p&gt;These &amp;ldquo;Getting to know&amp;rdquo; themed coworking sessions give us a chance to meet and
learn about other like-minded organizations and communities whom we support,
collaborate with, or generally cheer on!&lt;/p&gt;</description></item><item><title>LatinR 2025 - ¡Miércoles, Git!</title><link>https://ropensci.org/events/latinr25-git/</link><pubDate>Tue, 02 Dec 2025 08:00:00 +0000</pubDate><guid>https://ropensci.org/events/latinr25-git/</guid><description/></item><item><title>rOpenSci News Digest, November 2025</title><link>https://ropensci.org/blog/2025/11/28/news-november-2025/</link><pubDate>Fri, 28 Nov 2025 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2025/11/28/news-november-2025/</guid><description>
&lt;!-- Before sending DELETE THE INDEX_CACHE and re-knit! --&gt;
&lt;p&gt;Dear rOpenSci friends, it&amp;rsquo;s time for our monthly news roundup! &lt;!-- blabla --&gt; You can read this post &lt;a href="https://ropensci.org/blog/2025/11/28/news-november-2025"&gt;on our blog&lt;/a&gt;. Now let&amp;rsquo;s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;h3&gt;
rOpenSci at LatinR
&lt;/h3&gt;&lt;p&gt;We&amp;rsquo;re excited to continue supporting LatinR as a community partner in 2025. &lt;a href="https://www.eventbrite.com.ar/e/1939670499679"&gt;Registration is now open for the free LatinR Conference&lt;/a&gt;, bringing together researchers, developers, and open science advocates from across the region.&lt;/p&gt;</description></item><item><title>uRos2025 - Bucharest</title><link>https://ropensci.org/events/uros2025/</link><pubDate>Wed, 26 Nov 2025 17:00:00 +0000</pubDate><guid>https://ropensci.org/events/uros2025/</guid><description>
&lt;p&gt;&lt;a href="https://r-project.ro/conference2025.html"&gt;uRos2025 (The Use of R in Official Statistics)&lt;/a&gt; will take place in Bucharest, Romania, November 24-26, 2025.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Maëlle will be presenting her tutorial &amp;ldquo;Painlessly Improve Your Git History&amp;rdquo; on November 24.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Maëlle will be presenting her keynote &amp;ldquo;R packages, good vibes only&amp;rdquo; on November 25.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>uRos2025 - Bucharest</title><link>https://ropensci.org/events/uros2025/</link><pubDate>Wed, 26 Nov 2025 17:00:00 +0000</pubDate><guid>https://ropensci.org/events/uros2025/</guid><description>
&lt;p&gt;&lt;a href="https://r-project.ro/conference2025.html"&gt;uRos2025 (The Use of R in Official Statistics)&lt;/a&gt; will take place in Bucharest, Romania, November 24-26, 2025.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Maëlle will be presenting her tutorial &amp;ldquo;Painlessly Improve Your Git History&amp;rdquo; on November 24.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Maëlle will be presenting her keynote &amp;ldquo;R packages, good vibes only&amp;rdquo; on November 25.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>Translating the rOpenSci Dev Guide into Portuguese: Collaboration, Community, Challenges, and Impact</title><link>https://ropensci.org/blog/2025/11/25/translation-devguide-pt/</link><pubDate>Tue, 25 Nov 2025 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2025/11/25/translation-devguide-pt/</guid><description><i><a href="https://ropensci.org/pt/blog/2025/11/25/tradu%C3%A7%C3%A3o-devguide-pt/">Read it in: Português</a>.</i>
&lt;h2&gt;
Introduction
&lt;/h2&gt;&lt;p&gt;rOpenSci curates packages developed in the R programming language and also offers a well-established &lt;a href="https://ropensci.org/software-review"&gt;peer review process&lt;/a&gt; for R packages. To guide this process, rOpenSci created the &lt;strong&gt;rOpenSci Packages: Development, Maintenance, and Peer Review&lt;/strong&gt; guide (also known as the &amp;ldquo;Dev Guide&amp;rdquo;). The guide presents recommended procedures for developing and submitting packages to the rOpenSci collection, clarifying each step and ensuring transparency throughout the process.&lt;/p&gt;
&lt;p&gt;Initially, the Dev Guide was created in &lt;a href="https://devguide.ropensci.org/"&gt;English&lt;/a&gt; and later gained a &lt;a href="https://devguide.ropensci.org/es/index.es.html"&gt;Spanish&lt;/a&gt; version, thanks to a &lt;a href="https://ropensci.org/blog/2024/03/11/devguide-0.9.0/"&gt;community-driven translation effort&lt;/a&gt;. More recently, a group of collaborators worked together to translate the Dev Guide into Portuguese. In this post, we describe how this collaborative translation process unfolded, recognizing that translating resources is one way to contribute to rOpenSci’s mission of fostering a culture of open and reproducible research.&lt;/p&gt;</description></item><item><title>Cancelled Event. Graceful Internet Packages</title><link>https://ropensci.org/commcalls/graceful-internet-packages/</link><pubDate>Thu, 06 Nov 2025 00:00:00 +0000</pubDate><guid>https://ropensci.org/commcalls/graceful-internet-packages/</guid><description>
&lt;h2&gt;
Event Cancelled
&lt;/h2&gt;&lt;p&gt;Unfortunally we have to cancel this community call.&lt;/p&gt;
&lt;p&gt;Thanks so much to those who planned to join. We’ll &lt;strong&gt;share a new date soon&lt;/strong&gt; — stay tuned!&lt;/p&gt;
&lt;h2&gt;
Original Event Description
&lt;/h2&gt;&lt;p&gt;Join us for our next Community Call, “Graceful Internet Packages,” featuring Matthias, Tan, and Salix. In this session, we’ll explore how to design and maintain R packages that interact with online data sources. Our speakers will share practical lessons, examples, and best practices to help R package developers create reliable packages.&lt;/p&gt;</description></item><item><title>Computo - A Journal for Transparent and Reproducible Research in Statistics and Machine Learning</title><link>https://ropensci.org/blog/2025/11/06/computo-journal-reproducible-research-statistics-machine-learning/</link><pubDate>Thu, 06 Nov 2025 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2025/11/06/computo-journal-reproducible-research-statistics-machine-learning/</guid><description>
&lt;div class="float-left"&gt;&lt;figure class="m-0"&gt;&lt;a href="https://computo-journal.org/site/about.html"&gt;&lt;img src="https://computo-journal.org/assets/img/logo_text_vertical.svg"
alt="Computo logo"ZgotmplZ
ZgotmplZ
style=" object-fit: cover; object-position: center; height: 250px; width: 250px; margin-right: 15px"
/&gt; &lt;/a&gt;
&lt;p&gt;
&lt;a href="https://computo-journal.org"&gt;Computo&lt;/a&gt; is a journal promoting methodological, computational, and algorithmic contributions in statistics and machine learning that provide a better understanding of which models or methods are most appropriate to answer specific scientific questions. Computo leverages modern tools in programming and scientific reporting to support more transparent, interactive, and reproducible research outputs. We&amp;rsquo;re excited to introduce Computo to the rOpenSci community as a complementary road to publishing reproducible research alongside rOpenSci&amp;rsquo;s software peer review initiatives.
&lt;/p&gt;</description></item><item><title>Social Coworking and Office Hours - Code Review with rOpenSci</title><link>https://ropensci.org/events/coworking-2025-11/</link><pubDate>Tue, 04 Nov 2025 03:00:00 +0000</pubDate><guid>https://ropensci.org/events/coworking-2025-11/</guid><description>
&lt;p&gt;&lt;strong&gt;Join us for 2 hours Tuesday November 04, 09:00 Australia Western (01:00 UTC) for
&lt;a href="https://ropensci.org/blog/2023/06/21/coworking/"&gt;Social Coworking + Office Hours&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This month we&amp;rsquo;re focusing on the theme &lt;strong&gt;Code Review with rOpenSci&lt;/strong&gt;
with community host &lt;strong&gt;Liz Hare&lt;/strong&gt;, rOpenSci Champion and Software Reviewer,
Dog Genetics Researcher, and accessibility advocate.&lt;/p&gt;
&lt;p&gt;Come for the full 2 hrs or only as long as you need!&lt;/p&gt;
&lt;h3&gt;
Cowork
&lt;/h3&gt;&lt;ul&gt;
&lt;li&gt;Explore resources for Code Review&lt;/li&gt;
&lt;li&gt;Sign up to volunteer to do &lt;a href="https://airtable.com/app8dssb6a7PG6Vwj/shrnfDI2S9uuyxtDw"&gt;software peer-review&lt;/a&gt; at rOpenSci&lt;/li&gt;
&lt;li&gt;Cowork independently on something related to R&lt;/li&gt;
&lt;li&gt;Cowork on whatever you need to get done!&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;
Socialize/Network
&lt;/h3&gt;&lt;ul&gt;
&lt;li&gt;Meet community host, &lt;strong&gt;Liz Hare&lt;/strong&gt;, and discuss Code Review with rOpenSci and which resources are available.&lt;/li&gt;
&lt;li&gt;Meet other R users and rOpenSci staff in Zoom&lt;/li&gt;
&lt;li&gt;Get answers to your questions: Ask hosts or coworkers&lt;/li&gt;
&lt;li&gt;Discuss your work, best practices, or get advice and resources&lt;/li&gt;
&lt;li&gt;Answer other coworkers&amp;rsquo; questions!&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;We host &lt;a href="https://ropensci.org/blog/2023/06/21/coworking/"&gt;Social Coworking + Office Hours&lt;/a&gt;
on the first Tuesday of each month, alternating among timezones to
accommodate different parts of the world.&lt;/p&gt;</description></item><item><title>rOpenSci News Digest, October 2025</title><link>https://ropensci.org/blog/2025/10/24/news-october-2025/</link><pubDate>Fri, 24 Oct 2025 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2025/10/24/news-october-2025/</guid><description>
&lt;!-- Before sending DELETE THE INDEX_CACHE and re-knit! --&gt;
&lt;p&gt;Dear rOpenSci friends, it&amp;rsquo;s time for our monthly news roundup! &lt;!-- blabla --&gt; You can read this post &lt;a href="https://ropensci.org/blog/2025/10/24/news-october-2025"&gt;on our blog&lt;/a&gt;. Now let&amp;rsquo;s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;h3&gt;
2025-11-06 Community call: Graceful Internet Packages
&lt;/h3&gt;&lt;p&gt;Join us for our next Community Call, &lt;a href="https://ropensci.org/commcalls/graceful-internet-packages/"&gt;&amp;ldquo;Graceful Internet Packages&amp;rdquo;&lt;/a&gt;, on Thursday, 06 November 2025 at 15:00 UTC featuring Matthias Grenié, Tan Ho, and Salix Dubois. In this session, we&amp;rsquo;ll explore how to design and maintain R packages that interact with online data sources. Our speakers will share practical lessons, examples, and best practices to help R package developers create reliable packages.&lt;/p&gt;</description></item><item><title>Go for Launch! Packages Shipped to the R-Multiverse</title><link>https://ropensci.org/blog/2025/10/22/packages-multiverse/</link><pubDate>Wed, 22 Oct 2025 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2025/10/22/packages-multiverse/</guid><description><i><a href="https://ropensci.org/es/blog/2025/10/22/paquetes-r-multiverse/">Read it in: Español</a>.</i><i><a href="https://ropensci.org/fr/blog/2025/10/22/paquets-r-multiverse/">Read it in: Français</a>.</i>
&lt;p&gt;Will Landau recently introduced the R-multiverse, &lt;a href="https://ropensci.org/commcalls/r-multiverse/"&gt;a new way to publish R packages&lt;/a&gt;, during an rOpenSci community call.&lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt;
After that event, a &lt;a href="https://ropensci.org/blog/2023/06/21/coworking/"&gt;coworking&lt;/a&gt; session allowed even more discussion between Will, his R-multiverse fellow administrators Jeroen Ooms and Maëlle Salmon, and community members.&lt;/p&gt;
&lt;p&gt;A key mission in that coworking session was to submit packages to the R-multiverse live!
Following the &lt;a href="https://r-multiverse.org/contributors.html"&gt;instructions&lt;/a&gt;, any package maintainer wishing to send their software to the community repository needs to:&lt;/p&gt;</description></item><item><title>Recognition Beyond Blog Post Authors</title><link>https://ropensci.org/blog/2025/10/14/blog-roles/</link><pubDate>Tue, 14 Oct 2025 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2025/10/14/blog-roles/</guid><description><i><a href="https://ropensci.org/es/blog/2025/10/14/reconocimiento_blog/">Read it in: Español</a>.</i><i><a href="https://ropensci.org/fr/blog/2025/10/14/reconnaissance-blog/">Read it in: Français</a>.</i>
&lt;p&gt;Our own dev guide &lt;a href="https://devguide.ropensci.org/maintenance_collaboration.html#attributions"&gt;states&lt;/a&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Be generous with attributions&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Recognizing the diverse forms of &lt;a href="https://contributing.ropensci.org/"&gt;contributions&lt;/a&gt; to our mission is very important to us:
we like thanking &lt;a href="https://ropensci.org/blog/2018/03/16/thanking-reviewers-in-metadata/"&gt;package reviewers&lt;/a&gt; and more generally &lt;a href="https://ropensci.org/blog/2024/11/26/allcontributors/"&gt;all package contributors&lt;/a&gt;, &lt;a href="https://ropensci.org/blog/2025/05/09/ror/"&gt;organizations as well as individuals&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;We have recently extended our efforts to acknowledging the different roles there are when publishing a blog post.&lt;/p&gt;
&lt;h2&gt;
New blog roles: editors, translators, interviewees
&lt;/h2&gt;&lt;p&gt;The metadata of our blog posts now feature:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;who edited the blog post
&lt;ul&gt;
&lt;li&gt;for example, &lt;a href="https://ropensci.org/blog/2025/09/18/markdown-programmatic-parsing/"&gt;Steffi LaZerte edited a recent post&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;who translated the blog post
&lt;ul&gt;
&lt;li&gt;for example, &lt;a href="https://ropensci.org/es/blog/2025/06/23/edicion-multilingue-preguntas-frecuentes/"&gt;Yanina Bellini Saibene translated a post into Spanish&lt;/a&gt;, and &lt;a href="fr/blog/2025/06/23/publication-multilingue-faq/"&gt;Maëlle Salmon translated it into French&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;who was &lt;em&gt;interviewed&lt;/em&gt; for a blog post
&lt;ul&gt;
&lt;li&gt;for example, &lt;a href="https://ropensci.org/blog/2023/03/30/r-universe-stars-3-en/"&gt;Athanasia Mo Mowinckel was interviewed in the Stars of the R-Universe series&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The &amp;ldquo;author page&amp;rdquo; of contributors list their various contributions to the content in the current language (authorships listed first, followed by other roles):&lt;/p&gt;</description></item><item><title>A Primer on Domain Verification</title><link>https://ropensci.org/blog/2025/10/10/verification/</link><pubDate>Fri, 10 Oct 2025 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2025/10/10/verification/</guid><description>
&lt;p&gt;Are you &lt;a href="https://en.wikipedia.org/wiki/The_Wolf_and_the_Seven_Young_Goats"&gt;the mother goat or the wolf&lt;/a&gt;?
Consumers of your online content might care!
Be it on social media or other platforms, your profile can sometimes be &amp;ldquo;verified&amp;rdquo;.
What does it mean? How does one get a green checkmark where it matters?
Here&amp;rsquo;s a primer on domain verification.&lt;/p&gt;
&lt;h2&gt;
A basic verification workflow
&lt;/h2&gt;&lt;p&gt;Say you, Jane Doe, have your resume and a blog on a website, janedoe.com.
You also publish content on another site, for instance Mastodon.
How do readers of Mastodon ensure they&amp;rsquo;re reading content by &amp;ldquo;Jane Doe from janedoe.com&amp;rdquo; and not a malicious impersonator?
Well, you can &lt;em&gt;verify&lt;/em&gt; the domain of janedoe.com on Mastodon.&lt;/p&gt;</description></item><item><title>Big Team Science Conference 2025</title><link>https://ropensci.org/events/btsconf-2025/</link><pubDate>Wed, 08 Oct 2025 18:00:00 +0000</pubDate><guid>https://ropensci.org/events/btsconf-2025/</guid><description>
&lt;p&gt;Liz Hare and Yanina Bellini Saibene will present on Big Team Collaboration on Software Peer Review with rOpenSci at the &lt;a href="https://bigteamscienceconference.github.io"&gt;Big Team Science Conference 2025&lt;/a&gt;. Monday October 6 at 10.30 am UTC.&lt;/p&gt;
&lt;p&gt;The event is online and have a registration model of &amp;ldquo;pay what you can&amp;rdquo;.&lt;/p&gt;
&lt;p&gt;If you will attend let us know!&lt;/p&gt;</description></item><item><title>Social Coworking and Office Hours -- Ship your R package to the R-multiverse!</title><link>https://ropensci.org/events/coworking-2025-10/</link><pubDate>Tue, 07 Oct 2025 18:00:00 +0000</pubDate><guid>https://ropensci.org/events/coworking-2025-10/</guid><description>
&lt;p&gt;&lt;strong&gt;Join us for 2 hours Tuesday October 07, 09:00 Americas Pacific (16:00 UTC) for
&lt;a href="https://ropensci.org/blog/2023/06/21/coworking/"&gt;Social Coworking + Office Hours&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This month we&amp;rsquo;re focusing on the theme
&lt;strong&gt;Ship your R package to the &lt;a href="https://r-multiverse.org"&gt;R-multiverse&lt;/a&gt;!&lt;/strong&gt;
with community host &lt;strong&gt;Will Landau&lt;/strong&gt;, co-creator of R-multiverse and author of
the &lt;a href="https://docs.ropensci.org/targets"&gt;targets&lt;/a&gt; R package,
and &lt;strong&gt;Maëlle Salmon&lt;/strong&gt;, rOpenSci Research Software Engineer and one of the
R-multiverse administrators.&lt;/p&gt;
&lt;p&gt;During this coworking event, participants will learn about submitting packages
to the R-multiverse and will be encouraged to do so during the session
(but regular coworkers are always welcome).&lt;/p&gt;</description></item><item><title>rOpenSci Code of Conduct Committee Templates</title><link>https://ropensci.org/blog/2025/09/30/coc-templates/</link><pubDate>Tue, 30 Sep 2025 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2025/09/30/coc-templates/</guid><description>
&lt;p&gt;At rOpenSci, our Code of Conduct (CoC) committee works to support a healthy, welcoming, and inclusive community. A big part of this work is making sure that the processes we follow are transparent, consistent, and fair. Over the years, we’ve developed a set of templates that guide us through different stages of incident response and reporting.&lt;/p&gt;
&lt;p&gt;We believe these templates may be useful for other communities and projects in open science that are establishing or refining their own CoC processes. Today, we are sharing them with you.&lt;/p&gt;</description></item><item><title>R-multiverse: a new way to publish R packages</title><link>https://ropensci.org/commcalls/r-multiverse/</link><pubDate>Mon, 29 Sep 2025 00:00:00 +0000</pubDate><guid>https://ropensci.org/commcalls/r-multiverse/</guid><description>
&lt;p&gt;R-multiverse is a new dual repository for R packages, based on infrastructure from R-universe and GitHub.
We would like to invite the developer community to contribute packages.&lt;/p&gt;
&lt;p&gt;With R-multiverse, users have a central place for installing packages.
Automated quarterly production snapshots enforce quality.&lt;/p&gt;
&lt;p&gt;Package maintainers retain most of the freedom and flexibility of self-publishing.
Maintainers directly control package releases through GitHub or GitLab.&lt;/p&gt;
&lt;p&gt;R-multiverse originated from the R Consortium Repositories Working Group.
It has transparent governance, and it operates in a collaborative and open way.&lt;/p&gt;</description></item><item><title>rOpenSci News Digest, September 2025</title><link>https://ropensci.org/blog/2025/09/29/news-september-2025/</link><pubDate>Mon, 29 Sep 2025 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2025/09/29/news-september-2025/</guid><description>
&lt;!-- Before sending DELETE THE INDEX_CACHE and re-knit! --&gt;
&lt;p&gt;Dear rOpenSci friends, it&amp;rsquo;s time for our monthly news roundup! &lt;!-- blabla --&gt; You can read this post &lt;a href="https://ropensci.org/blog/2025/09/29/news-september-2025"&gt;on our blog&lt;/a&gt;. Now let&amp;rsquo;s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;h3&gt;
10 quick tips for making your software outlive your job
&lt;/h3&gt;&lt;p&gt;Our community manager Yanina Bellini Saibene participated in the paper &lt;a href="https://arxiv.org/abs/2505.06484"&gt;&amp;ldquo;10 quick tips for making your software outlive your job&amp;rdquo;&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>A Gentle Introduction to Open Science</title><link>https://ropensci.org/blog/2025/09/23/gentle-openscience/</link><pubDate>Tue, 23 Sep 2025 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2025/09/23/gentle-openscience/</guid><description><i><a href="https://ropensci.org/fr/blog/2025/09/23/gentle-openscience/">Read it in: Français</a>.</i>
&lt;figure class="pull-right"&gt;&lt;img src="https://ropensci.org/blog/2025/09/23/gentle-openscience/sunny_and_steffi.jpg"
alt="Sunny and Steffi showing off their R hex stickers!" width="300"&gt;&lt;figcaption&gt;
&lt;p&gt;Sunny and Steffi showing off their R hex stickers!&lt;/p&gt;
&lt;/figcaption&gt;
&lt;/figure&gt;
&lt;p&gt;This summer I had a wonderful time attending the &lt;a href="https://www.sco-soc.ca/"&gt;Society for Canadian Ornithologists&lt;/a&gt; meeting in &lt;a href="https://en.wikipedia.org/wiki/Saskatoon"&gt;Saskatoon&lt;/a&gt;, Canada.
It was super exciting to run into &lt;a href="https://ropensci.org/author/yi-chin-sunny-tseng/"&gt;Sunny Tseng&lt;/a&gt;, rOpenSci Champion and fellow &lt;a href="https://en.wikipedia.org/wiki/Ornithology"&gt;ornithologist&lt;/a&gt;!
It&amp;rsquo;s not often that I am able to run into both types of colleagues (R developers and ornithologists) at the same conference, so I cherish these experiences.&lt;/p&gt;</description></item><item><title>posit::conf(2025) - Atlanta, USA</title><link>https://ropensci.org/events/posit-conf-2025/</link><pubDate>Thu, 18 Sep 2025 15:00:00 +0000</pubDate><guid>https://ropensci.org/events/posit-conf-2025/</guid><description>
&lt;p&gt;September 16-18, 2025 &lt;a href="https://posit.co/conference/"&gt;posit::conf(2025)&lt;/a&gt; will take place at the Hyatt Regency Atlanta (US).&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;rOpenSci will be there!&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href="https://ropensci.org/author/mauro-lepore"&gt;Mauro Lepore&lt;/a&gt; and &lt;a href="https://ropensci.org/author/eric-scott"&gt;Eric Scott&lt;/a&gt; will both present &lt;a href="https://reg.conf.posit.co/flow/posit/positconf25/attendee-portal/page/sessioncatalog/session/1745351143742001aTfb"&gt;lightning talks&lt;/a&gt; on Wednesday, September 17th at 1:00 PM. Mauro will talk about &amp;ldquo;Approaching Positron from RStudio&amp;rdquo;, Eric will talk about &amp;ldquo;Enabling geospatial workflow management with targets: an R package origin story&amp;rdquo;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href="https://ropensci.org/author/will-landau/"&gt;Will Landau&lt;/a&gt; will give his talk &amp;ldquo;R-multiverse: a next-generation R package repository system built on R-universe&amp;rdquo; in the &lt;a href="https://reg.conf.posit.co/flow/posit/positconf25/attendee-portal/page/sessioncatalog/session/1745351601442001aZMp"&gt;session &amp;ldquo;Strengthening the R Ecosystem&amp;rdquo;&lt;/a&gt; Thursday, September 18th at 10:20 AM.&lt;/p&gt;</description></item><item><title>Desarrollo de paquetes para principiantes (capacitación para campeones)</title><link>https://ropensci.org/events/2025-09-18-desarrollo-paquetes-basico/</link><pubDate>Thu, 18 Sep 2025 14:00:00 +0000</pubDate><guid>https://ropensci.org/events/2025-09-18-desarrollo-paquetes-basico/</guid><description/></item><item><title>All the Ways to Programmatically Edit or Parse R Markdown / Quarto Documents</title><link>https://ropensci.org/blog/2025/09/18/markdown-programmatic-parsing/</link><pubDate>Thu, 18 Sep 2025 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2025/09/18/markdown-programmatic-parsing/</guid><description><i><a href="https://ropensci.org/es/blog/2025/09/18/markdown-programatico/">Read it in: Español</a>.</i><i><a href="https://ropensci.org/fr/blog/2025/09/18/markdown-programmatique/">Read it in: Français</a>.</i>
&lt;p&gt;If life gives you a bunch of Markdown files to analyse or edit, do you warm up your regex muscles and get going? How about using more specific tools instead? In this post, we shall give an overview of programmatic ways to parse and edit Markdown files: Markdown, R Markdown, Quarto, Hugo files, you name it.&lt;/p&gt;
&lt;h2&gt;
What is Markdown?
&lt;/h2&gt;&lt;p&gt;Markdown is a (punny, eh) markup language created by John Gruber and Aaron Swartz. Here is an example:&lt;/p&gt;</description></item><item><title>From Surviving to Thriving: A Convening to Reclaim and Sustain Open Science Communities</title><link>https://ropensci.org/blog/2025/09/15/collaboration-communities/</link><pubDate>Mon, 15 Sep 2025 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2025/09/15/collaboration-communities/</guid><description>
&lt;p&gt;Open science has transformed how research is conducted, shared, and reused.
Yet the organisations at the heart of this transformation are often left vulnerable, underfunded, and disconnected from one another.
To move from simply surviving to truly thriving, five leading open science organisations &amp;ndash; &lt;a href="https://carpentries.org/"&gt;The Carpentries&lt;/a&gt;, &lt;a href="https://we-are-ols.org/"&gt;OLS&lt;/a&gt;, &lt;em&gt;rOpenSci&lt;/em&gt;, &lt;a href="https://www.pyopensci.org/"&gt;pyOpenSci&lt;/a&gt;, and &lt;a href="https://prereview.org/"&gt;PREreview&lt;/a&gt; &amp;ndash; are convening to chart a collective path forward.
We are so grateful to The Navigation Fund for supporting this work, and invite our communities to review the &lt;a href="https://commons.datacite.org/doi.org/10.71707/qttn-3j47"&gt;full proposal&lt;/a&gt; online.&lt;/p&gt;</description></item><item><title>Help Us Design a New Git(Hub) Organizational Dashboard</title><link>https://ropensci.org/blog/2025/09/11/repometrics-call-help/</link><pubDate>Thu, 11 Sep 2025 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2025/09/11/repometrics-call-help/</guid><description>
&lt;p&gt;We have developed a prototype dashboard which aims to help organizations maintain complex systems of inter-dependent software components.
Our initial &lt;a href="https://ropensci-review-tools.github.io/repometrics-demo/"&gt;prototype organizational dashboard&lt;/a&gt; provides insights into code contributors, their repositories, and maintenance status and needs.
The prototype dashboard shows data for the three related GitHub organizations, &lt;a href="https://github.com/reconhub"&gt;reconhub&lt;/a&gt;, &lt;a href="https://github.com/epiverse"&gt;epiverse&lt;/a&gt;, and &lt;a href="https://github.com/epiverse-trace"&gt;epiverse-trace&lt;/a&gt;, all of which develop and host open-source software for understanding and analysing epidemics.
We aim to develop the current prototype as a template for adoption and adaptation by other open-source organizations.&lt;/p&gt;</description></item><item><title>Social Coworking and Office Hours -- Improving accessibility in your work</title><link>https://ropensci.org/events/coworking-2025-09/</link><pubDate>Tue, 09 Sep 2025 14:00:00 +0000</pubDate><guid>https://ropensci.org/events/coworking-2025-09/</guid><description>
&lt;!--
```{r}
d &lt;- lubridate::ymd_hms('2025-09-09 14:00:00', tz = 'Europe/Paris')
lubridate::with_tz(d, 'UTC')
lubridate::with_tz(d, 'America/Winnipeg')
```
--&gt;
&lt;p&gt;&lt;strong&gt;Join us for 2 hours Tuesday September 09, 14:00 European Central (12:00 UTC) for
&lt;a href="https://ropensci.org/blog/2023/06/21/coworking/"&gt;Social Coworking + Office Hours&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This month we&amp;rsquo;re focusing on the theme &lt;strong&gt;Improving accessibility in your work&lt;/strong&gt;
(teaching materials, websites, presentations, etc.)
with community host &lt;strong&gt;Silvia Canelón&lt;/strong&gt;, researcher, R educator, and data journalist.
Silvia is passionate about improving accessibility in her own work and in helping others
learn how to do the same.&lt;/p&gt;</description></item><item><title>¡Código hermoso, porque lo valemos! (capacitación para campeones)</title><link>https://ropensci.org/events/2025-09-02-codigo-hermoso/</link><pubDate>Tue, 02 Sep 2025 18:00:00 +0000</pubDate><guid>https://ropensci.org/events/2025-09-02-codigo-hermoso/</guid><description/></item><item><title>rOpenSci Champions Second Cohort: Projects Wrap-Up</title><link>https://ropensci.org/blog/2025/09/02/champions-program-projects-cohort2/</link><pubDate>Tue, 02 Sep 2025 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2025/09/02/champions-program-projects-cohort2/</guid><description>
&lt;p&gt;As we welcome the third cohort of the &lt;a href="https://ropensci.org/champions/"&gt;rOpenSci Champions Program&lt;/a&gt;, our second cohort has now completed the second phase of the program.
In this article, we share each Champion&amp;rsquo;s project, their achievements, and their outreach activities.&lt;/p&gt;
&lt;h2&gt;
Champions&amp;rsquo; Projects
&lt;/h2&gt;&lt;p&gt;In their applications Champions choose to develop a new package or to participate in the review process as authors or reviewers.&lt;/p&gt;
&lt;figure&gt;&lt;img src="https://ropensci.org/blog/2025/09/02/champions-program-projects-cohort2/proyectos.png"
alt="Logos of all the packages developed or improved during the champions program 2023-2024"&gt;
&lt;/figure&gt;
&lt;h3&gt;
New packages
&lt;/h3&gt;&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Andrea Gomez Vargas&lt;/strong&gt;, from Argentina, developed the package &lt;a href="https://soyandrea.github.io/arcenso/"&gt;arcenso&lt;/a&gt;, to provide access to the official data of the national population censuses in Argentina from the National Institute of Statistics and Census - INDEC, and to make this historical census data available, homogenized, and ready to use. Her mentor was &lt;a href="https://ropensci.org/author/luis-verde-arregoitia/"&gt;Luis Verde&lt;/a&gt; from Mexico. You can learn more about the package in &lt;a href="https://ropensci.org/blog/2025/05/15/puentes-comunidades-campeones-ropensci/"&gt;the blog post Andrea wrote about her project and her journey on the program&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>rOpenSci News Digest, August 2025</title><link>https://ropensci.org/blog/2025/08/28/news-august-2025/</link><pubDate>Thu, 28 Aug 2025 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2025/08/28/news-august-2025/</guid><description>
&lt;!-- Before sending DELETE THE INDEX_CACHE and re-knit! --&gt;
&lt;p&gt;Dear rOpenSci friends, it&amp;rsquo;s time for our monthly news roundup! &lt;!-- blabla --&gt; You can read this post &lt;a href="https://ropensci.org/blog/2025/08/28/news-august-2025"&gt;on our blog&lt;/a&gt;. Now let&amp;rsquo;s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;h3&gt;
Community call: &amp;ldquo;R-multiverse: a new way to publish R packages&amp;rdquo;
&lt;/h3&gt;&lt;p&gt;On Monday, 29 September 2025 14:00 UTC, we&amp;rsquo;ll host a &lt;a href="https://ropensci.org/commcalls/r-multiverse/"&gt;community call&lt;/a&gt; about the R-multiverse, starring &lt;a href="https://ropensci.org/author/will-landau"&gt;Will Landau&lt;/a&gt;!&lt;/p&gt;
&lt;p&gt;R-multiverse is a new dual repository for R packages, based on infrastructure from R-universe and GitHub. We would like to invite the developer community to contribute packages.&lt;/p&gt;</description></item><item><title>Exploring Open Science, R Packages, and Research Software Development at the CSIDNet AGM 2025</title><link>https://ropensci.org/blog/2025/08/26/csidnet-agm-2025/</link><pubDate>Tue, 26 Aug 2025 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2025/08/26/csidnet-agm-2025/</guid><description>
&lt;p&gt;The “Climate Sensitive Infectious Disease” (CSID) Network looks to connect a global community of actors contributing towards impactful CSID software tools and establish localized CSID communities that can link existing on-the-ground issues and initiatives to the development and maintenance of CSID tools.&lt;/p&gt;
&lt;p&gt;On July 21, during the &lt;a href="https://csidnet.org/2025-virtual-annual-general-meeting-hub/"&gt;2025 Annual General Meeting of the CSIDNet&lt;/a&gt;, Yanina Bellini Saibene and Samuel Schildhauer co-lead a session titled &lt;strong&gt;“Open Science, R Packages, and Research Software Development”&lt;/strong&gt;.
The session was designed not only to introduce participants to tools and practices in open science with R but also to encourage active reflection and discussion on their own workflows and the challenges they face.&lt;/p&gt;</description></item><item><title>Desarrollando software en comunidad con git (capacitación para campeones)</title><link>https://ropensci.org/events/2025-08-21-git-desarrollo-software/</link><pubDate>Thu, 21 Aug 2025 23:59:00 +0000</pubDate><guid>https://ropensci.org/events/2025-08-21-git-desarrollo-software/</guid><description/></item><item><title>El rol del software de investigación a lo largo del ciclo de vida investigativo</title><link>https://ropensci.org/events/2025-08-20-softwareydatosinvestigacion/</link><pubDate>Wed, 20 Aug 2025 09:00:00 +0000</pubDate><guid>https://ropensci.org/events/2025-08-20-softwareydatosinvestigacion/</guid><description>
&lt;p&gt;El Miércoles 20 de Agosto el tema es &lt;strong&gt;El rol del software de investigación a lo largo del ciclo de vida investigativo&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;Tópicos:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Conceptos y buenas prácticas clave: FAIR4RS (principios FAIR aplicados al software de investigación), sostenibilidad del software. Fuentes de buenas prácticas para la programación, documentación y mantenimiento.&lt;/li&gt;
&lt;li&gt;Planes de Gestión de Software (PGS): cómo crearlos e implementarlos de forma efectiva.&lt;/li&gt;
&lt;li&gt;Software de código abierto.&lt;/li&gt;
&lt;li&gt;Infraestructuras regionales: introducción a herramientas y plataformas de software de investigación comúnmente utilizadas.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Yanina Bellini Saibene participa en la serie de Webinars Software y Datos de investigación donde presenta rOpenSci y como contribuimos al software de investigación abierto.&lt;/p&gt;</description></item><item><title>useR! 2025 - Durham, North Carolina</title><link>https://ropensci.org/events/user-2025/</link><pubDate>Sun, 10 Aug 2025 15:00:00 +0000</pubDate><guid>https://ropensci.org/events/user-2025/</guid><description>
&lt;p&gt;August 1, &lt;a href="https://user2025.r-project.org/program/virtual/"&gt;useR! 2025 Virtual&lt;/a&gt; with &lt;strong&gt;free registration&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;August 08-10, 2025 &lt;a href="https://user2025.r-project.org"&gt;useR! 2025&lt;/a&gt; will take place in Penn Pavilion, Duke University, Durham, North Carolina.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;rOpenSci will be there!&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href="https://ropensci.org/author/yanina-bellini-saibene/"&gt;Yanina Bellini Saibene&lt;/a&gt; will be presenting her keynote &lt;a href="https://user2025.r-project.org/program/in-person/keynotes/yanina-bellini-saibene"&gt;&amp;ldquo;We R Together. How to learn, use and improve a programming language as a community.&amp;rdquo;&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href="https://ropensci.org/author/will-landau/"&gt;Will Landau&lt;/a&gt; will be presenting his keynote &lt;a href="https://user2025.r-project.org/program/in-person/keynotes/will-landau"&gt;&amp;ldquo;Poweful simulation pipelines with {targets}&amp;rdquo;&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href="https://ropensci.org/author/noam-ross/"&gt;Noam Ross&lt;/a&gt; will be presenting &amp;ldquo;Curating a Community of Packages: Lessons from a Decade of rOpenSci Peer Review&amp;rdquo; on Sat, Aug 9, 2025 - 13:00–14:10 (EDT)&lt;/p&gt;</description></item><item><title>Social Coworking and Office Hours - Drawing publication-ready plots using R</title><link>https://ropensci.org/events/coworking-2025-08/</link><pubDate>Tue, 05 Aug 2025 03:00:00 +0000</pubDate><guid>https://ropensci.org/events/coworking-2025-08/</guid><description>
&lt;!--
```{r}
d &lt;- lubridate::ymd_hms('2025-08-05 09:00:00', tz = 'Australia/Perth')
lubridate::with_tz(d, 'UTC')
lubridate::with_tz(d, 'America/Winnipeg')
```
--&gt;
&lt;p&gt;&lt;strong&gt;Join us for 2 hours Tuesday August 05, 09:00 Australian Western (01:00 UTC) for
&lt;a href="https://ropensci.org/blog/2023/06/21/coworking/"&gt;Social Coworking + Office Hours&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This month we&amp;rsquo;re focusing on the theme &lt;strong&gt;Drawing publication-ready plots using R&lt;/strong&gt;
with community host &lt;strong&gt;Emi Tanaka&lt;/strong&gt;, rOpenSci editor,
Applied Statistician, Statistical Data Artist,
and Scientist at the Australian National University.&lt;/p&gt;
&lt;p&gt;Come for the full 2 hrs or only as long as you need!&lt;/p&gt;</description></item><item><title>Learning from Each Other's Journeys: Case Studies from Open Initiatives</title><link>https://ropensci.org/events/ttt-firesidechat-2025/</link><pubDate>Thu, 31 Jul 2025 18:30:00 +0000</pubDate><guid>https://ropensci.org/events/ttt-firesidechat-2025/</guid><description>
&lt;p&gt;Join us for the next seminar in the Fireside Chat Series on Governance in Research and Open Science, co-organised by The Turing Way and the Software Sustainability Institute!&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;When: 31 July 2025&lt;/li&gt;
&lt;li&gt;Time: 18:00–19:30 UTC+1 (UK time)&lt;/li&gt;
&lt;li&gt;Featuring: Aleksandra Nenadic, Chris Holdgraf, &lt;strong&gt;Yanina Bellini Saibene&lt;/strong&gt;, chaired by Yo Yehudi and Arielle Bennett-Lovell.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;For more information and registration, visit: &lt;a href="https://lnkd.in/gk7zbfGW"&gt;https://lnkd.in/gk7zbfGW&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Statistical Computing 2025</title><link>https://ropensci.org/events/statscomputing-2025/</link><pubDate>Wed, 30 Jul 2025 18:00:00 +0000</pubDate><guid>https://ropensci.org/events/statscomputing-2025/</guid><description>
&lt;p&gt;The &lt;a href="https://sysbio.uni-ulm.de/ocs/index.php/statcomp/statcomp2025"&gt;Statistical Computing 2025&lt;/a&gt; conference will take place in Günzburg, Germany, from July 27 to July 30, 2025.&lt;/p&gt;
&lt;p&gt;Noam Ross will attend the event in person and will give the keynote &amp;ldquo;Supporting the Statistical Software Lifecycle: Peer-Review, Publishing, and Sustainability&amp;rdquo;.&lt;/p&gt;
&lt;p&gt;If you are coming, please come to chat!&lt;/p&gt;</description></item><item><title>2025 CSID Network Annual General Meeting</title><link>https://ropensci.org/events/csidnetwork-2025/</link><pubDate>Sat, 26 Jul 2025 18:00:00 +0000</pubDate><guid>https://ropensci.org/events/csidnetwork-2025/</guid><description>
&lt;p&gt;The 2025 &lt;a href="https://csidnet.org"&gt;CSID Network&lt;/a&gt; Annual General Meeting will take place in Thailand from July 20 to July 26, 2025. This event is an opportunity for members of the CSID Network to come together, share knowledge, and discuss the future of the network.&lt;/p&gt;
&lt;p&gt;Yani Bellini Saibene will attend the event in person and will host a session on rOpenSci activities, tools and resources around research open source software, R package development and software peer review.&lt;/p&gt;</description></item><item><title>rOpenSci News Digest, July 2025</title><link>https://ropensci.org/blog/2025/07/23/news-july-2025/</link><pubDate>Wed, 23 Jul 2025 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2025/07/23/news-july-2025/</guid><description>
&lt;!-- Before sending DELETE THE INDEX_CACHE and re-knit! --&gt;
&lt;p&gt;Dear rOpenSci friends, it&amp;rsquo;s time for our monthly news roundup! &lt;!-- blabla --&gt; You can read this post &lt;a href="https://ropensci.org/blog/2025/07/23/news-july-2025"&gt;on our blog&lt;/a&gt;. Now let&amp;rsquo;s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;h3&gt;
Open Science with a Latin American Identity: Meet the New Cohort of the rOpenSci Champions Program
&lt;/h3&gt;&lt;p&gt;We&amp;rsquo;re very excited to introduce the new rOpenSci &lt;a href="https://ropensci.org/champions"&gt;Champions&lt;/a&gt;! This cohort will participate in the program and carry out their work in Spanish, allowing us to continue strengthening the open science and research software development community in this language. We&amp;rsquo;re excited about the projects they&amp;rsquo;ll be developing, which tackle real-world challenges across diverse disciplines and regions of Latin America.&lt;/p&gt;</description></item><item><title>Open Science with a Latin American Identity: Meet the New Cohort of the rOpenSci Champions Program</title><link>https://ropensci.org/blog/2025/07/03/champions-2025/</link><pubDate>Thu, 03 Jul 2025 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2025/07/03/champions-2025/</guid><description><i><a href="https://ropensci.org/es/blog/2025/07/03/champions-2025/">Read it in: Español</a>.</i>
&lt;p&gt;We’re very excited to introduce the new rOpenSci Champions! This cohort will participate in the program and carry out their work in Spanish, allowing us to continue strengthening the open science and research software development community in this language. We’re excited about the projects they’ll be developing, which tackle real-world challenges across diverse disciplines and regions of Latin America.&lt;/p&gt;
&lt;p&gt;We invite you to get to know each of these individuals and the projects they’ll be working on throughout the program.&lt;/p&gt;</description></item><item><title>Social Coworking and Office Hours - Research Software Engineering and R</title><link>https://ropensci.org/events/coworking-2025-07/</link><pubDate>Tue, 01 Jul 2025 18:00:00 +0000</pubDate><guid>https://ropensci.org/events/coworking-2025-07/</guid><description>
&lt;!--
```{r}
d &lt;- lubridate::ymd_hms('2025-07-01 09:00:00', tz = 'America/Vancouver')
lubridate::with_tz(d, 'UTC')
lubridate::with_tz(d, 'America/Winnipeg')
```
--&gt;
&lt;p&gt;&lt;strong&gt;Join us for 2 hours Tuesday July 01, 09:00 Americas Pacific (16:00 UTC) for
&lt;a href="https://ropensci.org/blog/2023/06/21/coworking/"&gt;Social Coworking + Office Hours&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This month we&amp;rsquo;re focusing on the theme &lt;strong&gt;Research Software Engineering and R&lt;/strong&gt;
with community host &lt;strong&gt;Saranjeet Kaur Bhogal&lt;/strong&gt;, passionate advocate for Communities of
Practice, Open Science, and Open Source, as well as Research Software Engineer
at Imperial College London.&lt;/p&gt;</description></item><item><title>rOpenSci News Digest, June 2025</title><link>https://ropensci.org/blog/2025/06/27/news-june-2025/</link><pubDate>Fri, 27 Jun 2025 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2025/06/27/news-june-2025/</guid><description>
&lt;!-- Before sending DELETE THE INDEX_CACHE and re-knit! --&gt;
&lt;p&gt;Dear rOpenSci friends, it&amp;rsquo;s time for our monthly news roundup! &lt;!-- blabla --&gt; You can read this post &lt;a href="https://ropensci.org/blog/2025/06/27/news-may-2025"&gt;on our blog&lt;/a&gt;. Now let&amp;rsquo;s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;h3&gt;
Farewell to software review editor Julia Gustavsen
&lt;/h3&gt;&lt;p&gt;This month we say farewell to Software Peer-Review Editor Julia Gustavsen. Julia has been an essential member of the rOpenSci peer-review team for more than &lt;em&gt;10 years&lt;/em&gt;, since before we had an editorial board, and before we even called it peer review! Julia was one of rOpenSci&amp;rsquo;s original reviewers as we figured out how to transform from a team publishing our in-house developed tools to a broader, community-driven ecosystem. Her early reviews were a model for the careful, helpful, non-confrontational style that has set the tone for our approach. We were lucky to have her join as an editor in 2020. She has expertly guided many authors and reviewers through the peer-review process, served as Editor in Chief, and been a pleasure to have as colleague making the process better, smoother, and more valuable to our community. Thanks Julia for your service!&lt;/p&gt;</description></item><item><title>Announcing New Stats Software Peer Review Editors: Emi Tanaka and Nima Hejazi</title><link>https://ropensci.org/blog/2025/06/25/editors2025/</link><pubDate>Wed, 25 Jun 2025 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2025/06/25/editors2025/</guid><description>
&lt;p&gt;We are excited to welcome Emi Tanaka and Nima Hejazi to our team of &lt;a href="https://ropensci.org/software-review/#editors"&gt;Associate Editors&lt;/a&gt; for rOpenSci &lt;a href="https://ropensci.org/software-review/"&gt;Stats Software Peer Review&lt;/a&gt;.
They join Laura DeCicco, Julia Gustavsen, Jouni Helske, Toby Hocking, Rebecca Killick, Anna Krystalli, Mauro Lepore, Noam Ross, Maëlle Salmon, Emily Riederer, Adam Sparks, Beatriz Milz, Margaret Siple and Jeff Hollister.
Since 2015, rOpenSci has operated a thorough and collaborative software peer review system.
Our &lt;a href="https://devguide.ropensci.org/editorguide.html"&gt;editorial team&lt;/a&gt; oversees the entire review process — conducting initial checks, selecting reviewers, and guiding the review until the package is approved for inclusion in rOpenSci’s &lt;a href="https://ropensci.org/packages/"&gt;software suite&lt;/a&gt;.
Given the wide range and number of packages we receive, having a team of editors with diverse and complementary expertise is essential.
Emi brings her experiences in experimental design, mixed-effects models and data visualisation, while Nima contributes his expertise in causal inference, de-biased machine learning, and semi-parametric and computational statistics.&lt;/p&gt;</description></item><item><title>¡Miércoles, Git! Manejo de errores en Git y no morir en el intento</title><link>https://ropensci.org/events/r-ba-r-ladies-santa-rosa-2025/</link><pubDate>Tue, 24 Jun 2025 14:45:00 +0000</pubDate><guid>https://ropensci.org/events/r-ba-r-ladies-santa-rosa-2025/</guid><description>
&lt;p&gt;Maëlle Salmon will be teaching a workshop about Git in Spanish in an event hosted by R en Buenos Aires and R-Ladies+ Santa Rosa.&lt;/p&gt;
&lt;p&gt;You can find more information about the event on Meetup: &lt;a href="https://www.meetup.com/rbuenosaires/events/308338205/"&gt;R en Buenos Aires&lt;/a&gt; and &lt;a href="https://www.meetup.com/es/rladies-santa-rosa/events/308395195/"&gt;R-Ladie+ Santa Rosa&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Organizers: Andrea Gomez Vargas and Ariana Bardauil 🙏&lt;/p&gt;</description></item><item><title>Multilingual Publishing: Frequently Asked Questions</title><link>https://ropensci.org/blog/2025/06/23/translation-faq/</link><pubDate>Mon, 23 Jun 2025 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2025/06/23/translation-faq/</guid><description><i><a href="https://ropensci.org/es/blog/2025/06/23/edicion-multilingue-preguntas-frecuentes/">Read it in: Español</a>.</i><i><a href="https://ropensci.org/fr/blog/2025/06/23/publication-multilingue-faq/">Read it in: Français</a>.</i>
&lt;p&gt;As we&amp;rsquo;ve &lt;a href="https://ropensci.org/multilingual-publishing"&gt;said before&lt;/a&gt;, we believe that publishing multilingual resources can lower the barrier to access to knowledge, help democratize access to quality resources and increase the possibilities of contributing to software and open science projects.
Our ongoing efforts at &lt;a href="https://ropensci.org/multilingual-publishing"&gt;multilingual publishing&lt;/a&gt; are crucial work for rOpenSci&amp;rsquo;s &lt;a href="https://ropensci.org/about"&gt;mission&lt;/a&gt;.
When discussing this project at &lt;a href="https://ropensci.org/talks-papers/"&gt;conferences&lt;/a&gt; and &lt;a href="https://ropensci.org/commcalls/nov2023-multilingual/"&gt;elsewhere&lt;/a&gt;, we start an important conversation with people less familiar with such projects or unfamiliar with our specific &lt;a href="https://translationguide.ropensci.org/"&gt;workflows&lt;/a&gt;.
In this post, we summarize frequently asked questions, and our best answers to them (even better formulated than in the heat of a post-talk Q&amp;amp;A session &amp;#x1f601;).&lt;/p&gt;</description></item><item><title>Git, un gentil 'push' vers une meilleure maîtrise</title><link>https://ropensci.org/events/stateofther-2025/</link><pubDate>Fri, 20 Jun 2025 14:45:00 +0000</pubDate><guid>https://ropensci.org/events/stateofther-2025/</guid><description>
&lt;p&gt;Maëlle Salmon will be teaching a workshop about Git during an Happy R session, organized by StateoftheR (an INRAE MathNum scientific network) at Campus AgroParisSaclay (Université Paris-Saclay, AgroParisTech, INRAE), Palaiseau, France.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://stateofther.netlify.app/#upcoming_workshops"&gt;You can find more information about the event in their website and calendar&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Automated generation of a taxonomic classification document</title><link>https://ropensci.org/usecases/automated-generation-of-a-taxonomic-classification-document/</link><pubDate>Fri, 13 Jun 2025 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/automated-generation-of-a-taxonomic-classification-document/</guid><description>
&lt;h3&gt;
rOpenSci package or resource used
&lt;/h3&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/taxlist"&gt;taxlist&lt;/a&gt;, &lt;a href="https://docs.ropensci.org/targets"&gt;targets&lt;/a&gt;&lt;/p&gt;
&lt;h3&gt;
What did you do?
&lt;/h3&gt;&lt;p&gt;I import a taxonomic database of &lt;a href="https://pteridogroup.github.io/"&gt;ferns and lycophytes&lt;/a&gt; in &lt;a href="https://docs.ropensci.org/dwctaxon/articles/what-is-dwc.html"&gt;Darwin Core format&lt;/a&gt; into R, then use &lt;a href="https://github.com/ropensci/taxlist"&gt;taxlist&lt;/a&gt; to help convert it into a human-readable classification. The code is automated using &lt;a href="https://github.com/ropensci/targets"&gt;targets&lt;/a&gt; and runs as a cron-job once per day. Whenever the source data are updated, the workflow runs and pushes the final result (a Markdown file) to GitHub and updates the website.&lt;/p&gt;</description></item><item><title>New Mentoring Team, Same Open Science Spirit</title><link>https://ropensci.org/blog/2025/06/05/mentors-2025/</link><pubDate>Thu, 05 Jun 2025 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2025/06/05/mentors-2025/</guid><description><i><a href="https://ropensci.org/es/blog/2025/06/05/mentors-2025/">Read it in: Español</a>.</i>
&lt;p&gt;We are excited to introduce the new team of mentors for the rOpenSci Champions Program! This year, we have ten very talented individuals, all from Latin America, who bring a unique combination of experience, enthusiasm, and commitment to open science. Some of them have already been part of the program in previous editions, either as mentors or Champions, and today, they return to continue strengthening this community.&lt;/p&gt;
&lt;p&gt;Our new mentors come from a wide variety of disciplines and are active voices within the R community in the region, participating in different groups and initiatives. With their support, our new group of Champions will not only develop their projects but also grow as leaders in open science and research software development.&lt;/p&gt;</description></item><item><title>Social Coworking and Office Hours - Getting to know the DSLC</title><link>https://ropensci.org/events/coworking-2025-06/</link><pubDate>Tue, 03 Jun 2025 14:00:00 +0000</pubDate><guid>https://ropensci.org/events/coworking-2025-06/</guid><description>
&lt;!--
```{r}
d &lt;- lubridate::ymd_hms('2025-06-03 14:00:00', tz = 'Europe/Paris')
lubridate::with_tz(d, 'UTC')
lubridate::with_tz(d, 'America/Winnipeg')
```
--&gt;
&lt;p&gt;&lt;strong&gt;Join us for 2 hours Tuesday June 03, 14:00 European Central (12:00 UTC) for
&lt;a href="https://ropensci.org/blog/2023/06/21/coworking/"&gt;Social Coworking + Office Hours&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This month we&amp;rsquo;re focusing on the theme &lt;strong&gt;Getting to know the DSLC&lt;/strong&gt;
with community host &lt;strong&gt;Jon Harmon&lt;/strong&gt;. Jon is an rOpenSci package maintainer, R/shiny software engineer,
and the Executive Director of the Data Science Learning Community.&lt;/p&gt;
&lt;p&gt;These &amp;ldquo;Getting to know&amp;rdquo; themed coworking sessions give us a chance to meet and
learn about other like-minded organizations and communities whom we support,
collaborate with, or generally cheer on!&lt;/p&gt;</description></item><item><title>Why Small Git Commits Matter (and How to Make Them!)</title><link>https://ropensci.org/events/r-ladies-plus-rome-2025/</link><pubDate>Tue, 27 May 2025 11:00:00 +0000</pubDate><guid>https://ropensci.org/events/r-ladies-plus-rome-2025/</guid><description>
&lt;p&gt;A confident git practice can change the work life of anyone writing code or prose with R, resulting in a useful history to browse or go back to, the possibility to work in parallel on different aspects, etc. In particular, it is best git practice to create small, atomic commits with informative messages. Why? And how?&lt;/p&gt;
&lt;p&gt;Learn three reasons why small git commits are worth it. Discover how to realistically create them, without too much hassle. Find out how the saperlipopette R package can help you practice safely, and share your own git tips and questions!&lt;/p&gt;</description></item><item><title>rOpenSci News Digest, May 2025</title><link>https://ropensci.org/blog/2025/05/26/news-may-2025/</link><pubDate>Mon, 26 May 2025 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2025/05/26/news-may-2025/</guid><description>
&lt;!-- Before sending DELETE THE INDEX_CACHE and re-knit! --&gt;
&lt;p&gt;Dear rOpenSci friends, it&amp;rsquo;s time for our monthly news roundup! &lt;!-- blabla --&gt; You can read this post &lt;a href="https://ropensci.org/blog/2025/05/26/news-may-2025"&gt;on our blog&lt;/a&gt;. Now let&amp;rsquo;s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;h3&gt;
Help us maintain {pkgcheck}!
&lt;/h3&gt;&lt;p&gt;You might know of &lt;a href="https://docs.ropensci.org/pkgcheck/"&gt;our {pkgcheck} system&lt;/a&gt; used for our automated package checks, and for your own stand-alone and &lt;a href="https://github.com/ropensci-review-tools/pkgcheck-action"&gt;GitHub-action usage&lt;/a&gt; on any package. We are seeking co-maintainers for the {pkgcheck} package which powers this system. In particular, we have several &lt;a href="https://github.com/ropensci-review-tools/pkgcheck/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22%3Amag%3A%20Check%20Idea%22"&gt;ideas for additional checks in current repo issues&lt;/a&gt;. We would like volunteers to attend an online get-together for us to coach you on how to implement new checks, and so to help you get involved in maintaining and further developing our checking system. If you&amp;rsquo;re interested and already part of the rOpenSci Slack, please join our dedicated &lt;code&gt;#pkgcheck&lt;/code&gt; channel, otherwise email &lt;code&gt;mark@ropensci.org&lt;/code&gt;.&lt;/p&gt;</description></item><item><title>11èmes Rencontres R</title><link>https://ropensci.org/events/rencontres-r-2025/</link><pubDate>Wed, 21 May 2025 21:30:00 +0000</pubDate><guid>https://ropensci.org/events/rencontres-r-2025/</guid><description>
&lt;p&gt;rOpenSci will be present at the 11èmes Rencontres R. Maëlle Salmon will be presenting the talk &amp;ldquo;Comment traduire vos documents efficacement dans R&amp;rdquo; on May the 20th in the 4:10pm session.&lt;/p&gt;</description></item><item><title>Bridges and Communities. My Journey as an rOpenSci Champion</title><link>https://ropensci.org/blog/2025/05/15/puentes-comunidades-campeones-ropensci/</link><pubDate>Thu, 15 May 2025 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2025/05/15/puentes-comunidades-campeones-ropensci/</guid><description><i><a href="https://ropensci.org/es/blog/2025/05/15/puentes-comunidades-campeones-ropensci/">Read it in: Español</a>.</i>
&lt;p&gt;To be part of the &lt;a href="https://champions-program.ropensci.org"&gt;rOpenSci Champions program&lt;/a&gt; has been an experience of &lt;strong&gt;professional growth and an opportunity to contribute to the rOpenSci community&lt;/strong&gt;. I learned about R package development while working on a tool to facilitate access to census data from Argentina.&lt;/p&gt;
&lt;p&gt;In this blog, I want to share how this experience &lt;em&gt;opened new opportunities, connected me with people and communities, and led me to be part of new projects, strengthening my commitment to open access to data&lt;/em&gt;.&lt;/p&gt;</description></item><item><title>Hack your way to a good git history</title><link>https://ropensci.org/events/rug-salt-lake-city-2025/</link><pubDate>Tue, 13 May 2025 19:00:00 +0000</pubDate><guid>https://ropensci.org/events/rug-salt-lake-city-2025/</guid><description>
&lt;p&gt;A confident git practice can change the work life of anyone writing code or prose with R, resulting in a useful history to browse or go back to, the possibility to work in parallel on different aspects, etc. In particular, it is best git practice to create small, atomic commits with informative messages. Why? And how?&lt;/p&gt;
&lt;p&gt;Learn three reasons why small git commits are worth it. Discover how to realistically create them, without too much hassle. Find out how the saperlipopette R package can help you practice safely, and share your own git tips and questions!&lt;/p&gt;</description></item><item><title>Roaringly Acknowledge Organizations with ROR IDs in DESCRIPTION</title><link>https://ropensci.org/blog/2025/05/09/ror/</link><pubDate>Fri, 09 May 2025 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2025/05/09/ror/</guid><description>
&lt;p&gt;A few years ago, the R community started using &lt;a href="https://orcid.org/"&gt;ORCID&lt;/a&gt; (&amp;ldquo;Open Researcher and Contributor ID&amp;rdquo;) to persistently and uniquely identify individual authors of packages in DESCRIPTION.
The idea is the following: you enter authors&amp;rsquo; ORCID as a specially named comment in their &lt;code&gt;person()&lt;/code&gt; object.
For instance I can be represented by:&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-r" data-lang="r"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nf"&gt;person&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s"&gt;&amp;#34;Maëlle&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s"&gt;&amp;#34;Salmon&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s"&gt;&amp;#34;maelle@ropensci.org&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;role&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nf"&gt;c&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s"&gt;&amp;#34;cre&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s"&gt;&amp;#34;aut&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;),&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="n"&gt;comment&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nf"&gt;c&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;ORCID&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="s"&gt;&amp;#34;0000-0002-2815-0399&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;))&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Although anyone could use your ORCID, maliciously or inadvertently&lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt;, you definitely benefit from using your ORCID in your work.
In the case of R packages, CRAN pages and pkgdown websites feature a pretty icon linking to your ORCID profile that in turn can link to your favorite online presence.
Recognition! Personal branding!&lt;/p&gt;</description></item><item><title>Explorando o pacote pcir para análise de conflictos e consenso</title><link>https://ropensci.org/events/champions-program-r-ladies-floripa-2025/</link><pubDate>Wed, 07 May 2025 23:00:00 +0000</pubDate><guid>https://ropensci.org/events/champions-program-r-ladies-floripa-2025/</guid><description>
&lt;p&gt;Francesca Palmeira is a Bióloga com experiência em Ecologia Aplicada, Modelagem Ecológica e Biologia da Conservação. Pesquisa os impactos das mudanças ambientais na distribuição de espécies e na dinâmica ecológica, com atuação nos biomas Mata Atlântica, Cerrado e Amazônia. Trabalha com R, BUGS e ferramentas open source para análise e visualização de dados. Fundadora da analisaR, presta consultoria para empresas, governo e terceiro setor. É mentora na RLadies Ribeirão Preto, incentivando a inclusão no uso de R. É produtora e roteirista do Baile das Onças, programa da Rádio UFSCar sobre a presença da onça na música brasileira.&lt;/p&gt;</description></item><item><title>Non-Government Career Paths for U.S. Federal Data Scientists</title><link>https://ropensci.org/events/datasci-careers-feds/</link><pubDate>Wed, 07 May 2025 02:00:00 +0000</pubDate><guid>https://ropensci.org/events/datasci-careers-feds/</guid><description>
&lt;!--
```{r}
d &lt;- lubridate::ymd_hms('2025-05-06 20:30:00', tz = 'EDT')
lubridate::with_tz(d, 'UTC')
```
--&gt;
&lt;p&gt;rOpenSci and &lt;a href="https://openscapes.org/"&gt;Openscapes&lt;/a&gt; are lucky to have as members many U.S. federal employees
who enrich our work and community. In a time of great uncertainty for so many
government workers, we want to support our members who are considering their
next career steps.&lt;/p&gt;
&lt;p&gt;Join us on Tuesday, May 6 at 8:30PM EDT for a discussion and networking event
for and with current and former U.S. federal government data scientists.&lt;/p&gt;</description></item><item><title>Social Coworking and Office Hours - Writing functions in R</title><link>https://ropensci.org/events/coworking-2025-05/</link><pubDate>Tue, 06 May 2025 03:00:00 +0000</pubDate><guid>https://ropensci.org/events/coworking-2025-05/</guid><description>
&lt;!--
```{r}
d &lt;- lubridate::ymd_hms('2025-05-06 09:00:00', tz = 'Australia/Perth')
lubridate::with_tz(d, 'UTC')
lubridate::with_tz(d, 'America/Winnipeg')
```
--&gt;
&lt;p&gt;&lt;strong&gt;Join us for 2 hours Tuesday May 06, 09:00 Australian Western (01:00 UTC) for
&lt;a href="https://ropensci.org/blog/2023/06/21/coworking/"&gt;Social Coworking + Office Hours&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This month we&amp;rsquo;re focusing on the theme &lt;strong&gt;Writing functions in R&lt;/strong&gt;
with community host &lt;strong&gt;Nick Tierney&lt;/strong&gt;, maintainer for numerous R packages including
several with rOpenSci.&lt;/p&gt;
&lt;p&gt;Come for the full 2 hrs or only as long as you need!&lt;/p&gt;</description></item><item><title>Enseñando datos espaciales vectoriales en R</title><link>https://ropensci.org/usecases/ense-ando-datos-espaciales-vectoriales-en-r/</link><pubDate>Mon, 28 Apr 2025 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/ense-ando-datos-espaciales-vectoriales-en-r/</guid><description>
&lt;h3&gt;
Paquete o recurso rOpenSci utilizado
&lt;/h3&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/rnaturalearth"&gt;rnaturalearth&lt;/a&gt;&lt;/p&gt;
&lt;h3&gt;
¿Qué hiciste?
&lt;/h3&gt;&lt;p&gt;Desarrolle una serie de lecciones para introducir a las personas al manejo de datos espaciales vectoriales en R y utilizo rnaturalearth en esa leccion para proveer limites politicos de paises.&lt;/p&gt;
&lt;h3&gt;
URL o fragmento de código para su caso de uso
&lt;/h3&gt;&lt;p&gt;&lt;a href="https://yabellini.github.io/AgriRemoteSensing/02-r-spatial.html"&gt;https://yabellini.github.io/AgriRemoteSensing/02-r-spatial.html&lt;/a&gt;&lt;/p&gt;
&lt;h3&gt;
Idioma del caso práctico
&lt;/h3&gt;&lt;p&gt;Español&lt;/p&gt;
&lt;h3&gt;
Imagen
&lt;/h3&gt;&lt;p&gt;&lt;img src="https://yabellini.github.io/AgriRemoteSensing/02-r-spatial_files/figure-html/unnamed-chunk-8-1.png" alt=""&gt;&lt;/p&gt;
&lt;h3&gt;
Texto alternativo
&lt;/h3&gt;&lt;p&gt;Mapa hecho con R.&lt;/p&gt;
&lt;h3&gt;
Sector
&lt;/h3&gt;&lt;p&gt;Academico&lt;/p&gt;</description></item><item><title>rOpenSci News Digest, April 2025</title><link>https://ropensci.org/blog/2025/04/28/news-april-2025/</link><pubDate>Mon, 28 Apr 2025 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2025/04/28/news-april-2025/</guid><description>
&lt;!-- Before sending DELETE THE INDEX_CACHE and re-knit! --&gt;
&lt;p&gt;Dear rOpenSci friends, it&amp;rsquo;s time for our monthly news roundup! &lt;!-- blabla --&gt; You can read this post &lt;a href="https://ropensci.org/blog/2025/04/28/news-april-2025"&gt;on our blog&lt;/a&gt;. Now let&amp;rsquo;s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;h3&gt;
Event: Career Paths for U.S. Federal Data Scientists
&lt;/h3&gt;&lt;p&gt;rOpenSci and Openscapes are lucky to have as members many U.S. federal employees who enrich our work and community. In a time of great uncertainty for so many government workers, we want to support our members who are considering their next career steps.&lt;/p&gt;</description></item><item><title>Multilingual support for Teaching Tech Together Book</title><link>https://ropensci.org/usecases/multilingual-support-for-teaching-tech-together-book/</link><pubDate>Fri, 25 Apr 2025 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/multilingual-support-for-teaching-tech-together-book/</guid><description>
&lt;h3&gt;
rOpenSci package or resource used
&lt;/h3&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/babelquarto"&gt;babelquarto&lt;/a&gt;&lt;/p&gt;
&lt;h3&gt;
What did you do?
&lt;/h3&gt;&lt;p&gt;We use babelquarto to add multilingual support to the second edition of the book Teaching Tech Together (Enseñar tenología en comunidad, in Spanish).&lt;br&gt;
This second edition is still a work in progress, and we start with the text in Spanish and then translate to English. Book website: &lt;a href="https://teachingtechtogether.netlify.app/"&gt;https://teachingtechtogether.netlify.app/&lt;/a&gt;&lt;/p&gt;
&lt;h3&gt;
URL or code snippet for your use case
&lt;/h3&gt;&lt;p&gt;&lt;a href="https://github.com/yabellini/t3es2ed"&gt;https://github.com/yabellini/t3es2ed&lt;/a&gt;&lt;/p&gt;
&lt;h3&gt;
Image
&lt;/h3&gt;&lt;figure&gt;&lt;img src="https://ropensci.org/usecases/multilingual-support-for-teaching-tech-together-book/use-case-1.png"
alt="Homepage of our babelquarto book"&gt;
&lt;/figure&gt;
&lt;h3&gt;
Sector
&lt;/h3&gt;&lt;p&gt;Other&lt;/p&gt;</description></item><item><title>Desarrollando Paquetes de R con ayuda de rOpenSci</title><link>https://ropensci.org/events/rladies-champions-2025/</link><pubDate>Wed, 23 Apr 2025 21:00:00 +0000</pubDate><guid>https://ropensci.org/events/rladies-champions-2025/</guid><description>
&lt;p&gt;El miércoles 23 de abril a las 17hs (AR), &lt;a href=""&gt;R-Ladies Resistencia-Corrientes&lt;/a&gt; y &lt;a href=""&gt;R-Ladies Santa Rosa&lt;/a&gt; se unen para un meetup imperdible con el apoyo de rOpenSci y el RConsortium.&lt;/p&gt;
&lt;p&gt;Nuestra invitada especial será Yani Bellini Saibene, Community Manager de rOpenSci, quien nos hablará sobre herramientas clave para desarrollar paquetes de R y cómo participar en el Programa de Campeones de rOpenSci. ¡Una oportunidad única para recibir entrenamiento y mentoría personalizada para llevar tu idea de paquete al siguiente nivel!&lt;/p&gt;</description></item><item><title>Clinica de Aplicación para el Programa de Campeon(e|a)s de rOpenSci</title><link>https://ropensci.org/events/clinica-champions-2025-04/</link><pubDate>Tue, 15 Apr 2025 15:00:00 +0000</pubDate><guid>https://ropensci.org/events/clinica-champions-2025-04/</guid><description>
&lt;!--
```{r}
d &lt;- lubridate::ymd_hms('2025-04-01 09:00:00', tz = 'America/Vancouver')
lubridate::with_tz(d, 'UTC')
lubridate::with_tz(d, 'America/Winnipeg')
```
--&gt;
&lt;p&gt;&lt;strong&gt;Sumate a esta clinica de aplicaciones durante 2 horas el martes, 15 de abril, 10 AM UTC-3 (Argentina, Uruguay) / 13:00 UTC&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;Este mes tenemos una sesión especial que funciona como una Clínica de Aplicación para
el Programa Campeon(e|a)s con nuestra community manager, &lt;strong&gt;Yanina Bellini Saibene&lt;/strong&gt;,
como co-anfitriona.&lt;/p&gt;
&lt;p&gt;¡Ven a las 2 horas completas o sólo el tiempo que necesites!&lt;/p&gt;</description></item><item><title>Un meilleur historique Git, sans difficulté</title><link>https://ropensci.org/events/r-ladies-paris-2025/</link><pubDate>Fri, 11 Apr 2025 11:00:00 +0000</pubDate><guid>https://ropensci.org/events/r-ladies-paris-2025/</guid><description>
&lt;p&gt;Une pratique confiante de git peut changer la vie professionnelle de quiconque écrit du code ou de la prose avec R. Avec git on obtient un historique utile à parcourir ou à consulter, la possibilité de travailler en parallèle sur différents aspects, etc. En particulier, un conseil récurrent sur git est de créer de petits commits atomiques avec des messages informatifs. Pourquoi ? Et comment ?
Apprenez trois avantages des petits commits git. Découvrez comment les créer de manière réaliste, sans trop de tracas. Découvrez comment le paquet R saperlipopette peut vous aider à vous entraîner en toute sécurité, et partagez vos propres conseils et questions sur git !&lt;/p&gt;</description></item><item><title>eDNAjoint: a Modeling Tool for Environmental DNA Data</title><link>https://ropensci.org/blog/2025/04/10/ednajoint-a-modeling-tool-for-environmental-dna-data/</link><pubDate>Thu, 10 Apr 2025 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2025/04/10/ednajoint-a-modeling-tool-for-environmental-dna-data/</guid><description>
&lt;div class="float-left"&gt;&lt;figure class="m-0"&gt;&lt;img src="eDNAjoint_logo.png"
alt="eDNAjoint logo"ZgotmplZ
ZgotmplZ
ZgotmplZ
style=" object-fit: cover; object-position: center; height: 250px; width: 400; margin-right: 15px"
/&gt;
&lt;p&gt;
In 2024, the version 0.2 of &lt;a href="https://docs.ropensci.org/eDNAjoint/"&gt;eDNAjoint&lt;/a&gt; was &lt;a href="https://github.com/ropensci/software-review/issues/642#issuecomment-2328265662"&gt;peer-reviewed&lt;/a&gt; and approved by rOpenSci, and a few months later, a &lt;a href="https://doi.org/10.1111/2041-210X.70000"&gt;manuscript about the package&lt;/a&gt; was published in &lt;em&gt;Methods in Ecology and Evolution&lt;/em&gt;. Reflecting on my experience, I detail below the reasons why I wrote &lt;strong&gt;eDNAjoint&lt;/strong&gt;, provide an example of how to use the package, and make a call to action for anyone interested in helping me expand the package further.
&lt;/p&gt;</description></item><item><title>Supporting rOpenSci Mentors with Practical Tools</title><link>https://ropensci.org/blog/2025/04/08/mentoring-tools/</link><pubDate>Tue, 08 Apr 2025 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2025/04/08/mentoring-tools/</guid><description><i><a href="https://ropensci.org/es/blog/2025/04/08/mentoring-tools/">Read it in: Español</a>.</i>
&lt;p&gt;Mentoring is at the heart of what makes rOpenSci a community.
Our members mentoring each other at different moments:
when someone new joins and needs help navigating the community;
when a member steps into a new role, like a reviewer for our software peer review,
or project, like become the maintainer of a package, and could use some guidance;
during everyday interactions, where people share tips and advise with each other;
when someone shares an idea and gets constructive and friendly feedback
or when a more experienced member helps others grow into leadership roles.
Each of these moments is a chance to share what you know, build connections, and keep the community strong.&lt;/p&gt;</description></item><item><title>Social Coworking and Office Hours - R you joking? Silly R packages for April Fools' day</title><link>https://ropensci.org/events/coworking-2025-04/</link><pubDate>Tue, 01 Apr 2025 18:00:00 +0000</pubDate><guid>https://ropensci.org/events/coworking-2025-04/</guid><description>
&lt;!--
```{r}
d &lt;- lubridate::ymd_hms('2025-04-01 09:00:00', tz = 'America/Vancouver')
lubridate::with_tz(d, 'UTC')
lubridate::with_tz(d, 'America/Winnipeg')
```
--&gt;
&lt;p&gt;&lt;strong&gt;Join us for 2 hours Tuesday April 01, 09:00 Americas Pacific (16:00 UTC) for
&lt;a href="https://ropensci.org/blog/2023/06/21/coworking/"&gt;Social Coworking + Office Hours&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This month we&amp;rsquo;re focusing on the theme &lt;strong&gt;R you joking? Silly R packages for &lt;a href="https://en.wikipedia.org/wiki/April_Fools%27_Day"&gt;April Fools&amp;rsquo; day&lt;/a&gt;&lt;/strong&gt;
with &lt;strong&gt;Steffi LaZerte&lt;/strong&gt;, rOpenSci Community Assistant.&lt;/p&gt;
&lt;p&gt;Come for the full 2 hrs or only as long as you need!&lt;/p&gt;
&lt;h3&gt;
Cowork
&lt;/h3&gt;&lt;ul&gt;
&lt;li&gt;Explore silly R packages&lt;/li&gt;
&lt;li&gt;Have fun designing your own silly R package&lt;/li&gt;
&lt;li&gt;Cowork independently on work related to R
&lt;ul&gt;
&lt;li&gt;Plan out that package you’ve always wanted to create&lt;/li&gt;
&lt;li&gt;Work on packages that tend to be neglected&lt;/li&gt;
&lt;li&gt;What ever you need to get done!&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;
Socialize/Network
&lt;/h3&gt;&lt;ul&gt;
&lt;li&gt;Meet rOpenSci Community Assistant, &lt;strong&gt;Steffi LaZerte&lt;/strong&gt;, and discuss your favourite silly R package!&lt;/li&gt;
&lt;li&gt;Meet other R users and rOpenSci staff in Zoom&lt;/li&gt;
&lt;li&gt;Get answers to your questions
&lt;ul&gt;
&lt;li&gt;Ask your hosts&lt;/li&gt;
&lt;li&gt;Ask your fellow coworkers&lt;/li&gt;
&lt;li&gt;Discuss your work, best practices, or get advice and resources&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Answer other coworkers&amp;rsquo; questions!&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;We host
&lt;a href="https://ropensci.org/blog/2023/06/21/coworking/"&gt;Social Coworking + Office Hours&lt;/a&gt;
on the first Tuesday of each month, alternating among timezones to
accommodate different parts of the world.&lt;/p&gt;</description></item><item><title>rOpenSci News Digest, March 2025</title><link>https://ropensci.org/blog/2025/03/27/news-march-2025/</link><pubDate>Thu, 27 Mar 2025 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2025/03/27/news-march-2025/</guid><description>
&lt;!-- Before sending DELETE THE INDEX_CACHE and re-knit! --&gt;
&lt;p&gt;Dear rOpenSci friends, it&amp;rsquo;s time for our monthly news roundup! &lt;!-- blabla --&gt; You can read this post &lt;a href="https://ropensci.org/blog/2025/03/27/news-march-2025"&gt;on our blog&lt;/a&gt;. Now let&amp;rsquo;s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;h3&gt;
rOpenSci Champions Program 2025 In Spanish: Apply before April 30th!
&lt;/h3&gt;&lt;p&gt;We have great news: The call for applications to be part of the new cohort of our 2025 Program is now open! And for the first time it will be in Spanish!&lt;/p&gt;</description></item><item><title>Advancing Open-Source Scientific Software with Peer Review</title><link>https://ropensci.org/events/rug-princeton-2025/</link><pubDate>Wed, 26 Mar 2025 17:15:00 +0000</pubDate><guid>https://ropensci.org/events/rug-princeton-2025/</guid><description>
&lt;p&gt;For a decade, rOpenSci has made software peer-review the linchpin of their project of improving open-software scientific software, using it as a mechanism to develop technology, skills, collaboration, and building a diverse and inclusive community of researchers and developers.&lt;/p&gt;
&lt;p&gt;Noam Ross will discuss lessons learned and how researchers can participate in a gain from working with the rOpenSci community.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://www.addevent.com/event/Pr24477696"&gt;In this post is more information about the event.&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Software Review, Perspectives from an Academic</title><link>https://ropensci.org/blog/2025/03/25/r-package-review/</link><pubDate>Tue, 25 Mar 2025 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2025/03/25/r-package-review/</guid><description><i><a href="https://ropensci.org/es/blog/2025/03/25/r-package-review/">Read it in: Español</a>.</i>
&lt;blockquote&gt;
&lt;p&gt;There&amp;rsquo;s an R package for this&amp;hellip; right?&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2&gt;
How it started
&lt;/h2&gt;&lt;p&gt;My journey in creating my first R package all started when I received an email from a colleague who was working with archived soil samples that were collected prior to the advent of GPS technology.
These samples were georeferenced using the Manitoba Original Survey Legal Descriptions, which originate from the &lt;a href="https://en.wikipedia.org/wiki/Dominion_Land_Survey"&gt;Dominion Land Survey system&lt;/a&gt;, introduced in the late 19th century to organize the European settlement and colonization of Western Canada.
I was asked by my colleague if there was an R package that could locate these samples so they could be plotted on a map.
There wasn&amp;rsquo;t.
The data was publicly available so I wrote a short script that searched the data set for the legal land description and returned the coordinates.
This morphed into a series of functions, which eventually turned into a package!
And thanks to the encouragement of the rOpenSci community assistant, &lt;a href="https://ropensci.org/author/steffi-lazerte/"&gt;Steffi LaZerte&lt;/a&gt;, I submitted my package for peer review.
That is how &lt;a href="https://github.com/ropensci/mbquartR/"&gt;&lt;code&gt;mbquartR&lt;/code&gt;&lt;/a&gt; was born.&lt;/p&gt;</description></item><item><title>Translating course to Spanish and French</title><link>https://ropensci.org/usecases/translating-course-to-spanish-and-french/</link><pubDate>Tue, 25 Mar 2025 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/translating-course-to-spanish-and-french/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/babelquarto/"&gt;babelquarto&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;Translated course content from English to Spanish and French to support rollout of an analytical framework and tools (created for that framework) in around 20 countries.&lt;/p&gt;
&lt;p&gt;Initially, the idea was to have a face to face training with participants. The packages were developed in R, it made sense to use Quarto to create the teaching material. It was combining the reading, code, inputs in the same GitHub folder. That make it easy to share and maintain.&lt;/p&gt;</description></item><item><title>rOpenSci Participation at NumFOCUS’ DISC Unconf</title><link>https://ropensci.org/blog/2025/03/24/numfocus-unconf/</link><pubDate>Mon, 24 Mar 2025 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2025/03/24/numfocus-unconf/</guid><description>
&lt;p&gt;&lt;a href="https://numfocus.github.io/disc-unconference-2025/"&gt;The NumFOCUS Diversity &amp;amp; Inclusion in Scientific Computing (“DISC”) Unconf&lt;/a&gt; took place as a hybrid event in São Paulo, Brazil, from March 14 to 16, 2025.
Our community manager, &lt;a href="https://ropensci.org/author/yanina-bellini-saibene/"&gt;Yanina Bellini Saibene&lt;/a&gt;, and rOpenSci Champions, &lt;a href="https://ropensci.org/author/andrea-gomez-vargas/"&gt;Andrea Gomez Vargas&lt;/a&gt; and &lt;a href="https://ropensci.org/author/liz-hare/"&gt;Liz Hare&lt;/a&gt;, participated.
In this short post we report on our experience at and around the unconference.&lt;/p&gt;
&lt;p&gt;Prior to the meeting in São Paulo, participants met online to get to know each other and present their ideas for projects.
Ten projects were selected and then developed during the weekend.&lt;/p&gt;</description></item><item><title>rOpenSci Code of Conduct Annual Review</title><link>https://ropensci.org/blog/2025/03/21/conduct2024/</link><pubDate>Fri, 21 Mar 2025 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2025/03/21/conduct2024/</guid><description>
&lt;p&gt;rOpenSci’s activities and spaces are supported by a &lt;a href="https://ropensci.org/code-of-conduct/"&gt;Code of Conduct&lt;/a&gt;
that applies to all people participating in the rOpenSci community,
including rOpenSci staff and leadership.
It applies to all modes of interaction including GitHub project repositories,
the rOpenSci discussion forum, Slack, Community Calls, Co-working and social sessions,
and in person at rOpenSci-hosted events, including affiliated social gatherings.
Our Code of Conduct is developed and enforced by a committee including rOpenSci staff and an independent community member.&lt;/p&gt;</description></item><item><title>Template To Handle Code of Conduct Incidents Reports</title><link>https://ropensci.org/blog/2025/03/20/coc-incident-template/</link><pubDate>Thu, 20 Mar 2025 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2025/03/20/coc-incident-template/</guid><description>
&lt;p&gt;Handling reported incidents related to a Code of Conduct (CoC) is a complex and delicate task. Managing reports timely and with care is crucial for maintaining a healthy and inclusive community.&lt;/p&gt;
&lt;p&gt;To assist with this process we’ve developed a template, based on the work of the &lt;a href="https://rconf.gitlab.io/userknowledgebase/main/code-of-conduct-response-team-documents.html"&gt;useR! 2021 CoC Team&lt;/a&gt;, designed specifically for analyzing &lt;a href="https://ropensci.org/code-of-conduct/"&gt;rOpenSci&amp;rsquo;s CoC&lt;/a&gt; incident reports. This template aims to provide a structured approach for assessing and addressing reports, ensuring that each report is reviewed with consistency.&lt;/p&gt;</description></item><item><title>NumFOCUS’ DISC Unconf</title><link>https://ropensci.org/events/disc-unconf-2025/</link><pubDate>Sun, 16 Mar 2025 21:30:00 +0000</pubDate><guid>https://ropensci.org/events/disc-unconf-2025/</guid><description>
&lt;p&gt;Our community manager, Yanina Bellini Saibene, and rOpenSci Champions, Andrea Gomez Vargas and Liz Hare, participated.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://ropensci.org/blog/2025/03/24/numfocus-unconf/"&gt;In this blog post, you can read about their experience at the event&lt;/a&gt;&lt;/p&gt;</description></item><item><title>rOpenSci Champions Program 2025: In Spanish!</title><link>https://ropensci.org/blog/2025/03/10/champeons-latin-america/</link><pubDate>Mon, 10 Mar 2025 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2025/03/10/champeons-latin-america/</guid><description><i><a href="https://ropensci.org/es/blog/2025/03/10/campeones-america-latina/">Read it in: Español</a>.</i>
&lt;p&gt;We have great news: The call for applications to be part of the new cohort of our 2025 Program is now open! And for the first time it will be in Spanish!&lt;/p&gt;
&lt;p&gt;Our program seeks to identify, recognize and reward people who are leaders in an open science community, research software engineering and the R programming community.&lt;/p&gt;
&lt;p&gt;This year&amp;rsquo;s program is focused on people from Latin America and for the first time will be conducted entirely in Spanish. The main goal is to foster sustainable research software as a pillar of Open Science in Latin America through capacity and community building.&lt;/p&gt;</description></item><item><title>Coworking Mini-Hackathon for First-Time Contributors!</title><link>https://ropensci.org/events/coworking-2025-03/</link><pubDate>Tue, 04 Mar 2025 15:00:00 +0000</pubDate><guid>https://ropensci.org/events/coworking-2025-03/</guid><description>
&lt;!--
```{r}
d &lt;- lubridate::ymd_hms('2025-03-04 14:00:00', tz = 'Europe/Paris')
lubridate::with_tz(d, 'UTC')
lubridate::with_tz(d, 'America/Winnipeg')
```
--&gt;
&lt;p&gt;&lt;strong&gt;Join us for 2 hours Tuesday March 04, 14:00 European Central (13:00 UTC) for
a special coworking event.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This is the second of two &lt;strong&gt;mini hackathons&lt;/strong&gt; we&amp;rsquo;ll be hosting to &lt;strong&gt;&lt;a href="https://ropensci.org/blog/2025/01/21/coworking-hackathons/#mini-hackathons"&gt;Support First Time
Contributors to Open Source Software&lt;/a&gt;&lt;/strong&gt;.
If you&amp;rsquo;re curious about contributing to Open Source Software, and would like
some support to get started, this event is for you!&lt;/p&gt;</description></item><item><title>Combining with Population Density Rasters with OSM data in R with {sf}, {osmextract} and {ggplot2}</title><link>https://ropensci.org/usecases/combining-with-population-density-rasters-with-osm-data-in-r-with-sf-osmextract-and-ggplot2/</link><pubDate>Sat, 01 Mar 2025 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/combining-with-population-density-rasters-with-osm-data-in-r-with-sf-osmextract-and-ggplot2/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/osmextract"&gt;osmextract&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;&lt;img src="https://ropensci.org/usecases/combining-with-population-density-rasters-with-osm-data-in-r-with-sf-osmextract-and-ggplot2/image.jpg" alt="osm_packages_5|375x500"&gt;&lt;/p&gt;
&lt;h3&gt;
Combining with Population Density Raster Dataset with OSM maps
&lt;/h3&gt;&lt;p&gt;The population raster data is sourced from &lt;em&gt;Global High-Resolution Annual Population Grids (2000-2023), v1&lt;/em&gt; by &lt;strong&gt;Ciesin, Center for International Earth Science Information Network, Columbia University&lt;/strong&gt; &lt;a href="https://zenodo.org/records/11179644"&gt;(CIESIN, 2024)&lt;/a&gt;. This dataset provides high-resolution population estimates globally, integrating census and administrative data with geospatial modeling to refine population distributions. The data, maintained by &lt;strong&gt;NASA’s Socioeconomic Data and Applications Center (SEDAC)&lt;/strong&gt;, is valuable for demographic analysis, urban planning, and environmental studies. The full dataset and documentation are available on &lt;a href="https://zenodo.org/records/11179644"&gt;Zenodo&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Visualizing Highways, Toll Booths with {ggplot2} in R with {osmextract}</title><link>https://ropensci.org/usecases/visualizing-highways-toll-booths-with-ggplot2-in-r-with-osmextract/</link><pubDate>Sat, 01 Mar 2025 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/visualizing-highways-toll-booths-with-ggplot2-in-r-with-osmextract/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/osmextract"&gt;osmextract&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;&lt;img src="https://ropensci.org/usecases/visualizing-highways-toll-booths-with-ggplot2-in-r-with-osmextract/highways.jpg" alt="osm_packages_6|400x500"&gt;&lt;/p&gt;
&lt;p&gt;This code chunk demonstrates the process of downloading geospatial data for the state of Haryana in India and performing some basic preprocessing. First, it uses the &lt;code&gt;osmextract&lt;/code&gt; package to download points, lines, and polygon data from OpenStreetMap for Haryana using the &lt;code&gt;oe_get()&lt;/code&gt; function. Then, the code fetches the district-wise boundary map for Haryana using the &lt;code&gt;geodata::gadm()&lt;/code&gt; function to retrieve administrative boundaries, which are converted into simple features (&lt;code&gt;sf&lt;/code&gt;) objects using the &lt;code&gt;sf&lt;/code&gt; package. Lastly, the overall state boundary map for Haryana is retrieved similarly and cleaned up.&lt;/p&gt;</description></item><item><title>Better documentation for R-universe!</title><link>https://ropensci.org/blog/2025/02/28/r-universe-docs-launch/</link><pubDate>Fri, 28 Feb 2025 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2025/02/28/r-universe-docs-launch/</guid><description>
&lt;p&gt;Since the initial launch in 2021, our &lt;a href="https://r-universe.dev"&gt;R-universe&lt;/a&gt; platform has steadily grown into a comprehensive infrastructure for publishing and discovering R material.
As functionality keeps evolving and community adoption increases, we felt the need for a central documentation point.&lt;/p&gt;
&lt;p&gt;New features and developments are generally discussed in the &lt;a href="https://github.com/r-universe-org/help/issues"&gt;issue tracker&lt;/a&gt; or &lt;a href="https://github.com/r-universe-org/help/discussions"&gt;discussion board&lt;/a&gt;, and sometimes on the &lt;a href="https://ropensci.org/technotes/"&gt;rOpenSci blog&lt;/a&gt;.
Technical details can be found in the README files and source code of the respective repositories under &lt;a href="https://github.com/r-universe-org/"&gt;r-universe-org&lt;/a&gt; that contain all the workflows, actions, and server code (the R-universe system is entirely open source).
This fragmentation can make it difficult to find up-to-date information, especially for new users.&lt;/p&gt;</description></item><item><title>rOpenSci News Digest, February 2025</title><link>https://ropensci.org/blog/2025/02/27/news-february-2025/</link><pubDate>Thu, 27 Feb 2025 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2025/02/27/news-february-2025/</guid><description>
&lt;!-- Before sending DELETE THE INDEX_CACHE and re-knit! --&gt;
&lt;p&gt;Dear rOpenSci friends, it&amp;rsquo;s time for our monthly news roundup!&lt;/p&gt;
&lt;!-- blabla --&gt;
&lt;p&gt;You can read this post &lt;a href="https://ropensci.org/blog/2025/02/27/news-february-2025"&gt;on our blog&lt;/a&gt;.
Now let&amp;rsquo;s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;h3&gt;
Open Science and Open Source only with Diversity, Equity, Inclusion, and Accessibility
&lt;/h3&gt;&lt;p&gt;Including all of humanity is and always will be at the heart of open science.
Read more about our mission in our &lt;a href="https://ropensci.org/blog/2025/02/05/no-science-without-deia/"&gt;blog post&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>METAR analysis for flight conditions</title><link>https://ropensci.org/usecases/metar-analysis-for-flight-conditions/</link><pubDate>Thu, 20 Feb 2025 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/metar-analysis-for-flight-conditions/</guid><description>
&lt;p&gt;Reporting on behalf of &lt;a href="https://github.com/jhchou"&gt;Joseph Chou&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
rOpenSci package or resource used
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/riem"&gt;riem&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;Use case example: developed an R Shiny app that allows interactive analysis of 20+ years of hourly METAR data of flight conditions by time of day and month at multiple airports, including:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;VFR / MVFR / IFR / LIFR category&lt;/li&gt;
&lt;li&gt;winds, gusts, crosswinds (based on best available runway)&lt;/li&gt;
&lt;li&gt;visibility and ceilings&lt;/li&gt;
&lt;li&gt;temperatures&lt;/li&gt;
&lt;li&gt;prevailing winds&lt;/li&gt;
&lt;li&gt;customizable personal minimums&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Deployed using &lt;code&gt;shinylive&lt;/code&gt; so can be served as a static webpage from GitHub Pages, running under web assembly (WASM) in the client browser. Additional airports pretty easy to add (but not by users, unless I make the GitHub page public and accept pull requests).&lt;/p&gt;</description></item><item><title>The Dynamic Relationship of Forks with their Upstream Repository</title><link>https://ropensci.org/blog/2025/02/20/forks-upstream-relationship/</link><pubDate>Thu, 20 Feb 2025 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2025/02/20/forks-upstream-relationship/</guid><description>
&lt;h2&gt;
Context setting
&lt;/h2&gt;&lt;p&gt;rOpenSci organizes &lt;a href="https://ropensci.org/coworking/"&gt;monthly co-working hours&lt;/a&gt; on a variety of topics.
But the constant is the quality of the discussion that ensues and the renewed energy that comes from it.&lt;/p&gt;
&lt;p&gt;The November coworking session welcomed Stefanie Butland from &lt;a href="https://www.openscapes.org/"&gt;Openscapes&lt;/a&gt; as a co-host.
She shared Openscapes&amp;rsquo; approach of &lt;a href="https://docs.google.com/presentation/d/1aL0TVFM7xxzTCJoE3tEArDE32wh59wkmBCy6Vcmwvy4/"&gt;&amp;ldquo;Forking as a worldview&amp;rdquo;&lt;/a&gt;.
Forks in the open-source software world refer to copies of an existing open-source project that add their own changes on top of the original codebase.
Openscapes is extending this classic software development interpretation to an even more open philosophy of encouraging people to take anything that works to new places.
Things like the value of sharing, reusing, and remixing of &lt;em&gt;how we work&lt;/em&gt;, in addition to the work itself.
Stefanie invited participants to share their experiences in forking to adapt or build on existing projects, and we came back to some practical challenges of forking.&lt;/p&gt;</description></item><item><title>Open Science and Open Source only with Diversity, Equity, Inclusion, and Accessibility</title><link>https://ropensci.org/blog/2025/02/05/no-science-without-deia/</link><pubDate>Wed, 05 Feb 2025 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2025/02/05/no-science-without-deia/</guid><description><i><a href="https://ropensci.org/es/blog/2025/02/05/no-ciencia-sin-deia/">Read it in: Español</a>.</i>
&lt;p&gt;At rOpenSci, our mission is to&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;foster a culture that values open and reproducible research using shared data and reusable software&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;and we achieve this through&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;creating social infrastructure through a welcoming and diverse community&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;We feel it is a time to reiterate and clarify why this is and what it means.&lt;/p&gt;
&lt;p&gt;The open in open source and open science means more than how we share code or data.
It means knocking down the barriers to participation so that it is open and accessible to all,
that everyone can join in the benefits and joys of science, and removing our blinders to the humanity of those we previously missed.&lt;/p&gt;</description></item><item><title>Coworking Mini-Hackathon for First-Time Contributors!</title><link>https://ropensci.org/events/coworking-2025-02/</link><pubDate>Tue, 04 Feb 2025 03:00:00 +0000</pubDate><guid>https://ropensci.org/events/coworking-2025-02/</guid><description>
&lt;!--
```{r}
d &lt;- lubridate::ymd_hms('2025-02-04 09:00:00', tz = 'Australia/Perth')
lubridate::with_tz(d, 'UTC')
lubridate::with_tz(d, 'America/Winnipeg')
```
--&gt;
&lt;p&gt;&lt;strong&gt;Join us for 2 hours Tuesday February 04, 09:00 Australian Western (01:00 UTC) for
a special coworking event.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This is the first of two &lt;strong&gt;mini hackathons&lt;/strong&gt; we&amp;rsquo;ll be hosting to &lt;strong&gt;&lt;a href="https://ropensci.org/blog/2025/01/21/coworking-hackathons/#mini-hackathons"&gt;Support First Time
Contributors to Open Source Software&lt;/a&gt;&lt;/strong&gt;.
If you&amp;rsquo;re curious about contributing to Open Source Software, and would like
some support to get started, this event is for you!&lt;/p&gt;</description></item><item><title>Advancing Research with Open Science and Collaborative Communities</title><link>https://ropensci.org/events/brandon-university-2025/</link><pubDate>Fri, 31 Jan 2025 21:30:00 +0000</pubDate><guid>https://ropensci.org/events/brandon-university-2025/</guid><description>
&lt;p&gt;Yanina will be talking about Advancing Research with Open Science and Collaborative Communities at Brandon University Science Seminar Friday Jan 31 at 2:30 (Central; GMT-6)&lt;/p&gt;
&lt;p&gt;This talk will be accessible by zoom and all are welcome to attend. Details can be found at &lt;a href="https://www.brandonu.ca/science/seminar-series/"&gt;https://www.brandonu.ca/science/seminar-series/&lt;/a&gt;&lt;/p&gt;</description></item><item><title>rOpenSci News Digest, January 2025</title><link>https://ropensci.org/blog/2025/01/27/news-january-2025/</link><pubDate>Mon, 27 Jan 2025 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2025/01/27/news-january-2025/</guid><description>
&lt;!-- Before sending DELETE THE INDEX_CACHE and re-knit! --&gt;
&lt;p&gt;Dear rOpenSci friends, it&amp;rsquo;s time for our monthly news roundup!&lt;/p&gt;
&lt;!-- blabla --&gt;
&lt;p&gt;You can read this post &lt;a href="https://ropensci.org/blog/2025/01/27/news-january-2025"&gt;on our blog&lt;/a&gt;.
Now let&amp;rsquo;s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;h3&gt;
rOpenSci 2024 Highlights and what comes next in 2025
&lt;/h3&gt;&lt;p&gt;In this blog post, the rOpenSci Team shares the highlights of 2024 and what come next in 2025. &lt;a href="https://ropensci.org/blog/2025/01/22/year-in-review-2024/"&gt;Read the full story&lt;/a&gt; for details about our project&amp;rsquo;s progress and activities, from R-Universe, our software peer review system, to the champions program and the multilingual project to the great work of our community.
We are excited to continue building an open science for all in 2025.&lt;/p&gt;</description></item><item><title>Coworking Mini-Hackathon for First-Time Contributors</title><link>https://ropensci.org/blog/2025/01/24/coworking-hackathons/</link><pubDate>Fri, 24 Jan 2025 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2025/01/24/coworking-hackathons/</guid><description>
&lt;p&gt;This week we had a wonderful community call, &lt;a href="https://ropensci.org/commcalls/first-time-contributor/"&gt;From Novice to Contributor: Making and Supporting First-Time Contributions to FOSS&lt;/a&gt;, where Sunny Tseng, Pascal Burkhard, and Yaoxiang Li shared with us their experiences with, and advice for, first time contributors, with the excellent moderation of &lt;a href="https://ropensci.org/author/hugo-gruson/"&gt;Hugo Gruson&lt;/a&gt;.
This was a perfect start to our &lt;a href="https://ropensci.org/blog/2024/10/22/first-time-contributions/"&gt;special series of activities&lt;/a&gt; to support first time contributors to Open Source Software.&lt;/p&gt;
&lt;p&gt;Our next two activities, Coworking Mini-Hackathons for First-Time Contributors, will take place &lt;strong&gt;&lt;a href="https://ropensci.org/events/coworking-2025-02/"&gt;February 4th 2025 1-3 UTC&lt;/a&gt;&lt;/strong&gt; and &lt;strong&gt;&lt;a href="https://ropensci.org/events/coworking-2025-03/"&gt;March 4th 2025 13-15 UTC&lt;/a&gt;&lt;/strong&gt; (see below for details), but first, let&amp;rsquo;s review what we learned from this Community Call.&lt;/p&gt;</description></item><item><title>rOpenSci 2024 Highlights</title><link>https://ropensci.org/blog/2025/01/22/year-in-review-2024/</link><pubDate>Wed, 22 Jan 2025 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2025/01/22/year-in-review-2024/</guid><description>
&lt;p&gt;In 2024, we remained committed to open science and open source software.
We continued to build a welcoming and
inclusive community, through innovation and collaboration.&lt;/p&gt;
&lt;p&gt;Here are the highlights of the year:&lt;/p&gt;
&lt;h2&gt;
R-Universe
&lt;/h2&gt;&lt;p&gt;R-Universe, rOpenSci&amp;rsquo;s platform for finding and publishing R packages,
saw major advancements in 2024,
making it an increasingly useful and trusted resource for the wider R community.&lt;/p&gt;
&lt;p&gt;Some of the highlights of our work have included a big rewrite of the &lt;a href="https://r-universe.dev"&gt;web frontend&lt;/a&gt;
and search engine to serve faster, beautiful, informative webpages, and
search through tens of thousands &lt;a href="https://r-universe.dev/packages"&gt;packages&lt;/a&gt;,
&lt;a href="https://r-universe.dev/articles"&gt;articles&lt;/a&gt; and &lt;a href="https://r-universe.dev/datasets"&gt;datasets&lt;/a&gt;.
On the build side we added support for new tools like Rust and Quarto,
and improved the process of building binaries for WebAssembly and Apple Silicon.&lt;/p&gt;</description></item><item><title>From Novice to Contributor: Making and Supporting First-Time Contributions to FOSS</title><link>https://ropensci.org/commcalls/first-time-contributor/</link><pubDate>Mon, 20 Jan 2025 00:00:00 +0000</pubDate><guid>https://ropensci.org/commcalls/first-time-contributor/</guid><description>
&lt;p&gt;Contributing to open source can be very rewarding, but also incredibly intimidating.
When we asked about first time contributions on the rOpenSci Slack,
people recalled the challenges and mistakes they made,
but mostly how much they learned from and enjoyed that experience.&lt;/p&gt;
&lt;p&gt;In this community call moderated by Hugo Gruson, our speaker,
Yaoxiang Li will discus the importance of tests with respect to first-time contributions, and share best practices and advanced techniques for supercharging
R package quality with testthat, Pascal Burkhard will discuss the basic git
skills that can help to make a first contribution, and Sunny Tseng will share
practical advice for making first contributions, common challenges and how to
overcome them.&lt;/p&gt;</description></item><item><title>rOpenSci 2024 Code of Conduct Transparency Report</title><link>https://ropensci.org/blog/2025/01/20/transparencycoc2024/</link><pubDate>Mon, 20 Jan 2025 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2025/01/20/transparencycoc2024/</guid><description>
&lt;h2&gt;
Maintaining Community Trust and Safety
&lt;/h2&gt;&lt;p&gt;The rOpenSci community is supported by our &lt;a href="https://ropensci.org/code-of-conduct"&gt;Code of Conduct&lt;/a&gt;
with a clear description of unacceptable behaviors,
instructions on how to make a report,
and information on how reports are handled.
We, the Code of Conduct Committee,
are responsible for receiving, investigating, deciding,
enforcing and reporting on all reports of potential violations of our Code.
We are committed to transparency with our community while upholding the privacy
of people who experience or report incidents.&lt;/p&gt;</description></item><item><title>Social Coworking and Office Hours - Working with Parquet in R</title><link>https://ropensci.org/events/coworking-2025-01/</link><pubDate>Tue, 14 Jan 2025 15:00:00 +0000</pubDate><guid>https://ropensci.org/events/coworking-2025-01/</guid><description>
&lt;!--
```{r}
d &lt;- lubridate::ymd_hms('2025-01-14 14:00:00', tz = 'Europe/Paris')
lubridate::with_tz(d, 'UTC')
lubridate::with_tz(d, 'America/Winnipeg')
```
--&gt;
&lt;p&gt;&lt;strong&gt;Join us for 2 hours Tuesday January 14, 14:00 European Central (13:00 UTC) for
&lt;a href="https://ropensci.org/blog/2023/06/21/coworking/"&gt;Social Coworking + Office Hours&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This month we&amp;rsquo;re focusing on the theme &lt;strong&gt;Working with Parquet in R&lt;/strong&gt;
with community host &lt;strong&gt;Rainer M Krug&lt;/strong&gt;, Researcher at the University of Zürich,
active in &lt;a href="https://www.ipbes.net/"&gt;IPBES&lt;/a&gt; data management, and Parquet enthusiast!&lt;/p&gt;
&lt;p&gt;Come for the full 2 hrs or only as long as you need!&lt;/p&gt;</description></item><item><title>R en Red. Arcenso, Oportunidades y Comunidad</title><link>https://ropensci.org/events/arcenso-2024/</link><pubDate>Fri, 20 Dec 2024 22:00:00 +0000</pubDate><guid>https://ropensci.org/events/arcenso-2024/</guid><description>
&lt;p&gt;📦 Andrea Gomez Vargas &amp;amp; Emanuel Ciardullo nos cuentan todo sobre el paquete de gestión de
datos censales ARcenso que están desarrollando como parte del programa de campeonas y
campeones de rOpenSci.&lt;/p&gt;
&lt;p&gt;📅 20 de Diciembre de 2024, 18:00 hs (Argentina)&lt;/p&gt;
&lt;p&gt;&lt;a href="https://www.meetup.com/es-ES/renbaires/events/304935866/"&gt;Inscripcion al Evento en Meetup&lt;/a&gt;&lt;/p&gt;</description></item><item><title>rOpenSci News Digest, December 2024</title><link>https://ropensci.org/blog/2024/12/19/news-december-2024/</link><pubDate>Thu, 19 Dec 2024 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2024/12/19/news-december-2024/</guid><description>
&lt;!-- Before sending DELETE THE INDEX_CACHE and re-knit! --&gt;
&lt;p&gt;Dear rOpenSci friends, it&amp;rsquo;s time for our monthly news roundup!&lt;/p&gt;
&lt;!-- blabla --&gt;
&lt;p&gt;You can read this post &lt;a href="https://ropensci.org/blog/2024/12/19/news-december-2024"&gt;on our blog&lt;/a&gt;.
Now let&amp;rsquo;s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;h3&gt;
R-Universe Named an R Consortium Top-Level Project
&lt;/h3&gt;&lt;p&gt;We are excited to announce that &lt;a href="https://ropensci.org/r-universe/"&gt;R-Universe&lt;/a&gt;
has been &lt;a href="https://r-consortium.org/posts/r-universe-named-r-consortiums-newest-top-level-project/"&gt;named&lt;/a&gt; the &lt;a href="https://r-consortium.org"&gt;R Consortium&amp;rsquo;s&lt;/a&gt; newest &lt;a href="https://r-consortium.org/all-projects/"&gt;Top-Level Project&lt;/a&gt;! We&amp;rsquo;re glad
to be in the company of community and infrastructure projects that have been
designated critical to the R Ecosystem, such as &lt;a href="https://blog.r-hub.io/"&gt;R-hub&lt;/a&gt;, &lt;a href="https://r-dbi.org/"&gt;DBI&lt;/a&gt;, &lt;a href="https://rladies.org/"&gt;R-Ladies&lt;/a&gt;, and the
&lt;a href="https://r-consortium.org/all-projects/isc-working-groups.html"&gt;R User Group program&lt;/a&gt;, and we are grateful for the support of the R Consortium and
its &lt;a href="https://r-consortium.org/about/governance#infrastructure-steering-committee"&gt;Infrastructure Steering Committee (ISC)&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Introducing the rOpenSci Localization and Translation Guidelines</title><link>https://ropensci.org/blog/2024/12/17/localization-guide/</link><pubDate>Tue, 17 Dec 2024 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2024/12/17/localization-guide/</guid><description><i><a href="https://ropensci.org/es/blog/2024/12/17/guia-localizacion/">Read it in: Español</a>.</i>
&lt;p&gt;Since 2022, rOpenSci has been developing tools and processes to localize and translate our content.
As a result of this effort, we created a set of guidelines to assist our community in translating and localizing our resources.
What started as an internal challenge has evolved into a collaborative blueprint that we believe can help transform how scientific resources are shared in a multilingual research landscape.&lt;/p&gt;
&lt;p&gt;Therefore, we&amp;rsquo;re excited to share the first version of the &lt;a href="https://translationguide.ropensci.org/"&gt;rOpenSci Localization and Translation Guidelines&lt;/a&gt;!&lt;/p&gt;</description></item><item><title>BioPackathon</title><link>https://ropensci.org/events/biopackathon-2024/</link><pubDate>Wed, 11 Dec 2024 10:00:00 +0000</pubDate><guid>https://ropensci.org/events/biopackathon-2024/</guid><description/></item><item><title>Social Coworking and Office Hours - Getting Involved in the Antarctic/Southern Ocean rOpenSci Community</title><link>https://ropensci.org/events/coworking-2024-12/</link><pubDate>Tue, 03 Dec 2024 03:00:00 +0000</pubDate><guid>https://ropensci.org/events/coworking-2024-12/</guid><description>
&lt;!--
```{r}
d &lt;- lubridate::ymd_hms('2024-12-03 09:00:00', tz = 'Australia/Perth')
lubridate::with_tz(d, 'UTC')
lubridate::with_tz(d, 'America/Winnipeg')
```
--&gt;
&lt;p&gt;&lt;strong&gt;Join us for 2 hours Tuesday December 03, 09:00 Australian Western (01:00 UTC) for
&lt;a href="https://ropensci.org/blog/2023/06/21/coworking/"&gt;Social Coworking + Office Hours&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This month we&amp;rsquo;re focusing on the theme &lt;strong&gt;Getting Involved in the Antarctic/Southern Ocean rOpenSci Community&lt;/strong&gt;
with community hosts &lt;strong&gt;Michael Sumner and Ben Raymond&lt;/strong&gt;.
Michael and Ben each maintain several rOpenSci packages for spatial and ocean research and
analyses, and both are also part
of the &lt;a href="https://ropensci.org/blog/2018/11/13/antarctic/"&gt;Antarctic/Southern Ocean rOpenSci community&lt;/a&gt;.
This is a special community within rOpenSci which promotes the development of
software to support open science in the Antarctic and Southern Ocean.&lt;/p&gt;</description></item><item><title>R-Universe Named an R Consortium Top-Level Project</title><link>https://ropensci.org/blog/2024/12/03/r-universe-r-consortium-tlp/</link><pubDate>Tue, 03 Dec 2024 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2024/12/03/r-universe-r-consortium-tlp/</guid><description><i><a href="https://ropensci.org/es/blog/2024/12/03/r-universe-r-consortium-tlp/">Read it in: Español</a>.</i>
&lt;p&gt;We are excited to announce that &lt;a href="https://ropensci.org/r-universe/"&gt;R-Universe&lt;/a&gt;
has been &lt;a href="https://r-consortium.org/posts/r-universe-named-r-consortiums-newest-top-level-project/"&gt;named&lt;/a&gt; the &lt;a href="https://r-consortium.org"&gt;R Consortium&amp;rsquo;s&lt;/a&gt; newest &lt;a href="https://r-consortium.org/all-projects/"&gt;Top-Level Project&lt;/a&gt;! We&amp;rsquo;re glad
to be in the company of community and infrastructure projects that have been
designated critical to the R Ecosystem, such as &lt;a href="https://blog.r-hub.io/"&gt;R-hub&lt;/a&gt;, &lt;a href="https://r-dbi.org/"&gt;DBI&lt;/a&gt;, &lt;a href="https://rladies.org/"&gt;R-Ladies&lt;/a&gt;, and the
&lt;a href="https://r-consortium.org/all-projects/isc-working-groups.html"&gt;R User Group program&lt;/a&gt;, and we are grateful for the support of the R Consortium and
its &lt;a href="https://r-consortium.org/about/governance#infrastructure-steering-committee"&gt;Infrastructure Steering Committee (ISC)&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;The R Consortium supports the R community to help develop the infrastructure
required to ensure the long-term stability and growth of the R Ecosystem. They
have generously supported R-Universe for the past year. Now, in
granting R-Universe top-level status, the R Consortium has committed to support
us for three more years. This endorsement and investment will help us meet our goal
of making R-Universe a sustainable and scalable platform for R package
development that individuals and organizations can rely on. Jeroen Ooms,
R-Universe&amp;rsquo;s lead developer, will also join the R-Consortium&amp;rsquo;s Infrastructure
Steering Committee. We are glad to play a part in helping support important
R community projects in the future!&lt;/p&gt;</description></item><item><title>rOpenSci News Digest, November 2024</title><link>https://ropensci.org/blog/2024/11/29/news-november-2024/</link><pubDate>Fri, 29 Nov 2024 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2024/11/29/news-november-2024/</guid><description>
&lt;!-- Before sending DELETE THE INDEX_CACHE and re-knit! --&gt;
&lt;p&gt;Dear rOpenSci friends, it&amp;rsquo;s time for our monthly news roundup!&lt;/p&gt;
&lt;!-- blabla --&gt;
&lt;p&gt;You can read this post &lt;a href="https://ropensci.org/blog/2024/11/29/news-november-2024"&gt;on our blog&lt;/a&gt;.
Now let&amp;rsquo;s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;h3&gt;
Looking for Maintainers to Support First-Time Contributors
&lt;/h3&gt;&lt;p&gt;&lt;strong&gt;Now open to non-rOpenSci package maintainers!&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Making your first contribution to Open Source can be both empowering and intimidating. As such, we’re exited to announce a special series of activities to support first-time contributors! 🎉&lt;/p&gt;</description></item><item><title>Give Thanks with the allcontributors Package</title><link>https://ropensci.org/blog/2024/11/26/allcontributors/</link><pubDate>Tue, 26 Nov 2024 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2024/11/26/allcontributors/</guid><description>
&lt;p&gt;Thanksgiving is celebrated in &lt;a href="https://en.wikipedia.org/wiki/Thanksgiving"&gt;many parts of the world&lt;/a&gt;.
The USA, rOpenSci&amp;rsquo;s official location, celebrates Thanksgiving this Thursday, 28th November.
Giving thanks to contributors is also an &lt;a href="https://devguide.ropensci.org/maintenance_collaboration.html#attributions"&gt;important part of open-source software development&lt;/a&gt;.
Many open-source software projects use the &lt;a href="https://allcontributors.org/"&gt;allcontributors.org system&lt;/a&gt; to acknowledge contributions, which includes&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;a bot to automate the tedious stuff for adding project contributors, so you
can focus on your project instead of managing your ReadMe.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;One strong motivation for &lt;a href="https://allcontributors.org"&gt;allcontributors.org&lt;/a&gt; is to &amp;ldquo;Recognize all contributors, including those that don&amp;rsquo;t push code.&amp;rdquo;
Usage of the bot is described in &lt;a href="https://allcontributors.org/docs/en/bot/usage"&gt;the documentation&lt;/a&gt;.
Acknowledgement happens through commit comments, which generally follow the format:&lt;/p&gt;</description></item><item><title>LatinR &lt;- Latinamerican Conference About the Use of R in R&amp;D 2024</title><link>https://ropensci.org/events/latinr-2024/</link><pubDate>Fri, 22 Nov 2024 15:00:00 +0000</pubDate><guid>https://ropensci.org/events/latinr-2024/</guid><description>
&lt;p&gt;Don’t miss the &lt;a href="https://latinr.org/en/"&gt;seventh edition of LatinR!&lt;/a&gt; This year, we will gather virtually to learn about the latest developments in R in Latin America. The program includes practical workshops, talks, and dialogue sessions with presenters.&lt;/p&gt;
&lt;h3&gt;
Keynotes
&lt;/h3&gt;&lt;ul&gt;
&lt;li&gt;&lt;a href="https://ropensci.org/author/will-landau/"&gt;Will Landau&lt;/a&gt; is a &lt;strong&gt;keynote speaker&lt;/strong&gt; at LatinR! with the talk &amp;ldquo;targets: a rediscovery from a different field&amp;rdquo;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The practice of Statistics creates non-statistical challenges whose solutions come from software engineering. Version control, portable package libraries, and literate programming are already well-known examples. Pipeline tools, however, are an unlooked-for answer to workflow management struggles people seldom realize they have. &lt;a href="https://docs.ropensci.org/targets/"&gt;The {targets} package&lt;/a&gt; is a pipeline tool that scales to large workloads, saves time, and embraces the comfort of your local R environment. This talk showcases {targets} tackling a formidable real-world example from Bayesian data analysis, and it posits a trove of unconventional breakthroughs waiting to be noticed by statisticians.&lt;/p&gt;</description></item><item><title>Containerization and R for Reproducibility and More</title><link>https://ropensci.org/events/rmedicine-2024/</link><pubDate>Tue, 19 Nov 2024 23:00:00 +0000</pubDate><guid>https://ropensci.org/events/rmedicine-2024/</guid><description>
&lt;p&gt;Containerization has become a dominant computing paradigm for computing in the past decade due to its many advantages: isolation and security, scalability and efficiency with lightweight containers sharing an operating kernel and resources, and portability across cloud computing providers. For the researcher, analyst, or R user, containers have applications ranging from reproducible analytical environments to packaging statistical code to use in web applications. I will discuss how biomedical researchers can make use of containerization technology, particularly the tools provided by the Rocker Project, which publishes powerful standardized containers for the R language.&lt;/p&gt;</description></item><item><title>R-universe and Cloudflare. How we get fast global routing and caching</title><link>https://ropensci.org/events/runiverse-cloudflare2024/</link><pubDate>Tue, 19 Nov 2024 23:00:00 +0000</pubDate><guid>https://ropensci.org/events/runiverse-cloudflare2024/</guid><description/></item><item><title>BioNT Community Event &amp; CarpentryConnect-Heidelberg 2024</title><link>https://ropensci.org/events/carpentryconnect-2024/</link><pubDate>Thu, 14 Nov 2024 15:00:00 +0000</pubDate><guid>https://ropensci.org/events/carpentryconnect-2024/</guid><description>
&lt;p&gt;The Bio Network for Training, BioNT consortium with all its international partners will host the second &lt;a href="https://biont-training.eu/event-details/CarpentryConnect2024"&gt;European CarpentryConnect event from November 12 to 14, 2024&lt;/a&gt;. This event will be happening alongside the BioNT community event, creating a great opportunity for collaboration and networking. It will be held at EMBL - Heidelberg in Germany&lt;/p&gt;
&lt;p&gt;Yanina Bellini Saibene will be presenting a keynote at the event.&lt;/p&gt;
&lt;p&gt;Come to chat with Yani if you are around!&lt;/p&gt;</description></item><item><title>A comunidade R fala português</title><link>https://ropensci.org/commcalls/translation-portuguese/</link><pubDate>Wed, 06 Nov 2024 00:00:00 +0000</pubDate><guid>https://ropensci.org/commcalls/translation-portuguese/</guid><description>
&lt;p&gt;A comunidade R está realizando vários esforços de traduções comunitárias para o português de diferentes recursos: livros, pacotes e guias.&lt;/p&gt;
&lt;p&gt;Nesta chamada da comunidade, três líderes da comunidade de língua portuguesa apresentarão suas experiências liderando e fazendo parte desses projetos e compartilharão como podemos participar desses esforços.&lt;/p&gt;
&lt;p&gt;Essa chamada da comunidade será seguida por uma reunião de tradução na LatinR, a conferência latino-americana de R para pesquisa e desenvolvimento, para aqueles que quiserem começar a participar.&lt;/p&gt;</description></item><item><title>Social Coworking and Office Hours - Getting to know Openscapes</title><link>https://ropensci.org/events/coworking-2024-11/</link><pubDate>Tue, 05 Nov 2024 19:00:00 +0000</pubDate><guid>https://ropensci.org/events/coworking-2024-11/</guid><description>
&lt;!--
```{r}
d &lt;- lubridate::ymd_hms('2024-11-05 09:00:00', tz = 'America/Vancouver')
lubridate::with_tz(d, 'UTC')
lubridate::with_tz(d, 'America/Winnipeg')
```
--&gt;
&lt;p&gt;&lt;strong&gt;Join us for 2 hours Tuesday November 05, 09:00 Americas Pacific (17:00 UTC) for
&lt;a href="https://ropensci.org/blog/2023/06/21/coworking/"&gt;Social Coworking + Office Hours&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This month we&amp;rsquo;re focusing on the theme &lt;strong&gt;Getting to know &lt;a href="https://openscapes.org"&gt;Openscapes&lt;/a&gt;&lt;/strong&gt;,
with community host &lt;strong&gt;Stefanie Butland&lt;/strong&gt;.
Stef is an Openscapes team member, co-lead of the Openscapes Champions Program, and rOpenSci&amp;rsquo;s former Community Manager.&lt;/p&gt;
&lt;p&gt;These &amp;ldquo;Getting to know&amp;rdquo; themed coworking sessions give us a chance to meet and
learn about other like-minded organizations and communities whom we support,
collaborate with, or generally cheer on!&lt;/p&gt;</description></item><item><title>rOpenSci News Digest, October 2024</title><link>https://ropensci.org/blog/2024/10/23/news-october-2024/</link><pubDate>Wed, 23 Oct 2024 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2024/10/23/news-october-2024/</guid><description>
&lt;!-- Before sending DELETE THE INDEX_CACHE and re-knit! --&gt;
&lt;p&gt;Dear rOpenSci friends, it&amp;rsquo;s time for our monthly news roundup!&lt;/p&gt;
&lt;!-- blabla --&gt;
&lt;p&gt;You can read this post &lt;a href="https://ropensci.org/blog/2024/10/23/news-october-2024"&gt;on our blog&lt;/a&gt;.
Now let&amp;rsquo;s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;h3&gt;
Fostering open science in Latin America: CZI awards funds for sustainable research software development
&lt;/h3&gt;&lt;p&gt;Exciting News!
The Chan Zuckerberg Initiative has awarded rOpenSci a new grant to foster sustainable scientific software as a pillar of Open Science in Latin America by building capacity and community.
With this $340K grant, we’re planning to launch a Spanish-language version of our Champions Program, along with other new initiatives to make sustainable software development more accessible to researchers across the region.
Read more in our &lt;a href="https://ropensci.org/blog/2024/10/10/czi-latam-grant/"&gt;announcement&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Looking for Maintainers to Support First-Time Contributors</title><link>https://ropensci.org/blog/2024/10/22/first-time-contributions/</link><pubDate>Tue, 22 Oct 2024 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2024/10/22/first-time-contributions/</guid><description>
&lt;p&gt;Do you remember your first contribution to open source?
Or are you still waiting to make it?&lt;/p&gt;
&lt;p&gt;Contributing to open source can be very rewarding, but also incredibly intimidating.
When we asked about first time contributions on the &lt;a href="https://contributing.ropensci.org/resources.html#channels"&gt;rOpenSci Slack&lt;/a&gt;,
people recalled the challenges and mistakes they made, but mostly how much they learned from and enjoyed that experience.
For open source maintainers, contributions can also lead to mixed feelings,
as reviewing contributions and making your repository contributor-friendly&lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt; can take time.
Despite this, contributions can super helpful and mentoring contributors is rewarding!&lt;/p&gt;</description></item><item><title>Fostering Open Science in Latin America: CZI Awards Funds for Sustainable Research Software Development</title><link>https://ropensci.org/blog/2024/10/10/czi-latam-grant/</link><pubDate>Thu, 10 Oct 2024 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2024/10/10/czi-latam-grant/</guid><description><i><a href="https://ropensci.org/es/blog/2024/10/10/czi-america-latina-grant/">Read it in: Español</a>.</i>
&lt;p&gt;&lt;strong&gt;Exciting News!&lt;/strong&gt; The Chan Zuckerberg Initiative has awarded rOpenSci a new grant to foster sustainable scientific software as a pillar of Open Science in Latin America by building capacity and community. With this $340K grant, we’re planning to launch a Spanish-language version of our Champions Program, along with other new initiatives to make sustainable software development more accessible to researchers across the region. Let’s dive into how this project will support Latin American scientists.&lt;/p&gt;</description></item><item><title>Social Coworking and Office Hours - Using R to tell (data science) stories</title><link>https://ropensci.org/events/coworking-2024-10/</link><pubDate>Tue, 01 Oct 2024 14:00:00 +0000</pubDate><guid>https://ropensci.org/events/coworking-2024-10/</guid><description>
&lt;!--
```{r}
d &lt;- lubridate::ymd_hms('2024-10-01 14:00:00', tz = 'Europe/Paris')
lubridate::with_tz(d, 'UTC')
lubridate::with_tz(d, 'America/Winnipeg')
```
--&gt;
&lt;p&gt;&lt;strong&gt;Join us for 2 hours Tuesday October 01, 14:00 European Central (12:00 UTC) for
&lt;a href="https://ropensci.org/blog/2023/06/21/coworking/"&gt;Social Coworking + Office Hours&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This month we&amp;rsquo;re focusing on the theme &lt;strong&gt;Using R to tell (data science) stories&lt;/strong&gt;
with community host &lt;strong&gt;Apoorv Anand&lt;/strong&gt;. Apoorv is a mentor in the
rOpenSci Champions Program and often uses R to make public datasets more accessible.&lt;/p&gt;</description></item><item><title>rOpenSci News Digest, September 2024</title><link>https://ropensci.org/blog/2024/09/27/news-september-2024/</link><pubDate>Fri, 27 Sep 2024 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2024/09/27/news-september-2024/</guid><description>
&lt;!-- Before sending DELETE THE INDEX_CACHE and re-knit! --&gt;
&lt;p&gt;Dear rOpenSci friends, it&amp;rsquo;s time for our monthly news roundup!&lt;/p&gt;
&lt;!-- blabla --&gt;
&lt;p&gt;You can read this post &lt;a href="https://ropensci.org/blog/2024/09/27/news-september-2024"&gt;on our blog&lt;/a&gt;.
Now let&amp;rsquo;s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;h3&gt;
Community call recording: Navigating the R ecosystem using R-universe
&lt;/h3&gt;&lt;p&gt;&lt;a href="https://ropensci.org/commcalls/nov2024-r-universe/"&gt;Video and resources&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Learn more about R-Universe and how you can use it to improve your R package development workflow.&lt;/p&gt;</description></item><item><title>Navigating the R ecosystem using R-universe</title><link>https://ropensci.org/commcalls/nov2024-r-universe/</link><pubDate>Tue, 13 Aug 2024 00:00:00 +0000</pubDate><guid>https://ropensci.org/commcalls/nov2024-r-universe/</guid><description>
&lt;p&gt;&lt;a href="https://ropensci.org/r-universe/"&gt;R-Universe&lt;/a&gt; is rOpenSci’s platform for testing, building, distributing, and discovering R packages, lead by Jeroen Ooms.&lt;/p&gt;
&lt;p&gt;R-Universe provides no-setup continuous integration, compilation for all platforms (including WebR!), accessible HTML R package manuals, a comprehensive API, and the ability for users or organizations to create their own “universes”.&lt;/p&gt;
&lt;p&gt;The R universe is in continuous development and in the last time the platform has evolved improving the services it offers and adding new functionalities and features.&lt;/p&gt;</description></item><item><title>Deposits In The Wild</title><link>https://ropensci.org/blog/2024/09/17/deposits-in-the-wild/</link><pubDate>Tue, 17 Sep 2024 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2024/09/17/deposits-in-the-wild/</guid><description>
&lt;script type="module"&gt;
import mermaid from 'https://cdn.jsdelivr.net/npm/mermaid/dist/mermaid.esm.min.mjs';
mermaid.initialize({ startOnLoad: true });
&lt;/script&gt;
&lt;p&gt;For the better part of a year, I have been looking for an opportunity to use the rOpenSci package &lt;a href="https://docs.ropensci.org/deposits/"&gt;deposits&lt;/a&gt; in my
role as the Data Librarian at EcoHealth Alliance.
I had done some initial testing with &lt;a href="https://ropensci.org/author/mark-padgham/"&gt;Mark Padgham&lt;/a&gt;, the brilliant person who developed this package, but there weren&amp;rsquo;t any projects ready for me to put deposits through its paces.
Enter the &lt;em&gt;Rift Valley Fever Virus in South Africa&lt;/em&gt; project, a ten year, multiple part study of humans, wildlife (mosquitoes and wild ungulates), and domestic animals that uses every data store from Dropbox to Google Drive to Airtable to ODK with a healthy mix of file formats for tabular data.
Additionally, the principal investigators (PIs) on the project are very enthusiastic about making the data FAIR (Findability, Accessibility, Interoperability, and Reusability).&lt;/p&gt;</description></item><item><title>Labels For Technical Writing Projects</title><link>https://ropensci.org/blog/2024/09/12/labels-writing-projects/</link><pubDate>Thu, 12 Sep 2024 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2024/09/12/labels-writing-projects/</guid><description>
&lt;p&gt;Over the past thirty years I have written &lt;a href="https://third-bit.com/bib/"&gt;five technical books,
co-written three others,
and edited a further six&lt;/a&gt;.
Since 2007 they have all lived in GitHub repositories,
as did the first versions of the &lt;a href="https://carpentries.org/"&gt;Software Carpentry&lt;/a&gt; lessons that I helped to write.&lt;/p&gt;
&lt;p&gt;A few months ago I wrote about &lt;a href="https://third-bit.com/2024/03/07/labels/"&gt;the GitHub issue labels I use&lt;/a&gt;
for writing projects like these.
As I put that post together,
I realized that I wasn&amp;rsquo;t actually using all of the labels I had created,
and that the problem of choosing good labels for a mixture of code and prose
is more complicated than it seems.&lt;/p&gt;</description></item><item><title>Screen Reader Accessible Tools and Resources for Learning and Working with R</title><link>https://ropensci.org/events/rsr-learn-and-use/</link><pubDate>Tue, 10 Sep 2024 18:30:00 +0000</pubDate><guid>https://ropensci.org/events/rsr-learn-and-use/</guid><description>
&lt;h2&gt;
English
&lt;/h2&gt;&lt;p&gt;This multilingual webinar will be held on September 10, 2024, at 17:00 UTC via Zoom. The webinar will be in English with translation into Turkish.&lt;/p&gt;
&lt;p&gt;The webinar is organized by rOpenSci&amp;rsquo;s Champions, &lt;a href="https://ropensci.org/author/alican-cagri-gokcek/"&gt;Alican Cagri Gokcek&lt;/a&gt;, in collaboration with &lt;a href="http://www.drenginyilmaz.net"&gt;Engine Yilmaz&lt;/a&gt; from &lt;a href="https://bogazici.edu.tr/en-US/Index"&gt;Boğaziçi University&lt;/a&gt; (Turkey).&lt;/p&gt;
&lt;p&gt;Our Community Manager, &lt;a href="https://ropensci.org/author/yanina-bellini-saibene/"&gt;Yani Bellini Saibene&lt;/a&gt;, will moderate a panel featuring &lt;a href="https://ropensci.org/author/liz-hare/"&gt;Liz Hare&lt;/a&gt; and &lt;a href="https://ropensci.org/author/alican-cagri-gokcek/"&gt;Alican Cagri Gokcek&lt;/a&gt;, both participants in our &lt;a href="https://ropensci.org/champions/"&gt;Champions Program&lt;/a&gt;, as speakers. Cagri and Liz will share their experiences with screen reader-accessible tools and resources for learning and working with R from the perspectives of a beginner and an experienced R user. They will also discuss their experiences in the rOpenSci Champions Program.&lt;/p&gt;</description></item><item><title>Capturing Screenshots Programmatically With R</title><link>https://ropensci.org/blog/2024/09/10/script-screenshots/</link><pubDate>Tue, 10 Sep 2024 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2024/09/10/script-screenshots/</guid><description>
&lt;p&gt;As part of our work &lt;a href="https://ropensci.org/blog/2024/04/12/gsod-announcement/"&gt;documenting R-Universe&lt;/a&gt;,
we&amp;rsquo;re adding screenshots of the interface to the &lt;a href="https://docs.r-universe.org"&gt;documentation website&lt;/a&gt;.
Taking screenshots manually could quickly become very cumbersome, especially as we expect they&amp;rsquo;ll need updating in future: we might want to change the universes we feature, the interface might improve &lt;a href="https://ropensci.org/blog/2024/06/12/runiverse-frontend/"&gt;yet again&lt;/a&gt; and therefore look slightly different.
Therefore, we decided to opt for a programmatic approach.
In this post we shall present our learnings from using the R packages &lt;a href="https://rstudio.github.io/chromote/"&gt;chromote&lt;/a&gt; and &lt;a href="https://docs.ropensci.org/magick/"&gt;magick&lt;/a&gt; to produce screenshots.&lt;/p&gt;</description></item><item><title>rOpenSci at the NumFOCUS Project Summit 2024</title><link>https://ropensci.org/events/numfocussummit-2024/</link><pubDate>Sat, 07 Sep 2024 15:00:00 +0000</pubDate><guid>https://ropensci.org/events/numfocussummit-2024/</guid><description>
&lt;p&gt;The &lt;a href="https://www.nfsummit24.com/schedule"&gt;NUMFocus Project Summit&lt;/a&gt; is an annual event aimed at strengthening the NumFOCUS project network by bringing project representatives together for two full days of presentations, workshops, and group discussions.&lt;/p&gt;
&lt;p&gt;Come to chat with rOpenSci Staff if you are around!&lt;/p&gt;</description></item><item><title>Research Software Engineering Conference 2024</title><link>https://ropensci.org/events/rseuk-2024/</link><pubDate>Thu, 05 Sep 2024 15:00:00 +0000</pubDate><guid>https://ropensci.org/events/rseuk-2024/</guid><description>
&lt;p&gt;The eighth annual conference for &lt;a href="https://rsecon24.society-rse.org/programme/schedule/"&gt;Research Software Engineering&lt;/a&gt; is taking place in Newcastle, UK from 3rd to 5th September 2024. Mark Padgham will be presenting a talk about rOpenSci. Come to chat if you are around!&lt;/p&gt;</description></item><item><title>Resources For Using R With Screen Readers</title><link>https://ropensci.org/blog/2024/09/05/screen-readers-tools/</link><pubDate>Thu, 05 Sep 2024 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2024/09/05/screen-readers-tools/</guid><description><i><a href="https://ropensci.org/es/blog/2024/09/05/recursos_para_utilizar_r_con_lectores_de_pantalla/">Read it in: Español</a>.</i><i><a href="https://ropensci.org/tr/blog/2024/09/05/ekran_okuyucularla_r_kullan%C4%B1m%C4%B1_i%CC%87%C3%A7in_kaynaklar/">Read it in: Türkçe</a>.</i>
&lt;p&gt;R is a language and environment for statistical computing.
There are several tools and approaches for interacting with R, but not all are accessible with screen readers.
This guide provides an overview of the tools and techniques available to screen reader users across different operating systems, with practical tips and resources to help them navigate the R environment.
This guide may not be complete, but I hope it serves as a valuable starting point. We welcome suggestions from other users to enhance it further.&lt;/p&gt;</description></item><item><title>rOpenSci News Digest, August 2024</title><link>https://ropensci.org/blog/2024/08/30/news-august-2024/</link><pubDate>Fri, 30 Aug 2024 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2024/08/30/news-august-2024/</guid><description>
&lt;!-- Before sending DELETE THE INDEX_CACHE and re-knit! --&gt;
&lt;p&gt;Dear rOpenSci friends, it&amp;rsquo;s time for our monthly news roundup!&lt;/p&gt;
&lt;!-- blabla --&gt;
&lt;p&gt;You can read this post &lt;a href="https://ropensci.org/blog/2024/08/30/news-august-2024"&gt;on our blog&lt;/a&gt;.
Now let&amp;rsquo;s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;h3&gt;
Community call: Navigating the R ecosystem using R-Universe!
&lt;/h3&gt;&lt;p&gt;On &lt;a href="https://ropensci.org/commcalls/nov2024-r-universe/"&gt;Tuesday, 24 September 2024 16:00 UTC&lt;/a&gt; (no RSVP needed), join us to learn more about R-Universe and how you can use it to improve your R package development workflow.&lt;/p&gt;</description></item><item><title>My Experience With Long Term Maintenance Of An R Package</title><link>https://ropensci.org/blog/2024/08/20/my-experience-with-long-term-maintenance-of-an-r-package/</link><pubDate>Tue, 20 Aug 2024 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2024/08/20/my-experience-with-long-term-maintenance-of-an-r-package/</guid><description>
&lt;p&gt;R packages, like any software, require &lt;a href="https://ropensci.org/blog/2023/02/07/what-does-it-mean-to-maintain-a-package/"&gt;maintenance&lt;/a&gt;. Package maintenance includes:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Fixing bugs when discovered.&lt;/li&gt;
&lt;li&gt;Adapting to updates in package dependencies.&lt;/li&gt;
&lt;li&gt;Providing some level of user and contributor support.&lt;/li&gt;
&lt;li&gt;When desired, refactoring code or adding new functionality.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Without maintenance efforts a package is at risk of losing its value. Yet, maintaining a package for years or even decades can be challenging as it is time consuming. Therefore, it is important for any package maintainer to adopt a strategy for sustaining the maintenance effort. In this blog post I share my own experience with a variety of strategies that I have explored myself. For readability I have categorized them into:&lt;/p&gt;</description></item><item><title>posit::conf(2024)</title><link>https://ropensci.org/events/posit-2024/</link><pubDate>Wed, 14 Aug 2024 19:30:00 +0000</pubDate><guid>https://ropensci.org/events/posit-2024/</guid><description>
&lt;p&gt;At Posit Conf? Come to chat with rOpenSci Champions and Mentors. We&amp;rsquo;ll be around to chat about rOpenSci, the Champions Program open science, R packages and more. Look for:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Andrea Gomez Vargas&lt;/li&gt;
&lt;li&gt;Yi-Chin Sunny Tseng&lt;/li&gt;
&lt;li&gt;Luis D. Verde Arregoitia&lt;/li&gt;
&lt;li&gt;Francisco Cardozo&lt;/li&gt;
&lt;li&gt;Jonathan Keane&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Don&amp;rsquo;t miss Luis&amp;rsquo; lightning talk &amp;ldquo;Why’d you load that package for?&amp;rdquo; on Tuesday, Aug 13 at 1:00 PM PDT&lt;/p&gt;</description></item><item><title>Social Coworking and Office Hours - Building your first R package</title><link>https://ropensci.org/events/coworking-2024-08/</link><pubDate>Tue, 06 Aug 2024 18:00:00 +0000</pubDate><guid>https://ropensci.org/events/coworking-2024-08/</guid><description>
&lt;!--
```{r}
d &lt;- lubridate::ymd_hms('2024-08-06 09:00:00', tz = 'America/Vancouver')
lubridate::with_tz(d, 'UTC')
lubridate::with_tz(d, 'America/Winnipeg')
```
--&gt;
&lt;p&gt;&lt;strong&gt;Join us for 2 hours Tuesday August 06, 09:00 Americas Pacific (16:00 UTC) for
&lt;a href="https://ropensci.org/blog/2023/06/21/coworking/"&gt;Social Coworking + Office Hours&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This month we&amp;rsquo;re focusing on the theme &lt;strong&gt;Building your first R package&lt;/strong&gt;
with community host &lt;strong&gt;Carolina Pradier&lt;/strong&gt;, rOpenSci Champion (2022-2023) and
author/maintainer of the &lt;a href="https://docs.ropensci.org/eph"&gt;eph&lt;/a&gt; package.&lt;/p&gt;
&lt;p&gt;Come for the full 2 hrs or only as long as you need!&lt;/p&gt;</description></item><item><title>Git Tricks for Working with Large Repositories</title><link>https://ropensci.org/blog/2024/08/06/git-tricks/</link><pubDate>Tue, 06 Aug 2024 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2024/08/06/git-tricks/</guid><description><i><a href="https://ropensci.org/es/blog/2024/08/06/git-tricks/">Read it in: Español</a>.</i>
&lt;p&gt;Recently &lt;a href="https://ropensci.org/author/yanina-bellini-saibene/"&gt;Yanina Bellini Saibene&lt;/a&gt; reminded us
to update our Slack profile:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Friendly reminder: Let&amp;rsquo;s increase the value of our rOpenSci Slack community.
Please add details to your profile, e.g., your photo, your favorite social media
handle, what you do, your pronouns, and how to pronounce your name.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;After doing that I went on to updating my profile photos on the rOpenSci
website, which ended up teaching me a few git tricks I would like to share here.
Thanks &lt;a href="https://ropensci.org/author/ma%C3%ABlle-salmon/"&gt;Maëlle Salmon&lt;/a&gt; for the encouragement, and
&lt;a href="https://ropensci.org/author/steffi-lazerte/"&gt;Steffi LaZerte&lt;/a&gt; for reviewing this post.&lt;/p&gt;</description></item><item><title>Developing Software Together (training for champions program applicants)</title><link>https://ropensci.org/events/dev-soft-together-2024/</link><pubDate>Wed, 24 Jul 2024 23:59:00 +0000</pubDate><guid>https://ropensci.org/events/dev-soft-together-2024/</guid><description/></item><item><title>rOpenSci News Digest, July 2024</title><link>https://ropensci.org/blog/2024/07/19/news-july-2024/</link><pubDate>Fri, 19 Jul 2024 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2024/07/19/news-july-2024/</guid><description>
&lt;!-- Before sending DELETE THE INDEX_CACHE and re-knit! --&gt;
&lt;p&gt;Dear rOpenSci friends, it&amp;rsquo;s time for our monthly news roundup!&lt;/p&gt;
&lt;!-- blabla --&gt;
&lt;p&gt;You can read this post &lt;a href="https://ropensci.org/blog/2024/07/19/news-july-2024"&gt;on our blog&lt;/a&gt;.
Now let&amp;rsquo;s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;h3&gt;
Announcing New Software Peer Review Editors: Beatriz Milz and Margaret Siple
&lt;/h3&gt;&lt;p&gt;We are excited to welcome &lt;a href="https://ropensci.org/author/beatriz-milz/"&gt;Beatriz Milz&lt;/a&gt; and &lt;a href="https://ropensci.org/author/margaret-siple/"&gt;Margaret Siple&lt;/a&gt; to our team of &lt;a href="https://ropensci.org/software-review/#editors"&gt;Associate Editors&lt;/a&gt; for rOpenSci &lt;a href="https://ropensci.org/software-review/"&gt;Software Peer Review&lt;/a&gt;. They join Laura DeCicco, Julia Gustavsen, Anna Krystalli, Mauro Lepore, Noam Ross, Maëlle Salmon, Emily Riederer, Adam Sparks, and Jeff Hollister.&lt;/p&gt;</description></item><item><title>Metrics, Impact and Community Management</title><link>https://ropensci.org/blog/2024/07/16/impact-community-management/</link><pubDate>Tue, 16 Jul 2024 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2024/07/16/impact-community-management/</guid><description>
&lt;p&gt;On June 14 I was invited to present at the &lt;a href="https://chanzuckerberg.com/science/programs-resources/open-science/"&gt;CZI Open Science 2024&lt;/a&gt; event. I was asked to participate in &amp;ldquo;Case Study Session 3: Demonstrating Impact of Open Science&amp;rdquo; and to explore the challenges of using traditional academic metrics for measuring project impact with an emphasis on alternative approaches.&lt;/p&gt;
&lt;p&gt;I was very excited to share our experiences and to learn from others projects. Here I present a summary of this talk.&lt;/p&gt;</description></item><item><title>Translating Carpentries workbench lessons with babeldown</title><link>https://ropensci.org/usecases/translating-carpentries-workbench-lessons-with-babeldown/</link><pubDate>Tue, 16 Jul 2024 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/translating-carpentries-workbench-lessons-with-babeldown/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/babeldown/"&gt;babeldown&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;We have training materials built with the Carpentries &lt;a href="https://carpentries.github.io/workbench/"&gt;workbench&lt;/a&gt; and wanted to translate them in Spanish for an upcoming training with a Peruvian audience.&lt;/p&gt;
&lt;p&gt;Since lessons in the workbench are markdown and Rmarkdown files, babeldown appeared as a good candidates to speed up the creation of a first draft.&lt;/p&gt;
&lt;p&gt;Output files were placed in the &lt;code&gt;locale/es/episodes/&lt;/code&gt;, following the convention started by @joelnitta in &lt;a href="https://github.com/joelnitta/dovetail"&gt;dovetail&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>useR! 2024 - Salzburg</title><link>https://ropensci.org/events/user-2024/</link><pubDate>Thu, 11 Jul 2024 15:00:00 +0000</pubDate><guid>https://ropensci.org/events/user-2024/</guid><description>
&lt;p&gt;July 08-11, 2024 &lt;a href="https://events.linuxfoundation.org/user/program/schedule/"&gt;useR! 2024&lt;/a&gt; will take place in Salzburg.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Maëlle will be presenting her keynote &lt;a href="https://sched.co/1c9Jy"&gt;&amp;ldquo;How your code might get rusty&amp;rdquo;&lt;/a&gt; on July 10 at 09:20 CEST&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Jeroen will present &lt;a href="https://sched.co/1c90h"&gt;&amp;ldquo;Navigating the R Ecosystem Using R-Universe&amp;rdquo;&lt;/a&gt; on Thursday, July 11, 11:30 - 11:50 CEST&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;And more contributions by rOpenSci community members!&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://ropensci.org/author/jon-harmon/"&gt;Jon Harmon&lt;/a&gt;&amp;rsquo;s virtual talk &amp;ldquo;Learning Together at the Data Science Learning Community&amp;rdquo; will go live on the &lt;a href="https://youtube.com/playlist?list=PL77T87Q0eoJhsC203plZ1H4p21AGrM9rl&amp;amp;si=usuV_NlAJ_nR0QA8"&gt;useR!2024 YouTube playlist&lt;/a&gt; at 10:30am CDT on July 2;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://ropensci.org/author/pao-corrales/"&gt;Paola Corrales&lt;/a&gt;&amp;rsquo; and &lt;a href="https://ropensci.org/author/elio-campitelli/"&gt;Elio Campitelli&lt;/a&gt;&amp;rsquo;s tutorial &lt;a href="https://sched.co/1c8yF"&gt;&amp;ldquo;Efficient Data Analysis with data.table&amp;rdquo;&lt;/a&gt; on Monday, July 8 (pre-registration required);&lt;/li&gt;
&lt;li&gt;&lt;a href="https://ropensci.org/author/elio-campitelli"&gt;Elio Campitelli&lt;/a&gt;&amp;rsquo;s talk &lt;a href="https://sched.co/1c8yj"&gt;&amp;ldquo;Building Bilingual Bridges with Multilingual Manuals&amp;rdquo;&lt;/a&gt; on Tuesday, July 9 at 11:40 CEST.&lt;/li&gt;
&lt;li&gt;&lt;a href="https://ropensci.org/author/hugo-gruson"&gt;Hugo Gruson&lt;/a&gt;&amp;rsquo;s talk &lt;a href="https://sched.co/1c8z3"&gt;&amp;quot;
Building Interoperability in Existing Software Ecosystems with S3 Classes&amp;quot;&lt;/a&gt; on Tuesday, July 9 at 14:50, and his poster &lt;a href="https://sched.co/1cDry"&gt;&amp;ldquo;A reproducible analysis of CRAN Task Views to understand the state of an R package ecosystem&amp;rdquo;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://ropensci.org/author/llu%C3%ADs-revilla-sancho/"&gt;Lluís Revilla&lt;/a&gt;&amp;rsquo;s and Henrik Bengtsson&amp;rsquo;s &lt;a href="https://sched.co/1cDsG"&gt;poster&lt;/a&gt; about CRAN packages archived and a the &lt;a href="http://cranhaven.org/"&gt;cranhaven.org&lt;/a&gt; R-universe created to reduce the impact of that on users.&lt;/li&gt;
&lt;li&gt;&lt;a href="https://ropensci.org/author/will-landau"&gt;Will Landau&lt;/a&gt;&amp;rsquo;s and Charlie Gao&amp;rsquo;s talk &lt;a href="https://sched.co/1c8ya"&gt;&amp;ldquo;Moju-Kapu: How {Mirai} and {Crew} Are Powering the Next Generation of Parallel Computing in R&amp;rdquo;&lt;/a&gt; on Tuesday, July 9 at 11:00 CEST.&lt;/li&gt;
&lt;li&gt;&lt;a href="https://ropensci.org/blog/2024/02/15/champions-program-champions-2024/#binod-jung-bogati"&gt;Binod Jung Bogati&lt;/a&gt;&amp;rsquo;s talks &lt;a href="https://sched.co/1c8w7"&gt;&amp;ldquo;Generate Raw Synthetic Dataset for Clinical Trial - Binod Jung Bogati, Numeric Mind&amp;rdquo;&lt;/a&gt; on Tuesday, July 9 at 13:30 CEST; and &lt;a href="https://sched.co/1c90Y"&gt;&amp;ldquo;Translate R for Global Reach&amp;rdquo;&lt;/a&gt; on Thursday, July 11 at 12:10 CEST.&lt;/li&gt;
&lt;li&gt;Chung-hong Chan talk on &lt;a href="https://userconf2024.sched.com/event/1c8zC"&gt;Maintaining the I/O Infrastructure of R: Ten Years of &lt;code&gt;Rio&lt;/code&gt; and &lt;code&gt;ReadODS&lt;/code&gt;&lt;/a&gt; on Wednesday July 10, 2024 10:40 - 11:00 CEST.&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>rOpenSci Community Collaboration Insight Using Social Networks Analysis</title><link>https://ropensci.org/blog/2024/07/11/collaboration-networks/</link><pubDate>Thu, 11 Jul 2024 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2024/07/11/collaboration-networks/</guid><description>
&lt;p&gt;In June 2022 I (Yani) become the rOpenSci Community Manager. To do a good job in this kind of role it is essential to know your community, so as soon I started I dug in: reading our documentation, learning our processes and their metrics, and conducting interviews with team-mates and community members.&lt;/p&gt;
&lt;p&gt;In my previous experience working with scientific and technological communities of practice, in collaboration with Sandro, I had used a tool called Social Network Analysis to understand the interaction of the members and plan strategies around the activities. This served me well and I was looking forward to applying it to the rOpenSci community&lt;/p&gt;</description></item><item><title>Multilingual Documentation in R Packages</title><link>https://ropensci.org/blog/2024/07/09/multilingual-documentation-wg/</link><pubDate>Tue, 09 Jul 2024 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2024/07/09/multilingual-documentation-wg/</guid><description><i><a href="https://ropensci.org/es/blog/2024/07/09/multilingual-documentation-wg/">Read it in: Español</a>.</i>
&lt;p&gt;We are happy to announce the brand-new &lt;a href="https://github.com/RConsortium/multilingual-documentation-wg"&gt;R Consortium Multilingual Working Group&lt;/a&gt;.
This Working Group came about after discussions during the &lt;a href="https://contributor.r-project.org/r-project-sprint-2023/"&gt;R Project Sprint 2023&lt;/a&gt; and will oversee the implementation of multilingual documentation support in R and organise community translation efforts.
Our first project is the (experimental) &lt;a href="https://github.com/eliocamp/rhelpi18n"&gt;&lt;strong&gt;rhelpi18n&lt;/strong&gt;&lt;/a&gt; package, which adds multilingual documentation support!&lt;/p&gt;
&lt;p&gt;Do you want to read the documentation for &lt;code&gt;base::mean()&lt;/code&gt; (partially) in Spanish?
Install the experimental &lt;a href="https://github.com/eliocamp/rhelpi18n"&gt;rhelpi18n&lt;/a&gt; package and the sample translation module base.es:&lt;/p&gt;</description></item><item><title>Announcing New Software Peer Review Editors: Beatriz Milz and Margaret Siple</title><link>https://ropensci.org/blog/2024/07/03/editors2024/</link><pubDate>Wed, 03 Jul 2024 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2024/07/03/editors2024/</guid><description>
&lt;p&gt;We are excited to welcome Beatriz Milz and Margaret Siple to our team of &lt;a href="https://ropensci.org/software-review/#editors"&gt;Associate Editors&lt;/a&gt; for rOpenSci &lt;a href="https://ropensci.org/software-review/"&gt;Software Peer Review&lt;/a&gt;.
They join Laura DeCicco, Julia Gustavsen, Anna Krystalli, Mauro Lepore, Noam Ross, Maëlle Salmon, Emily Riederer, Adam Sparks, and Jeff Hollister.
rOpenSci has been running a rigorous and collegial software peer review system since 2015.
Editors &lt;a href="https://devguide.ropensci.org/editorguide.html"&gt;manage the review process&lt;/a&gt;, performing initial package checks, identifying reviewers, and moderating the process until the package is accepted by reviewers as part of rOpenSci&amp;rsquo;s &lt;a href="https://ropensci.org/packages/"&gt;software suite&lt;/a&gt;.
To address the scope and volume of packages submitted for review, it&amp;rsquo;s critical that we have a team of editors with complementary expertise.
Beatriz brings her experiences in environmental science and active community engagement.
Margaret improves open data science and software development practices at the US Government&amp;rsquo;s National Oceanic and Atmospheric Administration (NOAA).&lt;/p&gt;</description></item><item><title>Social Coworking and Office Hours - Git and GitHub</title><link>https://ropensci.org/events/coworking-2024-07/</link><pubDate>Tue, 02 Jul 2024 14:00:00 +0000</pubDate><guid>https://ropensci.org/events/coworking-2024-07/</guid><description>
&lt;!--
```{r}
d &lt;- lubridate::ymd_hms('2024-07-02 14:00:00', tz = 'Europe/Paris')
lubridate::with_tz(d, 'UTC')
lubridate::with_tz(d, 'America/Winnipeg')
```
--&gt;
&lt;p&gt;&lt;strong&gt;Join us for 2 hours Tuesday July 02, 14:00 European Central (12:00 UTC) for
&lt;a href="https://ropensci.org/blog/2023/06/21/coworking/"&gt;Social Coworking + Office Hours&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This month we&amp;rsquo;re focusing on the theme &lt;strong&gt;Git and GitHub&lt;/strong&gt;
with community host &lt;strong&gt;Zhian Kamvar&lt;/strong&gt;, a Research Software Engineer and author of
several R packages and workflows, all with Git and on GitHub!&lt;/p&gt;
&lt;p&gt;Come for the full 2 hrs or only as long as you need!&lt;/p&gt;</description></item><item><title>rOpenSci News Digest, June 2024</title><link>https://ropensci.org/blog/2024/06/21/ropensci-news-june-2024/</link><pubDate>Fri, 21 Jun 2024 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2024/06/21/ropensci-news-june-2024/</guid><description>
&lt;!-- Before sending DELETE THE INDEX_CACHE and re-knit! --&gt;
&lt;p&gt;Dear rOpenSci friends, it&amp;rsquo;s time for our monthly news roundup!&lt;/p&gt;
&lt;!-- blabla --&gt;
&lt;p&gt;You can read this post &lt;a href="https://ropensci.org/blog/2024/06/21/ropensci-news-june-2024"&gt;on our blog&lt;/a&gt;.
Now let&amp;rsquo;s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;h3&gt;
rOpenSci takes over maintenance of the {goodpractice} package
&lt;/h3&gt;&lt;p&gt;The {goodpractice} package was started by Gábor Csárdi in 2016 to auto-magically provide advice on good practices for your own R package.
&lt;a href="https://devguide.ropensci.org"&gt;rOpenSci&amp;rsquo;s &lt;em&gt;Dev Guide&lt;/em&gt;&lt;/a&gt; has recommended using it from &lt;a href="https://github.com/ropensci/dev_guide/commits/main/?since=2018-03-26&amp;amp;until=2018-03-26"&gt;the first day we started writing it in 2018&lt;/a&gt;.
The package is now a central part of our own internal &lt;a href="https://https://docs.ropensci.org/pkgcheck/"&gt;{pkgcheck} system&lt;/a&gt;, which is run automatically on all new submissions, and we recommend that all authors use &lt;a href="https://github.com/ropensci-review-tools/pkgcheck-action"&gt;our &amp;lsquo;pkgcheck-action&amp;rsquo; GitHub action&lt;/a&gt;, which also runs {goodpractice}.&lt;/p&gt;</description></item><item><title>CZI Open Science 2024</title><link>https://ropensci.org/events/czi-2024/</link><pubDate>Fri, 14 Jun 2024 15:00:00 +0000</pubDate><guid>https://ropensci.org/events/czi-2024/</guid><description>
&lt;p&gt;June 11-14, 2024 Yanina, Noam and Mauro attended the &lt;a href="https://chanzuckerberg.com/science/programs-resources/open-science/"&gt;CZI Open Science 2024&lt;/a&gt; in Boston.&lt;/p&gt;
&lt;p&gt;Yanina presented &amp;ldquo;Reproducible Open Science by and for All&amp;rdquo; on June 14, 2024.&lt;/p&gt;</description></item><item><title>OAI interface request, response, and data download with R</title><link>https://ropensci.org/usecases/oai-interface-request-response-and-data-download-with-r/</link><pubDate>Fri, 14 Jun 2024 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/oai-interface-request-response-and-data-download-with-r/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/oai"&gt;oai&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;This tutorial provides examples of queries of the OAI interface of Berlin State Library with R. It deals with exemplary queries addressed to the OAI-PMH interface of the Staatsbibliothek zu Berlin and also explains how to download the data and save it in a CSV file.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://lab.sbb.berlin/oai-interface-request-response-and-data-download-with-r/?lang=en"&gt;https://lab.sbb.berlin/oai-interface-request-response-and-data-download-with-r/?lang=en&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;The tutorial includes a video (in German language only).&lt;/p&gt;
&lt;h4&gt;
Sector
&lt;/h4&gt;&lt;p&gt;academic / non-profit&lt;/p&gt;</description></item><item><title>Rencontres R 2024 - Vannes</title><link>https://ropensci.org/events/rr-2024/</link><pubDate>Thu, 13 Jun 2024 15:00:00 +0000</pubDate><guid>https://ropensci.org/events/rr-2024/</guid><description>
&lt;p&gt;&lt;a href="https://rr2024.sciencesconf.org/"&gt;Rencontres R&lt;/a&gt;&lt;/p&gt;</description></item><item><title>A fresh new look for R-universe!</title><link>https://ropensci.org/blog/2024/06/12/runiverse-frontend/</link><pubDate>Wed, 12 Jun 2024 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2024/06/12/runiverse-frontend/</guid><description>
&lt;h2&gt;
A whole new frontend!
&lt;/h2&gt;&lt;p&gt;As you may have noticed, we have given the &lt;a href="https://ropensci.r-universe.dev/packages"&gt;WebUI for R-universe&lt;/a&gt; a big refresh. This is the biggest UX overhaul since the beginning of the project.&lt;/p&gt;
&lt;p&gt;The old &amp;ldquo;dashboard&amp;rdquo; had become a bit convoluted over the years as features and ideas were added and removed while the project was taking shape. The new front-end keeps the same minimal design, but has been fully rewritten to improve performance, SEO, and incorporate feedback from users.&lt;/p&gt;</description></item><item><title>Using {weatherOz} to Plot Perth's May High Temperatures</title><link>https://ropensci.org/usecases/using-weatheroz-to-plot-perth-s-may-high-temperatures/</link><pubDate>Sun, 09 Jun 2024 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/using-weatheroz-to-plot-perth-s-may-high-temperatures/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/weatherOz/"&gt;{weatherOz}&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;I used {weatherOz} to get weather data for the Perth metropolitan area and recreate a figure from an ABC article, sorta.&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://adamhsparks.netlify.app/2024/06/02/plotting-perth-month-of-may-high-temperatures-with-weatheroz/"&gt;https://adamhsparks.netlify.app/2024/06/02/plotting-perth-month-of-may-high-temperatures-with-weatheroz/&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
Image
&lt;/h4&gt;&lt;p&gt;&lt;img src="https://ropensci.org/usecases/using-weatheroz-to-plot-perth-s-may-high-temperatures/using-weatheroz-to-plot-perths-may-high-temperatures.jpeg" alt="Screenshot 2024-06-09 at 17.32.59|500x500"&gt;&lt;/p&gt;
&lt;h4&gt;
Sector
&lt;/h4&gt;&lt;p&gt;Academic&lt;/p&gt;
&lt;h4&gt;
Field(s) of application
&lt;/h4&gt;&lt;p&gt;history, climate&lt;/p&gt;
&lt;h4&gt;
Social Handles
&lt;/h4&gt;&lt;p&gt;Mastodon: &lt;a href="https://rstats.me/@adamhsparks"&gt;https://rstats.me/@adamhsparks&lt;/a&gt;&lt;/p&gt;</description></item><item><title>From scripts to package. Developing dendroNetwork and learning with rOpenSci</title><link>https://ropensci.org/blog/2024/06/06/from-scripts-to-package/</link><pubDate>Thu, 06 Jun 2024 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2024/06/06/from-scripts-to-package/</guid><description>
&lt;p&gt;Developing &lt;a href="https://docs.ropensci.org/dendroNetwork/"&gt;dendroNetwork&lt;/a&gt; as a package was not a goal from the beginning, but looking back, I think that it should have been. I wish someone had suggested making a package to me much earlier. Why? Because of many things, but mostly: reproducibility and transparency. This enables others to also use the method and software. In addition, I really enjoyed the open peer-review process after submitting to rOpenSci, because the reviewers showed me various improvements and how people from outside my discipline viewed the software and documentation. Meeting new people is always nice and a great bonus of the process.&lt;/p&gt;</description></item><item><title>Amplificando voces: minorías en la frontera de la IA en la comunidad R</title><link>https://ropensci.org/events/ser-ropensci-2024/</link><pubDate>Tue, 04 Jun 2024 09:00:00 +0000</pubDate><guid>https://ropensci.org/events/ser-ropensci-2024/</guid><description/></item><item><title>Social Coworking and Office Hours - R in the Wild</title><link>https://ropensci.org/events/coworking-2024-06/</link><pubDate>Tue, 04 Jun 2024 03:00:00 +0000</pubDate><guid>https://ropensci.org/events/coworking-2024-06/</guid><description>
&lt;!--
```{r}
d &lt;- lubridate::ymd_hms('2024-06-04 09:00:00', tz = 'Australia/Perth')
lubridate::with_tz(d, 'UTC')
lubridate::with_tz(d, 'America/Winnipeg')
```
--&gt;
&lt;p&gt;&lt;strong&gt;Join us for 2 hours Tuesday June 04, 09:00 Australian Western (01:00 UTC) for
&lt;a href="https://ropensci.org/blog/2023/06/21/coworking/"&gt;Social Coworking + Office Hours&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This month we&amp;rsquo;re focusing on the theme &lt;strong&gt;R in the Wild&lt;/strong&gt;
with a team of community hosts! &lt;strong&gt;Ernest Guevarra, Tomás Zaba,
Nicholus Tint Zaw, and Zython Paul Lachica&lt;/strong&gt;, all of whom use R workflows in the wild for
work either on their own or with teams.&lt;/p&gt;</description></item><item><title>rOpenSci News Digest, May 2024</title><link>https://ropensci.org/blog/2024/05/24/ropensci-news-may-2024/</link><pubDate>Fri, 24 May 2024 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2024/05/24/ropensci-news-may-2024/</guid><description>
&lt;!-- Before sending DELETE THE INDEX_CACHE and re-knit! --&gt;
&lt;p&gt;Dear rOpenSci friends, it&amp;rsquo;s time for our monthly news roundup!&lt;/p&gt;
&lt;!-- blabla --&gt;
&lt;p&gt;You can read this post &lt;a href="https://ropensci.org/blog/2024/05/24/ropensci-news-may-2024"&gt;on our blog&lt;/a&gt;.
Now let&amp;rsquo;s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;h3&gt;
rOpenSci in the Research Organization Registry
&lt;/h3&gt;&lt;p&gt;rOpenSci was added to the &lt;a href="https://ror.org/"&gt;Research Organization Registry&lt;/a&gt; (ROR) in its latest &lt;a href="https://github.com/ror-community/ror-updates/releases/tag/v1.46"&gt;release&lt;/a&gt;. The ROR is a global, community-led registry of open persistent identifiers for research organizations. ROR IDs help link and disambiguate metadata about organizations in the scholarly record, much like DOIs and ORCiDs do for manuscripts and researchers. &lt;a href="https://ropensci.org/blog/2018/03/16/thanking-reviewers-in-metadata/"&gt;Linked metadata is rOpenSci&amp;rsquo;s love language ❤️ !&lt;/a&gt; Find us at &lt;a href="https://ror.org/019jywm96"&gt;https://ror.org/019jywm96&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Communication Tips for your Open-Source Project</title><link>https://ropensci.org/blog/2024/05/17/communication-tips-oss-project/</link><pubDate>Fri, 17 May 2024 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2024/05/17/communication-tips-oss-project/</guid><description><i><a href="https://ropensci.org/es/blog/2024/05/17/communication-tips-oss-project/">Read it in: Español</a>.</i><i><a href="https://ropensci.org/pt/blog/2024/05/17/communica-dicas-oss-projeto/">Read it in: Português</a>.</i>
&lt;p&gt;Do you maintain an open-source project like an R package or a collection thereof, and wonder how to best use various communication channels to inform and engage with your community of users?
We&amp;rsquo;ve consolidated this list of tips.
Some of them are required in our opinion, others are simply nice to have.&lt;/p&gt;
&lt;h2&gt;
Required: Having good release notes
&lt;/h2&gt;&lt;p&gt;Since you&amp;rsquo;re developing a product, the first act of communication is to write informative release notes.
Release notes generally describe updates and changes, commonly in a file called &lt;code&gt;NEWS.md&lt;/code&gt;. These files generally have one header per release, with sub-headers used to group changes in meaningful categories.&lt;/p&gt;</description></item><item><title>Social Coworking and Office Hours - Meet rOpenSci's new Executive Director!</title><link>https://ropensci.org/events/coworking-2024-05/</link><pubDate>Tue, 07 May 2024 18:00:00 +0000</pubDate><guid>https://ropensci.org/events/coworking-2024-05/</guid><description>
&lt;!--
```{r}
d &lt;- lubridate::ymd_hms('2024-05-07 09:00:00', tz = 'America/Vancouver')
lubridate::with_tz(d, 'UTC')
lubridate::with_tz(d, 'America/Winnipeg')
```
--&gt;
&lt;p&gt;&lt;strong&gt;Join us for 2 hours Tuesday May 07, 09:00 Americas Pacific (16:00 UTC) for
&lt;a href="https://ropensci.org/blog/2023/06/21/coworking/"&gt;Social Coworking + Office Hours&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This month we&amp;rsquo;re focusing on the theme &lt;strong&gt;Meet rOpenSci&amp;rsquo;s new Executive Director&lt;/strong&gt;
with cohost host &lt;strong&gt;Noam Ross&lt;/strong&gt;, who is excited to be stepping into the role of
&lt;a href="https://ropensci.org/blog/2024/03/29/hello-from-our-new-executive-director/"&gt;Executive Director&lt;/a&gt;
and wants to meet you and hear about what you think of rOpenSci. Noam was an
rOpenSci Strategic Advisor and has been a Software Peer Review Editor since 2015
and the Software Review Lead since 2019.&lt;/p&gt;</description></item><item><title>rOpenSci News Digest, April 2024</title><link>https://ropensci.org/blog/2024/04/22/ropensci-news-april-2024/</link><pubDate>Mon, 22 Apr 2024 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2024/04/22/ropensci-news-april-2024/</guid><description>
&lt;!-- Before sending DELETE THE INDEX_CACHE and re-knit! --&gt;
&lt;p&gt;Dear rOpenSci friends, it&amp;rsquo;s time for our monthly news roundup!&lt;/p&gt;
&lt;!-- blabla --&gt;
&lt;p&gt;You can read this post &lt;a href="https://ropensci.org/blog/2024/04/22/ropensci-news-april-2024"&gt;on our blog&lt;/a&gt;.
Now let&amp;rsquo;s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;h3&gt;
Coworking
&lt;/h3&gt;&lt;p&gt;Read &lt;a href="https://ropensci.org/blog/2023/06/21/coworking/"&gt;all about coworking&lt;/a&gt;!&lt;/p&gt;
&lt;p&gt;Join us for social coworking &amp;amp; office hours monthly on first Tuesdays!
Hosted by Steffi LaZerte and various community hosts.
Everyone welcome.
No RSVP needed.
Consult our &lt;a href="https://ropensci.org/events"&gt;Events&lt;/a&gt; page to find your local time and how to join.&lt;/p&gt;</description></item><item><title>Fostering Equity and Leadership: the rOpenSci Champions Program Selection Process</title><link>https://ropensci.org/blog/2024/04/18/champions-program-2024/</link><pubDate>Thu, 18 Apr 2024 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2024/04/18/champions-program-2024/</guid><description>
&lt;p&gt;The goal of the &lt;a href="https://ropensci.org/champions/"&gt;rOpenSci Champions Program&lt;/a&gt; is to enable more members of historically excluded groups to participate in, benefit from, and become leaders in the R, research software engineering, and open source and open science communities. This program includes 1-on-1 mentoring for the Champions as they complete a project and perform outreach activities in their local communities.&lt;/p&gt;
&lt;p&gt;Every year, rOpenSci opens a call for applications for the roles of Champions and Mentors which are selected following a rigorous process that we describe in this blog post.&lt;/p&gt;</description></item><item><title>How rOpenSci performs peer-review (champions training)</title><link>https://ropensci.org/events/2024-04-17-how-ropensci-review/</link><pubDate>Wed, 17 Apr 2024 17:00:00 +0000</pubDate><guid>https://ropensci.org/events/2024-04-17-how-ropensci-review/</guid><description/></item><item><title>R-Universe Documentation Gets a Boost from Google Season of Docs</title><link>https://ropensci.org/blog/2024/04/12/gsod-announcement/</link><pubDate>Fri, 12 Apr 2024 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2024/04/12/gsod-announcement/</guid><description>
&lt;p&gt;We are excited to announce that &lt;a href="https://r-universe.dev/"&gt;R-Universe&lt;/a&gt; has been awarded a &lt;a href="https://developers.google.com/season-of-docs"&gt;Google Season of Docs&lt;/a&gt; grant. R-Universe is rOpenSci&amp;rsquo;s platform for testing, building, distributing, and discovering R packages, led by &lt;a href="https://ropensci.org/author/jeroen-ooms"&gt;Jeroen Ooms&lt;/a&gt;. It provides no-setup continuous integration, compilation for all platforms (including WebR!), accessible HTML R package manuals, a comprehensive API, and the ability for users or organizations to create their own &amp;ldquo;universes&amp;rdquo; - package repositories with their standards, participation and publishing criteria. R-Universe seamlessly incorporates packages from CRAN and Bioconductor: tracks, builds, and tests over 24,000 packages by 12,000 maintainers and 21,000 contributors, with over 600 custom package registries so far.&lt;/p&gt;</description></item><item><title>How to contribute to open projects and communities</title><link>https://ropensci.org/events/champions-contribute-oss-2024/</link><pubDate>Wed, 03 Apr 2024 09:00:00 +0000</pubDate><guid>https://ropensci.org/events/champions-contribute-oss-2024/</guid><description/></item><item><title>Social Coworking and Office Hours - Sharing your work with Quarto</title><link>https://ropensci.org/events/coworking-2024-04/</link><pubDate>Tue, 02 Apr 2024 14:00:00 +0000</pubDate><guid>https://ropensci.org/events/coworking-2024-04/</guid><description>
&lt;!--
```{r}
d &lt;- lubridate::ymd_hms('2024-04-02 14:00:00', tz = 'Europe/Paris')
lubridate::with_tz(d, 'UTC')
lubridate::with_tz(d, 'America/Winnipeg')
```
--&gt;
&lt;p&gt;&lt;strong&gt;Join us for 2 hours Tuesday April 02, 14:00 European Central (12:00 UTC) for
&lt;a href="https://ropensci.org/blog/2023/06/21/coworking/"&gt;Social Coworking + Office Hours&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This month we&amp;rsquo;re focusing on the theme &lt;strong&gt;Sharing your work with Quarto&lt;/strong&gt;
with community host &lt;strong&gt;Pao Corrales&lt;/strong&gt;, rOpenSci Champion, Atmospheric Scientist,
R instructor, and enthusiastic creator of websites.&lt;/p&gt;
&lt;p&gt;Come for the full 2 hrs or only as long as you need!&lt;/p&gt;</description></item><item><title>From the Founding Director: My Farewell to rOpenSci</title><link>https://ropensci.org/blog/2024/03/29/from-the-founding-director-my-farewell-to-ropensci/</link><pubDate>Fri, 29 Mar 2024 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2024/03/29/from-the-founding-director-my-farewell-to-ropensci/</guid><description><i><a href="https://ropensci.org/es/blog/2024/03/29/from-the-founding-director-my-farewell-to-ropensci/">Read it in: Español</a>.</i>
&lt;p&gt;Dear rOpenSci community,&lt;/p&gt;
&lt;p&gt;This is a bit of a bittersweet announcement&amp;hellip; After nearly 13 years, it&amp;rsquo;s time for me to step down as the Executive Director of rOpenSci.&lt;/p&gt;
&lt;p&gt;In the summer of 2011 I co-founded rOpenSci alongside a group of dedicated colleagues. What began as a casual collaboration among open science enthusiasts quickly evolved into something far more meaningful. We never imagined it would become the global initiative it is today, with a team spanning the world and impacting countless researchers.&lt;/p&gt;</description></item><item><title>Hello from our New Executive Director!</title><link>https://ropensci.org/blog/2024/03/29/hello-from-our-new-executive-director/</link><pubDate>Fri, 29 Mar 2024 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2024/03/29/hello-from-our-new-executive-director/</guid><description><i><a href="https://ropensci.org/es/blog/2024/03/29/hello-from-our-new-executive-director/">Read it in: Español</a>.</i>
&lt;p&gt;I am pleased, excited, and humbled to announce that I am stepping into the role of Executive Director of rOpenSci starting April 1.&lt;/p&gt;
&lt;p&gt;First, let me give my gratitude to our outgoing Executive Director and friend Karthik Ram for his leadership and mentorship running rOpenSci the past decade. He’s been a steady hand and visionary that helped our community accomplish so much together in this time. Thanks to him and the rest of &lt;a href="https://ropensci.org/about/#team"&gt;the team&lt;/a&gt; for entrusting me with this role.&lt;/p&gt;</description></item><item><title>rOpenSci News Digest, March 2024</title><link>https://ropensci.org/blog/2024/03/29/ropensci-news-march-2024/</link><pubDate>Fri, 29 Mar 2024 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2024/03/29/ropensci-news-march-2024/</guid><description>
&lt;!-- Before sending DELETE THE INDEX_CACHE and re-knit! --&gt;
&lt;p&gt;Dear rOpenSci friends, it&amp;rsquo;s time for our monthly news roundup!&lt;/p&gt;
&lt;!-- blabla --&gt;
&lt;p&gt;You can read this post &lt;a href="https://ropensci.org/blog/2024/03/29/ropensci-news-march-2024"&gt;on our blog&lt;/a&gt;.
Now let&amp;rsquo;s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;h3&gt;
Leadership changes at rOpenSci
&lt;/h3&gt;&lt;p&gt;After 13 years at the helm of rOpenSci, our founding executive director Karthik Ram is stepping down.
Noam Ross, rOpenSci&amp;rsquo;s current lead for peer review, will be our new Executive Director.&lt;br&gt;
Karthik will remain a key advisor to rOpenSci.
We thank him for his years of leadership and service to the community!&lt;/p&gt;</description></item><item><title>rOpenSci Champions Pilot Year: Projects Wrap-Up</title><link>https://ropensci.org/blog/2024/03/20/champions-program-projects-cohort1/</link><pubDate>Wed, 20 Mar 2024 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2024/03/20/champions-program-projects-cohort1/</guid><description>
&lt;p&gt;Our first cohort of the &lt;a href="https://ropensci.org/champions/"&gt;rOpenSci Champions Program&lt;/a&gt; has now completed the second phase of the program by developing their project and carrying out outreach activities. In this article, we share each Champion&amp;rsquo;s project, their achievements and their outreach activities.&lt;/p&gt;
&lt;h2&gt;
Champions&amp;rsquo; Projects
&lt;/h2&gt;&lt;p&gt;In their applications Champions choose to develop a new package or to participate in the review process as authors or reviewers.&lt;/p&gt;
&lt;h3&gt;
Projects related to rOpenSci Software Peer Review
&lt;/h3&gt;&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Carolina Pradier&lt;/strong&gt; from Argentina worked on the &lt;a href="https://docs.ropensci.org/eph/"&gt;eph&lt;/a&gt; package, which facilitated working with data from the Permanent Household Survey - INDEC, Argentina. Carolina added functionality to the package, reduced the number of dependencies, improved error messages and increased test coverage before submitting the package for review. After peer review in Spanish, her package is now part of the rOpenSci suite and was published on CRAN. Her mentor was &lt;a href="https://ropensci.org/author/athanasia-mo-mowinckel/"&gt;Athanasia Mo Mowinckel&lt;/a&gt; from Norway.&lt;/p&gt;</description></item><item><title>An Example of the DRY/DAMP Principles for Package Tests</title><link>https://ropensci.org/blog/2024/03/18/dry-damp/</link><pubDate>Mon, 18 Mar 2024 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2024/03/18/dry-damp/</guid><description><i><a href="https://ropensci.org/es/blog/2024/03/18/dry-damp/">Read it in: Español</a>.</i><i><a href="https://ropensci.org/pt/blog/2024/03/18/dry-damp/">Read it in: Português</a>.</i>
&lt;p&gt;rOpenSci&amp;rsquo;s &lt;a href="https://ropensci.org/blog/2024/02/15/champions-program-champions-2024/"&gt;second cohort of Champions has been onboarded&lt;/a&gt;!
Their training first started with a &lt;a href="https://ropensci.org/blog/2024/02/22/beautiful-code/"&gt;session on code style&lt;/a&gt;, was followed by three sessions on the basics of R package development, and ended with a session on &lt;a href="https://rpkgdev-rocket-2024.netlify.app/"&gt;advanced R package development&lt;/a&gt;, which consisted of a potpourri of tips with discussion, followed by time for applying these principles to the participants&amp;rsquo; packages.
Here, I want to share one of the topics covered: Package testing, and in particular, the DRY (&amp;ldquo;don&amp;rsquo;t repeat yourself&amp;rdquo;) and DAMP (&amp;ldquo;descriptive and meaningful phrases&amp;rdquo;) principles.
For this topic, we used a &lt;a href="https://github.com/maelle/swamp"&gt;GitHub repository&lt;/a&gt;, containing an R package whose different commits illustrate the two principles. In each step we&amp;rsquo;ll share a commit or diff illustrating the changes made.&lt;/p&gt;</description></item><item><title>rOpenSci Dev Guide 0.9.0: Multilingual Now! And Better</title><link>https://ropensci.org/blog/2024/03/11/devguide-0.9.0/</link><pubDate>Mon, 11 Mar 2024 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2024/03/11/devguide-0.9.0/</guid><description><i><a href="https://ropensci.org/es/blog/2024/03/11/r_open_sci_dev_guide_0_9_0_ahora_multiling%C3%BCe_y_mejor/">Read it in: Español</a>.</i>
&lt;p&gt;rOpenSci Software Peer Review&amp;rsquo;s guidance is gathered in an &lt;a href="https://devguide.ropensci.org/booknews"&gt;online book&lt;/a&gt; that keeps improving!
This blog post summarises what&amp;rsquo;s new in our Dev Guide 0.9.0, with all changes listed in the &lt;a href="https://devguide.ropensci.org/booknews.html"&gt;changelog&lt;/a&gt;.&lt;/p&gt;
&lt;h2&gt;
Now available in Spanish!
&lt;/h2&gt;&lt;p&gt;Our guide is now bilingual (English and &lt;a href="https://devguide.ropensci.org/es/index.es.html"&gt;Spanish&lt;/a&gt;), thanks to work by &lt;a href="https://ropensci.org/author/yanina-bellini-saibene/"&gt;Yanina Bellini Saibene&lt;/a&gt;, &lt;a href="https://ropensci.org/author/elio-campitelli/"&gt;Elio Campitelli&lt;/a&gt; and &lt;a href="https://ropensci.org/author/pao-corrales/"&gt;Pao Corrales&lt;/a&gt;, and thanks to &lt;a href="https://ropensci.org/blog/2023/01/12/multilingual-publishing-en/"&gt;support of the Chan Zuckerberg Initiative, NumFOCUS, and the R Consortium&lt;/a&gt;.
&lt;a href="https://devguide.ropensci.org/es/index.es.html"&gt;Read the guide in Spanish&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;You can find out more about our multilingual publishing project in the materials and recording from a recent &lt;a href="https://ropensci.org/commcalls/nov2023-multilingual/"&gt;community call&lt;/a&gt;.
Useful tools produced by the project include our &lt;a href="https://translationguide.ropensci.org/"&gt;translation guide&lt;/a&gt;, the &lt;a href="https://docs.ropensci.org/babelquarto/"&gt;babelquarto package&lt;/a&gt; to render multilingual Quarto books or websites, and the &lt;a href="https://docs.ropensci.org/babeldown/"&gt;babeldown package&lt;/a&gt; to create and update translations using the DeepL API.&lt;/p&gt;</description></item><item><title>Marketing Ideas For Your Package</title><link>https://ropensci.org/blog/2024/03/07/package-marketing/</link><pubDate>Thu, 07 Mar 2024 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2024/03/07/package-marketing/</guid><description><i><a href="https://ropensci.org/es/blog/2024/03/07/package-marketing/">Read it in: Español</a>.</i><i><a href="https://ropensci.org/pt/blog/2024/03/07/package-marketing/">Read it in: Português</a>.</i>
&lt;p&gt;Now that you have created your package, presenting it to the world is a crucial step to &lt;strong&gt;gain visibility and attract users&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;Marketing your package effectively contributes to reaching the people your package can support, finding users to assist you in maintaining and improving your package and allowing you to learn about how people use it.&lt;/p&gt;
&lt;p&gt;In this blog post we suggest a series of activities and tools for advertising your package.&lt;/p&gt;</description></item><item><title>Social Coworking and Office Hours - Dates, Times and Timezones in R</title><link>https://ropensci.org/events/coworking-2024-03/</link><pubDate>Tue, 05 Mar 2024 03:00:00 +0000</pubDate><guid>https://ropensci.org/events/coworking-2024-03/</guid><description>
&lt;!--
```{r}
d &lt;- lubridate::ymd_hms('2024-03-05 09:00:00', tz = 'Australia/Perth')
lubridate::with_tz(d, 'UTC')
lubridate::with_tz(d, 'America/Winnipeg')
```
--&gt;
&lt;p&gt;&lt;strong&gt;Join us for 2 hours Tuesday March 05, 09:00 Australian Western (01:00 UTC) for
&lt;a href="https://ropensci.org/blog/2023/06/21/coworking/"&gt;Social Coworking + Office Hours&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This month we&amp;rsquo;re focusing on the theme &lt;strong&gt;Dates, Times and Timezones in R&lt;/strong&gt;
with community host &lt;strong&gt;Steffi LaZerte&lt;/strong&gt;, rOpenSci’s community assistant who
deals with timezones way too often for comfort!&lt;/p&gt;
&lt;p&gt;Come for the full 2 hrs or only as long as you need!&lt;/p&gt;</description></item><item><title>rOpenSci Code of Conduct Annual Review</title><link>https://ropensci.org/blog/2024/03/04/conduct2023/</link><pubDate>Mon, 04 Mar 2024 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2024/03/04/conduct2023/</guid><description>
&lt;p&gt;Our community is our best asset. It’s so important to us, it’s in our &lt;a href="https://ropensci.org/about/"&gt;mission statement&lt;/a&gt;. We recognize that communities are not inclusive by default; they require deliberate attention, including an enforceable &lt;a href="https://ropensci.org/code-of-conduct"&gt;Code of Conduct&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;rOpenSci is committed to providing a safe, inclusive, welcoming, and harassment-free experience for everyone. We welcome people of all backgrounds and identities, including but not limited to gender, gender identity and expression, age, sexual orientation, disability, physical appearance, body size, race, ethnicity, religion (or lack thereof), or technology choices. We are anti-racist. We welcome anyone, no matter their technical expertise, career stage, or work sector.&lt;/p&gt;</description></item><item><title>Package Development: the Mechanics (champions training)</title><link>https://ropensci.org/events/2024-03-01-pkg-dev-mechanics-champions/</link><pubDate>Fri, 01 Mar 2024 14:00:00 +0000</pubDate><guid>https://ropensci.org/events/2024-03-01-pkg-dev-mechanics-champions/</guid><description/></item><item><title>Package Development: Not Rocket Science (champions training)</title><link>https://ropensci.org/events/2024-04-01-pkg-dev-not-rocket-science-champions/</link><pubDate>Fri, 01 Mar 2024 11:00:00 +0000</pubDate><guid>https://ropensci.org/events/2024-04-01-pkg-dev-not-rocket-science-champions/</guid><description/></item><item><title>Help make qualtRics better! Code contributions wanted</title><link>https://ropensci.org/blog/2024/03/01/qualtrics-call-help/</link><pubDate>Fri, 01 Mar 2024 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2024/03/01/qualtrics-call-help/</guid><description>
&lt;p&gt;The package &lt;a href="https://docs.ropensci.org/qualtRics"&gt;qualtRics&lt;/a&gt; maintained by &lt;a href="https://ropensci.org/author/julia-silge"&gt;Julia Silge&lt;/a&gt; together with &lt;a href="https://ropensci.org/author/joseph-obrien"&gt;Joseph O’Brien&lt;/a&gt; provides functions to access survey results directly into R using the Qualtrics API. &lt;a href="https://www.qualtrics.com/about/"&gt;Qualtrics&lt;/a&gt; is an online survey and data collection software platform.&lt;/p&gt;
&lt;h2&gt;
Help test or improve qualtRics!
&lt;/h2&gt;&lt;p&gt;Are you a heavy user of the Qualtrics survey tooling in general, and of the qualtRics R package in particular? Then you can help build and test the package.&lt;/p&gt;
&lt;h2&gt;
How to help?
&lt;/h2&gt;&lt;p&gt;There are a few specific needs that the qualtRics package has today.&lt;/p&gt;</description></item><item><title>Help users and developers of targets by answering questions!</title><link>https://ropensci.org/blog/2024/02/29/targets-call-help/</link><pubDate>Thu, 29 Feb 2024 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2024/02/29/targets-call-help/</guid><description>
&lt;p&gt;The package &lt;a href="https://docs.ropensci.org/targets"&gt;targets&lt;/a&gt; maintained by &lt;a href="https://ropensci.org/author/will-landau"&gt;Will Landau&lt;/a&gt;, and its companion packages, are pipeline tools, that coordinate the pieces of computationally demanding analysis projects.&lt;/p&gt;
&lt;h2&gt;
Help sustain targets discussion forums!
&lt;/h2&gt;&lt;p&gt;Are you a routined user of the targets package and of more &lt;a href="https://wlandau.github.io/targetopia/"&gt;targetopia&lt;/a&gt; packages?
How about helping answer users questions on the GitHub discussion and issue forums for these packages?
This would help lighten the maintenance load of those packages, and you’d get to help other users directly.&lt;/p&gt;</description></item><item><title>Help make assertr better! Come close issues</title><link>https://ropensci.org/blog/2024/02/27/assertr-call-help/</link><pubDate>Tue, 27 Feb 2024 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2024/02/27/assertr-call-help/</guid><description>
&lt;p&gt;The package &lt;a href="https://docs.ropensci.org/assertr"&gt;assertr&lt;/a&gt; maintained by &lt;a href="https://ropensci.org/author/tony-fischetti/"&gt;Tony Fischetti&lt;/a&gt;, provides functionality to assert conditions that have to be met so that errors in data used in analysis pipelines can fail quickly.
The provided functionality is similar to &lt;code&gt;stopifnot()&lt;/code&gt; but more powerful, friendly, and easier for use in pipelines.&lt;/p&gt;
&lt;h2&gt;
Contributed to assertr!
&lt;/h2&gt;&lt;p&gt;The assertr &lt;a href="https://github.com/tonyfischetti/assertr/issues"&gt;issue tracker&lt;/a&gt; has a few tickets that you could help with, please have a &lt;a href="https://github.com/tonyfischetti/assertr/issues"&gt;look&lt;/a&gt;.
You can also &lt;a href="https://docs.github.com/en/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository"&gt;subscribe&lt;/a&gt; to be notified of new issues opened in this repository.&lt;/p&gt;</description></item><item><title>rOpenSci News Digest, February 2024</title><link>https://ropensci.org/blog/2024/02/23/news-february-2024/</link><pubDate>Fri, 23 Feb 2024 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2024/02/23/news-february-2024/</guid><description>
&lt;!-- Before sending DELETE THE INDEX_CACHE and re-knit! --&gt;
&lt;p&gt;Dear rOpenSci friends, it&amp;rsquo;s time for our monthly news roundup!&lt;/p&gt;
&lt;!-- blabla --&gt;
&lt;p&gt;You can read this post &lt;a href="https://ropensci.org/blog/2024/02/23/news-february-2024"&gt;on our blog&lt;/a&gt;.
Now let&amp;rsquo;s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;h3&gt;
rOpenSci 2023 Code of Conduct Transparency Report
&lt;/h3&gt;&lt;p&gt;Transparency reports are intended to help the community understand what kind of Code of Conduct incidents we receive reports about annually and how the Code of Conduct team responds, always preserving the privacy of the people who experience or report incidents.&lt;/p&gt;</description></item><item><title>Beautiful Code, Because We’re Worth It!</title><link>https://ropensci.org/blog/2024/02/22/beautiful-code/</link><pubDate>Thu, 22 Feb 2024 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2024/02/22/beautiful-code/</guid><description><i><a href="https://ropensci.org/es/blog/2024/02/22/beautiful-code/">Read it in: Español</a>.</i><i><a href="https://ropensci.org/pt/blog/2024/02/22/codigo-bonito/">Read it in: Português</a>.</i>
&lt;p&gt;rOpenSci&amp;rsquo;s &lt;a href="https://ropensci.org/blog/2024/02/15/champions-program-champions-2024/"&gt;second cohort of champions was onboarded&lt;/a&gt;!
Their training started with a session on code style, which we will summarize here in this post.
Knowing more about code quality is relevant to all Champion projects, be it creating a new package, submitting a package to software review, or reviewing a package.
This training session consisted of a talk and discussion, whereas the next package development training sessions will be more hands-on.&lt;/p&gt;</description></item><item><title>Read and Play Digital Music (MIDI) in R using the *fluidsynth* package</title><link>https://ropensci.org/blog/2024/02/20/fluidsynth/</link><pubDate>Tue, 20 Feb 2024 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2024/02/20/fluidsynth/</guid><description>
&lt;p&gt;A few weeks ago, prof &lt;a href="https://www.crumplab.com/people/matt_crump.html"&gt;Matt Crump&lt;/a&gt; wrote a &lt;a href="https://homophony.quest/blog/32_1_30_24_R_synth/"&gt;blog post&lt;/a&gt; in which he explores tools to handle MIDI data in R, in preparation for a cognition experiment that involves creating musical stimuli. In the article he ends up using a mix of external command line tools &lt;code&gt;ffmpeg&lt;/code&gt; and &lt;code&gt;fluidsynth&lt;/code&gt; and a python module.&lt;/p&gt;
&lt;p&gt;This solution of course hurts my R soul: Invoking shell commands from R &lt;a href="https://ropensci.org/blog/2021/09/13/system-calls-r-package/#downsides-of-system-commands"&gt;is unreliable&lt;/a&gt; and users are often unable (or unwilling) to install all kinds of extra software on their machine. Some tools may not even be available for all platforms, or create conflicts, or the user might not have permission to install software in the first place. So let&amp;rsquo;s see what we can do to improve the situation.&lt;/p&gt;</description></item><item><title>Help make waywiser better! User requests wanted</title><link>https://ropensci.org/blog/2024/02/19/waywiser-call-help/</link><pubDate>Mon, 19 Feb 2024 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2024/02/19/waywiser-call-help/</guid><description>
&lt;p&gt;The package &lt;a href="https://docs.ropensci.org/waywiser"&gt;waywiser&lt;/a&gt; maintained by &lt;a href="https://ropensci.org/author/mike-mahoney"&gt;Mike Mahoney&lt;/a&gt; provides ergonomic methods for assessing spatial models.
Assessing predictive models of spatial data can be challenging,
both because these models are typically built for extrapolating outside the original region represented by training data and due to potential spatially structured errors,
with &amp;ldquo;hot spots&amp;rdquo; of higher than expected error clustered geographically due to spatial structure in the underlying data.
The waywiser package tries to make it easier,
providing methods for assessing models fit to spatial data,
including approaches for measuring the spatial structure of model errors, assessing model predictions at multiple spatial scales,
and evaluating where predictions can be made safely.
Functions in waywiser are designed to be useful on their own,
and additionally integrate naturally with the tidymodels framework.&lt;/p&gt;</description></item><item><title>Beautiful code, because we’re worth it! (champions training)</title><link>https://ropensci.org/events/2024-02-15-stylish-code/</link><pubDate>Thu, 15 Feb 2024 18:00:00 +0000</pubDate><guid>https://ropensci.org/events/2024-02-15-stylish-code/</guid><description/></item><item><title>rOpenSci Champions Program. Mentorship Training and Orientation</title><link>https://ropensci.org/events/2024-02-15-mentor-orientation/</link><pubDate>Thu, 15 Feb 2024 14:00:00 +0000</pubDate><guid>https://ropensci.org/events/2024-02-15-mentor-orientation/</guid><description/></item><item><title>Introducing rOpenSci Champions - Cohort 2023-2024</title><link>https://ropensci.org/blog/2024/02/15/champions-program-champions-2024/</link><pubDate>Thu, 15 Feb 2024 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2024/02/15/champions-program-champions-2024/</guid><description>
&lt;p&gt;The rOpenSci Champions Program starts this 2024 with a new cohort of Champions. We are pleased to introduce you to our Champions and their projects!&lt;/p&gt;
&lt;h2&gt;
Ezekiel Adebayo Ogundepo
&lt;/h2&gt;&lt;figure&gt;&lt;img src="https://ropensci.org/img/team/ezekiel-ogundepo.png"
alt="Profile photo of Ezekiel Adebayo Ogundepo." width="300"&gt;&lt;figcaption&gt;
&lt;p&gt;&lt;strong&gt;Ezekiel Adebayo Ogundepo - GBG Analytics Limited&lt;/strong&gt;&lt;/p&gt;
&lt;/figcaption&gt;
&lt;/figure&gt;
&lt;p&gt;Hello, I&amp;rsquo;m Ezekiel, a data science professional deeply fascinated by the intersection of mathematics, statistics, and real-world challenges. My journey in data science has been marked by several achievements, including being a Certified RStudio Tidyverse Instructor, a Mastercard Scholar, a Federal Government of Nigeria (FSB) Scholar, an UNLEASH Talent, a Heidelberg Laureate Forum (HLF) Fellow and a Global Partnership for Sustainable Development Data Fellow.&lt;/p&gt;</description></item><item><title>Fostering Diversity and Sustainability in the Open Source Scientific Software Community. The rOpenSci Champions Program</title><link>https://ropensci.org/events/opdevroom-2024/</link><pubDate>Sat, 10 Feb 2024 10:20:00 +0000</pubDate><guid>https://ropensci.org/events/opdevroom-2024/</guid><description>
&lt;p&gt;Research software plays a crucial role in advancing knowledge and innovation, and its development should be inclusive and representative of the diverse communities it serves. Unfortunately, the R and research software communities face a lack of diversity, with developers predominantly being white, male, and from a limited number of countries. This lack of inclusivity raises concerns about the long-term sustainability and utility of projects. In response to this challenge, the rOpenSci Champions Program specifically targets individuals from underrepresented groups who are keen on contributing to rOpenSci and the broader open science ecosystem. In this talk, we will share the motivations behind the creation of the rOpenSci Champions Program, exploring its goals, structure, and the opportunities it provides for participants. We will share insights gained from the implementation of the program’s pilot phase, highlighting key outcomes, success stories, and lessons learned. Attendees will gain a deeper understanding of the strategies employed to foster a more inclusive and diverse developer community in the R ecosystem. By showcasing the rOpenSci Champions Program, this talk aims to inspire similar initiatives across the open source landscape and contribute to the ongoing dialogue on enhancing diversity, sustainability, and collaboration in research software development. Talk license:CC-BY.&lt;/p&gt;</description></item><item><title>Social Coworking and Office Hours - R-Universe Office Hours</title><link>https://ropensci.org/events/coworking-2024-02/</link><pubDate>Tue, 06 Feb 2024 19:00:00 +0000</pubDate><guid>https://ropensci.org/events/coworking-2024-02/</guid><description>
&lt;!--
```{r}
d &lt;- lubridate::ymd_hms('2024-02-06 09:00:00', tz = 'America/Vancouver')
lubridate::with_tz(d, 'UTC')
lubridate::with_tz(d, 'America/Winnipeg')
```
--&gt;
&lt;p&gt;&lt;strong&gt;Join us for 2 hours Tuesday February 06, 09:00 Americas Pacific (17:00 UTC) for
&lt;a href="https://ropensci.org/blog/2023/06/21/coworking/"&gt;Social Coworking + Office Hours&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This month we&amp;rsquo;re focusing on the theme &lt;strong&gt;&lt;a href="https://r-universe.dev"&gt;R-Universe&lt;/a&gt; Office Hours&lt;/strong&gt;
with community host &lt;strong&gt;Jeroen Ooms&lt;/strong&gt;, rOpenSci Infrastructure Engineer and creator
of the R-Universe!&lt;/p&gt;
&lt;p&gt;Come for the full 2 hrs or only as long as you need!&lt;/p&gt;
&lt;h3&gt;
Cowork
&lt;/h3&gt;&lt;ul&gt;
&lt;li&gt;Explore what the &lt;a href="https://r-universe.dev"&gt;R-Universe&lt;/a&gt; has to offer&lt;/li&gt;
&lt;li&gt;Create your own R-Universe&lt;/li&gt;
&lt;li&gt;Cowork independently on work related to R
&lt;ul&gt;
&lt;li&gt;Plan out that package you’ve always wanted to create&lt;/li&gt;
&lt;li&gt;Work on packages that tend to be neglected&lt;/li&gt;
&lt;li&gt;What ever you need to get done!&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;
Socialize/Network
&lt;/h3&gt;&lt;ul&gt;
&lt;li&gt;Meet community host, &lt;strong&gt;Jeroen Ooms&lt;/strong&gt;, and ask questions about the R-Universe or
troubleshoot your R-Universe problems&lt;/li&gt;
&lt;li&gt;Meet other R users and rOpenSci staff in Zoom&lt;/li&gt;
&lt;li&gt;Get answers to your questions
&lt;ul&gt;
&lt;li&gt;Ask your hosts&lt;/li&gt;
&lt;li&gt;Ask your fellow coworkers&lt;/li&gt;
&lt;li&gt;Discuss your work, best practices, or get advice and resources&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Answer other coworkers&amp;rsquo; questions!&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;We host
&lt;a href="https://ropensci.org/blog/2023/06/21/coworking/"&gt;Social Coworking + Office Hours&lt;/a&gt;
on the first Tuesday of each month, alternating among timezones to
accommodate different parts of the world.&lt;/p&gt;</description></item><item><title>Please Shut Up! Verbosity Control in Packages</title><link>https://ropensci.org/blog/2024/02/06/verbosity-control-packages/</link><pubDate>Tue, 06 Feb 2024 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2024/02/06/verbosity-control-packages/</guid><description><i><a href="https://ropensci.org/es/blog/2024/02/06/control-vervosidad-paquetes/">Read it in: Español</a>.</i><i><a href="https://ropensci.org/pt/blog/2024/02/06/verbosidade-control-pacotes/">Read it in: Português</a>.</i>
&lt;p&gt;We recently introduced a new paragraph to the development version of our dev guide&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Provide a way for users to opt out of verbosity, preferably at the package level: make message creation dependent on an environment variable or option (like &lt;a href="https://usethis.r-lib.org/reference/ui.html?q=usethis.quiet#silencing-output"&gt;&amp;ldquo;usethis.quiet&amp;rdquo;&lt;/a&gt; in the usethis package), rather than on a function parameter. The control of messages could be on several levels (&amp;ldquo;none, &amp;ldquo;inform&amp;rdquo;, &amp;ldquo;debug&amp;rdquo;) rather than logical (no messages at all / all messages). Control of verbosity is useful for end users but also in tests. More interesting comments can be found in an &lt;a href="https://github.com/tidyverse/design/issues/42"&gt;issue of the tidyverse design guide&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>rOpenSci News Digest, January 2024</title><link>https://ropensci.org/blog/2024/01/25/news-january-2024/</link><pubDate>Thu, 25 Jan 2024 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2024/01/25/news-january-2024/</guid><description>
&lt;!-- Before sending DELETE THE INDEX_CACHE and re-knit! --&gt;
&lt;p&gt;Dear rOpenSci friends, it&amp;rsquo;s time for our monthly news roundup!&lt;/p&gt;
&lt;!-- blabla --&gt;
&lt;p&gt;You can read this post &lt;a href="https://ropensci.org/blog/2024/01/25/news-january-2024"&gt;on our blog&lt;/a&gt;.
Now let&amp;rsquo;s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;h3&gt;
R-Universe
&lt;/h3&gt;&lt;p&gt;The R-Universe now builds MacOS ARM64 binaries for use on Apple Silicon (aka M1/M2/M3) systems!&lt;/p&gt;
&lt;p&gt;Find out more in the related &lt;a href="https://ropensci.org/blog/2024/01/14/runiverse-arm64/"&gt;tech note&lt;/a&gt;.&lt;/p&gt;
&lt;h3&gt;
Coworking
&lt;/h3&gt;&lt;p&gt;Read &lt;a href="https://ropensci.org/blog/2023/06/21/coworking/"&gt;all about coworking&lt;/a&gt; in our recent &lt;a href="https://ropensci.org/blog/2023/06/21/coworking/"&gt;post&lt;/a&gt;!&lt;/p&gt;</description></item><item><title>How to Update a Translation with Babeldown</title><link>https://ropensci.org/blog/2024/01/16/deepl-update-babeldown/</link><pubDate>Tue, 16 Jan 2024 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2024/01/16/deepl-update-babeldown/</guid><description>
&lt;p&gt;As part of rOpenSci&amp;rsquo;s &lt;a href="https://ropensci.org/multilingual-publishing/"&gt;multilingual publishing project&lt;/a&gt;&lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt;, we have been developing the &lt;a href="https://docs.ropensci.org/babeldown/"&gt;babeldown&lt;/a&gt; R package, for translating Markdown-based content using the DeepL API.&lt;/p&gt;
&lt;p&gt;In a previous tech note we demonstrated the &lt;a href="https://ropensci.org/blog/2023/09/26/how-to-translate-a-hugo-blog-post-with-babeldown/"&gt;use of babeldown for translating a blog post&lt;/a&gt; in a workflow supported by Git.
Here we use babeldown for translating &lt;strong&gt;living&lt;/strong&gt; documents, such as our &lt;a href="https://devguide.ropensci.org/"&gt;developer&amp;rsquo;s guide&lt;/a&gt;.
In this case, translations not only need to be created at the time in first writing, but also updated as the document is changed over time.&lt;/p&gt;</description></item><item><title>R-universe now builds MacOS ARM64 binaries for use on Apple Silicon (aka M1/M2/M3) systems</title><link>https://ropensci.org/blog/2024/01/14/runiverse-arm64/</link><pubDate>Sun, 14 Jan 2024 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2024/01/14/runiverse-arm64/</guid><description>
&lt;h2&gt;
Abstract / TLDR
&lt;/h2&gt;&lt;p&gt;&lt;a href="https://r-universe.dev"&gt;R-universe&lt;/a&gt; now provides MacOS arm64 binaries for all R packages. This means that MacOS users on Apple Silicon hardware (aka M1/M2/M3) can install the very latest builds of any R package without the need for any compilation:&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-r" data-lang="r"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nf"&gt;install.packages&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s"&gt;&amp;#39;arrow&amp;#39;&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="n"&gt;repos&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nf"&gt;c&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s"&gt;&amp;#39;https://apache.r-universe.dev&amp;#39;&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s"&gt;&amp;#39;https://cloud.r-project.org&amp;#39;&lt;/span&gt;&lt;span class="p"&gt;))&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;R-universe uses cross-compiling for arm64 binaries, though this should not make much of a difference for package authors and R users. Packages with C/C++/Fortran/Rust code are all supported.&lt;/p&gt;</description></item><item><title>rOpenSci 2023 Code of Conduct Transparency Report</title><link>https://ropensci.org/blog/2024/01/12/transparency2023/</link><pubDate>Fri, 12 Jan 2024 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2024/01/12/transparency2023/</guid><description>
&lt;p&gt;The rOpenSci community is supported by our &lt;a href="https://ropensci.org/code-of-conduct"&gt;Code of Conduct&lt;/a&gt; with a clear description of unacceptable behaviors,
instructions on how to make a report, and information on how reports are handled. We, the Code of Conduct Committee,
are responsible for receiving, investigating, deciding, enforcing and reporting on all reports of potential
violations of our Code. We are committed to transparency with our community while upholding the privacy
of people who experience or report incidents.&lt;/p&gt;</description></item><item><title>Social Coworking and Office Hours - Working with APIs</title><link>https://ropensci.org/events/coworking-2024-01/</link><pubDate>Tue, 09 Jan 2024 15:00:00 +0000</pubDate><guid>https://ropensci.org/events/coworking-2024-01/</guid><description>
&lt;!--
```{r}
d &lt;- lubridate::ymd_hms('2024-01-09 14:00:00', tz = 'Europe/Paris')
lubridate::with_tz(d, 'UTC')
lubridate::with_tz(d, 'America/Winnipeg')
```
--&gt;
&lt;p&gt;&lt;strong&gt;Join us for 2 hours Tuesday January 09, 14:00 European Central (13:00 UTC) for
&lt;a href="https://ropensci.org/blog/2023/06/21/coworking/"&gt;Social Coworking + Office Hours&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This month we&amp;rsquo;re focusing on the theme &lt;strong&gt;Working with APIs&lt;/strong&gt;
with community host &lt;strong&gt;Jon Harmon&lt;/strong&gt;, &lt;a href="https://rfordatasci.com/"&gt;R4DS&lt;/a&gt;
Chief Community Manager, &lt;a href="https://beekeeper.api2r.org/"&gt;R package developer&lt;/a&gt; and &lt;a href="https://wapir.io/"&gt;API enthusiast&lt;/a&gt;!&lt;/p&gt;
&lt;p&gt;Come for the full 2 hrs or only as long as you need!&lt;/p&gt;
&lt;h3&gt;
Cowork
&lt;/h3&gt;&lt;ul&gt;
&lt;li&gt;Do some studying to learn about APIs and how they work&lt;/li&gt;
&lt;li&gt;Explore using some APIs in your own work&lt;/li&gt;
&lt;li&gt;Cowork independently on work related to R
&lt;ul&gt;
&lt;li&gt;Plan out that package you’ve always wanted to create&lt;/li&gt;
&lt;li&gt;Work on packages that tend to be neglected&lt;/li&gt;
&lt;li&gt;What ever you need to get done!&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;
Socialize/Network
&lt;/h3&gt;&lt;ul&gt;
&lt;li&gt;Meet community host, &lt;strong&gt;Jon Harmon&lt;/strong&gt;, and discuss using APIs in R, and which packages can help&lt;/li&gt;
&lt;li&gt;Meet other R users and rOpenSci staff in Zoom&lt;/li&gt;
&lt;li&gt;Get answers to your questions
&lt;ul&gt;
&lt;li&gt;Ask your hosts&lt;/li&gt;
&lt;li&gt;Ask your fellow coworkers&lt;/li&gt;
&lt;li&gt;Discuss your work, best practices, or get advice and resources&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Answer other coworkers&amp;rsquo; questions!&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;We host
&lt;a href="https://ropensci.org/blog/2023/06/21/coworking/"&gt;Social Coworking + Office Hours&lt;/a&gt;
on the first Tuesday of each month, alternating among timezones to
accommodate different parts of the world.&lt;/p&gt;</description></item><item><title>rOpenSci News Digest, December 2023</title><link>https://ropensci.org/blog/2023/12/22/news-december-2023/</link><pubDate>Fri, 22 Dec 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2023/12/22/news-december-2023/</guid><description>
&lt;!-- Before sending DELETE THE INDEX_CACHE and re-knit! --&gt;
&lt;p&gt;Dear rOpenSci friends, it&amp;rsquo;s time for our monthly news roundup!&lt;/p&gt;
&lt;!-- blabla --&gt;
&lt;p&gt;You can read this post &lt;a href="https://ropensci.org/blog/2023/12/22/news-december-2023"&gt;on our blog&lt;/a&gt;.
Now let&amp;rsquo;s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;h3&gt;
Reminder about giving season: consider donating to rOpenSci
&lt;/h3&gt;&lt;p&gt;This Giving Season consider donating to rOpenSci to support our mission of empowering Open Science.&lt;/p&gt;
&lt;p&gt;Sustaining an open project with quality infrastructure freely accessible to the global and diverse community of R software users, research software developers, and engineers requires many different resources. Our organization’s ongoing costs are supported by grants and donations from individuals and organizations which share our vision and mission.&lt;/p&gt;</description></item><item><title>Traduzindo o guia Dev da rOpenSci para o Português</title><link>https://ropensci.org/events/portuguese-translation/</link><pubDate>Thu, 21 Dec 2023 13:00:00 +0000</pubDate><guid>https://ropensci.org/events/portuguese-translation/</guid><description/></item><item><title>2023 rOpensci Champions Program: My Experience</title><link>https://ropensci.org/blog/2023/12/19/champions-program-2023-experience/</link><pubDate>Tue, 19 Dec 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2023/12/19/champions-program-2023-experience/</guid><description>
&lt;p&gt;Being a part of the rOpenSci Champion&amp;rsquo;s program has been a transformative experience, pushing me to explore the world of R package development and contribute to the world of open science. While my initial project proposal took a different route, the unexpected journey led me to create a valuable tool that I am proud to call my own &amp;ndash; an R package &lt;a href="https://github.com/BWOlatunji/chartkickR"&gt;ChartkickR&lt;/a&gt;. In this blog post, I&amp;rsquo;ll take you through my adventure as a rOpenSci champion and how ChartkickR became the unexpected gem of my experience.&lt;/p&gt;</description></item><item><title>Paquete {eph}: Novedades e ideas para su uso.</title><link>https://ropensci.org/events/2023-12-15-eph/</link><pubDate>Fri, 15 Dec 2023 08:30:00 +0000</pubDate><guid>https://ropensci.org/events/2023-12-15-eph/</guid><description/></item><item><title>Social Coworking and Office Hours - Why won't it pass?! Troubleshooting R package checks</title><link>https://ropensci.org/events/coworking-2023-12/</link><pubDate>Tue, 05 Dec 2023 03:00:00 +0000</pubDate><guid>https://ropensci.org/events/coworking-2023-12/</guid><description>
&lt;!--
```{r}
d &lt;- lubridate::ymd_hms('2023-12-05 09:00:00', tz = 'Australia/Perth')
lubridate::with_tz(d, 'UTC')
lubridate::with_tz(d, 'America/Winnipeg')
```
--&gt;
&lt;p&gt;&lt;strong&gt;Join us for 2 hours Tuesday December 05, 09:00 Australian Western (01:00 UTC) for
&lt;a href="https://ropensci.org/blog/2023/06/21/coworking/"&gt;Social Coworking + Office Hours&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This month we&amp;rsquo;re focusing on the theme &lt;strong&gt;Why won&amp;rsquo;t it pass?! Troubleshooting R package checks&lt;/strong&gt;
with community host &lt;strong&gt;Adam Sparks&lt;/strong&gt;, maintainer of rOpenSci packages &lt;a href="https://docs.ropensci.org/GSODR/"&gt;GSODR&lt;/a&gt;
and &lt;a href="https://docs.ropensci.org/nasapower/"&gt;nasapower&lt;/a&gt;
and one who has the dubious honour of having troubleshooted &lt;strong&gt;many&lt;/strong&gt; problematic
package checks 😸.&lt;/p&gt;</description></item><item><title>Divide and Conquer: From polar To the Polarverse</title><link>https://ropensci.org/blog/2023/12/05/divide_and_you_will_win_from_polar_to_the_polarverse/</link><pubDate>Tue, 05 Dec 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2023/12/05/divide_and_you_will_win_from_polar_to_the_polarverse/</guid><description><i><a href="https://ropensci.org/es/blog/2023/12/05/2023-12-05-divide-y-venceras-de-polar-al-polarverse/">Read it in: Español</a>.</i><i><a href="https://ropensci.org/pt/blog/2023/12/05/2023-12-05-divide-y-venceras-de-polar-al-polarverse/">Read it in: Português</a>.</i>
&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;&amp;ldquo;I&amp;rsquo;m just a political scientist, standing in front of the R console asking it to help me finish my thesis.&amp;rdquo;&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;It was 2015, a Political Science master&amp;rsquo;s student had to process data to hand in his thesis and decided to take the opportunity to learn how to use R. To the long and winding road of the academic requirement was added an extra degree of difficulty: incorporating programming software from scratch, with a somewhat steep learning curve.&lt;/p&gt;</description></item><item><title>Introducing rOpenSci Mentors - Cohort 2023-2024</title><link>https://ropensci.org/blog/2023/11/29/champions-program-mentors-2023/</link><pubDate>Wed, 29 Nov 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2023/11/29/champions-program-mentors-2023/</guid><description>
&lt;p&gt;One important aspect of rOpenSci&amp;rsquo;s mission is to build capacity and promote passionate community members who help the open science and open source software community grow and improve.&lt;/p&gt;
&lt;p&gt;The rOpenSci Champions Program is a unique opportunity for us to identify, recognize, and reward such individuals and support them in their work to improve their communities and the wider ecosystem. Mentors play a vital role in the rOpenSci Champions Program by helping select Champions and advising and inspiring their mentees. They also help to shape this program by providing feedback and proposing activities and tools.&lt;/p&gt;</description></item><item><title>rOpenSci News Digest, November 2023</title><link>https://ropensci.org/blog/2023/11/24/news-november-2023/</link><pubDate>Fri, 24 Nov 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2023/11/24/news-november-2023/</guid><description>
&lt;!-- Before sending DELETE THE INDEX_CACHE and re-knit! --&gt;
&lt;p&gt;Dear rOpenSci friends, it&amp;rsquo;s time for our monthly news roundup!&lt;/p&gt;
&lt;!-- blabla --&gt;
&lt;p&gt;You can read this post &lt;a href="https://ropensci.org/blog/2023/11/24/news-november-2023"&gt;on our blog&lt;/a&gt;.
Now let&amp;rsquo;s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;h3&gt;
Giving season: consider donating to rOpenSci
&lt;/h3&gt;&lt;p&gt;This Giving Season consider donating to rOpenSci to support our mission of empowering Open Science.&lt;/p&gt;
&lt;p&gt;Sustaining an open project with quality infrastructure freely accessible to the global and diverse community of R software users, research software developers, and engineers requires many different resources. Our organization’s ongoing costs are supported by grants and donations from individuals and organizations which share our vision and mission.&lt;/p&gt;</description></item><item><title>rOpenSci. Ciencia abierta con R</title><link>https://ropensci.org/events/rday-ropensci-2023/</link><pubDate>Thu, 23 Nov 2023 23:00:00 +0000</pubDate><guid>https://ropensci.org/events/rday-ropensci-2023/</guid><description/></item><item><title>Multilingual Publishing</title><link>https://ropensci.org/commcalls/nov2023-multilingual/</link><pubDate>Thu, 03 Aug 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/commcalls/nov2023-multilingual/</guid><description>
&lt;p&gt;As global movements, Open Source and Open Science face language-based exclusion as most resources are in English. This affects scientists and research software engineers working in R, particularly those who don’t have English as their first language.&lt;/p&gt;
&lt;p&gt;rOpenSci multilingual efforts aim to lower access barriers, democratize quality resources, and increase the possibilities of contributing to open software and science. We successfully piloted our Spanish-language peer review and the localization to Spanish of our comprehensive guide to software development, with Portuguese translation underway.&lt;/p&gt;</description></item><item><title>Empowering Open Science: Donate to Support our Mission</title><link>https://ropensci.org/blog/2023/11/21/donation-2023/</link><pubDate>Tue, 21 Nov 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2023/11/21/donation-2023/</guid><description>
&lt;p&gt;rOpenSci is a nonprofit organization that is funded entirely by grants and donations. These contributions enable us to keep our projects and infrastructure active and accessible to the community.&lt;/p&gt;
&lt;p&gt;Our projects are dedicated to establishing and upholding both technical and social infrastructure that supports open and reproducible science for all our members. This means our efforts must be sustainable, inclusive, and created collaboratively by and for all groups.&lt;/p&gt;
&lt;p&gt;Each action taken by rOpenSci seeks to break down barriers to accessing knowledge in the drive to democratize access to quality resources. Examples are the &lt;a href="https://ropensci.org/r-universe/"&gt;R-Universe&lt;/a&gt;, the &lt;a href="https://ropensci.org/champions/"&gt;Champions Program&lt;/a&gt;, and the &lt;a href="https://ropensci.org/multilingual-publishing/"&gt;publication of multilingual&lt;/a&gt; resources. We also strive to transform science by creating processes and building capacity to ensure software quality and good practices, for example, our (&lt;a href="https://ropensci.org/software-review/"&gt;statistical&lt;/a&gt;) &lt;a href="https://ropensci.org/software-review/"&gt;software peer review&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Reemplazando la torre de Babel: herramientas para multilingüismo en R</title><link>https://ropensci.org/events/2023-11-17-r-bcn/</link><pubDate>Fri, 17 Nov 2023 12:00:00 +0000</pubDate><guid>https://ropensci.org/events/2023-11-17-r-bcn/</guid><description>
&lt;p&gt;&lt;a href="https://eventum.upf.edu/101896/programme/ii-conference-of-r-and-xiii-workshop-for-r-users.html"&gt;https://eventum.upf.edu/101896/programme/ii-conference-of-r-and-xiii-workshop-for-r-users.html&lt;/a&gt;&lt;/p&gt;</description></item><item><title>R-universe now builds WASM binaries for all R packages</title><link>https://ropensci.org/blog/2023/11/17/runiverse-wasm/</link><pubDate>Fri, 17 Nov 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2023/11/17/runiverse-wasm/</guid><description>
&lt;h2&gt;
Abstract / TLDR
&lt;/h2&gt;&lt;p&gt;&lt;a href="https://r-universe.dev"&gt;R-universe&lt;/a&gt; now builds WASM binaries of all R packages for use in WebR applications (such as &lt;a href="https://shinylive.io/r"&gt;shinylive&lt;/a&gt;). For example to test the dev version of dplyr, you can open the &lt;a href="https://webr.r-wasm.org/latest/"&gt;WebR demo&lt;/a&gt; page and run:&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-r" data-lang="r"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nf"&gt;install.packages&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s"&gt;&amp;#39;dplyr&amp;#39;&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="n"&gt;repos&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nf"&gt;c&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s"&gt;&amp;#39;https://tidyverse.r-universe.dev&amp;#39;&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s"&gt;&amp;#39;https://repo.r-wasm.org&amp;#39;&lt;/span&gt;&lt;span class="p"&gt;))&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;As explained below, not all R packages are supported yet; some packages need some fixes to work in WebAssembly, but coverage is rapidly growing. The r-universe dashboards shows which packages are available and link to the build logs to help you debug issues.&lt;/p&gt;</description></item><item><title>Social Coworking and Office Hours - Fixing scary bugs 😱🐛</title><link>https://ropensci.org/events/coworking-2023-11/</link><pubDate>Tue, 07 Nov 2023 19:00:00 +0000</pubDate><guid>https://ropensci.org/events/coworking-2023-11/</guid><description>
&lt;!--
```{r}
d &lt;- lubridate::ymd_hms('2023-11-07 09:00:00', tz = 'America/Vancouver')
lubridate::with_tz(d, 'UTC')
lubridate::with_tz(d, 'America/Winnipeg')
```
--&gt;
&lt;p&gt;&lt;strong&gt;Join us for 2 hours Tuesday November 07, 09:00 Americas Pacific (17:00 UTC) for
&lt;a href="https://ropensci.org/blog/2023/06/21/coworking/"&gt;Social Coworking + Office Hours&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This month we&amp;rsquo;re focusing on the theme &lt;strong&gt;Fixing scary bugs 😱 🐛&lt;/strong&gt;
with community host &lt;strong&gt;Salix Dubois&lt;/strong&gt;, maintainer of the rOpenSci &lt;a href="https://docs.ropensci.org/bold"&gt;bold&lt;/a&gt; package.&lt;/p&gt;
&lt;p&gt;Come for the full 2 hrs or only as long as you need!&lt;/p&gt;
&lt;h3&gt;
Cowork
&lt;/h3&gt;&lt;ul&gt;
&lt;li&gt;Identify some scary bugs to fix (maybe &lt;a href="https://ropensci.org/blog/2023/09/19/help-wanted/"&gt;ask for help&lt;/a&gt;!)&lt;/li&gt;
&lt;li&gt;Fix some scary bugs (in your packages/scripts, or chat with a maintainer about helping them)&lt;/li&gt;
&lt;li&gt;Cowork independently on work related to R
&lt;ul&gt;
&lt;li&gt;Plan out that package you’ve always wanted to create&lt;/li&gt;
&lt;li&gt;Work on packages that tend to be neglected&lt;/li&gt;
&lt;li&gt;What ever you need to get done!&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;
Socialize/Network
&lt;/h3&gt;&lt;ul&gt;
&lt;li&gt;Meet community host, &lt;strong&gt;Salix Dubois&lt;/strong&gt;, and discuss tips and tricks for identifying and fixing scary bugs.&lt;/li&gt;
&lt;li&gt;Meet other R users and rOpenSci staff in Zoom&lt;/li&gt;
&lt;li&gt;Get answers to your questions
&lt;ul&gt;
&lt;li&gt;Ask your hosts&lt;/li&gt;
&lt;li&gt;Ask your fellow coworkers&lt;/li&gt;
&lt;li&gt;Discuss your work, best practices, or get advice and resources&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Answer other coworkers&amp;rsquo; questions!&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;We host
&lt;a href="https://ropensci.org/blog/2023/06/21/coworking/"&gt;Social Coworking + Office Hours&lt;/a&gt;
on the first Tuesday of each month, alternating among timezones to
accommodate different parts of the world.&lt;/p&gt;</description></item><item><title>The rOpenSci Multiverse</title><link>https://ropensci.org/blog/2023/11/06/r-universe-stars-finale/</link><pubDate>Mon, 06 Nov 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2023/11/06/r-universe-stars-finale/</guid><description><i><a href="https://ropensci.org/es/blog/2023/11/06/r-universe-stars-finale-es/">Read it in: Español</a>.</i>
&lt;p&gt;The &lt;a href="https://r-universe.dev"&gt;R-Universe&lt;/a&gt; is used by professionals from different fields, although they all pursue the same objective: &lt;strong&gt;to offer their R packages in a simple and accessible way&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;At rOpenSci we work to provide tools that facilitate access to data and research software generated with good software development practices and in a friendly community. With the R-Universe platform we basically seek to present the entire #rstats universe so that anyone can find the most suitable package to solve a problem.&lt;/p&gt;</description></item><item><title>Unlock R functions with QR codes</title><link>https://ropensci.org/usecases/unlock-r-functions-with-qr-codes/</link><pubDate>Thu, 02 Nov 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/unlock-r-functions-with-qr-codes/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/opencv/"&gt;opencv&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;Wrote a demo function that only returns an answer when you present a QR code to your device&amp;rsquo;s camera that encodes the correct ‘password’.&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case
&lt;/h4&gt;&lt;p&gt;There&amp;rsquo;s a &lt;a href="https://www.rostrum.blog/posts/2023-11-01-qr-enabled-fn/"&gt;blog post&lt;/a&gt; and &lt;a href="https://fosstodon.org/@mattdray/111332716385219584"&gt;Mastodon post&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;The function:&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-r" data-lang="r"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="n"&gt;add_one&lt;/span&gt; &lt;span class="o"&gt;&amp;lt;-&lt;/span&gt; &lt;span class="kr"&gt;function&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;n&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="n"&gt;string_in&lt;/span&gt; &lt;span class="o"&gt;&amp;lt;-&lt;/span&gt; &lt;span class="n"&gt;opencv&lt;/span&gt;&lt;span class="o"&gt;::&lt;/span&gt;&lt;span class="nf"&gt;qr_scanner&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="n"&gt;password&lt;/span&gt; &lt;span class="o"&gt;&amp;lt;-&lt;/span&gt; &lt;span class="n"&gt;RCurl&lt;/span&gt;&lt;span class="o"&gt;::&lt;/span&gt;&lt;span class="nf"&gt;base64Decode&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s"&gt;&amp;#34;b3BlbmN2IHNlc2FtZSE=&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="kr"&gt;if&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;string_in&lt;/span&gt; &lt;span class="o"&gt;==&lt;/span&gt; &lt;span class="n"&gt;password&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="nf"&gt;cat&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s"&gt;&amp;#34;🔑 Correct password!\n&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="n"&gt;n&lt;/span&gt; &lt;span class="o"&gt;+&lt;/span&gt; &lt;span class="m"&gt;1&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="kr"&gt;else&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="nf"&gt;stop&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s"&gt;&amp;#34;Wrong password!&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;call.&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="kc"&gt;FALSE&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="p"&gt;}&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Running the function will cause &lt;code&gt;opencv::qr_scanner()&lt;/code&gt; to open your device&amp;rsquo;s camera. QR codes presented to the camera will be decoded. If the correct password is encoded by the QR code, then the function will print a result (so &lt;code&gt;add_one(1)&lt;/code&gt; will return &lt;code&gt;2&lt;/code&gt;). (Note that the password is exposed in the body of the function, so I&amp;rsquo;ve &amp;lsquo;hidden&amp;rsquo; it behind base64 encoding.)&lt;/p&gt;</description></item><item><title>Targets and other tools to make college comparison website</title><link>https://ropensci.org/usecases/targets-and-other-tools-to-make-college-comparison-website/</link><pubDate>Wed, 01 Nov 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/targets-and-other-tools-to-make-college-comparison-website/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used
&lt;/h4&gt;&lt;p&gt;The &lt;a href="https://books.ropensci.org/targets/"&gt;user manual&lt;/a&gt; for the &lt;a href="https://docs.ropensci.org/targets"&gt;targets&lt;/a&gt; and &lt;a href="https://docs.ropensci.org/tarchetypes"&gt;tarchetypes&lt;/a&gt; packages.&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;I made a 13,424 page website, &lt;a href="https://collegetables.info/"&gt;https://collegetables.info/&lt;/a&gt;, to compare US colleges; it tracks things like graduation rates and finances over time, as well as distributions of degrees by fields. It was featured in the &lt;em&gt;New York Times&lt;/em&gt; (&lt;a href="https://www.nytimes.com/2023/04/15/your-money/college-cost-data-tools.html?unlocked_article_code=hN2IwBdFONp5CmgbxhKM-HVUid0P2EEoomfIcGniJ6EcogeoxOwoimKabx7gynOb0f6-QxIpIELuqqT35rk-nLmDMZMDAljFtcY-YQBvNGWVgLCKOj7omvSxUjcQbXnG4B8H67gTFWQA8USo6Y3Xs5RWuXjQ8Chp2WchftGv-k9oTf7m0nPvki2JmPoQiawOquJTtiwFG9lxEX5-vSzJIvBPu5Gl_-jhW5wisUpTZCQWfzr9Ar56ix7q2rQ2B4qqyQxpPWqow2gJ_D0eF5c4PhAzh-QksTofGv9rUG0SJmgnDhUkCcF361B0kpugBjccqwqYBuaTbSFMqBowPacjapogDFA&amp;amp;giftCopy=1_CurrentCopy&amp;amp;smid=url-share"&gt;gift link&lt;/a&gt;).&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://brianomeara.info/posts/collegetables/"&gt;https://brianomeara.info/posts/collegetables/&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
Image
&lt;/h4&gt;&lt;p&gt;&lt;img src="https://ropensci.org/usecases/targets-and-other-tools-to-make-college-comparison-website/targets-and-other-tools-to-make-college-comparison-website.jpeg" alt="Teaching|690x438"&gt;&lt;/p&gt;
&lt;h4&gt;
Sector
&lt;/h4&gt;&lt;p&gt;academic&lt;/p&gt;</description></item><item><title>R in Government</title><link>https://ropensci.org/commcalls/oct2023-government/</link><pubDate>Sat, 30 Sep 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/commcalls/oct2023-government/</guid><description>
&lt;p&gt;In this community call, our panelists will share their experiences and examples of projects with R at different levels of government and in different countries.&lt;br&gt;
We invite you to learn about the challenges and lessons learned from our panelists and attendees in their efforts to make their government data, processes, and analyses more open and reproducible.&lt;/p&gt;
&lt;p&gt;See below for speaker bios and resources.&lt;/p&gt;</description></item><item><title>Scanning QR codes in R</title><link>https://ropensci.org/blog/2023/10/30/opencv-qr/</link><pubDate>Mon, 30 Oct 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2023/10/30/opencv-qr/</guid><description>
&lt;p&gt;The latest version of the &lt;a href="https://ropensci.r-universe.dev/opencv"&gt;opencv R package&lt;/a&gt; can detect and decode QR codes!&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-r" data-lang="r"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# Install latest opencv&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nf"&gt;install.packages&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s"&gt;&amp;#34;opencv&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;repos&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="s"&gt;&amp;#34;https://ropensci.r-universe.dev&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;There are two ways of using this: the &lt;a href="https://docs.ropensci.org/opencv/reference/qrcode.html"&gt;&lt;code&gt;ocv_qr_detect&lt;/code&gt;&lt;/a&gt; function tries to find the QR in an image file. It returns either a text string or NULL (if no QR code was found in the image):&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-r" data-lang="r"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="n"&gt;img&lt;/span&gt; &lt;span class="o"&gt;&amp;lt;-&lt;/span&gt; &lt;span class="n"&gt;opencv&lt;/span&gt;&lt;span class="o"&gt;::&lt;/span&gt;&lt;span class="nf"&gt;ocv_read&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s"&gt;&amp;#39;https://jeroen.github.io/images/qrtest.jpg&amp;#39;&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="n"&gt;opencv&lt;/span&gt;&lt;span class="o"&gt;::&lt;/span&gt;&lt;span class="nf"&gt;ocv_qr_detect&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;img&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;## https://www.r-project.org&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Alternatively if your laptop has a camera, you can use R as a true QR code scanner! The &lt;a href="https://docs.ropensci.org/opencv/reference/qrcode.html"&gt;&lt;code&gt;qr_scanner&lt;/code&gt;&lt;/a&gt; function starts the camera device and filters the video stream through the above &lt;code&gt;ocv_qr_detect&lt;/code&gt; until a QR code has been detected.&lt;/p&gt;</description></item><item><title>Análisis de colaboración en comunidades por medio de analisis de redes sociales</title><link>https://ropensci.org/events/latinr-ropensci-2023/</link><pubDate>Fri, 20 Oct 2023 23:00:00 +0000</pubDate><guid>https://ropensci.org/events/latinr-ropensci-2023/</guid><description/></item><item><title>Programa de Campeãs e Campeões na América Latina</title><link>https://ropensci.org/events/latinr-champions-2023/</link><pubDate>Fri, 20 Oct 2023 23:00:00 +0000</pubDate><guid>https://ropensci.org/events/latinr-champions-2023/</guid><description/></item><item><title>rOpenSci News Digest, October 2023</title><link>https://ropensci.org/blog/2023/10/20/news-october-2023/</link><pubDate>Fri, 20 Oct 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2023/10/20/news-october-2023/</guid><description>
&lt;!-- Before sending DELETE THE INDEX_CACHE and re-knit! --&gt;
&lt;p&gt;Dear rOpenSci friends, it&amp;rsquo;s time for our monthly news roundup!&lt;/p&gt;
&lt;!-- blabla --&gt;
&lt;p&gt;You can read this post &lt;a href="https://ropensci.org/blog/2023/10/20/news-october-2023"&gt;on our blog&lt;/a&gt;.
Now let&amp;rsquo;s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;h3&gt;
Help us translate our dev guide to Portuguese
&lt;/h3&gt;&lt;p&gt;Since last year we started the translation and localization of our Spanish version of our &lt;a href="https://devguide.ropensci.org/"&gt;comprehensive guide to software development&lt;/a&gt;. We have a &lt;a href="https://devdevguide.netlify.app/es/preface.es.html"&gt;first version in Spanish&lt;/a&gt; and now, thanks to the R Community initiative, we are working on the Portuguese version.&lt;/p&gt;</description></item><item><title>A toolkit workflow for climate-sensitive infectious disease modelling</title><link>https://ropensci.org/usecases/a-toolkit-workflow-for-climate-sensitive-infectious-disease-modelling/</link><pubDate>Thu, 05 Oct 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/a-toolkit-workflow-for-climate-sensitive-infectious-disease-modelling/</guid><description>
&lt;p&gt;Statistical modelling of Climate-Sensitive Infectious Disease (CSID) usually requires commons steps to harmonize and make compatible data from epidemiology and climate. Different teams do similar procedures in order to reach similar results for this purpose. But the actual coding of these steps involve lots of apparently small choices and details that, in the end, produce results very different and not directly comparable.&lt;/p&gt;
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/targets"&gt;targets&lt;/a&gt;, &lt;a href="https://docs.ropensci.org/tarchetypes"&gt;tarchetypes&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;To approach this problem, I started to code some dedicated R packages and integrate its use using the &lt;a href="https://docs.ropensci.org/targets/"&gt;targets&lt;/a&gt; and &lt;a href="https://docs.ropensci.org/tarchetypes/"&gt;tarchetypes&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Social Coworking and Office Hours - Creating nice command-line interfaces with cli</title><link>https://ropensci.org/events/coworking-2023-10/</link><pubDate>Tue, 03 Oct 2023 14:00:00 +0000</pubDate><guid>https://ropensci.org/events/coworking-2023-10/</guid><description>
&lt;!--
```{r}
d &lt;- lubridate::ymd_hms('2023-10-03 14:00:00', tz = 'Europe/Paris')
lubridate::with_tz(d, 'UTC')
lubridate::with_tz(d, 'America/Winnipeg')
```
--&gt;
&lt;p&gt;&lt;strong&gt;Join us for 2 hours Tuesday October 03, 14:00 European Central (12:00 UTC) for
&lt;a href="https://ropensci.org/blog/2023/06/21/coworking/"&gt;Social Coworking + Office Hours&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This month we&amp;rsquo;re focusing on the theme &lt;strong&gt;Creating nice command-line interfaces with cli&lt;/strong&gt;
with community host &lt;strong&gt;Athanasia Mo Mowinckel&lt;/strong&gt;, an rOpenSci champions mentor,
R package developer, and cognitive neuroscientist!&lt;/p&gt;
&lt;p&gt;Come for the full 2 hrs or only as long as you need!&lt;/p&gt;</description></item><item><title>How to Translate a Hugo Blog Post with Babeldown</title><link>https://ropensci.org/blog/2023/09/26/how-to-translate-a-hugo-blog-post-with-babeldown/</link><pubDate>Tue, 26 Sep 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2023/09/26/how-to-translate-a-hugo-blog-post-with-babeldown/</guid><description><i><a href="https://ropensci.org/es/blog/2023/09/26/c%C3%B3mo_traducir_una_entrada_de_blog_de_hugo_con_babeldown/">Read it in: Español</a>.</i><i><a href="https://ropensci.org/fr/blog/2023/09/26/comment_traduire_un_billet_de_blog_hugo_avec_babeldown/">Read it in: Français</a>.</i>
&lt;p&gt;As part of our &lt;a href="https://ropensci.org/multilingual-publishing/"&gt;multilingual publishing project&lt;/a&gt;, and with &lt;a href="https://www.r-consortium.org/all-projects/awarded-projects/2022-group-2"&gt;funding from the R Consortium&lt;/a&gt;, we&amp;rsquo;ve worked on the R package &lt;a href="https://docs.ropensci.org/babeldown/"&gt;babeldown&lt;/a&gt; for translating Markdown-based content using the DeepL API.
In this tech note, we&amp;rsquo;ll show how you can use babeldown to translate a Hugo blog post!&lt;/p&gt;
&lt;h2&gt;
Motivation
&lt;/h2&gt;&lt;p&gt;Translating a Markdown blog post from your R console is not only more comfortable (when you&amp;rsquo;ve already written said blog post in R), but also less frustrating.
With babeldown, compared to copy-pasting the content of a blog post into some translation service, the Markdown syntax won&amp;rsquo;t be broken&lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt;, and code chunks won&amp;rsquo;t be translated.
This works, because under the hood, babeldown uses &lt;a href="https://docs.ropensci.org/tinkr"&gt;tinkr&lt;/a&gt; to produce XML which it then sends to the DeepL API, flagging some tags as not to be translated. It then converts the XML translated by DeepL back into Markdown again.&lt;/p&gt;</description></item><item><title>Cuarto Encuentro Anual de R-Ladies México</title><link>https://ropensci.org/events/rladies-mexico-2023/</link><pubDate>Sat, 23 Sep 2023 13:00:00 +0000</pubDate><guid>https://ropensci.org/events/rladies-mexico-2023/</guid><description/></item><item><title>rOpenSci News Digest, September 2023</title><link>https://ropensci.org/blog/2023/09/22/news-september-2023/</link><pubDate>Fri, 22 Sep 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2023/09/22/news-september-2023/</guid><description>
&lt;!-- Before sending DELETE THE INDEX_CACHE and re-knit! --&gt;
&lt;p&gt;Dear rOpenSci friends, it&amp;rsquo;s time for our monthly news roundup!&lt;/p&gt;
&lt;!-- blabla --&gt;
&lt;p&gt;You can read this post &lt;a href="https://ropensci.org/blog/2023/09/22/news-september-2023"&gt;on our blog&lt;/a&gt;.
Now let&amp;rsquo;s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;h3&gt;
WIP: WebAssembly support in R-universe!
&lt;/h3&gt;&lt;p&gt;Thanks to some help from George Stagg, we added experimental support for building WebAssembly binary packages. This makes it possible to install packages in &lt;a href="https://docs.r-wasm.org/webr/latest/"&gt;webr&lt;/a&gt;, directly from the R-universe.&lt;/p&gt;</description></item><item><title>posit::conf(2023)</title><link>https://ropensci.org/events/2023-09-19-yani-posit/</link><pubDate>Thu, 21 Sep 2023 19:30:00 +0000</pubDate><guid>https://ropensci.org/events/2023-09-19-yani-posit/</guid><description>
&lt;p&gt;At Posit Conf? Come to chat with Yani, our Community Manager.&lt;/p&gt;</description></item><item><title>CRAN-ial Expansion: Taking Your R Package Development to New Frontiers with R-Universe</title><link>https://ropensci.org/events/2023-09-19-mo-runiverse-posit/</link><pubDate>Tue, 19 Sep 2023 19:30:00 +0000</pubDate><guid>https://ropensci.org/events/2023-09-19-mo-runiverse-posit/</guid><description>
&lt;p&gt;Say goodbye to installation headaches and hello to a universe of possibilities with R-Universe! Take your R package development to new frontiers by organizing and sharing packages beyond the bounds of CRAN. R-Universe&amp;rsquo;s reliable package-building process strengthens installation and usage instructions, resulting in fewer support requests and an easy installation experience for users. With webpages and an API for exploring packages, R-Universe creates a streamlined and tidy ecosystem for R-package constellations. Join me to learn how to explore the vastness of R-Universe and expand your package development possibilities!&lt;/p&gt;</description></item><item><title>Attract Contributors with 'help wanted' Issues</title><link>https://ropensci.org/blog/2023/09/19/help-wanted/</link><pubDate>Tue, 19 Sep 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2023/09/19/help-wanted/</guid><description><i><a href="https://ropensci.org/es/blog/2023/09/19/help-wanted/">Read it in: Español</a>.</i><i><a href="https://ropensci.org/pt/blog/2023/09/19/help-wanted/">Read it in: Português</a>.</i>
&lt;p&gt;Maintaining a package can be a lonesome activity, which sometimes poses a problem if you prefer team work or if you encounter a very thorny-for-you problem.
Beside belonging to a supportive community of maintainers (like rOpenSci &amp;#x1f609;), for collaborative help and commiseration you can try to build a community of contributors around your package!
In this post, we&amp;rsquo;ll explore one tool helping you towards that goal: &amp;ldquo;help wanted&amp;rdquo; issues, with which your repository could attract and retain new developers! We&amp;rsquo;ll discuss what &amp;ldquo;help wanted&amp;rdquo; issues are, four steps for soliciting external help, and remind you that this can be a beneficial process, even if you don&amp;rsquo;t end up attracting help.&lt;/p&gt;</description></item><item><title>Meeting the Stars of the R-Universe: The R-Universe Against Diseases.</title><link>https://ropensci.org/blog/2023/09/15/r-universe-stars-5-en/</link><pubDate>Fri, 15 Sep 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2023/09/15/r-universe-stars-5-en/</guid><description><i><a href="https://ropensci.org/es/blog/2023/09/15/r-universe-stars-5-es/">Read it in: Español</a>.</i>
&lt;p&gt;A new post of our interview series &lt;a href="https://ropensci.org/tags/r-universe-stars/"&gt;“Meeting the stars of the R-universe”&lt;/a&gt;. We aim to introduce the teams and people behind the development of software and packages many of us use and which are available through the R-Universe. We want to highlight and explore different teams and projects around the world, the work they do, their processes and users. This stop is at the &lt;strong&gt;United Kingdom&lt;/strong&gt; to talk with members of the Centre for Global Infectious Disease Analysis. Be sure to watch the video at the end with excerpts from the interview.&lt;/p&gt;</description></item><item><title>Social Coworking and Office Hours - AI in/for R</title><link>https://ropensci.org/events/coworking-2023-09/</link><pubDate>Tue, 05 Sep 2023 03:00:00 +0000</pubDate><guid>https://ropensci.org/events/coworking-2023-09/</guid><description>
&lt;!--
```{r}
d &lt;- lubridate::ymd_hms('2023-09-05 09:00:00', tz = 'Australia/Perth')
lubridate::with_tz(d, 'UTC')
lubridate::with_tz(d, 'America/Winnipeg')
```
--&gt;
&lt;p&gt;&lt;strong&gt;Join us for 2 hours Tuesday September 05, 09:00 Australian Western (01:00 UTC) for
&lt;a href="https://ropensci.org/blog/2023/06/21/coworking/"&gt;Social Coworking + Office Hours&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This month we&amp;rsquo;re focusing on the theme &lt;strong&gt;AI in/for R&lt;/strong&gt;
with community host &lt;strong&gt;Joel Nitta&lt;/strong&gt;, maintainer of several rOpenSci packages and
an AI enthusiast!&lt;/p&gt;
&lt;p&gt;Come for the full 2 hrs or only as long as you need!&lt;/p&gt;</description></item><item><title>Cómo crear un paquete de R... ¡y que sea multilingüe! + Qué es rOpenSci y cómo ser parte</title><link>https://ropensci.org/events/r-en-rosario-champions/</link><pubDate>Fri, 01 Sep 2023 23:00:00 +0000</pubDate><guid>https://ropensci.org/events/r-en-rosario-champions/</guid><description/></item><item><title>Organizing Community Calls using GitHub</title><link>https://ropensci.org/events/cscce-commcalls-github/</link><pubDate>Wed, 30 Aug 2023 15:00:00 +0000</pubDate><guid>https://ropensci.org/events/cscce-commcalls-github/</guid><description/></item><item><title>rOpenSci News Digest, August 2023</title><link>https://ropensci.org/blog/2023/08/25/news-august-2023/</link><pubDate>Fri, 25 Aug 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2023/08/25/news-august-2023/</guid><description>
&lt;!-- Before sending DELETE THE INDEX_CACHE and re-knit! --&gt;
&lt;p&gt;Dear rOpenSci friends, it&amp;rsquo;s time for our monthly news roundup!&lt;/p&gt;
&lt;!-- blabla --&gt;
&lt;p&gt;You can read this post &lt;a href="https://ropensci.org/blog/2023/08/25/news-august-2023"&gt;on our blog&lt;/a&gt;.
Now let&amp;rsquo;s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;h3&gt;
Open Call for rOpenSci Champions Program Applications!
&lt;/h3&gt;&lt;p&gt;Still open: &lt;a href="https://ropensci.org/blog/2023/07/14/call-champions-program/"&gt;our call&lt;/a&gt; for the second cohort of Champions and Mentors for the rOpenSci Champions Program 🎉 !&lt;/p&gt;
&lt;p&gt;This 12-month-long program will continue to support our goal of identifying, recognizing, and rewarding passionate community members who help the community grow and improve. The activities include &lt;a href="https://ropensci.org/blog/2023/08/04/champions-program-training/"&gt;cohort-based training&lt;/a&gt;, project development, and personal mentorship.&lt;/p&gt;</description></item><item><title>Social Coworking and Office Hours - Champions Program Application Clinic</title><link>https://ropensci.org/events/coworking-2023-08-23/</link><pubDate>Wed, 23 Aug 2023 17:00:00 +0000</pubDate><guid>https://ropensci.org/events/coworking-2023-08-23/</guid><description>
&lt;!--
```{r}
d &lt;- lubridate::ymd_hms('2023-08-23 09:00:00', tz = 'America/Vancouver')
lubridate::with_tz(d, 'UTC')
lubridate::with_tz(d, 'America/Winnipeg')
```
--&gt;
&lt;p&gt;&lt;strong&gt;Join us for 1 hour Wednesday August 23, 09:00 Americas Pacific (16:00 UTC) for
a special Champions Program Application Clinic&lt;/strong&gt; with rOpenSci Community Manager
&lt;strong&gt;Yanina Bellini Saibene&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt; We have &lt;a href="https://ropensci.org/events/coworking-2023-08-17"&gt;another clinic&lt;/a&gt; running Thursday August 17th,
09:00 Australian Western (01:00 UTC) if that&amp;rsquo;s a better time for you!&lt;/p&gt;
&lt;p&gt;Come for the full hour or only as long as you need!&lt;/p&gt;</description></item><item><title>Social Coworking and Office Hours - Champions Program Application Clinic</title><link>https://ropensci.org/events/coworking-2023-08-17/</link><pubDate>Thu, 17 Aug 2023 02:00:00 +0000</pubDate><guid>https://ropensci.org/events/coworking-2023-08-17/</guid><description>
&lt;!--
```{r}
d &lt;- lubridate::ymd_hms('2023-08-17 09:00:00', tz = 'Australia/Perth')
lubridate::with_tz(d, 'UTC')
lubridate::with_tz(d, 'America/Winnipeg')
```
--&gt;
&lt;p&gt;&lt;strong&gt;Join us for 1 hour Thursday August 17, 09:00 Australian Western (01:00 UTC) for
a special Champions Program Application Clinic&lt;/strong&gt; with rOpenSci Community Manager
&lt;strong&gt;Yanina Bellini Saibene&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt; We have &lt;a href="https://ropensci.org/events/coworking-2023-08-23"&gt;another clinic&lt;/a&gt; running Wednesday August 23rd,
09:00 Americas Pacific (16:00 UTC) if that&amp;rsquo;s a better time for you!&lt;/p&gt;
&lt;p&gt;Come for the full hour or only as long as you need!&lt;/p&gt;</description></item><item><title>Campeonas del software libre para ciencia</title><link>https://ropensci.org/events/cprladies-2023/</link><pubDate>Tue, 08 Aug 2023 22:30:00 +0000</pubDate><guid>https://ropensci.org/events/cprladies-2023/</guid><description/></item><item><title>rOpenSci Champions Pilot Year: Training Wrap-Up</title><link>https://ropensci.org/blog/2023/08/04/champions-program-training/</link><pubDate>Fri, 04 Aug 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2023/08/04/champions-program-training/</guid><description>
&lt;p&gt;Our first cohort of the &lt;a href="https://ropensci.org/champions/"&gt;rOpenSci Champions Program&lt;/a&gt; has now completed the first phase of their training.
One of the goals of this program was to ensure that all participants gained new skills and understanding.
We wanted to support Champions and Mentors, but also those who applied to the program but were not selected.
Therefore we ensured that all groups had access to different training opportunities.&lt;/p&gt;
&lt;p&gt;In this article, we share the curriculum created for the Champions, Mentors, and non-selected applicants, as well as what we learned during this pilot.&lt;/p&gt;</description></item><item><title>Building the rOpenSci Community of Practice</title><link>https://ropensci.org/events/tbep-2023/</link><pubDate>Wed, 02 Aug 2023 15:00:00 +0000</pubDate><guid>https://ropensci.org/events/tbep-2023/</guid><description/></item><item><title>Social Coworking and Office Hours - Spatial data in R</title><link>https://ropensci.org/events/coworking-2023-08/</link><pubDate>Tue, 01 Aug 2023 18:00:00 +0000</pubDate><guid>https://ropensci.org/events/coworking-2023-08/</guid><description>
&lt;!--
```{r}
d &lt;- lubridate::ymd_hms('2023-08-01 09:00:00', tz = 'America/Vancouver')
lubridate::with_tz(d, 'UTC')
lubridate::with_tz(d, 'America/Winnipeg')
```
--&gt;
&lt;p&gt;&lt;strong&gt;Join us for 2 hours Tuesday August 01, 09:00 Americas Pacific (16:00 UTC) for
&lt;a href="https://ropensci.org/blog/2023/06/21/coworking/"&gt;Social Coworking + Office Hours&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This month we&amp;rsquo;re focusing on the theme &lt;strong&gt;Spatial data in R&lt;/strong&gt;
with community host &lt;strong&gt;Mike Mahoney&lt;/strong&gt;, maintainer of several spatial packages with
rOpenSci such as &lt;a href="https://docs.ropensci.org/waywiser/"&gt;waywiser&lt;/a&gt;,
&lt;a href="https://docs.ropensci.org/terrainr/"&gt;terrainr&lt;/a&gt; and
&lt;a href="https://docs.ropensci.org/geojsonio/"&gt;geojsonio&lt;/a&gt;,
as well as &lt;a href="https://spatialsample.tidymodels.org/"&gt;spatialsample&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Come for the full 2 hrs or only as long as you need!&lt;/p&gt;</description></item><item><title>My Life with the R-universe</title><link>https://ropensci.org/blog/2023/08/01/r-universe-and-cran/</link><pubDate>Tue, 01 Aug 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2023/08/01/r-universe-and-cran/</guid><description>
&lt;h2&gt;
Summary
&lt;/h2&gt;&lt;p&gt;Installing a package that has &lt;em&gt;just&lt;/em&gt; been released to CRAN is painful for many users on Mac and Windows because often the difference between a &amp;lsquo;binary&amp;rsquo; and a &amp;lsquo;source&amp;rsquo; version is not immediately clear and they end up trying to install the source version, which leads to errors and heartbreak.
When I was designing &lt;a href="https://carpentries.github.io/workbench"&gt;The Carpentries Workbench&lt;/a&gt;, I needed to make sure that people could reliably install R packages at &lt;em&gt;any time&lt;/em&gt; regardless of whether or not they had a compiler set up.&lt;/p&gt;</description></item><item><title>New cran.dev shortlinks to package information and documentation</title><link>https://ropensci.org/blog/2023/07/26/cran-dev/</link><pubDate>Wed, 26 Jul 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2023/07/26/cran-dev/</guid><description>
&lt;h2&gt;
Introducing cran.dev shortlinks!
&lt;/h2&gt;&lt;p&gt;On r-universe you can find package repositories from many different organizations and maintainers. But sometimes you just want to lookup a particular CRAN package, without knowing the developer.
The new &lt;code&gt;cran.dev&lt;/code&gt; shortlink service lets you navigate or link directly to the r-universe homepage and docs of any established CRAN package.&lt;/p&gt;
&lt;p&gt;The root domain &lt;code&gt;https://cran.dev/{package}&lt;/code&gt; redirects to the primary homepage for a package:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://cran.dev/magick"&gt;https://cran.dev/magick&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://cran.dev/Matrix"&gt;https://cran.dev/Matrix&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://cran.dev/ggplot2"&gt;https://cran.dev/ggplot2&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The subdomain &lt;code&gt;https://docs.cran.dev/{package}&lt;/code&gt; redirects to package manual page:&lt;/p&gt;</description></item><item><title>Mentoring &amp; training program for Scientific Open Source Champions</title><link>https://ropensci.org/commcalls/july2023-championprogram/</link><pubDate>Fri, 30 Jun 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/commcalls/july2023-championprogram/</guid><description>
&lt;p&gt;Champions programs are designed to identify, recognize, and reward emerging leaders within a community. The &lt;a href="https://ropensci.org/champions/"&gt;rOpenSci Champions Program&lt;/a&gt; is part of a series of activities and projects we are carrying out to ensure our research software serves everyone in our communities, which means that it needs to be sustainable and open, and built by and for all groups.&lt;/p&gt;
&lt;p&gt;On this call &lt;em&gt;Beatriz Milz&lt;/em&gt;, &lt;em&gt;Victor Ordu&lt;/em&gt; and &lt;em&gt;Carolina Pradier&lt;/em&gt; will share their experience of being rOpenSci mentors and champions.
We will highlight the benefits of being part of the program for you and for your community, what kind of learning,
activities and opportunities an open source community champions program provides.
&lt;em&gt;Yani&lt;/em&gt; will present the details of our Champion Program and answer all your question about it.&lt;/p&gt;</description></item><item><title>rOpenSci News Digest, July 2023</title><link>https://ropensci.org/blog/2023/07/21/news-july-2023/</link><pubDate>Fri, 21 Jul 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2023/07/21/news-july-2023/</guid><description>
&lt;!-- Before sending DELETE THE INDEX_CACHE and re-knit! --&gt;
&lt;p&gt;Dear rOpenSci friends, it&amp;rsquo;s time for our monthly news roundup!&lt;/p&gt;
&lt;!-- blabla --&gt;
&lt;p&gt;You can read this post &lt;a href="https://ropensci.org/blog/2023/07/21/news-july-2023"&gt;on our blog&lt;/a&gt;.
Now let&amp;rsquo;s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;h3&gt;
Open Call for rOpenSci Champions Program Applications!
&lt;/h3&gt;&lt;p&gt;We are pleased to &lt;a href="https://ropensci.org/blog/2023/07/14/call-champions-program/"&gt;open the call&lt;/a&gt; for the second cohort of Champions and Mentors for the rOpenSci Champions Program 🎉 !&lt;/p&gt;</description></item><item><title>Teaching targets with Penguins</title><link>https://ropensci.org/blog/2023/07/20/teaching-targets-with-penguins/</link><pubDate>Thu, 20 Jul 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2023/07/20/teaching-targets-with-penguins/</guid><description>
&lt;p&gt;Many researchers are becoming more aware of the importance of reproducibility.
Although reproducibility involves a diverse array of topics and tools, one rOpenSci package has gained considerable attention for enabling reproducible analysis pipelines in R: &lt;a href="https://books.ropensci.org/targets/"&gt;targets&lt;/a&gt;, by Will Landau.&lt;/p&gt;
&lt;h2&gt;
Why a targets workshop?
&lt;/h2&gt;&lt;p&gt;Despite its popularity, targets can be challenging to learn because it requires code to be organized in a way that is different from what most people are used to.&lt;/p&gt;</description></item><item><title>Open Call for rOpenSci Champions Program Applications!</title><link>https://ropensci.org/blog/2023/07/14/call-champions-program/</link><pubDate>Fri, 14 Jul 2023 00:00:01 -0700</pubDate><guid>https://ropensci.org/blog/2023/07/14/call-champions-program/</guid><description><i><a href="https://ropensci.org/es/blog/2023/07/14/launch-champions-program-es/">Read it in: Español</a>.</i>
&lt;p&gt;We are pleased to open the call for the second cohort of &lt;strong&gt;Champions and Mentors&lt;/strong&gt; for the rOpenSci Champions Program 🎉 ! This program will continue to support our goal of identifying, recognizing, and rewarding passionate community members who help the community grow and improve.&lt;/p&gt;
&lt;p&gt;The Champions Program &lt;a href="https://ropensci.org/blog/2021/12/20/inclusive-leadership-program/"&gt;is part of a series of activities and projects we are carrying out to ensure our research software serves everyone in our communities&lt;/a&gt;, which means that it needs to be sustainable and open, and built &lt;strong&gt;by and for all groups.&lt;/strong&gt;&lt;/p&gt;</description></item><item><title>Social Coworking and Office Hours - Create/Update your 'Happy File'/'Brag Document'!</title><link>https://ropensci.org/events/coworking-2023-07/</link><pubDate>Tue, 04 Jul 2023 14:00:00 +0000</pubDate><guid>https://ropensci.org/events/coworking-2023-07/</guid><description>
&lt;!--
```{r}
d &lt;- lubridate::ymd_hms('2023-07-04 14:00:00', tz = 'Europe/Paris')
lubridate::with_tz(d, 'UTC')
lubridate::with_tz(d, 'America/Winnipeg')
```
--&gt;
&lt;p&gt;&lt;strong&gt;Join us for 2 hours Tuesday July 04, 14:00 European Central (12:00 UTC) for
&lt;a href="https://ropensci.org/blog/2023/06/21/coworking/"&gt;Social Coworking + Office Hours&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This month we&amp;rsquo;re focusing on the theme &lt;strong&gt;Create/Update your &lt;a href="https://twitter.com/JennyBryan/status/1582862196870373377"&gt;&amp;lsquo;Happy File&amp;rsquo;&lt;/a&gt; or &lt;a href="https://jvns.ca/blog/brag-documents/"&gt;&amp;lsquo;Brag Document&amp;rsquo;&lt;/a&gt;, listing your small and big accomplishments at work!&lt;/strong&gt;
with co-host &lt;strong&gt;Maëlle Salmon&lt;/strong&gt;, rOpenSci&amp;rsquo;s own Research Software Engineer!&lt;/p&gt;
&lt;p&gt;Come for the full 2 hrs or only as long as you need!&lt;/p&gt;</description></item><item><title>A Journey through Arrow in R</title><link>https://ropensci.org/commcalls/jun2023-arrow/</link><pubDate>Wed, 28 Jun 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/commcalls/jun2023-arrow/</guid><description>
&lt;p&gt;Apache Arrow is a software development platform for building high performance applications that process and transport large data sets. It is designed to improve the performance of data analysis methods, and to increase the efficiency of moving data from one system or programming language to another.&lt;/p&gt;
&lt;p&gt;In this community call moderated by Stephanie Hazlitt, our speakers, Nic Crane and Jonathan Keane, will lead us through the Arrow R package.&lt;/p&gt;
&lt;p&gt;See below for speaker bios and resources.&lt;/p&gt;</description></item><item><title>Using targets for an omics analysis and report / manuscript</title><link>https://ropensci.org/usecases/using-targets-for-an-omics-analysis-and-report-manuscript/</link><pubDate>Mon, 26 Jun 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/using-targets-for-an-omics-analysis-and-report-manuscript/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/targets/"&gt;targets&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;I used targets to analyze and report on omics (metabolomics in this case) data analysis.&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://rmflight.github.io/posts/2022-09-27-creating-an-analysis-using-targets/"&gt;Blog post&lt;/a&gt;, &lt;a href="https://github.com/rmflight/example_targets_workflow"&gt;GitHub repository&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
Image
&lt;/h4&gt;&lt;p&gt;&lt;img src="https://ropensci.org/usecases/using-targets-for-an-omics-analysis-and-report-manuscript/using-targets-for-an-omics-analysis-and-report-manuscript.png" alt="dependency_network|690x418"&gt;&lt;/p&gt;
&lt;h4&gt;
Sector
&lt;/h4&gt;&lt;p&gt;academic&lt;/p&gt;
&lt;h4&gt;
Field(s) of application
&lt;/h4&gt;&lt;p&gt;biomedical research&lt;/p&gt;
&lt;h4&gt;
Social Handles
&lt;/h4&gt;&lt;p&gt;Mastodon: &lt;a href="https://mastodon.social/@rmflight"&gt;https://mastodon.social/@rmflight&lt;/a&gt;&lt;/p&gt;</description></item><item><title>rOpenSci Champions Program Teams: Meet Ghozayel Elotteebi and Zebulun Arendsee</title><link>https://ropensci.org/blog/2023/06/23/ropensci-champions-program-teams-meet-ghozayel-elotteebi-and-zebulun-arendsee/</link><pubDate>Fri, 23 Jun 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2023/06/23/ropensci-champions-program-teams-meet-ghozayel-elotteebi-and-zebulun-arendsee/</guid><description>
&lt;p&gt;&lt;em&gt;We designed the &lt;a href="https://ropensci.org/champions/"&gt;rOpenSci Champions Program&lt;/a&gt; with a mentorship aspect. Mentoring plays a significant role in the growth and development of both mentors and mentees alike. In our program, each Champion has a mentor who accompanies them during their training and development of their project.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;In this series of blog posts, we introduce you to the ten teams of this first cohort and what they will be working on in the program.&lt;/em&gt;&lt;/p&gt;</description></item><item><title>rOpenSci News Digest, June 2023</title><link>https://ropensci.org/blog/2023/06/22/ropensci-news-digest-june-2023/</link><pubDate>Thu, 22 Jun 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2023/06/22/ropensci-news-digest-june-2023/</guid><description>
&lt;!-- Before sending DELETE THE INDEX_CACHE and re-knit! --&gt;
&lt;p&gt;Dear rOpenSci friends, it&amp;rsquo;s time for our monthly news roundup!&lt;/p&gt;
&lt;!-- blabla --&gt;
&lt;p&gt;You can read this post &lt;a href="https://ropensci.org/blog/2023/06/22/ropensci-news-digest-june-2023"&gt;on our blog&lt;/a&gt;.
Now let&amp;rsquo;s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;h3&gt;
Meeting the stars of the R-universe: PEcAn, an Open Source Project to Take Care of the Planet
&lt;/h3&gt;&lt;p&gt;Knowing our community&amp;rsquo;s stories helps us to learn about the people behind our software, brings us closer and offers us new opportunities. To share some of these community stories, we created the rOpenSci interview series &lt;a href="https://ropensci.org/tags/r-universe-stars/"&gt;&lt;em&gt;&amp;ldquo;Meeting the stars of the R-Universe&amp;rdquo;&lt;/em&gt;&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>All About Coworking Sessions with rOpenSci</title><link>https://ropensci.org/blog/2023/06/21/coworking/</link><pubDate>Wed, 21 Jun 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2023/06/21/coworking/</guid><description>
&lt;p&gt;We first &lt;a href="https://ropensci.org/blog/2021/08/17/coworking-sessions"&gt;introduced&lt;/a&gt; our Coworking and
Office Hour sessions in August 2021 after a successful pilot of several
&amp;rsquo;label-athon&amp;rsquo;s in the April and May prior.&lt;/p&gt;
&lt;p&gt;We&amp;rsquo;ve had a successful couple of years since then and the coworking sessions
have evolved into themed events with different community hosts and me as
a facilitator. It&amp;rsquo;s been a lovely change and we thought it was time to share these updates with the rOpenSci community! 🎉&lt;/p&gt;</description></item><item><title>rOpenSci Champions Program Teams: Meet Alican Cagri Gokcek and Elio Campitelli</title><link>https://ropensci.org/blog/2023/06/19/ropensci-champions-program-teams-meet-alican-cagri-gokcek-and-elio-campitelli/</link><pubDate>Mon, 19 Jun 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2023/06/19/ropensci-champions-program-teams-meet-alican-cagri-gokcek-and-elio-campitelli/</guid><description>
&lt;p&gt;&lt;em&gt;We designed the &lt;a href="https://ropensci.org/champions/"&gt;rOpenSci Champions Program&lt;/a&gt; with a mentorship aspect. Mentoring plays a significant role in the growth and development of both mentors and mentees alike. In our program, each Champion has a mentor who accompanies them during their training and development of their project.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;In this series of blog posts, we introduce you to the ten teams of this first cohort and what they will be working on in the program.&lt;/em&gt;&lt;/p&gt;</description></item><item><title>How do you measure the impact of a champions program?</title><link>https://ropensci.org/blog/2023/06/15/ropensci-champions-impact-en/</link><pubDate>Thu, 15 Jun 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2023/06/15/ropensci-champions-impact-en/</guid><description>
&lt;blockquote&gt;
&lt;p&gt;This post can also be &lt;a href="https://www.cscce.org/2023/06/15/how-do-you-measure-the-impact-of-a-community-champions-program/"&gt;found on the CSCCE blog&lt;/a&gt;.&amp;quot;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;How do you measure the impact of a champions program? This was the central question of a working session at &lt;em&gt;CZI’s Accelerating Open Science in Latin America&lt;/em&gt; workshop, convened by rOpenSci’s Community Manager Yani Bellini Saibene and attended by CSCCE’s Founder and Director, Lou Woodley.&lt;/p&gt;
&lt;p&gt;Measuring the impact of any kind of community program presents a series of challenges:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;What is the impact that you’re hoping your program will have?&lt;/p&gt;</description></item><item><title>rOpenSciの紹介</title><link>https://ropensci.org/events/2023-06-14-joel-biopackathon/</link><pubDate>Wed, 14 Jun 2023 09:00:00 +0000</pubDate><guid>https://ropensci.org/events/2023-06-14-joel-biopackathon/</guid><description/></item><item><title>rOpenSci's Communication Channels for Safe and Friendly Exchange</title><link>https://ropensci.org/blog/2023/06/14/ropensci-communication-channels-en/</link><pubDate>Wed, 14 Jun 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2023/06/14/ropensci-communication-channels-en/</guid><description><i><a href="https://ropensci.org/es/blog/2023/06/14/ropensci-communication-channels-es/">Read it in: Español</a>.</i>
&lt;p&gt;As &lt;a href="https://ropensci.org/blog/2022/11/16/mastodon-en"&gt;we anticipated in November 2022&lt;/a&gt; the changes implemented by Twitter have generated a less safe and friendly space for our community. That is why from &lt;em&gt;June 2023&lt;/em&gt;, we will stop interacting on this platform. We will maintain the account in hopes that we can return when Twitter is once again a safe and supportive space, but in the meanwhile will focus our communication efforts elsewhere.&lt;/p&gt;
&lt;p&gt;We understand that until now Twitter has been one of the reference platforms for the R community, data, research and open science community but we have to be responsible and
coherent with the spaces we choose for exchange and interaction and &lt;a href="https://ropensci.org/code-of-conduct/"&gt;our values as a community&lt;/a&gt; and &lt;a href="https://ropensci.org/about/"&gt;organization&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>rOpenSci Champions Program Teams: Meet Cheryl Isabella Lim and Mauro Lepore</title><link>https://ropensci.org/blog/2023/06/12/ropensci-champions-program-teams-meet-cheryl-isabella-lim-and-mauro-lepore/</link><pubDate>Mon, 12 Jun 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2023/06/12/ropensci-champions-program-teams-meet-cheryl-isabella-lim-and-mauro-lepore/</guid><description>
&lt;p&gt;&lt;em&gt;We designed the &lt;a href="https://ropensci.org/champions/"&gt;rOpenSci Champions Program&lt;/a&gt; with a mentorship aspect. Mentoring plays a significant role in the growth and development of both mentors and mentees alike. In our program, each Champion has a mentor who accompanies them during their training and development of their project.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;In this series of blog posts, we introduce you to the ten teams of this first cohort and what they will be working on in the program.&lt;/em&gt;&lt;/p&gt;</description></item><item><title>Social Coworking and Office Hours - Integrating and merging datasets from different sources</title><link>https://ropensci.org/events/coworking-2023-06/</link><pubDate>Tue, 06 Jun 2023 03:00:00 +0000</pubDate><guid>https://ropensci.org/events/coworking-2023-06/</guid><description>
&lt;!--
```{r}
d &lt;- lubridate::ymd_hms('2023-06-06 09:00:00', tz = 'Australia/Perth')
lubridate::with_tz(d, 'UTC')
lubridate::with_tz(d, 'America/Winnipeg')
```
--&gt;
&lt;p&gt;&lt;strong&gt;Join us for 2 hours Tuesday June 06, 09:00 Australian Western (01:00 UTC) for
&lt;a href="https://ropensci.org/blog/2021/08/17/coworking-sessions/"&gt;Social Coworking + Office Hours&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This month we&amp;rsquo;re focusing on the theme &lt;strong&gt;Integrating and merging datasets from different sources&lt;/strong&gt;
with community host &lt;strong&gt;Cynthia Huang&lt;/strong&gt; who has been tackling how to integrate
data from multiple sources as part of her PhD at Monash University!&lt;/p&gt;</description></item><item><title>Meeting the Stars of the R-Universe: PEcAn, an Open Source Project to Take Care of the Planet</title><link>https://ropensci.org/blog/2023/06/06/r-universe-stars-4-en/</link><pubDate>Tue, 06 Jun 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2023/06/06/r-universe-stars-4-en/</guid><description><i><a href="https://ropensci.org/es/blog/2023/06/06/r-universe-stars-4-es/">Read it in: Español</a>.</i>
&lt;p&gt;A new post of our interview series &lt;a href="https://ropensci.org/tags/r-universe-stars/"&gt;“Meeting the stars of the R-universe”&lt;/a&gt;. We aim to introduce the teams and people behind the development of software and packages many of us use and which are available through the R-Universe. We want to highlight and explore different teams and projects around the world, the work they do, their processes and users. Our third stop is the &lt;strong&gt;United States&lt;/strong&gt; to talk with members of the PEcAn project. Be sure to watch the video at the end with excerpts from the interview.&lt;/p&gt;</description></item><item><title>Troubleshooting Pandoc Problems as an R User</title><link>https://ropensci.org/blog/2023/06/01/troubleshooting-pandoc-problems-as-an-r-user/</link><pubDate>Thu, 01 Jun 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2023/06/01/troubleshooting-pandoc-problems-as-an-r-user/</guid><description><i><a href="https://ropensci.org/fr/blog/2023/06/01/troubleshooting-pandoc-problems-as-an-r-user/">Read it in: Français</a>.</i>
&lt;p&gt;The Pandoc CLI by &lt;a href="https://johnmacfarlane.net/"&gt;John MacFarlane&lt;/a&gt; is a really useful tool: for instance, rOpenSci community manager Yanina Bellini Saibene recently asked Maëlle whether she could convert a Google Document into a Quarto book.
Maëlle solved the request with a combination of Pandoc (conversion from docx to HTML then to Markdown through &lt;a href="https://cderv.github.io/pandoc/reference/pandoc_convert.html"&gt;&lt;code&gt;pandoc::pandoc_convert()&lt;/code&gt;&lt;/a&gt;) and XPath.
You can find the resulting experimental package &lt;a href="https://github.com/ropenscilabs/quartificate"&gt;quartificate&lt;/a&gt; on GitHub.
Pandoc is not only anecdotally useful: it&amp;rsquo;s part of the &lt;a href="https://rmarkdown.rstudio.com/"&gt;R Markdown&lt;/a&gt; machinery, and powers &lt;a href="https://quarto.org/"&gt;Quarto&lt;/a&gt;.
So, whether you&amp;rsquo;re juggling documents in various formats or simply trying to publish your reproducible analysis, you might have been using Pandoc (even if you didn&amp;rsquo;t know!), or maybe you &lt;em&gt;should&lt;/em&gt; be using Pandoc.&lt;/p&gt;</description></item><item><title>Downloading snapshots and creating stable R packages repositories using r-universe</title><link>https://ropensci.org/blog/2023/05/31/runiverse-snapshots/</link><pubDate>Wed, 31 May 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2023/05/31/runiverse-snapshots/</guid><description>
&lt;h2&gt;
Downloading repository snapshots
&lt;/h2&gt;&lt;p&gt;The new snapshot API lets you download a full copy of any CRAN-like repository on r-universe. You can use such a snapshot to mirror the entire CRAN-like repository on your own servers, or for example to build a stable, validated release of your package suite.&lt;/p&gt;
&lt;p&gt;The API endpoint is simply &lt;code&gt;/api/snapshot&lt;/code&gt; and has several options to filter content. By default it returns a zip file with all the packages, binaries, and documentation in your repository. If this is more than you need, there are parameters to include e.g. only binaries for certain platforms or certain versions of R, or to create a repository from a subset of the packages in your universe. Explore the parameters on the API tab of any universe, for example: &lt;a href="https://ggseg.r-universe.dev/api"&gt;https://ggseg.r-universe.dev/api&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Developing Software Together (training for champions program applicants)</title><link>https://ropensci.org/events/2023-05-19-developing-software-together/</link><pubDate>Fri, 19 May 2023 17:00:00 +0000</pubDate><guid>https://ropensci.org/events/2023-05-19-developing-software-together/</guid><description/></item><item><title>rOpenSci News Digest, May 2023</title><link>https://ropensci.org/blog/2023/05/19/ropensci-news-digest-may-2023/</link><pubDate>Fri, 19 May 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2023/05/19/ropensci-news-digest-may-2023/</guid><description>
&lt;!-- Before sending DELETE THE INDEX_CACHE and re-knit! --&gt;
&lt;p&gt;Dear rOpenSci friends, it&amp;rsquo;s time for our monthly news roundup!&lt;/p&gt;
&lt;!-- blabla --&gt;
&lt;p&gt;You can read this post &lt;a href="https://ropensci.org/blog/2023/05/19/ropensci-news-digest-may-2023"&gt;on our blog&lt;/a&gt;.
Now let&amp;rsquo;s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;h3&gt;
Statistical software review updates
&lt;/h3&gt;&lt;p&gt;We are very happy to welcome &lt;a href="https://ropensci.org/author/jouni-helske"&gt;Jouni Helske&lt;/a&gt; to the editorial team for statistical software review.
Jouni jumped straight in to act as editor for the &lt;a href="https://github.com/ropensci/software-review/issues/546"&gt;fwildclusterboot submission&lt;/a&gt;, an exciting first extension of our system beyond R alone to include functions in the Julia language.
We have so far approved &lt;a href="https://github.com/ropensci/software-review/issues?q=is%3Aissue+sort%3Aupdated-desc+label%3Astats+is%3Aclosed+label%3A6%2Fapproved"&gt;eight packages&lt;/a&gt;, five of which have a silver badge, and three gold, with two further packages currently under review.&lt;/p&gt;</description></item><item><title>How to contribute to base R (champions training)</title><link>https://ropensci.org/events/2023-05-18-how-to-contribute-base-r/</link><pubDate>Thu, 18 May 2023 17:00:00 +0000</pubDate><guid>https://ropensci.org/events/2023-05-18-how-to-contribute-base-r/</guid><description/></item><item><title>rOpenSci Champions Program Teams: Meet César and Marc</title><link>https://ropensci.org/blog/2023/05/18/ropensci-champions-program-teams-meet-c%C3%A9sar-and-marc/</link><pubDate>Thu, 18 May 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2023/05/18/ropensci-champions-program-teams-meet-c%C3%A9sar-and-marc/</guid><description>
&lt;p&gt;&lt;em&gt;We designed the &lt;a href="https://ropensci.org/champions/"&gt;rOpenSci Champions Program&lt;/a&gt; with a mentorship aspect. Mentoring plays a significant role in the growth and development of both mentors and mentees alike. In our program, each Champion has a mentor who accompanies them during their training and development of their project.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;In this series of blog posts, we introduce you to the ten teams of this first cohort and what they will be working on in the program.&lt;/em&gt;&lt;/p&gt;</description></item><item><title>Scheduling Mastodon Posts in R with rtoot and GitHub Actions</title><link>https://ropensci.org/blog/2023/05/17/scheduling-mastodon/</link><pubDate>Wed, 17 May 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2023/05/17/scheduling-mastodon/</guid><description>
&lt;p&gt;A lot of what I do as rOpenSci&amp;rsquo;s community assistant is related to social media.
I check for posts about rOpenSci packages, invite people to share &lt;a href="https://ropensci.org/usecases"&gt;usecases&lt;/a&gt;,
advertise &lt;a href="https://ropensci.org/events"&gt;upcoming events&lt;/a&gt;, as well as promoting
&lt;a href="https://ropensci.org/software-review"&gt;new packages which completed software peer review&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Up &lt;a href="https://ropensci.org/blog/2022/11/16/mastodon-en/"&gt;until this past year&lt;/a&gt; most of this work was
focused on Twitter and because we want to reach an international audience,
we used Tweetdeck to schedule posts for different timezones&lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt;.
Being able to see when posts were queued was also important for us as a team to
better plan our post timing.&lt;/p&gt;</description></item><item><title>CRediTas is Now Part of rOpenSci</title><link>https://ropensci.org/blog/2023/05/16/creditas-is-now-part/</link><pubDate>Tue, 16 May 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2023/05/16/creditas-is-now-part/</guid><description>
&lt;p&gt;I&amp;rsquo;m thrilled to share that &lt;a href="https://docs.ropensci.org/CRediTas/"&gt;CRediTas&lt;/a&gt; has passed &lt;a href="https://github.com/ropensci/software-review/issues/576"&gt;peer review&lt;/a&gt; and been accepted to rOpenSci as well as to &lt;a href="https://cran.r-project.org/web/packages/CRediTas/index.html"&gt;CRAN&lt;/a&gt;. I am glad to acknowledge the editor &lt;a href="https://ropensci.org/author/emily-riederer/"&gt;Emily Riedered&lt;/a&gt; and the two reviewers &lt;a href="https://ropensci.org/author/marcelo-s.-perlin/"&gt;Marcelo S. Perlin&lt;/a&gt; and &lt;a href="https://zambujo.github.io/"&gt;João Martins&lt;/a&gt;. Their comments and support were really insightful.&lt;/p&gt;
&lt;p&gt;CRediTas is a tiny package to facilitate the tedious job of creating &lt;a href="https://credit.niso.org/"&gt;CRediT authors statements&lt;/a&gt; for scientific publications. Normally, the first author of a scientific paper organizes a table in a spreadsheet where all the authors self-state their contributions. Often too, it is the first author&amp;rsquo;s responsibility to state the contributions of all co-authors. However, at the end, the information has to be translated to the CRediT statement format of “Author 1: roles Authors 2: roles …” which is prone to errors and tedious, especially if there are many co-authors. The CRediTas package aims to make this easier by providing a template to be filled in form of a table (csv) and then converting this table to CRediT statement format.&lt;/p&gt;</description></item><item><title>rOpenSci Champions Program Teams: Meet Victor Ordu and Laura DeCicco</title><link>https://ropensci.org/blog/2023/05/11/intro-champion-program-team-victor-laura/</link><pubDate>Thu, 11 May 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2023/05/11/intro-champion-program-team-victor-laura/</guid><description>
&lt;p&gt;&lt;em&gt;We designed the &lt;a href="https://ropensci.org/champions/"&gt;rOpenSci Champions Program&lt;/a&gt; with a mentorship aspect. Mentoring plays a significant role in the growth and development of both mentors and mentees alike. In our program, each Champion has a mentor who accompanies them during their training and development of their project.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;In this series of blog posts, we introduce you to the ten teams of this first cohort and what they will be working on in the program.&lt;/em&gt;&lt;/p&gt;</description></item><item><title>Programming for Science</title><link>https://ropensci.org/events/2023-05-10-ols/</link><pubDate>Wed, 10 May 2023 11:00:00 +0000</pubDate><guid>https://ropensci.org/events/2023-05-10-ols/</guid><description/></item><item><title>rOpenSci Champions Program Teams: Meet Haydée Svab and Beatriz Milz</title><link>https://ropensci.org/blog/2023/05/09/ropensci-champions-program-teams-meet-haydee-svab-and-beatriz-milz/</link><pubDate>Tue, 09 May 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2023/05/09/ropensci-champions-program-teams-meet-haydee-svab-and-beatriz-milz/</guid><description>
&lt;p&gt;&lt;em&gt;We designed the &lt;a href="https://ropensci.org/champions/"&gt;rOpenSci Champions Program&lt;/a&gt; with a mentorship aspect. Mentoring plays a significant role in the growth and development of both mentors and mentees alike. In our program, each Champion has a mentor who accompanies them during their training and development of their project.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;In this series of blog posts, we introduce you to the ten teams of this first cohort and what they will be working on in the program.&lt;/em&gt;&lt;/p&gt;</description></item><item><title>Preparing remote sensing data for deep learning using r-spatial</title><link>https://ropensci.org/events/2023-05-08-cesar-champion/</link><pubDate>Mon, 08 May 2023 09:00:00 +0000</pubDate><guid>https://ropensci.org/events/2023-05-08-cesar-champion/</guid><description/></item><item><title>rOpenSci Champions Program Teams: Meet Carolina Pradier and Athanasia Monika Mowinckel</title><link>https://ropensci.org/blog/2023/05/05/ropensci-champions-program-teams-meet-carolina-pradier-and-athanasia-monika-mowinckel/</link><pubDate>Fri, 05 May 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2023/05/05/ropensci-champions-program-teams-meet-carolina-pradier-and-athanasia-monika-mowinckel/</guid><description>
&lt;p&gt;&lt;em&gt;We designed the &lt;a href="https://ropensci.org/champions/"&gt;rOpenSci Champions Program&lt;/a&gt; with a mentorship aspect. Mentoring plays a significant role in the growth and development of both mentors and mentees alike. In our program, each Champion has a mentor who accompanies them during their training and development of their project.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;In this series of blog posts, we introduce you to the ten teams of this first cohort and what they will be working on in the program.&lt;/em&gt;&lt;/p&gt;</description></item><item><title>Social Coworking and Office Hours - Spring Cleaning for R packages and Scripts</title><link>https://ropensci.org/events/coworking-2023-05/</link><pubDate>Tue, 02 May 2023 18:00:00 +0000</pubDate><guid>https://ropensci.org/events/coworking-2023-05/</guid><description>
&lt;!--
```{r}
d &lt;- lubridate::ymd_hms('2023-05-02 09:00:00', tz = 'America/Vancouver')
lubridate::with_tz(d, 'UTC')
lubridate::with_tz(d, 'America/Winnipeg')
```
--&gt;
&lt;p&gt;&lt;strong&gt;Join us for 2 hours Tuesday May 02, 09:00 Americas Pacific (16:00 UTC) for
&lt;a href="https://ropensci.org/blog/2021/08/17/coworking-sessions/"&gt;Social Coworking + Office Hours&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This month we&amp;rsquo;re focusing on the theme &lt;strong&gt;Spring Cleaning&lt;/strong&gt;*
with &lt;strong&gt;Steffi LaZerte&lt;/strong&gt;, rOpenSci&amp;rsquo;s community assistant who forgets all too often
to spring clean her own packages &amp;#x1f631;.&lt;/p&gt;
&lt;p&gt;* For those of us in the Northern Hemisphere and &lt;strong&gt;Fall Cleaning&lt;/strong&gt; for our Southern friends.&lt;/p&gt;</description></item><item><title>rOpenSci Champions Program Teams: Meet Bilikisu Wunmi Olatunji and Christina Maimone</title><link>https://ropensci.org/blog/2023/04/25/ropensci-champions-program-teams-meet-bilikisu-wunmi-olatunji-and-christina-maimone/</link><pubDate>Tue, 25 Apr 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2023/04/25/ropensci-champions-program-teams-meet-bilikisu-wunmi-olatunji-and-christina-maimone/</guid><description>
&lt;p&gt;&lt;em&gt;We designed the &lt;a href="https://ropensci.org/champions/"&gt;rOpenSci Champions Program&lt;/a&gt; with a mentorship aspect. Mentoring plays a significant role in the growth and development of both mentors and mentees alike. In our program, each Champion has a mentor who accompanies them during their training and development of their project.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;In this series of blog posts, we introduce you to the ten teams of this first cohort and what they will be working on in the program.&lt;/em&gt;&lt;/p&gt;</description></item><item><title>rOpenSci News Digest, April 2023</title><link>https://ropensci.org/blog/2023/04/21/ropensci-news-digest-april-2023/</link><pubDate>Fri, 21 Apr 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2023/04/21/ropensci-news-digest-april-2023/</guid><description>
&lt;!-- Before sending DELETE THE INDEX_CACHE and re-knit! --&gt;
&lt;p&gt;Dear rOpenSci friends, it&amp;rsquo;s time for our monthly news roundup!&lt;/p&gt;
&lt;!-- blabla --&gt;
&lt;p&gt;You can read this post &lt;a href="https://ropensci.org/blog/2023/04/21/ropensci-news-digest-april-2023"&gt;on our blog&lt;/a&gt;.
Now let&amp;rsquo;s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;h3&gt;
Meeting the stars of the R-universe: Athanasia Monika Mowinckel
&lt;/h3&gt;&lt;p&gt;Knowing our community&amp;rsquo;s stories helps us to learn about the people behind our software, brings us closer and offers us new opportunities. To share some of these community stories, we created the rOpenSci interview series &lt;a href="https://ropensci.org/tags/r-universe-stars/"&gt;&lt;em&gt;&amp;ldquo;Meeting the stars of the R-Universe&amp;rdquo;&lt;/em&gt;&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Tell me who you hang out with and I will tell you who you are. A collaborations analysis using social networks analysis</title><link>https://ropensci.org/events/2023-04-20-csvconf-regulartalk/</link><pubDate>Thu, 20 Apr 2023 17:35:00 +0000</pubDate><guid>https://ropensci.org/events/2023-04-20-csvconf-regulartalk/</guid><description/></item><item><title>How to enable and sustain thriving Open Source Ecosystems (OSE).</title><link>https://ropensci.org/events/2023-04-19-csvconf_keynote/</link><pubDate>Wed, 19 Apr 2023 17:00:00 +0000</pubDate><guid>https://ropensci.org/events/2023-04-19-csvconf_keynote/</guid><description/></item><item><title>rOpenSci Champions Program Teams: Meet Marcos Prunello and Lukas Wallrich</title><link>https://ropensci.org/blog/2023/04/18/ropensci-champions-program-teams-meet-marcos-prunello-and-lukas-wallrich/</link><pubDate>Tue, 18 Apr 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2023/04/18/ropensci-champions-program-teams-meet-marcos-prunello-and-lukas-wallrich/</guid><description>
&lt;p&gt;&lt;em&gt;We designed the &lt;a href="https://ropensci.org/champions/"&gt;rOpenSci Champions Program&lt;/a&gt; with a mentorship aspect. Mentoring plays a significant role in the growth and development of both mentors and mentees alike. In our program, each Champion has a mentor who accompanies them during their training and development of their project.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;In this series of blog posts, we introduce you to the ten teams of this first cohort and what they will be working on in the program.&lt;/em&gt;&lt;/p&gt;</description></item><item><title>rOpenSci Champions Program Teams: Meet Pao Corrales and Adam Sparks</title><link>https://ropensci.org/blog/2023/04/13/ropensci-champions-program-teams-meet-pao-corrales-and-adam-sparks/</link><pubDate>Thu, 13 Apr 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2023/04/13/ropensci-champions-program-teams-meet-pao-corrales-and-adam-sparks/</guid><description>
&lt;p&gt;&lt;em&gt;We designed the &lt;a href="https://ropensci.org/champions/"&gt;rOpenSci Champions Program&lt;/a&gt; with a mentorship aspect. Mentoring plays a significant role in the growth and development of both mentors and mentees alike. In our program, each Champion has a mentor who accompanies them during their training and development of their project.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;In this series of blog posts, we introduce you to the ten teams of this first cohort and what they will be working on in the program.&lt;/em&gt;&lt;/p&gt;</description></item><item><title>How rOpenSci performs peer-review (champions training)</title><link>https://ropensci.org/events/2023-04-04-how-ropensci-review/</link><pubDate>Tue, 04 Apr 2023 17:00:00 +0000</pubDate><guid>https://ropensci.org/events/2023-04-04-how-ropensci-review/</guid><description/></item><item><title>Social Coworking and Office Hours - Working with taxonomic lists in R</title><link>https://ropensci.org/events/coworking-2023-04/</link><pubDate>Tue, 04 Apr 2023 14:00:00 +0000</pubDate><guid>https://ropensci.org/events/coworking-2023-04/</guid><description>
&lt;!--
```{r}
d &lt;- lubridate::ymd_hms('2023-04-04 14:00:00', tz = 'Europe/Paris')
lubridate::with_tz(d, 'UTC')
lubridate::with_tz(d, 'America/Winnipeg')
```
--&gt;
&lt;p&gt;&lt;strong&gt;Join us for 2 hours Tuesday April 04, 14:00 European Central (12:00 UTC) for
&lt;a href="https://ropensci.org/blog/2021/08/17/coworking-sessions/"&gt;Social Coworking + Office Hours&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This month we&amp;rsquo;re focusing on the theme &lt;strong&gt;Working with taxonomic lists in R&lt;/strong&gt;
with community host &lt;strong&gt;Miguel Alvarez&lt;/strong&gt;, maintainer of the rOpenSci package taxlist.&lt;/p&gt;
&lt;p&gt;Come for the full 2 hrs or only as long as you need!&lt;/p&gt;</description></item><item><title>waywiser is Now a Part of rOpenSci</title><link>https://ropensci.org/blog/2023/04/04/waywiser-is-now-a-part-of-ropensci/</link><pubDate>Tue, 04 Apr 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2023/04/04/waywiser-is-now-a-part-of-ropensci/</guid><description>
&lt;p&gt;I&amp;rsquo;m thrilled to share that &lt;a href="https://docs.ropensci.org/waywiser/"&gt;waywiser&lt;/a&gt;, my R package focused on providing framework-agnostic (but &lt;a href="https://www.tidymodels.org/"&gt;tidymodels&lt;/a&gt;-friendly) methods for assessing models fit to spatial data&lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt;, has passed &lt;a href="https://ropensci.org/software-review/"&gt;peer review&lt;/a&gt; and been accepted to &lt;a href="https://ropensci.org/"&gt;rOpenSci&lt;/a&gt;. As always, &lt;a href="https://github.com/ropensci/software-review/issues/571"&gt;the review process&lt;/a&gt; improved the package immensely, thanks to the thoughtful reviews of &lt;a href="https://becarioprecario.github.io/"&gt;Virgilio Gómez-Rubio&lt;/a&gt; and &lt;a href="https://jakubnowosad.com/"&gt;Jakub Nowosad&lt;/a&gt;&lt;sup id="fnref:2"&gt;&lt;a href="#fn:2" class="footnote-ref" role="doc-noteref"&gt;2&lt;/a&gt;&lt;/sup&gt;, as well as the shepherding of &lt;a href="https://www.r-rse.eu/"&gt;Anna Krystalli&lt;/a&gt; and &lt;a href="https://www.paulamoraga.com/"&gt;Paula Moraga&lt;/a&gt; as editors.&lt;/p&gt;
&lt;p&gt;As of Monday, March 20th, the reviewed version has officially &lt;a href="https://cran.r-project.org/package=waywiser"&gt;made its way to CRAN&lt;/a&gt;. This is a &lt;a href="https://docs.ropensci.org/waywiser/news/index.html#waywiser-030"&gt;huge update&lt;/a&gt;, bringing in a ton of new functions and improving consistency and speed across the package, and I&amp;rsquo;m excited to have it officially released.&lt;/p&gt;</description></item><item><title>How r-universe searches for packages on CRAN / Bioconductor</title><link>https://ropensci.org/blog/2023/04/03/cran-to-git/</link><pubDate>Mon, 03 Apr 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2023/04/03/cran-to-git/</guid><description>
&lt;h2&gt;
How packages appear in r-universe
&lt;/h2&gt;&lt;p&gt;Last month we explained how r-universe makes it easy to search and browse through the countless R packages, articles, and datasets to let you &lt;a href="https://ropensci.org/blog/2023/02/27/runiverse-discovering/"&gt;discover and learn&lt;/a&gt; new things. We are continuously growing this database by adding more R projects, to guide you through everything the R ecosystem has to offer.&lt;/p&gt;
&lt;p&gt;Currently r-universe is tracking and indexing of over 18.000 R packages. These are a mix of packages found on popular networks like &lt;a href="https://cran.r-project.org/"&gt;CRAN&lt;/a&gt; or &lt;a href="https://www.bioconductor.org/"&gt;Bioconductor&lt;/a&gt;, and packages that were registered by users.&lt;/p&gt;</description></item><item><title>Meeting the Stars of the R-Universe: Researching Our Brain with the Magic of the R-Universe</title><link>https://ropensci.org/blog/2023/03/30/r-universe-stars-3-en/</link><pubDate>Thu, 30 Mar 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2023/03/30/r-universe-stars-3-en/</guid><description><i><a href="https://ropensci.org/es/blog/2023/03/30/r-universe-stars-3-es/">Read it in: Español</a>.</i>
&lt;p&gt;A new post of our interview series &lt;a href="https://ropensci.org/tags/r-universe-stars/"&gt;“Meeting the stars of the R-universe”&lt;/a&gt;. We aim to introduce the teams and people behind the development of software and packages many of us use and which are available through the R-Universe. We want to highlight and explore different teams and projects around the world, the work they do, their processes and users. Our third stop is &lt;strong&gt;Norway&lt;/strong&gt; to talk with &lt;strong&gt;Athanasia Monika Mowinckel&lt;/strong&gt;. Be sure to watch the &lt;a href="https://ropensci.org/blog/2023/03/30/r-universe-stars-3-en/#video-of-the-interview"&gt;video&lt;/a&gt; at the end with excerpts from the interview.&lt;/p&gt;</description></item><item><title>Package Development: Not Rocket Science (champions training)</title><link>https://ropensci.org/events/2023-03-23-pkg-dev-not-rocket-science-champions/</link><pubDate>Thu, 23 Mar 2023 11:00:00 +0000</pubDate><guid>https://ropensci.org/events/2023-03-23-pkg-dev-not-rocket-science-champions/</guid><description/></item><item><title>rOpenSci News Digest, March 2023</title><link>https://ropensci.org/blog/2023/03/17/ropensci-news-digest-march-2023/</link><pubDate>Fri, 17 Mar 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2023/03/17/ropensci-news-digest-march-2023/</guid><description>
&lt;!-- Before sending DELETE THE INDEX_CACHE and re-knit! --&gt;
&lt;p&gt;Dear rOpenSci friends, it&amp;rsquo;s time for our monthly news roundup!&lt;/p&gt;
&lt;!-- blabla --&gt;
&lt;p&gt;You can read this post &lt;a href="https://ropensci.org/blog/2023/03/17/ropensci-news-digest-march-2023"&gt;on our blog&lt;/a&gt;.
Now let&amp;rsquo;s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;h3&gt;
Meeting the stars of the R-universe: Sébastien Rochette
&lt;/h3&gt;&lt;p&gt;Knowing our community&amp;rsquo;s stories helps us to learn about the people behind our software, brings us closer and offers us new opportunities. To share some of these community stories, we created the rOpenSci interview series &lt;a href="https://ropensci.org/tags/r-universe-stars/"&gt;&lt;em&gt;&amp;ldquo;Meeting the stars of the R-Universe&amp;rdquo;&lt;/em&gt;&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Package Development: the Mechanics (champions training)</title><link>https://ropensci.org/events/2023-03-14-pkg-dev-mechanics-champions/</link><pubDate>Tue, 14 Mar 2023 14:00:00 +0000</pubDate><guid>https://ropensci.org/events/2023-03-14-pkg-dev-mechanics-champions/</guid><description/></item><item><title>Social Coworking and Office Hours - Checking data with naniar, visdat, assertr, and skimr</title><link>https://ropensci.org/events/coworking-2023-03/</link><pubDate>Tue, 07 Mar 2023 03:00:00 +0000</pubDate><guid>https://ropensci.org/events/coworking-2023-03/</guid><description>
&lt;!--
d &lt;- lubridate::ymd_hms('2023-03-07 09:00:00', tz = 'Australia/Perth')
lubridate::with_tz(d, 'UTC')
lubridate::with_tz(d, 'America/Winnipeg')
--&gt;
&lt;p&gt;&lt;strong&gt;Join us for 2 hours Tuesday March 07, 09:00 Australian Western (01:00 UTC) for
&lt;a href="https://ropensci.org/blog/2021/08/17/coworking-sessions/"&gt;Social Coworking + Office Hours&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This month we&amp;rsquo;re focusing on the theme &lt;strong&gt;Checking data with &lt;a href="https://naniar.njtierney.com/"&gt;naniar&lt;/a&gt;, &lt;a href="https://docs.ropensci.org/visdat/"&gt;visdat&lt;/a&gt;,
&lt;a href="https://docs.ropensci.org/assertr/"&gt;assertr&lt;/a&gt;, and
&lt;a href="https://docs.ropensci.org/skimr/"&gt;skimr&lt;/a&gt;&lt;/strong&gt;
with community host &lt;strong&gt;Nick Tierney&lt;/strong&gt;, R enthusiast and author of several R packages (including naniar and visdat!).&lt;/p&gt;
&lt;p&gt;Come for the full 2 hrs or only as long as you need!&lt;/p&gt;</description></item><item><title>Meeting the Stars of the R-universe: ThinkR's Approach to Contributing to a Growing and Friendly R Community</title><link>https://ropensci.org/blog/2023/02/28/r-universe-stars-2-en/</link><pubDate>Tue, 28 Feb 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2023/02/28/r-universe-stars-2-en/</guid><description><i><a href="https://ropensci.org/es/blog/2023/02/28/r-universe-stars-2-es/">Read it in: Español</a>.</i><i><a href="https://ropensci.org/fr/blog/2023/02/28/r-universe-stars-2-fr/">Read it in: Français</a>.</i>
&lt;p&gt;This is the second post of our interview series &lt;a href="https://ropensci.org/tags/r-universe-stars/"&gt;“Meeting the stars of the R-universe”&lt;/a&gt;. We aim to introduce the working groups and people behind the development of software and packages many of us use and which are available through the R-universe. We want to highlight and explore different teams and projects around the world, the work they do, their processes and users.&lt;/p&gt;
&lt;p&gt;We continue our journey in France with Sébastien Rochette, R Expert at &lt;a href="https://rtask.thinkr.fr"&gt;ThinkR&lt;/a&gt;, a company focused on teaching and training as well as developing open source R packages. Be sure to watch the &lt;a href="2023/02/23/r-universe-stars-2-en/#video-of-the-interview"&gt;video&lt;/a&gt; at the end with excerpts from the interview.
&lt;figure class="pull-left"&gt;&lt;img src="https://ropensci.org/img/community/sebastien-rochette.jpeg"
alt="Profile photo of Sébastien Rochette." width="300"&gt;&lt;figcaption&gt;
&lt;p&gt;&lt;center&gt;&lt;strong&gt;Sébastien Rochette&lt;/strong&gt;&lt;br&gt;Head of Production at ThinkR&lt;/center&gt;&lt;/p&gt;</description></item><item><title>Discovering and learning everything there is to know about R packages using r-universe</title><link>https://ropensci.org/blog/2023/02/27/runiverse-discovering/</link><pubDate>Mon, 27 Feb 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2023/02/27/runiverse-discovering/</guid><description><i><a href="https://ropensci.org/es/blog/2023/02/27/runiverse-discovering-es/">Read it in: Español</a>.</i>
&lt;h2&gt;
Finding the right tool for the job
&lt;/h2&gt;&lt;p&gt;The hardest part about effectively using R is finding the best packages for the problem you are trying to solve. I think this is even more important than being fluent in the language itself, which you will pick up along the way as you start using R more frequently. However, building your code on reliable foundations is essential for good results, and difficult to fix later on in a project.&lt;/p&gt;</description></item><item><title>rOpenSci. Reproducible Open Science for (and by) All</title><link>https://ropensci.org/events/2023-02-23-toronto_workshop/</link><pubDate>Thu, 23 Feb 2023 13:15:00 +0000</pubDate><guid>https://ropensci.org/events/2023-02-23-toronto_workshop/</guid><description/></item><item><title>rOpenSci Champions Program. Mentorship Training and Orientation</title><link>https://ropensci.org/events/2023-03-01-mentor-orientation/</link><pubDate>Tue, 21 Feb 2023 14:00:00 +0000</pubDate><guid>https://ropensci.org/events/2023-03-01-mentor-orientation/</guid><description/></item><item><title>rOpenSci Champions Program Kick off</title><link>https://ropensci.org/blog/2023/02/21/champions-program-kick-off/</link><pubDate>Tue, 21 Feb 2023 00:00:01 -0600</pubDate><guid>https://ropensci.org/blog/2023/02/21/champions-program-kick-off/</guid><description><i><a href="https://ropensci.org/es/blog/2023/02/21/champions-program-kick-off-es/">Read it in: Español</a>.</i>
&lt;h2&gt;
The Champions Program got off to a great start in 2023!
&lt;/h2&gt;&lt;p&gt;We&amp;rsquo;re happy to report on the first couple of months in our first run of the &lt;a href="https://ropensci.org/champions/"&gt;rOpenSci Champions Program&lt;/a&gt;. In September 2022, we launched the program, advertising for both mentors and mentees to apply.&lt;/p&gt;
&lt;p&gt;We received a total of &lt;strong&gt;102&lt;/strong&gt; applications from &lt;strong&gt;31&lt;/strong&gt; different countries. Seventy-four applications were for champions and twenty eight for mentors. We are very grateful to everyone who took the time to apply to our program.&lt;/p&gt;</description></item><item><title>rOpenSci News Digest, February 2023</title><link>https://ropensci.org/blog/2023/02/17/ropensci-news-digest-february-2023/</link><pubDate>Fri, 17 Feb 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2023/02/17/ropensci-news-digest-february-2023/</guid><description>
&lt;!-- Before sending DELETE THE INDEX_CACHE and re-knit! --&gt;
&lt;p&gt;Dear rOpenSci friends, it&amp;rsquo;s time for our monthly news roundup!&lt;/p&gt;
&lt;!-- blabla --&gt;
&lt;p&gt;You can read this post &lt;a href="https://ropensci.org/blog/2023/02/17/ropensci-news-digest-february-2023"&gt;on our blog&lt;/a&gt;.
Now let&amp;rsquo;s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;h3&gt;
R-universe improvements!
&lt;/h3&gt;&lt;p&gt;We have changed the preferred git repo name where you host your &lt;code&gt;packages.json&lt;/code&gt; registry for R-universe, see our post &lt;a href="https://ropensci.org/blog/2023/02/07/runiverse-registry-repo/"&gt;New preferred repo name for r-universe registries&lt;/a&gt;.
We now recommend to use the full lowercase name of your R-universe domain as the repo name, for instance &lt;code&gt;TileDB-Inc/tiledb-inc.r-universe.dev&lt;/code&gt;.&lt;/p&gt;</description></item><item><title>rOpenSci Champions Program. A mentoring &amp; training program for Scientific Open Source Champions</title><link>https://ropensci.org/events/2023-02-16-eurobioimaging/</link><pubDate>Thu, 16 Feb 2023 11:00:00 +0000</pubDate><guid>https://ropensci.org/events/2023-02-16-eurobioimaging/</guid><description/></item><item><title>Multilingual Publishing</title><link>https://ropensci.org/events/2023-02-09-bioconductor/</link><pubDate>Thu, 09 Feb 2023 09:00:00 +0000</pubDate><guid>https://ropensci.org/events/2023-02-09-bioconductor/</guid><description/></item><item><title>Social Coworking and Office Hours - Setting up Continuous Integration</title><link>https://ropensci.org/events/coworking-2023-02/</link><pubDate>Tue, 07 Feb 2023 19:00:00 +0000</pubDate><guid>https://ropensci.org/events/coworking-2023-02/</guid><description>
&lt;!--
```{r}
d &lt;- lubridate::ymd_hms('2023-02-07 09:00:00', tz = 'America/Vancouver')
lubridate::with_tz(d, 'UTC')
lubridate::with_tz(d, 'America/Winnipeg')
```
--&gt;
&lt;p&gt;&lt;strong&gt;Join us for 2 hours Tuesday February 07, 09:00 Americas Pacific (17:00 UTC) for
&lt;a href="https://ropensci.org/blog/2021/08/17/coworking-sessions/"&gt;Social Coworking + Office Hours&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This month we&amp;rsquo;re focusing on the theme &lt;strong&gt;Setting up Continuous Integration (CI)&lt;/strong&gt;
with community host &lt;strong&gt;&lt;a href="https://ropensci.org/author/hugo-gruson"&gt;Hugo Gruson&lt;/a&gt;&lt;/strong&gt;, Research Software Engineer in Epidemiology
and CI/automation addict.&lt;/p&gt;
&lt;p&gt;Come for the full 2 hrs or only as long as you need!&lt;/p&gt;</description></item><item><title>New preferred repo name for r-universe registries</title><link>https://ropensci.org/blog/2023/02/07/runiverse-registry-repo/</link><pubDate>Tue, 07 Feb 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2023/02/07/runiverse-registry-repo/</guid><description>
&lt;h2&gt;
Running your own package registry
&lt;/h2&gt;&lt;p&gt;Tiny update for &lt;a href="https://r-universe.dev"&gt;r-universe&lt;/a&gt; users whos run their own package registry: we have changed the preferred git repo name where you host your &lt;code&gt;packages.json&lt;/code&gt; registry file.&lt;/p&gt;
&lt;p&gt;Previously the git repository was simply called &lt;code&gt;universe&lt;/code&gt;, i.e. the registry for &lt;a href="https://tiledb-inc.r-universe.dev"&gt;tiledb-inc.r-universe.dev&lt;/a&gt; was in the GitHub repository &lt;code&gt;tiledb-inc/universe&lt;/code&gt;. We now recommend to instead use the full lowercase name of your r-universe domain as the repo name, i.e &lt;a href="https://github.com/tiledb-inc/tiledb-inc.r-universe.dev"&gt;&lt;code&gt;tiledb-inc/tiledb-inc.r-universe.dev&lt;/code&gt;&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;For now the old name &lt;code&gt;universe&lt;/code&gt; will keep working as well, but this will be deprecated in 2024 so we recommend renaming it now.&lt;/p&gt;</description></item><item><title>What Does It Mean to Maintain a Package?</title><link>https://ropensci.org/blog/2023/02/07/what-does-it-mean-to-maintain-a-package/</link><pubDate>Tue, 07 Feb 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2023/02/07/what-does-it-mean-to-maintain-a-package/</guid><description><i><a href="https://ropensci.org/es/blog/2023/02/07/what-does-it-mean-to-maintain-a-package/">Read it in: Español</a>.</i><i><a href="https://ropensci.org/pt/blog/2023/02/07/o-que-significa-manter-um-pacote/">Read it in: Português</a>.</i>
&lt;p&gt;Part of what we aim to do at rOpenSci is nurture a community of package maintainers who help each other.
In addition to support during package maintenance, we also want to support maintainers who wish to move on. Situations can change, and there may come a time when a maintainer is looking to pass maintenance on to another. If a maintainer finds themself in this situation and would like to transfer maintainership, we help by &lt;a href="https://ropensci.org/blog/2022/10/17/maintain-or-co-maintain-an-ropensci-package/"&gt;advertising&lt;/a&gt;, and also help the new maintainer(s) with advice, generally à la &amp;ldquo;look around to see if anything needs fixing, then do routine maintenance&amp;rdquo;.
But what is routine maintenance? This post is an attempt to define what package maintenance entails, with a few tips.&lt;/p&gt;</description></item><item><title>{targets} in Action</title><link>https://ropensci.org/commcalls/jan2023-targets/</link><pubDate>Fri, 06 Jan 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/commcalls/jan2023-targets/</guid><description>
&lt;p&gt;The &lt;a href="https://docs.ropensci.org/targets/"&gt;{targets}&lt;/a&gt; package is a pipeline tool for Statistics and data science in R. With {targets}, you can maintain a reproducible workflow without repeating yourself. {targets} learns how your pipeline fits together, skips costly runtime for tasks that are already up to date, runs only the necessary computation, supports implicit parallel computing, abstracts files as R objects, and shows tangible evidence that the results match the underlying code and data.&lt;/p&gt;
&lt;p&gt;On this call Will, Eric and Joel will share their experience putting &lt;strong&gt;{targets} into action&lt;/strong&gt;. Eric will share with us &lt;em&gt;Using {targets} with HPC&lt;/em&gt; and Joel will talk about &lt;em&gt;Using {targets} for bioinformatics pipelines&lt;/em&gt;, then Will will demonstrate &lt;em&gt;Debugging {targets} pipelines&lt;/em&gt;.&lt;/p&gt;</description></item><item><title>Dynamite for Causal Inference from Panel Data using Dynamic Multivariate Panel Models</title><link>https://ropensci.org/blog/2023/01/31/dynamite-r-package/</link><pubDate>Tue, 31 Jan 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2023/01/31/dynamite-r-package/</guid><description>
&lt;h2&gt;
Introduction
&lt;/h2&gt;&lt;p&gt;Panel data contains measurements from multiple subjects measured over multiple time points.
Such data can be encountered in many social science applications such as when analysing register data or cohort studies (for example).
Often the aim is to perform causal inference based on such observational data (instead of randomized control trials).&lt;/p&gt;
&lt;p&gt;A new &lt;a href="https://github.com/ropensci/software-review/issues/554"&gt;rOpensci-reviewed&lt;/a&gt; R package &lt;a href="https://docs.ropensci.org/dynamite"&gt;dynamite&lt;/a&gt; available on CRAN implements a new class of panel models called the Bayesian dynamic multivariate panel model (DMPM) which supports&lt;/p&gt;</description></item><item><title>Improved permanent URL schema for r-universe.dev</title><link>https://ropensci.org/blog/2023/01/30/runiverse-permanent-urls/</link><pubDate>Mon, 30 Jan 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2023/01/30/runiverse-permanent-urls/</guid><description>
&lt;style&gt;
ul a:hover{text-decoration: underline;}
&lt;/style&gt;
&lt;h2&gt;
Pretty permanent URLs!
&lt;/h2&gt;&lt;p&gt;We have improved the URL schema for the &lt;a href="https://r-universe.dev"&gt;r-universe.dev&lt;/a&gt; front-end to make it even easier to find and share a link to an R package, article, API, or other resource.&lt;/p&gt;
&lt;p&gt;The old URLs will now automatically be redirected to the new locations, so this should be a non-breaking change. But of course we recommend updating your references to link to the new permanent URLs.&lt;/p&gt;</description></item><item><title>rOpenSci News Digest, January 2023</title><link>https://ropensci.org/blog/2023/01/20/ropensci-news-digest-january-2023/</link><pubDate>Fri, 20 Jan 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2023/01/20/ropensci-news-digest-january-2023/</guid><description>
&lt;!-- Before sending DELETE THE INDEX_CACHE and re-knit! --&gt;
&lt;p&gt;Dear rOpenSci friends, it&amp;rsquo;s time for our monthly news roundup!&lt;/p&gt;
&lt;!-- blabla --&gt;
&lt;p&gt;You can read this post &lt;a href="https://ropensci.org/blog/2023/01/20/ropensci-news-digest-january-2023"&gt;on our blog&lt;/a&gt;.
Now let&amp;rsquo;s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;h3&gt;
{targets} in Action Community Call
&lt;/h3&gt;&lt;p&gt;Tuesday, 31 January 2023 20:00 UTC / Tuesday, 31 January 2023 15:00 EST / Wednesday, 1st February 07:00 AEDT.&lt;/p&gt;
&lt;p&gt;The &lt;a href="https://docs.ropensci.org/targets/"&gt;{targets}&lt;/a&gt; package is a pipeline tool for Statistics and data science in R. With {targets}, you can maintain a reproducible workflow without repeating yourself. {targets} learns how your pipeline fits together, skips costly runtime for tasks that are already up to date, runs only the necessary computation, supports implicit parallel computing, abstracts files as R objects, and shows tangible evidence that the results match the underlying code and data.&lt;/p&gt;</description></item><item><title>curl 5.0.0: massive concurrent downloads and HTTP/2</title><link>https://ropensci.org/blog/2023/01/13/curl5-release/</link><pubDate>Fri, 13 Jan 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2023/01/13/curl5-release/</guid><description>
&lt;h2&gt;
curl 5.0.0 is on CRAN
&lt;/h2&gt;&lt;p&gt;A new major version of the &lt;a href="https://cran.r-project.org/web/packages/curl/index.html"&gt;curl&lt;/a&gt; package has been released to CRAN. This release both brings internal improvements as well as new user-facing functionality, in particular with respect to concurrent downloads. From the &lt;a href="https://cran.r-project.org/web/packages/curl/NEWS"&gt;NEWS&lt;/a&gt; file:&lt;/p&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;curl 5.0.0
- New function multi_download() which supports concurrent downloads and resuming
download for large files, while giving detailed progress information.
- Windows: updated libcurl to 7.84.0 + nghttp2
- Windows: default to CURLSSLOPT_NATIVE_CA when using openssl unless an ennvar
with CURL_CA_BUNDLE is set.
- Use the new optiontype API for type checking if available (libcurl 7.73.0)
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;The curl package is used by most other R packages for performing HTTP requests. Over 60% of rOpenSci packages directly or indirectly depend on curl for network interaction, hence improvements and bugs in curl have a big impact on the entire ecosystem.&lt;/p&gt;</description></item><item><title>Expanding our Community through Multilingual Publishing</title><link>https://ropensci.org/blog/2023/01/12/multilingual-publishing-en/</link><pubDate>Thu, 12 Jan 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2023/01/12/multilingual-publishing-en/</guid><description><i><a href="https://ropensci.org/es/blog/2023/01/12/multilingual-publishing-es/">Read it in: Español</a>.</i>
&lt;p&gt;We are excited to announce that, with the support of the Chan Zuckerberg Initiative, NumFOCUS, and the R Consortium, we have begun the process of translating rOpenSci&amp;rsquo;s materials on best practices for software development, code review, and contribution to open source projects into Spanish.
As part of this effort, we are also developing guidelines and tools for translating open source resources to reach a wider audience.&lt;/p&gt;
&lt;p&gt;According to a &lt;a href="https://www.linuxfoundation.org/research/the-2021-linux-foundation-report-on-diversity-equity-and-inclusion-in-open-source"&gt;recent report&lt;/a&gt; from The Linux Foundation, &lt;em&gt;language access&lt;/em&gt; is one of the &lt;em&gt;environmental barriers to equity in open source&lt;/em&gt;. The report states that&lt;/p&gt;</description></item><item><title>Social Coworking and Office Hours - Working with new R users</title><link>https://ropensci.org/events/coworking-2023-01/</link><pubDate>Tue, 10 Jan 2023 15:00:00 +0000</pubDate><guid>https://ropensci.org/events/coworking-2023-01/</guid><description>
&lt;!--
```{r}
d &lt;- lubridate::ymd_hms('2023-01-10 14:00:00', tz = 'Europe/Paris')
lubridate::with_tz(d, 'UTC')
lubridate::with_tz(d, 'America/Winnipeg')
```
--&gt;
&lt;p&gt;&lt;strong&gt;Join us for 2 hours Tuesday January 10, 14:00 European Central (13:00 UTC) for
&lt;a href="https://ropensci.org/blog/2021/08/17/coworking-sessions/"&gt;Social Coworking + Office Hours&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This month we&amp;rsquo;re focusing on the theme &lt;strong&gt;Working with new R users&lt;/strong&gt;
with community host &lt;strong&gt;&lt;a href="https://alexkoiter.ca"&gt;Alex Koiter&lt;/a&gt;&lt;/strong&gt;, who is a professor in Geography and is
enthusiastic about introducing R to undergraduate students.&lt;/p&gt;
&lt;p&gt;Come for the full 2 hrs or only as long as you need!&lt;/p&gt;</description></item><item><title>rOpenSci 2022 Code of Conduct Transparency Report</title><link>https://ropensci.org/blog/2023/01/06/transparency2022/</link><pubDate>Fri, 06 Jan 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2023/01/06/transparency2022/</guid><description>
&lt;p&gt;The rOpenSci community is supported by our &lt;a href="https://ropensci.org/code-of-conduct"&gt;Code of Conduct&lt;/a&gt; with a clear description of unacceptable behaviors,
instructions on how to make a report, and information on how reports are handled. We, the Code of Conduct Committee,
are responsible for receiving, investigating, deciding, enforcing and reporting on all reports of potential
violations of our Code. We are committed to transparency with our community while upholding the privacy
of people who experience or report incidents.&lt;/p&gt;</description></item><item><title>rOpenSci Code of Conduct Annual Review</title><link>https://ropensci.org/blog/2023/01/06/conduct2023/</link><pubDate>Fri, 06 Jan 2023 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2023/01/06/conduct2023/</guid><description>
&lt;p&gt;This report presents our annual review of the rOpenSci Code of Conduct, reporting process, and internal guidelines for handling reports and enforcement.&lt;/p&gt;
&lt;h3&gt;
Updates
&lt;/h3&gt;&lt;ul&gt;
&lt;li&gt;Changes to the text, including addition of greater detail about acceptable and unacceptable behaviors in online settings.&lt;/li&gt;
&lt;li&gt;Added a new language, through doing the first translation of the text to Spanish.&lt;/li&gt;
&lt;li&gt;Changes to the committee. We thank &lt;a href="https://www.esipfed.org/about/people/megan-carter"&gt;Megan Carter&lt;/a&gt; for serving as independent community member until June 2022
and welcome back &lt;a href="https://karawoo.com/"&gt;Kara Woo&lt;/a&gt; to serve in this role. &lt;a href="https://ropensci.org/author/yanina-bellini-saibene/"&gt;Yanina Bellini Saibene&lt;/a&gt; joins the
committee as the new rOpenSci Community Manager.&lt;/li&gt;
&lt;li&gt;Review of our processes. We reviewed our onboarding and offboarding process for the code of conduct committee and generated templates for incident management.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;These changes were released July 7, 2022 as version 2.4.&lt;/p&gt;</description></item><item><title>rOpenSci News Digest, December 2022</title><link>https://ropensci.org/blog/2022/12/16/ropensci-news-digest-december-2022/</link><pubDate>Fri, 16 Dec 2022 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2022/12/16/ropensci-news-digest-december-2022/</guid><description>
&lt;!-- Before sending DELETE THE INDEX_CACHE and re-knit! --&gt;
&lt;p&gt;Dear rOpenSci friends, it&amp;rsquo;s time for our monthly news roundup!&lt;/p&gt;
&lt;!-- blabla --&gt;
&lt;p&gt;You can read this post &lt;a href="https://ropensci.org/blog/2022/12/16/ropensci-news-digest-december-2022"&gt;on our blog&lt;/a&gt;.
Now let&amp;rsquo;s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;!-- to be curated manually --&gt;
&lt;h3&gt;
One-page HTML package manuals on R-universe!
&lt;/h3&gt;&lt;p&gt;We have recently started building HTML reference manuals for each package in the R-universe! For packages that have had an update in the past 3 weeks, the reference manual is now linked from the package homepage on &lt;a href="https://r-universe.dev"&gt;R-universe.dev&lt;/a&gt;. All packages in the R-universe are rebuilt at least once per month, so soon all packages should have an online HTML manual.
You can also find &lt;a href="https://r-universe.dev/manuals/"&gt;reference manuals for base-R packages&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Social Coworking and Office Hours - Getting started with targets!</title><link>https://ropensci.org/events/coworking-2022-12/</link><pubDate>Tue, 06 Dec 2022 03:00:00 +0000</pubDate><guid>https://ropensci.org/events/coworking-2022-12/</guid><description>
&lt;!--
```{r}
d &lt;- lubridate::ymd_hms("2022-12-06 09:00:00", tz = "Australia/Perth")
lubridate::with_tz(d, "UTC")
lubridate::with_tz(d, "America/Winnipeg")
lubridate::with_tz(d, "America/Vancouver")
```
--&gt;
&lt;p&gt;&lt;strong&gt;Join us for 2 hours Tuesday, December 6th, 9 AM Australian Western / 1:00 UTC for&lt;br&gt;&lt;a href="https://ropensci.org/blog/2021/08/17/coworking-sessions/"&gt;Social Coworking + Office Hours&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This October we&amp;rsquo;re focusing on the theme &lt;strong&gt;Getting started with targets!&lt;/strong&gt;
with community host &lt;strong&gt;&lt;a href="https://ropensci.org/author/nicholas-tierney"&gt;Nick Tierney&lt;/a&gt;&lt;/strong&gt;, R and targets enthusiast and author of several R packages.&lt;/p&gt;
&lt;p&gt;Come for the full 2 hrs or only as long as you need!&lt;/p&gt;</description></item><item><title>How to Save ggplot2 Plots in a targets Workflow?</title><link>https://ropensci.org/blog/2022/12/06/save-ggplot2-targets/</link><pubDate>Tue, 06 Dec 2022 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2022/12/06/save-ggplot2-targets/</guid><description>
&lt;p&gt;I really enjoy using &lt;a href="https://docs.ropensci.org/targets"&gt;targets&lt;/a&gt; for all of my data analysis projects, especially because it helps me structure all of the projects nicely in the same folder.
For targets projects, I often produce several figures using ggplot2.
However, there are no formal recommendations for saving ggplot2 objects (as opposed to static images) in a targets workflow.&lt;/p&gt;
&lt;p&gt;I want to keep my plots accessible to be able to revisit them any time and to assemble them with &lt;a href="https://patchwork.data-imaginist.com/"&gt;patchwork&lt;/a&gt; into more complex figures for a potential paper.
In a regular project I generate 10 to 20 figures, some only diagnostic ones and some polished ones for the finished manuscript.
I do revisit the list of figures often, as co-authors or reviewers ask me for more detailed analyses and visualizations.&lt;/p&gt;</description></item><item><title>Our First Peer-Reviewed Statistical R Packages!</title><link>https://ropensci.org/blog/2022/11/30/first-peer-reviewed-stats-packages/</link><pubDate>Wed, 30 Nov 2022 00:00:01 -0700</pubDate><guid>https://ropensci.org/blog/2022/11/30/first-peer-reviewed-stats-packages/</guid><description>
&lt;p&gt;rOpenSci is &lt;em&gt;very&lt;/em&gt; excited to announce our first peer-reviewed statistical R
packages!&lt;/p&gt;
&lt;p&gt;One of rOpenSci&amp;rsquo;s core programs is software peer-review, where we use &lt;a href="https://www.youtube.com/watch?v=o_WEhg6sSSQ"&gt;best
practices from software engineering and academic peer-review to improve
scientific software&lt;/a&gt;. Through this, we aim to make scientific software more
robust, usable, and trustworthy, and build a supportive community of practitioners.&lt;/p&gt;
&lt;p&gt;Historically, we have focused on R packages that manage
the &lt;a href="https://devguide.ropensci.org/policies.html#aims-and-scope"&gt;research data life
cycle&lt;/a&gt;. Now, thanks
to work over the past two years &lt;a href="https://ropensci.org/blog/2019/07/15/expanding-software-review/"&gt;supported by the Sloan
Foundation&lt;/a&gt; we
also facilitate peer-review of packages that implement statistical algorithms. The first
statistical packages to pass peer review are:&lt;/p&gt;</description></item><item><title>postdoc 1.0: minimal and uncluttered HTML package manuals</title><link>https://ropensci.org/blog/2022/11/29/postdoc-docs/</link><pubDate>Tue, 29 Nov 2022 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2022/11/29/postdoc-docs/</guid><description>
&lt;h2&gt;
Two new packages!
&lt;/h2&gt;&lt;p&gt;We released two new packages that we are using in &lt;a href="https://r-universe.dev"&gt;r-universe&lt;/a&gt; to render package documentation: &lt;a href="https://docs.ropensci.org/postdoc/"&gt;postdoc&lt;/a&gt; and &lt;a href="https://docs.ropensci.org/prismjs/"&gt;prismjs&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;The goal of postdoc is very simple: generate beautiful single-page package manuals in HTML format. Postdoc uses our &lt;a href="https://docs.ropensci.org/prismjs/"&gt;prismjs&lt;/a&gt; and &lt;a href="https://docs.ropensci.org/katex/"&gt;katex&lt;/a&gt; packages for server-side highlighting and math. Try it yourself:&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-r" data-lang="r"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# Download and install postdoc in R&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nf"&gt;install.packages&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s"&gt;&amp;#39;postdoc&amp;#39;&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="n"&gt;repos&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nf"&gt;c&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s"&gt;&amp;#39;https://ropensci.r-universe.dev&amp;#39;&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="s"&gt;&amp;#39;https://cloud.r-project.org&amp;#39;&lt;/span&gt;&lt;span class="p"&gt;))&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# Generate a manual for &amp;#39;jsonlite&amp;#39;&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="n"&gt;html&lt;/span&gt; &lt;span class="o"&gt;&amp;lt;-&lt;/span&gt; &lt;span class="n"&gt;postdoc&lt;/span&gt;&lt;span class="o"&gt;::&lt;/span&gt;&lt;span class="nf"&gt;render_package_manual&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s"&gt;&amp;#34;jsonlite&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s"&gt;&amp;#34;.&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="n"&gt;utils&lt;/span&gt;&lt;span class="o"&gt;::&lt;/span&gt;&lt;span class="nf"&gt;browseURL&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;html&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;We have recently started building the reference manuals for each package r-universe: for packages that have had an update in the past 10 days, the reference manual is now linked from the package homepage on &lt;a href="https://r-universe.dev"&gt;r-universe.dev&lt;/a&gt;. All packages in in r-universe gets rebuilt at least once per month, so soon all packages should have the manual. Postdoc reference manuals for base-R packages can be found &lt;a href="https://r-universe.dev/manuals/"&gt;here&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Meeting the stars of the R-universe: R Community, Exchange and Learn</title><link>https://ropensci.org/blog/2022/11/23/r-universe-stars-1-en/</link><pubDate>Wed, 23 Nov 2022 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2022/11/23/r-universe-stars-1-en/</guid><description><i><a href="https://ropensci.org/es/blog/2022/11/23/r-universe-stars-1-es/">Read it in: Español</a>.</i>
&lt;p&gt;This is the first post of our interview series &lt;strong&gt;&amp;ldquo;Meeting the stars of the R-universe&amp;rdquo;&lt;/strong&gt;. We aim to introduce the working groups and people behind the development of software and packages many of us use and which are available through the &lt;em&gt;R-Universe&lt;/em&gt;. We want to highlight and explore different teams and projects around the world, the work they do, their processes and users. We begin our journey in &lt;em&gt;Argentina&lt;/em&gt; with a team that uses R and develops R packages for the Argentinean State. Be sure to watch the &lt;a href="#video-of-the-interview"&gt;video&lt;/a&gt; at the end with excerpts from the interview.&lt;/p&gt;</description></item><item><title>Delete all your tweets using rtweet</title><link>https://ropensci.org/usecases/delete-all-your-tweets-using-rtweet/</link><pubDate>Tue, 22 Nov 2022 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/delete-all-your-tweets-using-rtweet/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/rtweet/"&gt;rtweet&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;Worried about how a certain social media platform is going and want to start reducing your footprint there? If you are looking to remove yourself Twitter, you can entirely delete your account, but I’ve seen some folks say a better initial move may be to delete the content from your account (perhaps including followers and following), and then take your account private or deactivate it. This has the benefit of you keeping control of your username. In this blog post, I walked through how to use &lt;a href="https://docs.ropensci.org/rtweet/"&gt;rtweet&lt;/a&gt; to automate some of these steps. I deleted about 25,000 tweets using this method!&lt;/p&gt;</description></item><item><title>rOpenSci News Digest, November 2022</title><link>https://ropensci.org/blog/2022/11/18/ropensci-news-digest-november-2022/</link><pubDate>Fri, 18 Nov 2022 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2022/11/18/ropensci-news-digest-november-2022/</guid><description>
&lt;!-- Before sending DELETE THE INDEX_CACHE and re-knit! --&gt;
&lt;p&gt;Dear rOpenSci friends, it’s time for our monthly news roundup!&lt;/p&gt;
&lt;!-- blabla --&gt;
&lt;p&gt;You can read this post &lt;a href="https://ropensci.org/blog/2022/11/18/ropensci-news-digest-november-2022"&gt;on our blog&lt;/a&gt;.
Now let’s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;h3&gt;
Multilingual Publishing
&lt;/h3&gt;&lt;p&gt;Open Source and Open Science are global movements, but most of their material and resources are published in English, meaning non-English speakers face a significant barrier to being part of these movements.&lt;br&gt;
Publishing multilingual resources can lower these barriers by increasing access to knowledge, which helps democratize access to quality resources, and therefore increases the potential for contributing to software and open science projects.&lt;/p&gt;</description></item><item><title>rOpenSci's Communication Channels: Twitter</title><link>https://ropensci.org/blog/2022/11/16/mastodon-en/</link><pubDate>Wed, 16 Nov 2022 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2022/11/16/mastodon-en/</guid><description><i><a href="https://ropensci.org/es/blog/2022/11/16/mastodon-es/">Read it in: Español</a>.</i>
&lt;p&gt;Twitter is one of the preferred social media platforms and networks for the R community and for the data, open science and research communities. Since the beginning of rOpenSci we have used Twitter to connect with our community and other parallel communities, to share what we do, and to be part of conversations around the topics important to our &lt;a href="https://ropensci.org/about/"&gt;mission&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;We aim to provide a safe and friendly space for everyone in our community, and this influences how we choose which spaces we use to interact with our community members.&lt;/p&gt;</description></item><item><title>Adding missing EXIF data to wildlife trail camera images</title><link>https://ropensci.org/usecases/adding-missing-exif-data-to-wildlife-trail-camera-images/</link><pubDate>Thu, 10 Nov 2022 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/adding-missing-exif-data-to-wildlife-trail-camera-images/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://github.com/ropensci/magick"&gt;magick&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;Use R/magick in combination with ffmpeg and exiftool, to add geolocation and date-time metadata to images where metadata was not created by the camera.&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://nsaunders.wordpress.com/2022/10/25/editing-metadata-in-trail-camera-images-using-r-magick-and-exiftool/"&gt;Editing metadata in trail camera images using R, magick and exiftool&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
Image
&lt;/h4&gt;&lt;p&gt;&lt;img src="https://ropensci.org/usecases/adding-missing-exif-data-to-wildlife-trail-camera-images/adding-missing-exif-data-to-wildlife-trail-camera-images.jpeg" alt="lXYtUbMxk8T5QM9jNPjUp6sZfraGvUtgl_vcaYsgvGBFgQK5EQBflHLs37cB_GXFo_|690x388"&gt;&lt;/p&gt;
&lt;h4&gt;
Sector
&lt;/h4&gt;&lt;p&gt;Other&lt;/p&gt;
&lt;h4&gt;
Field(s) of application
&lt;/h4&gt;&lt;p&gt;&lt;em&gt;ecology, citizen science&lt;/em&gt;&lt;/p&gt;</description></item><item><title>rOpenSci. Bringing the best parts of academic peer-review to research software</title><link>https://ropensci.org/events/notebooks-now-2022/</link><pubDate>Fri, 04 Nov 2022 20:00:00 +0000</pubDate><guid>https://ropensci.org/events/notebooks-now-2022/</guid><description/></item><item><title>The Challenges &amp; Opportunities of Sustaining Open Source Ecosystems</title><link>https://ropensci.org/events/2022-11-03-karthik-esa-esrin/</link><pubDate>Fri, 04 Nov 2022 18:00:00 +0000</pubDate><guid>https://ropensci.org/events/2022-11-03-karthik-esa-esrin/</guid><description>
&lt;p&gt;Our Project Lead and co-founder Karthik Ram gave a talk on Open Source Ecosystems (OSEs) at the Open Innovation for Earth Observation Programmes workshop organized by ESA and NASA in Frascati.&lt;/p&gt;
&lt;p&gt;In this talk, Karthik describe how The rOpenSci Project began as a small club (using Nadia Asparouhova’s terminology) and grew into a modest federation by engaging the community collaboration models described by CSCCE. We started out by conveying tools, then accepting contributions, collaborating with researchers via the peer-review system, and finally enabling co-creation via the r-universe. Karthik then cover how organizations like space agencies can stand up lightweight OSPOs to start, and use metrics (like those from CHAOSS) to help open-source projects thrive and succeed. Karthik then cover the various factors necessary to turn a nascent project into an OSE from early conversations as part of my newly funded POSE training program.&lt;/p&gt;</description></item><item><title>Social Coworking and Office Hours - Champions Program Application Clinic</title><link>https://ropensci.org/events/coworking-2022-11/</link><pubDate>Tue, 01 Nov 2022 18:00:00 +0000</pubDate><guid>https://ropensci.org/events/coworking-2022-11/</guid><description>
&lt;!--
```{r}
d &lt;- lubridate::ymd_hms("2022-11-01 09:00:00", tz = "America/Vancouver")
lubridate::with_tz(d, "UTC")
lubridate::with_tz(d, "America/Winnipeg")
```
--&gt;
&lt;p&gt;&lt;strong&gt;Join us for 2 hours Tuesday, November 1st, 9 AM North American Pacific / 16:00 UTC for &lt;a href="https://ropensci.org/blog/2021/08/17/coworking-sessions/"&gt;Social Coworking + Office Hours&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This month we have a special session operating as an Application Clinic for
the Champions Program with our community manager, &lt;strong&gt;Yanina Bellini Saibene&lt;/strong&gt;,
as co-host!&lt;/p&gt;
&lt;p&gt;Come for the full 2 hrs or only as long as you need!&lt;/p&gt;</description></item><item><title>Mentoring &amp; training program for Scientific Open Source Champions</title><link>https://ropensci.org/commcalls/oct2022-champions/</link><pubDate>Fri, 23 Sep 2022 00:00:00 +0000</pubDate><guid>https://ropensci.org/commcalls/oct2022-champions/</guid><description>
&lt;p&gt;Champions programs are designed to identify, recognize, and reward emerging leaders within a community. The &lt;a href="https://ropensci.org/champions/"&gt;rOpenSci Champions Program&lt;/a&gt; is part of a series of activities and projects we are carrying out to ensure our research software serves everyone in our communities, which means that it needs to be sustainable and open, and built by and for all groups.&lt;/p&gt;
&lt;p&gt;On this call &lt;em&gt;Santosh&lt;/em&gt; and &lt;em&gt;Emanuele&lt;/em&gt; will share their experience of being champions in their communities. We will highlight the benefits of being part of a champions program for you and for your community, what kind of learning, activities and opportunities an open source community champions program provides. &lt;em&gt;Yani&lt;/em&gt; will present the details of our Champion Program and answer all your question about it.&lt;/p&gt;</description></item><item><title>rOpenSci News Digest, October 2022</title><link>https://ropensci.org/blog/2022/10/21/ropensci-news-digest-october-2022/</link><pubDate>Fri, 21 Oct 2022 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2022/10/21/ropensci-news-digest-october-2022/</guid><description>
&lt;!-- Before sending DELETE THE INDEX_CACHE and re-knit! --&gt;
&lt;p&gt;Dear rOpenSci friends, it&amp;rsquo;s time for our monthly news roundup!&lt;/p&gt;
&lt;!-- blabla --&gt;
&lt;p&gt;You can read this post &lt;a href="https://ropensci.org/blog/2022/10/21/ropensci-news-digest-october-2022"&gt;on our blog&lt;/a&gt;.
Now let&amp;rsquo;s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;h3&gt;
rOpenSci Champions Program: call for Champions and call for Mentors
&lt;/h3&gt;&lt;p&gt;The &lt;a href="https://ropensci.org/champions/"&gt;rOpenSci Champions Program&lt;/a&gt; is part of a series of activities and projects we are carrying out to ensure our research software serves everyone in our communities.
That is why this program focuses on &lt;strong&gt;people who belong to groups that are historically and systematically excluded&lt;/strong&gt; from the open software and research software communities and who are interested in contributing to rOpenSci and the broader open source and research software communities.&lt;/p&gt;</description></item><item><title>Become a Mentor for rOpenSci Champions!</title><link>https://ropensci.org/blog/2022/10/20/mentors-champions-program/</link><pubDate>Thu, 20 Oct 2022 00:00:01 -0700</pubDate><guid>https://ropensci.org/blog/2022/10/20/mentors-champions-program/</guid><description>
&lt;h2&gt;
rOpenSci is seeking mentors to support our inaugural cohort of rOpenSci Champions!
&lt;/h2&gt;&lt;p&gt;The &lt;a href="https://ropensci.org/champions/"&gt;rOpenSci Champions Program&lt;/a&gt; is for &lt;em&gt;people from historically and systematically excluded groups&lt;/em&gt; who are interested in contributing to rOpenSci and the broader ecosystem of open source and open science communities. After receiving training, mentors will work with Champions to develop their project, which can be one of the following options:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Create a new package;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Go through the review process with an R package they have already developed;&lt;/p&gt;</description></item><item><title>Interesting Uses of censo2017 a Year After Publishing</title><link>https://ropensci.org/blog/2022/10/19/censo2017-one-year-after/</link><pubDate>Wed, 19 Oct 2022 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2022/10/19/censo2017-one-year-after/</guid><description><i><a href="https://ropensci.org/es/blog/2022/10/19/censo2017-one-year-after-es/">Read it in: Español</a>.</i>
&lt;h2&gt;
Summary
&lt;/h2&gt;&lt;p&gt;This post is about the surprising uses I’ve noticed and the questions
about the &lt;a href="https://docs.ropensci.org/censo2017"&gt;censo2017&lt;/a&gt; R package, a tool for
accessing the Chilean census 2017 data, I’ve gotten since it was peer-reviewed
through rOpenSci one year ago. The &lt;a href="https://ropensci.org/blog/2021/07/27/censo2017/"&gt;original
post&lt;/a&gt; about the
package one year ago didn’t cover the different examples I present here,
including a Python port of the R package.&lt;/p&gt;
&lt;h2&gt;
Organizing the census data
&lt;/h2&gt;&lt;p&gt;&lt;a href="https://ropensci.org/blog/2021/07/27/censo2017/"&gt;Three years ago&lt;/a&gt;, I had to complete an assignment that required me to
extract data from Windows-only software in DVD format, which got very
complicated.&lt;/p&gt;</description></item><item><title>rOpenSci. Open Source Software Community</title><link>https://ropensci.org/events/abuja-2022/</link><pubDate>Tue, 18 Oct 2022 15:00:00 +0000</pubDate><guid>https://ropensci.org/events/abuja-2022/</guid><description/></item><item><title>Maintain or Co-Maintain an rOpenSci Package!</title><link>https://ropensci.org/blog/2022/10/17/maintain-or-co-maintain-an-ropensci-package/</link><pubDate>Mon, 17 Oct 2022 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2022/10/17/maintain-or-co-maintain-an-ropensci-package/</guid><description>
&lt;p&gt;The rOpenSci &lt;a href="https://ropensci.org/packages"&gt;suite of packages&lt;/a&gt; is mainly composed of packages contributed by the community through &lt;a href="https://ropensci.org/software-review"&gt;peer-review&lt;/a&gt;, but also includes some packages maintained by staff.
Over time, the commitments and availability of the original developers of a package can change. This leads to some maintainers stepping down from their maintainer role, or other maintainers looking to lower their workload through more teamwork and therefore looking for co-maintainers.&lt;/p&gt;
&lt;p&gt;We&amp;rsquo;re so grateful for all our community maintainers and want to make sure that they feel good about the work they do and not burdened by the responsibility. This is why we started conducting annual maintainer surveys, to ensure that maintainers feel supported and feel free to say when they need help, or are ready to move on.
Following our recent annual maintainer survey, we have projects looking for both new maintainers and co-maintainers. Therefore, we say &lt;strong&gt;thank you!&lt;/strong&gt; to our maintainers looking to move on, and in this blog post we will explain why &lt;strong&gt;you&lt;/strong&gt; might want to help, and we&amp;rsquo;ll list the packages currently up for adoption or collaboration.&lt;/p&gt;</description></item><item><title>Backing up GitHub organisation with gitcellar</title><link>https://ropensci.org/usecases/backing-up-github-organisation-with-gitcellar/</link><pubDate>Wed, 12 Oct 2022 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/backing-up-github-organisation-with-gitcellar/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;ul&gt;
&lt;li&gt;&lt;a href="https://docs.ropensci.org/gitcellar/"&gt;gitcellar&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;blog post: &lt;a href="https://ropensci.org/blog/2022/03/22/safeguards-and-backups-for-github-organizations/"&gt;Safeguards and Backups for GitHub Organizations&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;I replicated the back-up infrastructure from rOpenSci in our GitHub organisation: &lt;a href="https://github.com/epiverse-trace"&gt;https://github.com/epiverse-trace&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Migration archives are created with gitcellar and are then uploaded to a DigitalOcean S3-compatible space with the &lt;code&gt;aws.s3&lt;/code&gt; R package.&lt;/p&gt;
&lt;p&gt;This is automated via GitHub Actions and runs on a weekly basis (each Saturday in the night).&lt;/p&gt;
&lt;p&gt;For increased security, I have created a dedicated GitHub account, &lt;a href="https://github.com/epiverse-trace-bot"&gt;&lt;code&gt;@epiverse-trace-bot&lt;/code&gt;&lt;/a&gt;, which hosts the repository with the automation and also provides a Personal Access Token (PAT) with minimal permissions.&lt;/p&gt;</description></item><item><title>Social Coworking and Office Hours - Start writing that package!</title><link>https://ropensci.org/events/coworking-2022-10/</link><pubDate>Tue, 04 Oct 2022 03:00:00 +0000</pubDate><guid>https://ropensci.org/events/coworking-2022-10/</guid><description>
&lt;!--
```{r}
d &lt;- lubridate::ymd_hms("2022-10-04 09:00:00", tz = "Australia/Perth")
lubridate::with_tz(d, "UTC")
lubridate::with_tz(d, "America/Winnipeg")
lubridate::with_tz(d, "America/Vancouver")
```
--&gt;
&lt;p&gt;&lt;strong&gt;Join us for 2 hours Tuesday, October 4th, 9 AM Australian Western / 1:00 UTC for&lt;br&gt;&lt;a href="https://ropensci.org/blog/2021/08/17/coworking-sessions/"&gt;Social Coworking + Office Hours&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This October we&amp;rsquo;re focusing on the theme &lt;strong&gt;Start writing that package!&lt;/strong&gt;
with community host &lt;strong&gt;Nick Tierney&lt;/strong&gt;, R enthusiast and author of several R packages.&lt;/p&gt;
&lt;p&gt;Come for the full 2 hrs or only as long as you need!&lt;/p&gt;</description></item><item><title>Using a targets pipeline to query data from the Water Quality Portal</title><link>https://ropensci.org/usecases/using-a-targets-pipeline-to-query-data-from-the-water-quality-portal/</link><pubDate>Mon, 03 Oct 2022 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/using-a-targets-pipeline-to-query-data-from-the-water-quality-portal/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/targets/"&gt;targets&lt;/a&gt;
&lt;a href="https://waterdata.usgs.gov/blog/dataretrieval/"&gt;dataRetrieval&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;We developed a reproducible pipeline to query data from the &lt;a href="https://www.waterqualitydata.us/"&gt;Water Quality Portal (WQP)&lt;/a&gt; based upon a user-specified area of interest. This template provides a framework for others to inventory, query, and then clean data from WQP.&lt;/p&gt;
&lt;p&gt;Querying and cleaning data from the WQP based on an area of interest is a common data access pattern across many projects from USGS, so we developed a template repository that other users could fork and integrate into their project-specific workflows. The blog post goes into further detail about the &amp;ldquo;ins and outs&amp;rdquo; of this access pattern - focusing on the first two phases of the pipeline (&lt;code&gt;01_inventory&lt;/code&gt; and &lt;code&gt;02_download&lt;/code&gt;) because these phases tend to be consistent across projects. In the GitHub repo we also include a few example cleaning functions that users can review and use to guide their own data cleaning methodologies.&lt;/p&gt;</description></item><item><title>rOpenSci News Digest, September 2022</title><link>https://ropensci.org/blog/2022/09/23/ropensci-news-digest-september-2022/</link><pubDate>Fri, 23 Sep 2022 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2022/09/23/ropensci-news-digest-september-2022/</guid><description>
&lt;!-- Before sending DELETE THE INDEX_CACHE and re-knit! --&gt;
&lt;p&gt;Dear rOpenSci friends, it&amp;rsquo;s time for our monthly news roundup!&lt;/p&gt;
&lt;!-- blabla --&gt;
&lt;p&gt;You can read this post &lt;a href="https://ropensci.org/blog/2022/09/23/ropensci-news-digest-september-2022"&gt;on our blog&lt;/a&gt;.
Now let&amp;rsquo;s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;h3&gt;
We are thrilled to launch our Champions program!
&lt;/h3&gt;&lt;p&gt;&lt;a href="https://ropensci.org/champions/"&gt;rOpenSci Champions Program&lt;/a&gt; is part of a series of activities and projects we are carrying out to ensure our research software serves everyone in our communities.
That is why this program focuses on &lt;strong&gt;people who belong to groups that are historically and systematically excluded&lt;/strong&gt; from the open software and research software communities and who are interested in contributing to rOpenSci and the broader open source and research software communities.&lt;/p&gt;</description></item><item><title>Announcing the rOpenSci Champions Program!</title><link>https://ropensci.org/blog/2022/09/22/launch-champions-program/</link><pubDate>Thu, 22 Sep 2022 00:00:01 -0700</pubDate><guid>https://ropensci.org/blog/2022/09/22/launch-champions-program/</guid><description><i><a href="https://ropensci.org/es/blog/2022/09/22/launch-champions-program-es/">Read it in: Español</a>.</i>
&lt;blockquote&gt;
&lt;p&gt;We are thrilled to launch our Champions Program pilot!&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2&gt;
Why a Champions Program?
&lt;/h2&gt;&lt;p&gt;Champion programs are designed to identify, recognize, and reward passionate community members.&lt;/p&gt;
&lt;p&gt;At rOpenSci, we recognize that there is a dismaying lack of diversity in the ecosystem of research software and open source communities. The R Community is no exception; its developers are overwhelmingly white, male, and from a handful of countries. This disappointing lack of diversity is potentially detrimental to the sustainability, utility and productivity of projects.&lt;/p&gt;</description></item><item><title>Using handlr to convert bibtex citation to cff</title><link>https://ropensci.org/usecases/using-handlr-to-convert-bibtex-citation-to-cff/</link><pubDate>Fri, 16 Sep 2022 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/using-handlr-to-convert-bibtex-citation-to-cff/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://github.com/ropensci/handlr"&gt;handlr&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;I was working on an R package with data to become publicly available. The data is already described and used in a scientific paper, and as such I had a bibtex citation I wanted to use as CITATION.cff on github. I was struggling to find a way to turn bibtex to cff, and &lt;a href="http://ropensci.discourse.group/t/generating-citation-cff-from-bibtex/3105"&gt;asked on the forum&lt;/a&gt; if there were any tools to help. The citation has quite a lot of co-authors, so I didnt want to start writing all that by hand.
I got an amazing reply and {handlr} seemed to be what I was looking for.&lt;/p&gt;</description></item><item><title>How to Participate with rOpenSci</title><link>https://ropensci.org/blog/2022/09/13/contributing-ropensci/</link><pubDate>Tue, 13 Sep 2022 00:00:01 -0700</pubDate><guid>https://ropensci.org/blog/2022/09/13/contributing-ropensci/</guid><description><i><a href="https://ropensci.org/es/blog/2022/09/13/contributing-ropensci-es/">Read it in: Español</a>.</i>
&lt;p&gt;This blog post is intended to help you get started in rOpenSci community by highlighting some key links and activities. If you have questions, please get in touch with our Community Manager, Yanina Bellini Saibene &lt;a href="mailto:yabellini@ropensci.org"&gt;by email&lt;/a&gt; or &lt;a href="https://calendly.com/yabellini-ropensci/"&gt;schedule a meeting&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;We are here for you as you begin your journey with our community. Welcome!&lt;/p&gt;
&lt;h2&gt;
Where do I get started?
&lt;/h2&gt;&lt;p&gt;Glad you asked! rOpenSci fosters a culture that values open and reproducible research using shared data and reusable software. We are dedicated to providing a welcoming and supportive environment for all people. By participating in this community, participants agree to &lt;a href="https://ropensci.org/code-of-conduct/"&gt;abide by our Code of Conduct&lt;/a&gt;. Whether you have a little or a lot of time, there are &lt;a href="https://contributing.ropensci.org/"&gt;many ways to contribute and engage with us&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Using taxize and highcharter in R to extract and visualize taxonomic data</title><link>https://ropensci.org/usecases/using-taxize-and-highcharter-in-r-to-extract-and-visualize-taxonomic-data/</link><pubDate>Tue, 13 Sep 2022 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/using-taxize-and-highcharter-in-r-to-extract-and-visualize-taxonomic-data/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/taxize"&gt;taxize&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;I used taxize to classify a list of endangered species and visualized the taxonomic hierarchical relationship via highcharter.&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://github.com/stepminer/TidyTuesday/blob/dc558ff4830c1798a100a5822e72fb6b9f138b0d/hti_endangered_sp.R"&gt;R Script&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
Image
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://github.com/stepminer/TidyTuesday/blob/dc558ff4830c1798a100a5822e72fb6b9f138b0d/endangered_species.png"&gt;Image&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
Sector
&lt;/h4&gt;&lt;p&gt;other&lt;/p&gt;
&lt;h4&gt;
Field(s) of application
&lt;/h4&gt;&lt;p&gt;ecology, taxonomy&lt;/p&gt;</description></item><item><title>Social Coworking and Office Hours - Teaching with R</title><link>https://ropensci.org/events/coworking-2022-09/</link><pubDate>Tue, 06 Sep 2022 18:00:00 +0000</pubDate><guid>https://ropensci.org/events/coworking-2022-09/</guid><description>
&lt;!--
```{r}
d &lt;- lubridate::ymd_hms("2022-09-06 09:00:00", tz = "America/Vancouver")
lubridate::with_tz(d, "UTC")
lubridate::with_tz(d, "America/Winnipeg")
```
--&gt;
&lt;p&gt;We&amp;rsquo;re back!&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Join us for 2 hours Tuesday, September 6th, 9 AM North American Pacific / 16:00 UTC for &lt;a href="https://ropensci.org/blog/2021/08/17/coworking-sessions/"&gt;Social Coworking + Office Hours&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This September we&amp;rsquo;re focusing on the theme &lt;strong&gt;Teaching with R&lt;/strong&gt; with our new community manager,
&lt;strong&gt;Yanina Bellini Saibene&lt;/strong&gt;, as co-host!&lt;/p&gt;
&lt;p&gt;Come for the full 2 hrs or only as long as you need!&lt;/p&gt;</description></item><item><title>rOpenSci News Digest, August 2022</title><link>https://ropensci.org/blog/2022/08/26/ropensci-news-digest-august-2022/</link><pubDate>Fri, 26 Aug 2022 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2022/08/26/ropensci-news-digest-august-2022/</guid><description>
&lt;!-- Before sending DELETE THE INDEX_CACHE and re-knit! --&gt;
&lt;p&gt;Dear rOpenSci friends, it&amp;rsquo;s time for our monthly news roundup!&lt;/p&gt;
&lt;!-- blabla --&gt;
&lt;p&gt;You can read this post &lt;a href="https://ropensci.org/blog/2022/08/26/ropensci-news-digest-august-2022"&gt;on our blog&lt;/a&gt;.
Now let&amp;rsquo;s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;h3&gt;
Coworking sessions resume!
&lt;/h3&gt;&lt;p&gt;Join us for social coworking &amp;amp; office hours monthly on first Tuesdays!
Hosted by Steffi LaZerte and various community hosts.
Everyone welcome.
No RSVP needed.
Consult our &lt;a href="https://ropensci.org/events"&gt;Events&lt;/a&gt; page to find your local time and how to join.&lt;/p&gt;</description></item><item><title>Working with Qualtrics Data - Part 2: Excluding Data</title><link>https://ropensci.org/blog/2022/08/09/working-with-qualtrics-data-excluding/</link><pubDate>Tue, 09 Aug 2022 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2022/08/09/working-with-qualtrics-data-excluding/</guid><description>
&lt;p&gt;In the &lt;a href="https://ropensci.org/blog/2022/08/02/working-with-qualtrics-data-importing/"&gt;last post&lt;/a&gt;, we used the &lt;a href="https://docs.ropensci.org/qualtRics/"&gt;qualtRics&lt;/a&gt;&lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt; package to import survey data directly from &lt;a href="https://www.qualtrics.com/"&gt;Qualtrics&lt;/a&gt; accounts.
I often use Qualtrics for survey data collected via &lt;a href="https://www.mturk.com/"&gt;Amazon’s Mechanical Turk&lt;/a&gt;, which is an automated system that connects online respondents to paid surveys.
However, sometimes those data are not super useful because the quality of the data is poor.
In the anonymous, large-scale market of online survey respondents, the financial incentives for completing surveys attract respondents who blast through the study just to collect the money or, worse, automated bots programmed to act like humans and reap the incentives. 🤖
As a scientist, I’m collecting survey data to understand human nature, so I’m looking for honest responses.
But low-quality data can be common in online surveys, and not just on Mechanical Turk&lt;sup id="fnref:2"&gt;&lt;a href="#fn:2" class="footnote-ref" role="doc-noteref"&gt;2&lt;/a&gt;&lt;/sup&gt;.&lt;/p&gt;</description></item><item><title>Working with Qualtrics Data - Part 1: Importing Data</title><link>https://ropensci.org/blog/2022/08/02/working-with-qualtrics-data-importing/</link><pubDate>Tue, 02 Aug 2022 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2022/08/02/working-with-qualtrics-data-importing/</guid><description>
&lt;p&gt;The online survey system &lt;a href="https://www.qualtrics.com/"&gt;Qualtrics&lt;/a&gt; can be a great way to collect data from research participants, customers, and stakeholders. I use it frequently to conduct research studies with participants or just to poll students and collaborators. However, while Qualtrics makes survey design straightforward, once the data are collected, there is a lot of work to do. Fortunately, two R packages (&lt;a href="https://docs.ropensci.org/qualtRics/"&gt;qualtRics&lt;/a&gt;&lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt; and &lt;a href="https://docs.ropensci.org/excluder/"&gt;excluder&lt;/a&gt;&lt;sup id="fnref:2"&gt;&lt;a href="#fn:2" class="footnote-ref" role="doc-noteref"&gt;2&lt;/a&gt;&lt;/sup&gt;) can make importing data and excluding low-quality data easier.&lt;/p&gt;</description></item><item><title>New Package yfR</title><link>https://ropensci.org/blog/2022/07/26/package-yfr/</link><pubDate>Tue, 26 Jul 2022 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2022/07/26/package-yfr/</guid><description>
&lt;p&gt;Package yfR recently passed &lt;a href="https://github.com/ropensci/software-review/issues/523"&gt;peer review at rOpenSci&lt;/a&gt; and is all about downloading stock price data from &lt;a href="https://finance.yahoo.com/"&gt;Yahoo Finance (YF)&lt;/a&gt;. I wrote this package to solve a particular problem I had as a teacher: I needed a large volume of clean stock price data to use in my classes, either for explaining how financial markets work or for class exercises. While there are several R packages to import raw data from YF, none solved my problem.&lt;/p&gt;</description></item><item><title>rOpenSci News Digest, July 2022</title><link>https://ropensci.org/blog/2022/07/22/ropensci-news-digest-july-2022/</link><pubDate>Fri, 22 Jul 2022 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2022/07/22/ropensci-news-digest-july-2022/</guid><description>
&lt;!-- Before sending DELETE THE INDEX_CACHE and re-knit! --&gt;
&lt;p&gt;Dear rOpenSci friends, it&amp;rsquo;s time for our monthly news roundup!&lt;/p&gt;
&lt;!-- blabla --&gt;
&lt;p&gt;You can read this post &lt;a href="https://ropensci.org/blog/2022/07/22/ropensci-news-digest-july-2022"&gt;on our blog&lt;/a&gt;.
Now let&amp;rsquo;s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;h3&gt;
rOpenSci Code of Conduct update
&lt;/h3&gt;&lt;p&gt;We are pleased to announce the release of a new version of our Code of Conduct.&lt;br&gt;
Based on the feedback of our community we added greater detail about acceptable and unacceptable behaviors in online settings and we have the first translation of the text to Spanish.&lt;/p&gt;</description></item><item><title>Upgrading rtweet</title><link>https://ropensci.org/blog/2022/07/21/rtweet-1-0-0/</link><pubDate>Thu, 21 Jul 2022 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2022/07/21/rtweet-1-0-0/</guid><description>
&lt;p&gt;In this post I will provide some examples of what has changed between rtweet 0.7.0 and rtweet 1.0.2.
I hope both the changes and this guide will help all users.
I highlight the most important and interesting changes in this blog post, and for a full list of changes you can consult it on the &lt;a href="https://docs.ropensci.org/rtweet/news/index.html"&gt;NEWS&lt;/a&gt;.&lt;/p&gt;
&lt;h2&gt;
&lt;strong&gt;Big breaking changes&lt;/strong&gt;
&lt;/h2&gt;&lt;h3&gt;
More consistent output
&lt;/h3&gt;&lt;p&gt;This is probably what will affect the most users.
All functions that return data about tweets&lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt; now return the same columns.&lt;/p&gt;</description></item><item><title>rOpenSci Code of Conduct Update</title><link>https://ropensci.org/blog/2022/07/12/coc-update/</link><pubDate>Tue, 12 Jul 2022 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2022/07/12/coc-update/</guid><description>
&lt;p&gt;We are pleased to announce the release of &lt;em&gt;Version 2.4&lt;/em&gt; of our Code of Conduct with changes based on the feedback of our community.&lt;/p&gt;
&lt;h3&gt;
What’s new?
&lt;/h3&gt;&lt;ul&gt;
&lt;li&gt;Greater detail about acceptable and unacceptable behaviors in online settings.&lt;/li&gt;
&lt;li&gt;First translation of the text to Spanish.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;You can access now the last version full-text in &lt;a href="https://ropensci.org/code-of-conduct/"&gt;English&lt;/a&gt; and &lt;a href="https://ropensci.org/codigo-de-conducta/"&gt;Spanish&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;We welcome your feedback by email to &lt;code&gt;conduct at ropensci.org&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;As always our Code of Conduct uses community sources to improve. For these changes, we have consulted and adapted the &lt;a href="https://user2021.r-project.org/participation/coc/"&gt;useR! 2021 Code of Conduct&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Evaluating GitHub Activity for Contributors</title><link>https://ropensci.org/blog/2022/07/01/evaluating-github-activity-for-contributors/</link><pubDate>Fri, 01 Jul 2022 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2022/07/01/evaluating-github-activity-for-contributors/</guid><description><i><a href="https://ropensci.org/es/blog/2022/07/01/evaluating-github-activity-for-contributors/">Read it in: Español</a>.</i>
&lt;p&gt;Say you have a bug report or feature request to make to a package.
How can you use information on GitHub to manage your expectations (will there be a quick fix) and actions (should you go ahead and fork the repository)?
In this post, we shall go over sources of information and explain how they can be used.
In the end, there is no magical recipe, except perhaps graciousness, as software is made by humans. &amp;#x1f609;&lt;/p&gt;</description></item><item><title>rOpenSci News Digest, June 2022</title><link>https://ropensci.org/blog/2022/06/24/ropensci-news-digest-june-2022/</link><pubDate>Fri, 24 Jun 2022 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2022/06/24/ropensci-news-digest-june-2022/</guid><description>
&lt;!-- Before sending DELETE THE INDEX_CACHE and re-knit! --&gt;
&lt;p&gt;Dear rOpenSci friends, it&amp;rsquo;s time for our monthly news roundup!&lt;/p&gt;
&lt;!-- blabla --&gt;
&lt;p&gt;You can read this post &lt;a href="https://ropensci.org/blog/2022/06/24/ropensci-news-digest-june-2022"&gt;on our blog&lt;/a&gt;.
Now let&amp;rsquo;s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;h3&gt;
Introducing rOpenSci new Community Manager, Yanina Bellini Saibene
&lt;/h3&gt;&lt;p&gt;We&amp;rsquo;re excited and extremely thrilled to announce &lt;a href="https://ropensci.org/author/yanina-bellini-saibene/"&gt;&lt;strong&gt;Yanina Bellini Saibene&lt;/strong&gt;&lt;/a&gt; is our new community manager!
Yanina is a computer and data scientist by training and an educator by choice.
She lives in Argentina, where she has been a researcher for the last 24 years.
She is also a professor at Universidad Nacional Guillermo Brown.
She is part of several communities as a member of The Carpentries Executive Council, R-Ladies Global and Leadership Team, R Forwards Core Team, R Consortium Infrastructure Steering Committee, useR! Working Group, Minorities in R (MiR), and Sociedad Argentina de Informática.&lt;/p&gt;</description></item><item><title>Introducing rOpenSci new Community Manager, Yanina Bellini Saibene</title><link>https://ropensci.org/blog/2022/06/21/introducing-yanina/</link><pubDate>Tue, 21 Jun 2022 00:00:01 -0700</pubDate><guid>https://ropensci.org/blog/2022/06/21/introducing-yanina/</guid><description><i><a href="https://ropensci.org/es/blog/2022/06/21/introducing-yanina-es/">Read it in: Español</a>.</i>
&lt;h2&gt;
Hello! I am Yanina Bellini Saibene, your new community manager.
&lt;/h2&gt;&lt;p&gt;I&amp;rsquo;m so excited to join rOpenSci in this role, and support such an important project in open science and in the R Community.&lt;/p&gt;
&lt;p&gt;When I saw the call for the position, I thought that my over 20 years of experience as a community builder, teacher, and researcher aligned perfectly with it.&lt;/p&gt;
&lt;p&gt;I believe in the power of open science at the service of people, that education is the best tool we have to improve lives, and that the most effective way to make changes is as part of a community. rOpenSci combines my passion for open software and open science with my favorite programming language and community. I am particularly excited by our &lt;a href="https://ropensci.org/blog/2021/12/20/inclusive-leadership-program/"&gt;new project to empower community leaders from historically excluded groups&lt;/a&gt; and looking forward to playing a role in its development. I have worked to improve diversity, equity, and inclusion throughout my career, both because I am a member of groups that are historically excluded from science and because it’s the right thing to do.&lt;/p&gt;</description></item><item><title>Why You Should (or Shouldn't) Build an API Client</title><link>https://ropensci.org/blog/2022/06/16/publicize-api-client-yes-no/</link><pubDate>Thu, 16 Jun 2022 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2022/06/16/publicize-api-client-yes-no/</guid><description>
&lt;p&gt;These days web Application Programming Interfaces (APIs) are everywhere (scientific data sources, your system for Customer relationship management, cat facts API&amp;hellip;). Do you need to write some R code wrapping a web resource such as an API? Packaging it up might be useful to you or your team for the same reason as any code. Now, whether you really want to publicize the package and to guarantee its maintenance might be slightly trickier than for other packages, as the usefulness and status of your package will depend on the web API being up and running according to expectations. This creates a surface for failures that might be more or less scary depending on your trust in the upstream maintainers.&lt;/p&gt;</description></item><item><title>Communication &amp; Collaboration with Contributors in an Open-Source Organization</title><link>https://ropensci.org/blog/2022/06/14/communication-with-contributors-in-an-open-source-organization/</link><pubDate>Tue, 14 Jun 2022 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2022/06/14/communication-with-contributors-in-an-open-source-organization/</guid><description>
&lt;p&gt;&lt;em&gt;Zhiam Kamvar is Lesson Infrastructure Technology Developer at &lt;a href="https://carpentries.org/"&gt;The Carpentries&lt;/a&gt; (Software Carpentry, Data Carpentry &amp;amp; Library Carpentry), an open global community teaching the skills &amp;amp; perspectives to turn data into knowledge.&lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt;&lt;/em&gt;
&lt;em&gt;Maëlle Salmon is a Research Software Engineer with rOpenSci.&lt;/em&gt;
&lt;em&gt;In this post they compare their experiences in the two distinct organizations The Carpentries and rOpenSci.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;At rOpenSci, many &lt;a href="https://ropensci.org/commcalls/2020-03-18/"&gt;packages are maintained&lt;/a&gt; by volunteer community members, and similarly at The Carpentries &lt;a href="https://carpentries.org/maintainers/"&gt;lessons are maintained&lt;/a&gt; by volunteer community members.
We&amp;rsquo;re very thankful for the effort our volunteers put into that role and our organisations could literally not run without their work.
However, sometimes infrastructure changes are decided centrally. For example, &lt;a href="https://ropensci.org/blog/2022/05/16/requiring-2fa-for-the-ropensci-github-organization/"&gt;requiring two-factor authentication for all GitHub organization members at rOpenSci&lt;/a&gt; or &lt;a href="https://carpentries.org/blog/2022/05/workbench-beta/"&gt;overhauling the foundation of the lesson infrastructure at The Carpentries&lt;/a&gt;.
In this post, we shall share some insights from our experiences regarding how we, as staff members, best support our volunteers through these transformations.&lt;/p&gt;</description></item><item><title>rOpenSci.Convertite en una campeona del desarrollo de paquetes de R</title><link>https://ropensci.org/events/renbaires-2022/</link><pubDate>Fri, 10 Jun 2022 21:00:00 +0000</pubDate><guid>https://ropensci.org/events/renbaires-2022/</guid><description/></item><item><title>Reunión Argentina de Agrometeorología (Argentine Meeting of Agrometeorology)</title><link>https://ropensci.org/events/rada-2022/</link><pubDate>Fri, 10 Jun 2022 13:00:00 +0000</pubDate><guid>https://ropensci.org/events/rada-2022/</guid><description/></item><item><title>WiDS La Plata</title><link>https://ropensci.org/events/wids-la-plata/</link><pubDate>Fri, 10 Jun 2022 13:00:00 +0000</pubDate><guid>https://ropensci.org/events/wids-la-plata/</guid><description>
&lt;p&gt;Canal de YouTube &lt;a href="https://www.youtube.com/c/VideosUNLP"&gt;https://www.youtube.com/c/VideosUNLP&lt;/a&gt;&lt;/p&gt;</description></item><item><title>rOpenSci Dev Guide 0.8.0: Updates</title><link>https://ropensci.org/blog/2022/06/09/devguide-0.8.0/</link><pubDate>Thu, 09 Jun 2022 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2022/06/09/devguide-0.8.0/</guid><description>
&lt;p&gt;rOpenSci Software Peer Review&amp;rsquo;s guidance is gathered in an &lt;a href="https://devguide.ropensci.org/"&gt;online book&lt;/a&gt; that keeps improving!
This blog post summarises what&amp;rsquo;s new in our Dev Guide 0.8.0, with all changes listed in the &lt;a href="https://devguide.ropensci.org/booknews.html"&gt;changelog&lt;/a&gt;.&lt;/p&gt;
&lt;h2&gt;
Farewell Stefanie Butland
&lt;/h2&gt;&lt;p&gt;After many years of fabulous contributions to the rOpenSci community, Stefanie Butland &lt;a href="https://ropensci.org/blog/2022/01/14/msg-from-stefanie/"&gt;left the role of community manager&lt;/a&gt; at the start of 2022. The Dev Guide included several references to Stefanie, particularly regarding preparing blog posts, as well as preparing Dev Guide releases. Her name has been removed and replaced with a generic &amp;ldquo;&lt;em&gt;Community Manager&lt;/em&gt;&amp;rdquo; title.&lt;/p&gt;</description></item><item><title>rOpenSci Software Peer Review, 🤗 Empathy, 📶 communication, 🗒️ documentation, and 🤖 automation</title><link>https://ropensci.org/events/2022-06-07-epiverse/</link><pubDate>Tue, 07 Jun 2022 03:00:00 +0000</pubDate><guid>https://ropensci.org/events/2022-06-07-epiverse/</guid><description/></item><item><title>Social Coworking and Office Hours - Tackle something you've always wanted to learn</title><link>https://ropensci.org/events/coworking-2022-06/</link><pubDate>Tue, 07 Jun 2022 03:00:00 +0000</pubDate><guid>https://ropensci.org/events/coworking-2022-06/</guid><description>
&lt;!--
```{r}
d &lt;- lubridate::ymd_hms("2022-06-07 09:00:00", tz = "Australia/Perth")
lubridate::with_tz(d, "UTC")
lubridate::with_tz(d, "America/Winnipeg")
lubridate::with_tz(d, "America/Vancouver")
```
--&gt;
&lt;p&gt;&lt;strong&gt;Join us for 2 hours Tuesday, June 7th, 9 AM Australian Western / 1:00 UTC for&lt;br&gt;&lt;a href="https://ropensci.org/blog/2021/08/17/coworking-sessions/"&gt;Social Coworking + Office Hours&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This June we&amp;rsquo;re focusing on the theme &lt;strong&gt;Tackle something you&amp;rsquo;ve always wanted to learn&lt;/strong&gt;
with community host &lt;strong&gt;Nick Tierney&lt;/strong&gt;, R enthusiast and author of several R packages.&lt;/p&gt;
&lt;p&gt;Come for the full 2 hrs or only as long as you need!&lt;/p&gt;</description></item><item><title>Map of linguae francae of Dagestan, Russia</title><link>https://ropensci.org/usecases/map-of-linguae-francae-of-dagestan-russia/</link><pubDate>Thu, 02 Jun 2022 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/map-of-linguae-francae-of-dagestan-russia/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used
&lt;/h4&gt;&lt;ul&gt;
&lt;li&gt;&lt;a href="https://ropensci.github.io/lingtypology/"&gt;&lt;code&gt;lingtypology&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h4&gt;
What did I do?
&lt;/h4&gt;&lt;p&gt;There is a long tradition in linguistics of drawing polygons to delimit the areas in which languages are spoken. However, in typological studies in linguistics, a lot of languages need to be represented on maps, so the “one dot per language” approach is used. In multilingual areas with high language density like Dagestan (see the &lt;a href="https://multidagestan.com/about"&gt;Multidagestan project&lt;/a&gt; (Dobrushina et al. 2017) that shows this), it is common for people to know more than one language, including linguae francae, i.e., languages used by speakers of different languages to communicate with one another. Nowadays, for all Post-Soviet states, the common lingua franca is Russian. However, historically, there were three linguae francae in Dagestan. Nina Dobrushina and I decided to create a map to show this old distribution of linguae francae. In order to do so, I used the &lt;a href="https://github.com/sverhees/master_villages"&gt;dataset of East Caucasian villages&lt;/a&gt; (Moroz, Verhees 2020), which contains information about modern settlements of Dagestan with language attribution. Afterwards, I used the &lt;code&gt;density.estimation&lt;/code&gt; argument from &lt;code&gt;lingtypology&lt;/code&gt;, hid dots used in the extrapolation and overlayed with another map based on the “one dot per language” approach.&lt;/p&gt;</description></item><item><title>Editorial Automation: Why &amp; How to Set Up Chat-Ops for your Own Review System on GitHub</title><link>https://ropensci.org/blog/2022/05/31/chatops-review-system-github/</link><pubDate>Tue, 31 May 2022 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2022/05/31/chatops-review-system-github/</guid><description>
&lt;p&gt;Anyone can contribute a software package to the rOpenSci suite as long as it fits our scope (&lt;a href="https://devguide.ropensci.org/policies.html#aims-and-scope"&gt;research lifecycle software&lt;/a&gt; and &lt;a href="https://stats-devguide.ropensci.org/pkgdev.html#scope"&gt;statistical software&lt;/a&gt;) for a transparent, constructive, nonadversarial and open review. In practice, the review steps are all recorded in &lt;strong&gt;GitHub issue threads&lt;/strong&gt; (&lt;a href="https://github.com/ropensci/software-review/issues/485"&gt;example&lt;/a&gt;).
Software peer-review involves coordinating and tracking many moving parts: software submissions (new issues), testing and diagnostics, assignment of editors and reviewers, and logging the progression of submissions through revisions and acceptance.&lt;/p&gt;</description></item><item><title>Extração de dados sobre heróis negros e negras da Marvel e DC</title><link>https://ropensci.org/usecases/extra-o-de-dados-sobre-her-is-negros-e-negras-da-marvel-e-dc/</link><pubDate>Mon, 30 May 2022 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/extra-o-de-dados-sobre-her-is-negros-e-negras-da-marvel-e-dc/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/tabulizer/"&gt;tabulizer&lt;/a&gt; [pt-br]&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;Uso do tabulizer para extrair dados sobre heróis negros e negras da DC e Marvel disponibilizados em uma tabela de uma dissertação disponibilizada em arquivo pdf.&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://github.com/fernandobarbalho/herois_negros_negras"&gt;https://github.com/fernandobarbalho/herois_negros_negras&lt;/a&gt;&lt;/p&gt;</description></item><item><title>rOpenSci News Digest, May 2022</title><link>https://ropensci.org/blog/2022/05/20/ropensci-news-digest-may-2022/</link><pubDate>Fri, 20 May 2022 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2022/05/20/ropensci-news-digest-may-2022/</guid><description>
&lt;!-- Before sending DELETE THE INDEX_CACHE and re-knit! --&gt;
&lt;p&gt;Dear rOpenSci friends, it&amp;rsquo;s time for our monthly news roundup! &lt;!-- blabla --&gt; You can read this post &lt;a href="https://ropensci.org/blog/2022/05/20/ropensci-news-digest-may-2022"&gt;on our blog&lt;/a&gt;. Now let&amp;rsquo;s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;h3&gt;
R-universe prominently displays more information on packages!
&lt;/h3&gt;&lt;p&gt;We have extended the &lt;a href="https://r-universe.dev"&gt;r-universe.dev&lt;/a&gt; platform to provide even more real-time information and metadata about R packages to help users quickly find and compare relevant software for a given topic, maintainer or organization.&lt;/p&gt;</description></item><item><title>Requiring 2FA for Our Main GitHub Organization</title><link>https://ropensci.org/blog/2022/05/16/requiring-2fa-for-the-ropensci-github-organization/</link><pubDate>Mon, 16 May 2022 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2022/05/16/requiring-2fa-for-the-ropensci-github-organization/</guid><description>
&lt;p&gt;Following our recent post on &lt;a href="https://ropensci.org/blog/2022/03/22/safeguards-and-backups-for-github-organizations/"&gt;&amp;ldquo;Safeguards and Backups for GitHub Organizations&amp;rdquo;&lt;/a&gt;, nearly one month ago we went one step further and made two-factor authentication (2FA) required for all members and outside collaborators of our main organization, &lt;a href="https://github.com/ropensci/"&gt;&lt;code&gt;ropensci&lt;/code&gt;&lt;/a&gt;.
It was a timely decision as GitHub since then announced it &lt;a href="https://github.blog/2022-05-04-software-security-starts-with-the-developer-securing-developer-accounts-with-2fa/"&gt;&lt;em&gt;will require all users who contribute code on GitHub.com to enable one or more forms of two-factor authentication (2FA) by the end of 2023&lt;/em&gt;&lt;/a&gt;.
Here is how (and why) we went about it.&lt;/p&gt;</description></item><item><title>Analyze your Twitter timeline with rtweet and lubridate</title><link>https://ropensci.org/usecases/analyze-your-twitter-timeline-with-rtweet-and-lubridate/</link><pubDate>Sat, 14 May 2022 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/analyze-your-twitter-timeline-with-rtweet-and-lubridate/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://github.com/ropensci/rtweet"&gt;rtweet&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;In this blog post I give a quick tour of the rtweet and lubridate package. These help you to analyse your Twitter timeline. And they helped me to visualize my follower count as I reached 1000 followers this week.&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case*
&lt;/h4&gt;&lt;p&gt;Find my blog post at &lt;a href="https://albert-rapp.de/post/2022-05-06-track-twitter-follower/"&gt;albert-rapp.de&lt;/a&gt;.&lt;/p&gt;
&lt;h4&gt;
Image
&lt;/h4&gt;&lt;p&gt;Here&amp;rsquo;s a visual I created using the data I extracted the data from Twitter over time. It was a celebratory dataviz as I reached 1000 followers.
&lt;img src="https://ropensci.org/usecases/analyze-your-twitter-timeline-with-rtweet-and-lubridate/analyze-your-twitter-timeline-with-rtweet-and-lubridate.png" alt="A visual that depicts the evolution of my follower count"&gt;&lt;/p&gt;</description></item><item><title>Social Coworking and Office Hours - Why be an R package reviewer?</title><link>https://ropensci.org/events/coworking-2022-05/</link><pubDate>Tue, 03 May 2022 18:00:00 +0000</pubDate><guid>https://ropensci.org/events/coworking-2022-05/</guid><description>
&lt;!--
```{r}
d &lt;- lubridate::ymd_hms("2022-05-03 09:00:00", tz = "America/Vancouver")
lubridate::with_tz(d, "UTC")
```
--&gt;
&lt;p&gt;&lt;strong&gt;Join us for 2 hours Tuesday, May 3rd, 9 AM North American Pacific / 16:00 UTC for&lt;br&gt;&lt;a href="https://ropensci.org/blog/2021/08/17/coworking-sessions/"&gt;Social Coworking + Office Hours&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This May we&amp;rsquo;re focusing on the theme &lt;strong&gt;Why be an R package reviewer?&lt;/strong&gt; with community host
&lt;strong&gt;François Michonneau&lt;/strong&gt;, reviewer for rOpenSci Software Peer Review, Senior Director of Technology at The Carpentries, as well as maintainer of rOpenSci package &lt;a href="https://docs.ropensci.org/rotl/"&gt;rotl&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Don't Lose your HEAD over Default Branches</title><link>https://ropensci.org/blog/2022/04/29/don-t-lose-your-head-over-default-branches/</link><pubDate>Fri, 29 Apr 2022 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2022/04/29/don-t-lose-your-head-over-default-branches/</guid><description>
&lt;p&gt;Did you know that GitHub lets you refer to the default branch of any repository by substituting the branch name with &lt;code&gt;HEAD&lt;/code&gt; in the url? This is a very useful trick to write robust code that works regardless of whether the default branch is called &lt;code&gt;main&lt;/code&gt; or &lt;code&gt;master&lt;/code&gt;, and will keep working when the default branch gets renamed at some point.&lt;/p&gt;
&lt;p&gt;While git has no &amp;ldquo;default&amp;rdquo; branch, online code platforms such as GitHub need to define a default for the branch that someone sees when they look at code online. While the community standard for the default branch is now becoming main instead of master&lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt;, and while the switch for any repo is rather &lt;a href="https://www.hanselman.com/blog/easily-rename-your-git-default-branch-from-master-to-main"&gt;easy&lt;/a&gt; and is &lt;a href="https://www.tidyverse.org/blog/2021/10/renaming-default-branch/"&gt;well supported by usethis&lt;/a&gt;, for a while (forever) there will still be repos with different default branches in the wild.&lt;sup id="fnref:2"&gt;&lt;a href="#fn:2" class="footnote-ref" role="doc-noteref"&gt;2&lt;/a&gt;&lt;/sup&gt; Especially as nothing prevents you from using any other name for the default branch (although this could trip up collaborators).&lt;sup id="fnref:3"&gt;&lt;a href="#fn:3" class="footnote-ref" role="doc-noteref"&gt;3&lt;/a&gt;&lt;/sup&gt;&lt;/p&gt;</description></item><item><title>rOpenSci News Digest, April 2022</title><link>https://ropensci.org/blog/2022/04/22/ropensci-news-digest-april-2022/</link><pubDate>Fri, 22 Apr 2022 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2022/04/22/ropensci-news-digest-april-2022/</guid><description>
&lt;!-- Before sending DELETE THE INDEX_CACHE and re-knit! --&gt;
&lt;p&gt;Dear rOpenSci friends, it&amp;rsquo;s time for our monthly news roundup!&lt;/p&gt;
&lt;!-- blabla --&gt;
&lt;p&gt;You can read this post &lt;a href="https://ropensci.org/blog/2022/04/22/ropensci-news-digest-april-2022"&gt;on our blog&lt;/a&gt;.
Now let&amp;rsquo;s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;h3&gt;
pkgcheck reports now include dependencies
&lt;/h3&gt;&lt;p&gt;Our &lt;a href="https://ropensci.org/commcalls/dec2021-automation/"&gt;automated checking system for packages&lt;/a&gt; submitted for peer review now has a new section, &amp;ldquo;&lt;em&gt;Package Dependencies&lt;/em&gt;&amp;rdquo;.
This is intended to help editors and reviewers understand how package dependencies (that is, packages listed in &lt;em&gt;Imports&lt;/em&gt;, &lt;em&gt;Depends&lt;/em&gt;, or &lt;em&gt;Suggests&lt;/em&gt; &lt;code&gt;DESCRIPTION&lt;/code&gt; fields) are actually used by a package.
The section summarises total numbers of function calls made to each package, followed by collapsible &amp;ldquo;details&amp;rdquo; sections containing numbers of calls made to the individual functions of each packages.
Dependencies include base R and all recommended packages, ensuring that this section provides a comprehensive overview of how each package submitted for peer review uses and depends upon the entire R ecosystem.&lt;/p&gt;</description></item><item><title>Estimating leaf temperatures worldwide</title><link>https://ropensci.org/usecases/estimating-leaf-temperatures-worldwide/</link><pubDate>Thu, 21 Apr 2022 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/estimating-leaf-temperatures-worldwide/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://ropensci.github.io/nasapower/articles/nasapower.html"&gt;nasapower&lt;/a&gt;.&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;As a plant pathologist, I am interested in improving the characterisation of environmental influences on pathogen infection. This piqued my interest if there are any R packages that estimate leaf temperatures and/or humidity from ambient weather variables. A cursory search led me to the &lt;a href="https://doi.org/10.1093/aobpla/plz054"&gt;tealeaves&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;However, the &lt;a href="https://doi.org/10.1093/aobpla/plz054"&gt;tealeaves&lt;/a&gt; package requires additional parameters which are not logged by common weather stations, such as &lt;em&gt;short wave solar radiation&lt;/em&gt; and &lt;em&gt;albedo&lt;/em&gt;. However, I was aware that &lt;a href="https://ropensci.github.io/nasapower/articles/nasapower.html"&gt;nasapower&lt;/a&gt; provides all the weather inputs required on a 0.5 degree grid from satellite remote sensing.&lt;/p&gt;</description></item><item><title>Editorial Challenges and Solutions in Software Peer Review</title><link>https://ropensci.org/blog/2022/04/19/software-review-editorial-challenges/</link><pubDate>Tue, 19 Apr 2022 00:00:02 -0700</pubDate><guid>https://ropensci.org/blog/2022/04/19/software-review-editorial-challenges/</guid><description><i><a href="https://ropensci.org/es/blog/2022/04/19/software-review-editorial-challenges-es/">Read it in: Español</a>.</i><i><a href="https://ropensci.org/pt/blog/2022/04/19/software-review-editorial-challenges/">Read it in: Português</a>.</i>
&lt;p&gt;rOpenSci &lt;a href="https://ropensci.org/software-review/"&gt;Software Peer Review&lt;/a&gt; and &lt;a href="https://ropensci.org/software-review/"&gt;Statistical Software Peer Review&lt;/a&gt; rely on the volunteer work of reviewers, and editors.
Editors manage the day-to-day flow of submissions, recruit reviewers and guide the peer-review process from start to finish. (Their role, like much of our process, is &lt;a href="https://devguide.ropensci.org/editorguide.html"&gt;codified in the rOpenSci Developer Guide&lt;/a&gt;). While many in our community have participated in the peer-review process, only a few have been involved as editors and guest editors. Here we thought we&amp;rsquo;d shed some light on some of challenges our editors face, and some of the solutions we have found over the years, to make this part our work more transparent.&lt;/p&gt;</description></item><item><title>Social Coworking and Office Hours - Making figures sparkle</title><link>https://ropensci.org/events/coworking-2022-04/</link><pubDate>Tue, 05 Apr 2022 03:00:00 +0000</pubDate><guid>https://ropensci.org/events/coworking-2022-04/</guid><description>
&lt;!--
```{r}
d &lt;- lubridate::ymd_hms("2022-04-05 09:00:00", tz = "Australia/Perth")
lubridate::with_tz(d, "UTC")
lubridate::with_tz(d, "America/Winnipeg")
lubridate::with_tz(d, "America/Vancouver")
```
--&gt;
&lt;p&gt;&lt;strong&gt;Join us for 2 hours Tuesday, April 5th, 9 AM Australian Western / 1:00 UTC for&lt;br&gt;&lt;a href="https://ropensci.org/blog/2021/08/17/coworking-sessions/"&gt;Social Coworking + Office Hours&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This April we&amp;rsquo;re focusing on the theme &lt;strong&gt;Making figures sparkle&lt;/strong&gt; with community host
&lt;strong&gt;Nick Tierney&lt;/strong&gt;, author of several data visualization packages using ggplot2, including &lt;a href="https://docs.ropensci.org/visdat/"&gt;visdat&lt;/a&gt; with rOpenSci, and &lt;a href="https://naniar.njtierney.com/"&gt;naniar&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Come for the full 2 hrs or only as long as you need!&lt;/p&gt;</description></item><item><title>rsnps 0.5.0: New ncbi_snp_query() Features</title><link>https://ropensci.org/blog/2022/03/29/rsnps-update/</link><pubDate>Tue, 29 Mar 2022 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2022/03/29/rsnps-update/</guid><description>
&lt;h2&gt;
TL;DR
&lt;/h2&gt;&lt;p&gt;&lt;code&gt;rsnps&lt;/code&gt; is a package that enables the retrieval of single nucleotide polymorphism (SNP) data from the &lt;a href="https://www.ncbi.nlm.nih.gov/"&gt;NCBI&amp;rsquo;s&lt;/a&gt; &lt;a href="https://www.ncbi.nlm.nih.gov/snp/"&gt;dbSNP&lt;/a&gt; database and &lt;a href="https://opensnp.org/"&gt;openSNP&lt;/a&gt; by providing wrappers for the APIs. Single nucleotide polymorphisms represent differences at one specific position in a detected biological sequence compared to the reference.&lt;/p&gt;
&lt;p&gt;&lt;code&gt;ncbi_snp_query()&lt;/code&gt; now returns all reported variant allele frequencies in dbSNP in column &lt;code&gt;maf_population&lt;/code&gt; in form of a &lt;code&gt;tibble&lt;/code&gt;. Previously (version &amp;lt;= 0.4.0), it reported only the allele frequency from &lt;a href="https://gnomad.broadinstitute.org/"&gt;gnomAD&lt;/a&gt; in column &lt;code&gt;maf&lt;/code&gt; as a &lt;code&gt;data.frame&lt;/code&gt;.&lt;/p&gt;</description></item><item><title>Using vcr for HTTP testing of a package for Kobotoolbox</title><link>https://ropensci.org/usecases/using-vcr-for-http-testing-of-a-package-for-kobotoolbox/</link><pubDate>Thu, 24 Mar 2022 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/using-vcr-for-http-testing-of-a-package-for-kobotoolbox/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;ul&gt;
&lt;li&gt;&lt;a href="https://docs.ropensci.org/vcr/"&gt;vcr&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;the excellent &lt;a href="https://books.ropensci.org/http-testing/index.html"&gt;http testing in r book&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;We - a couple of volunteers from data4good network &lt;a href="https://correlaid.org"&gt;CorrelAid&lt;/a&gt; developed a wrapper for the API of &lt;a href="https://kobotoolbox.org"&gt;Kobotoolbox&lt;/a&gt;, a data collection tool widely used in humanitarian aid. For testing the package functions, we used the &lt;code&gt;vcr&lt;/code&gt; package and the HTTP testing book.&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://github.com/correlaid/kbtbr"&gt;https://github.com/correlaid/kbtbr&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Disclaimer: while we were developing, another package for the exact same purpose was published which is maybe better than ours (e.g. it uses &lt;code&gt;labelled&lt;/code&gt; to store question labels as well): &lt;a href="https://gitlab.com/dickoa/robotoolbox"&gt;https://gitlab.com/dickoa/robotoolbox&lt;/a&gt; :)&lt;/p&gt;</description></item><item><title>Searching and browsing the R universe</title><link>https://ropensci.org/blog/2022/03/23/runiverse-search/</link><pubDate>Wed, 23 Mar 2022 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2022/03/23/runiverse-search/</guid><description>
&lt;h2&gt;
R-universe now has search!
&lt;/h2&gt;&lt;p&gt;We made a series of structural improvements in r-universe to make it easier to browse and discover interesting R packages and articles.&lt;/p&gt;
&lt;p&gt;Most notably, the &lt;a href="https://r-universe.dev"&gt;r-universe.dev&lt;/a&gt; landing page has been overhauled: you can now search directly for any name or keyword across the entire ecosystem:&lt;/p&gt;
&lt;p&gt;&lt;a href="https://r-universe.dev"&gt;&lt;img src="https://ropensci.org/blog/2022/03/23/runiverse-search/search.png" alt="screenshot of r-universe homepage with search bar"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;The homepage also lists the popular topics and organizations, and links to recently active packages, articles, and maintainers. &lt;a href="https://r-universe.dev"&gt;Give it a try&lt;/a&gt; and search for any topic, author, or organization!&lt;/p&gt;</description></item><item><title>Safeguards and Backups for GitHub Organizations</title><link>https://ropensci.org/blog/2022/03/22/safeguards-and-backups-for-github-organizations/</link><pubDate>Tue, 22 Mar 2022 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2022/03/22/safeguards-and-backups-for-github-organizations/</guid><description>
&lt;p&gt;At rOpenSci, much of our code, content and infrastructure is hosted on GitHub over several organizations &amp;ndash; described on our &lt;a href="https://ropensci.org/resources/"&gt;resources page&lt;/a&gt;.
This post summarizes some steps we&amp;rsquo;ve taken to safeguard our GitHub organizations.&lt;/p&gt;
&lt;h2&gt;
Paying attention to access rights &amp;amp; individual security setup
&lt;/h2&gt;&lt;p&gt;GitHub defines several possible &lt;a href="https://docs.github.com/en/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization"&gt;roles for organizations&lt;/a&gt;.
The principal ones are:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;em&gt;Organization owners&lt;/em&gt; who have all rights;&lt;/li&gt;
&lt;li&gt;&lt;em&gt;Organization members&lt;/em&gt; who only have basic rights and access to specific repositories (more on that later!);&lt;/li&gt;
&lt;li&gt;&lt;em&gt;Outside collaborators&lt;/em&gt; who only have access to specific repositories.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;To decide what role to give someone we use the &lt;a href="https://en.wikipedia.org/wiki/Principle_of_least_privilege"&gt;&lt;strong&gt;principle of least privilege&lt;/strong&gt;&lt;/a&gt; &amp;ndash; obviously balanced with trust&amp;hellip; and some consideration of the &lt;a href="https://en.wikipedia.org/wiki/Bus_factor"&gt;bus factor&lt;/a&gt;.
We want everyone to be able to do their job (for instance, accessing all repo settings), to have more than one person able to perform something (in case of vacation and other vacancy reasons), but we do not want to give people unnecessary access to sensitive settings and information.&lt;/p&gt;</description></item><item><title>rOpenSci News Digest, March 2022</title><link>https://ropensci.org/blog/2022/03/18/ropensci-news-digest-march-2022/</link><pubDate>Fri, 18 Mar 2022 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2022/03/18/ropensci-news-digest-march-2022/</guid><description>
&lt;!-- Before sending DELETE THE INDEX_CACHE and re-knit! --&gt;
&lt;p&gt;Dear rOpenSci friends, it&amp;rsquo;s time for our monthly news roundup!&lt;/p&gt;
&lt;!-- blabla --&gt;
&lt;p&gt;You can read this post &lt;a href="https://ropensci.org/blog/2022/03/18/ropensci-news-digest-march-2022"&gt;on our blog&lt;/a&gt;.
Now let&amp;rsquo;s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;h3&gt;
R-universe gets advanced search!
&lt;/h3&gt;&lt;p&gt;The landing page for rOpenSci&amp;rsquo;s &lt;a href="https://r-universe.dev"&gt;R-universe&lt;/a&gt; platform has gotten a makeover to facilitate easy searching through thousands of available R packages and articles. Discover new content by searching for keywords in package descriptions, authors, topics, vignettes, etc.&lt;/p&gt;</description></item><item><title>Social Coworking and Office Hours - Changing package maintainers</title><link>https://ropensci.org/events/coworking-2022-03/</link><pubDate>Tue, 01 Mar 2022 19:00:00 +0000</pubDate><guid>https://ropensci.org/events/coworking-2022-03/</guid><description>
&lt;!--
```{r}
d &lt;- lubridate::ymd_hms("2022-03-01 09:00:00", tz = "America/Vancouver")
lubridate::with_tz(d, "UTC")
```
--&gt;
&lt;p&gt;&lt;strong&gt;Join us for 2 hours Tuesday, March 1st, 9 AM North American Pacific / 17:00 UTC for&lt;br&gt;&lt;a href="https://ropensci.org/blog/2021/08/17/coworking-sessions/"&gt;Social Coworking + Office Hours&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;This March we&amp;rsquo;re focusing on the theme &lt;strong&gt;Changing package maintainers&lt;/strong&gt; with community host
&lt;strong&gt;Hannah Owens&lt;/strong&gt;, who recently took over maintenance of the &lt;a href="https://docs.ropensci.org/spocc/"&gt;rOpenSci spocc package&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Come for the full 2 hrs or only as long as you need!&lt;/p&gt;</description></item><item><title>Use rtweet to manage lists and who you follow</title><link>https://ropensci.org/usecases/use-rtweet-to-manage-lists-and-who-you-follow/</link><pubDate>Tue, 22 Feb 2022 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/use-rtweet-to-manage-lists-and-who-you-follow/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/rtweet/"&gt;rtweet&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;After capturing a list of the people you follow, this workflow enables you to:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;assign twitter accounts to different groups (e.g. via RegEx over the profile)&lt;/li&gt;
&lt;li&gt;use the group boolean columns as the basis to create and populate lists*&lt;/li&gt;
&lt;li&gt;mass un-follow people so that your core twitter feed is streamlined&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;* I noticed significant instability in the Twitter list APIs. A workaround (&lt;em&gt;that was still a bit flaky!&lt;/em&gt;) is to split the accounts into groups of 100 and use &lt;a href="https://tweetdeck.twitter.com"&gt;Tweetdeck&lt;/a&gt; to bulk add people to lists. The &lt;code&gt;spit()&lt;/code&gt; function in the gist is how I tackled this.&lt;/p&gt;</description></item><item><title>rOpenSci News Digest, February 2022</title><link>https://ropensci.org/blog/2022/02/18/ropensci-news-digest-february-2022/</link><pubDate>Fri, 18 Feb 2022 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2022/02/18/ropensci-news-digest-february-2022/</guid><description>
&lt;!-- Before sending DELETE THE INDEX_CACHE and re-knit! --&gt;
&lt;p&gt;Dear rOpenSci friends, it&amp;rsquo;s time for our monthly news roundup!&lt;/p&gt;
&lt;!-- blabla --&gt;
&lt;p&gt;You can read this post &lt;a href="https://ropensci.org/blog/2022/02/18/ropensci-news-digest-february-2022"&gt;on our blog&lt;/a&gt;.
Now let&amp;rsquo;s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;h3&gt;
rOpenSci is hiring its next Community Manager!
&lt;/h3&gt;&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Come be part of making our great community even better;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Help start a new program promoting diverse leadership in open source;&lt;/p&gt;</description></item><item><title>A Journey to gghdr</title><link>https://ropensci.org/blog/2022/02/15/gghdr/</link><pubDate>Tue, 15 Feb 2022 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2022/02/15/gghdr/</guid><description>
&lt;blockquote&gt;
&lt;p&gt;They may forget what you said, but they will never forget how you made them feel.&lt;/p&gt;
&lt;footer&gt;Carl W. Buehner&lt;/footer&gt;
&lt;/blockquote&gt;
&lt;p&gt;This was how being a newcomer to &lt;a href="https://ozunconf19.ropensci.org/"&gt;rOpenSci OzUnconf 2019&lt;/a&gt; felt. It was incredible to be a part of such a diverse, welcoming and inclusive environment. I thought it would be fun to blog about how it all began, and the twists and turns we experienced along the way as we developed the &lt;a href="https://sayani07.github.io/gghdr/"&gt;gghdr&lt;/a&gt; package. The package provides tools for plotting &lt;a href="https://www.jstor.org/stable/2684423?seq=1"&gt;highest density regions&lt;/a&gt; with ggplot2 and was inspired by the package &lt;a href="https://cran.r-project.org/web/packages/hdrcde/index.html"&gt;hdrcde&lt;/a&gt; developed by &lt;a href="https://robjhyndman.com/"&gt;Rob J Hyndman&lt;/a&gt;. The highest density region approach of summarizing a distribution is useful for analyzing multimodal distributions and can be composed of numerous disjoint subsets. For example, the histogram of the highway mileage (&lt;code&gt;hwy&lt;/code&gt;) data from the mpg dataset (a) shows that cars with 6 cylinders (&lt;code&gt;cyl&lt;/code&gt;) are bimodally distributed, which is reflected in the highest density region (HDR) boxplot (c) but not in the standard boxplot (b). Hence, we see that HDRs are useful in displaying multimodality in the distribution.&lt;/p&gt;</description></item><item><title>Calculating US Residential Segregation Indices in A Reproducible Pipeline</title><link>https://ropensci.org/usecases/calculating-us-residential-segregation-indices-in-a-reproducible-pipeline/</link><pubDate>Fri, 11 Feb 2022 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/calculating-us-residential-segregation-indices-in-a-reproducible-pipeline/</guid><description>
&lt;p&gt;We provide a simple and reproducible &lt;a href="https://www.r-project.org/"&gt;R&lt;/a&gt; pipeline to investigate residential segregation (RS) using US census data. The pipeline contains two components:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;pulling decennial US census data of Year 2000, 2010, 2020 via R package &lt;a href="https://walker-data.com/tidycensus/index.html"&gt;tidycensus&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;calculating three residential segregation indices, including dissimilarity, isolation and interaction indices, at the preferred geographical level, e.g. county or census tract level&lt;/li&gt;
&lt;/ol&gt;
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/targets/"&gt;targets&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;We pull decennial US census data with &lt;a href="https://walker-data.com/tidycensus/index.html"&gt;tidycensus&lt;/a&gt; and calculate three residential segregation indices.&lt;/p&gt;</description></item><item><title>Social Coworking and Office Hours</title><link>https://ropensci.org/events/coworking-2022-02/</link><pubDate>Tue, 01 Feb 2022 03:00:00 +0000</pubDate><guid>https://ropensci.org/events/coworking-2022-02/</guid><description>
&lt;p&gt;&lt;strong&gt;Join us for 2 hours Tuesday, February 1st, 9 AM Australian Western / 1:00 UTC for Social Coworking + Office Hours.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;We are hosting &lt;a href="https://ropensci.org/blog/2021/08/17/coworking-sessions/"&gt;Social Coworking + Office Hours&lt;/a&gt; on the first Tuesday of each month, alternating times to accommodate different parts of the world.&lt;/p&gt;
&lt;p&gt;Come for the full 2 hrs or only as long as you need!&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Meet other package developers and rOpenSci staff in Zoom&lt;/li&gt;
&lt;li&gt;Cowork independently on work related to R
&lt;ul&gt;
&lt;li&gt;Plan out that package you&amp;rsquo;ve always wanted to create&lt;/li&gt;
&lt;li&gt;Work on packages that tend to be neglected&lt;/li&gt;
&lt;li&gt;Make your packages more &lt;a href="https://ropensci.org/blog/2021/04/28/commcall-pkg-community/"&gt;contributor-friendly&lt;/a&gt; (create issues, write a road map, etc.)&lt;/li&gt;
&lt;li&gt;What ever you need to get done!&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Get answers to your questions
&lt;ul&gt;
&lt;li&gt;Ask rOpenSci staff&lt;/li&gt;
&lt;li&gt;Ask your fellow developers&lt;/li&gt;
&lt;li&gt;Discuss your work, best practices, or get advice and resources&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Answer other developers questions!&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>pkgcheck now available as a GitHub action!</title><link>https://ropensci.org/blog/2022/02/01/pkgcheck-action/</link><pubDate>Tue, 01 Feb 2022 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2022/02/01/pkgcheck-action/</guid><description><i><a href="https://ropensci.org/es/blog/2022/02/01/pkgcheck-action/">Read it in: Español</a>.</i><i><a href="https://ropensci.org/pt/blog/2022/02/01/pkgcheck-action/">Read it in: Português</a>.</i>
&lt;h2&gt;
What is pkgcheck?
&lt;/h2&gt;&lt;p&gt;The &lt;a href="https://github.com/ropensci-review-tools/pkgcheck"&gt;pkgcheck package&lt;/a&gt; has
been developed by rOpenSci to automate the process of checking all packages on
submission. The &lt;code&gt;ropensci-review-bot&lt;/code&gt; automatically runs pkgcheck on all submissions, and checks can also be called at any time by editors using the command:&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-r" data-lang="r"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="o"&gt;@&lt;/span&gt;&lt;span class="n"&gt;ropensci&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;review&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;bot&lt;/span&gt; &lt;span class="n"&gt;check&lt;/span&gt; &lt;span class="n"&gt;package&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;The bot will return a list of checks which should ideally look like this:&lt;/p&gt;
&lt;figure&gt;&lt;a href="https://github.com/ropensci/software-review/issues/463#issuecomment-921010197"&gt;&lt;img src="https://ropensci.org/blog/2022/02/01/pkgcheck-action/cffr-pkgcheck.png"
alt="pkgcheck results for recent submission"&gt;&lt;/a&gt;
&lt;/figure&gt;
&lt;p&gt;To be ready for peer review, pkgcheck should return a series of ✔, indicating successful checks, and there shouldn&amp;rsquo;t be any ✘ symbols, which indicate failed checks. Anybody preparing a package to submit is recommended to &lt;a href="https://devguide.ropensci.org/authors-guide.html"&gt;&amp;ldquo;use pkgcheck&amp;rdquo;&lt;/a&gt; to confirm that a package is indeed ready to submit. Until now, this has only been possible through locally &lt;a href="https://devguide.ropensci.org/authors-guide.html"&gt;installing the package and running the &lt;code&gt;pkgcheck()&lt;/code&gt; command&lt;/a&gt;. Local checks suffer two important disadvantages:&lt;/p&gt;</description></item><item><title>A Blend of Package Build Failures</title><link>https://ropensci.org/blog/2022/01/31/package-build-failures/</link><pubDate>Mon, 31 Jan 2022 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2022/01/31/package-build-failures/</guid><description>
&lt;p&gt;The &lt;a href="https://ropensci.r-universe.dev/"&gt;rOpenSci R-universe&lt;/a&gt; is a bit special as, compared to other R-universes, it &lt;a href="https://ropensci.org/blog/2021/09/03/runiverse-docs/"&gt;builds docs&lt;/a&gt; for all the packages in our &lt;a href="https://ropensci.org/packages"&gt;suite&lt;/a&gt;.
Looking at the dashboard helps us identify failures in building the packages as well as in building the pkgdown websites.
We then help authors fix these issues in order to comply with our &lt;a href="https://devguide.ropensci.org/curationpolicy.html"&gt;package curation policy&lt;/a&gt;.
As a package author you should also rely on &lt;a href="https://devdevguide.netlify.app/ci.html"&gt;continuous integration&lt;/a&gt; in your own repo for catching e.g. &lt;code&gt;R CMD check&lt;/code&gt; problems.
Following one of our latest rounds of monitoring, we summarize some common and less common mistakes.
Many of them are &lt;em&gt;not&lt;/em&gt; specific to our build system.&lt;/p&gt;</description></item><item><title>rOpenSci News Digest, January 2022</title><link>https://ropensci.org/blog/2022/01/21/ropensci-news-digest-january-2022/</link><pubDate>Fri, 21 Jan 2022 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2022/01/21/ropensci-news-digest-january-2022/</guid><description>
&lt;!-- Before sending DELETE THE INDEX_CACHE and re-knit! --&gt;
&lt;p&gt;Dear rOpenSci friends, it&amp;rsquo;s time for our monthly news roundup!&lt;/p&gt;
&lt;!-- blabla --&gt;
&lt;p&gt;You can read this post &lt;a href="https://ropensci.org/blog/2022/01/21/ropensci-news-digest-january-2022"&gt;on our blog&lt;/a&gt;.
Now let&amp;rsquo;s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;!-- to be curated manually --&gt;
&lt;h3&gt;
Co-working events
&lt;/h3&gt;&lt;!-- Can use same coworking text every month and ping Steffi to ask if there are any special guests to add --&gt;
&lt;p&gt;Join us for social coworking &amp;amp; office hours monthly on 1st Tuesdays! Hosted by Steffi LaZerte and Nick Tierney. Everyone welcome. No RSVP needed. Consult our &lt;a href="https://ropensci.org/events"&gt;Events&lt;/a&gt; page to find your local time and how to join.&lt;/p&gt;</description></item><item><title>Community Management Transition for rOpenSci. A Message from Stefanie Butland</title><link>https://ropensci.org/blog/2022/01/14/msg-from-stefanie/</link><pubDate>Fri, 14 Jan 2022 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2022/01/14/msg-from-stefanie/</guid><description>
&lt;p&gt;I’m writing to share news that I’m moving on from my position as rOpenSci’s Community Manager. Friday, January 14th is my last day.
Being rOpenSci’s first Community Manager has been my dream job. You have all given me such joy over the past 5.5 years.
I love collaborating to create new things, so it’s time for me to step away and take some time to explore what might come next.&lt;/p&gt;</description></item><item><title>rOpenSci 2021 Code of Conduct Transparency Report</title><link>https://ropensci.org/blog/2022/01/13/transparency2021/</link><pubDate>Thu, 13 Jan 2022 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2022/01/13/transparency2021/</guid><description>
&lt;p&gt;The rOpenSci community is supported by our &lt;a href="https://ropensci.org/code-of-conduct"&gt;Code of Conduct&lt;/a&gt; with a clear description of unacceptable behaviors, instructions on how to make a report, and information on how reports are handled. We, the Code of Conduct Committee, are responsible for receiving, investigating, deciding, enforcing and reporting on all reports of potential violations of our Code. We are committed to transparency with our community while upholding the privacy of people who experience or report incidents.&lt;/p&gt;</description></item><item><title>rOpenSci Code of Conduct Annual Review</title><link>https://ropensci.org/blog/2022/01/13/conduct2022/</link><pubDate>Thu, 13 Jan 2022 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2022/01/13/conduct2022/</guid><description>
&lt;p&gt;Our community is our best asset. It’s so important to us, it’s in our &lt;a href="https://ropensci.org/about/"&gt;mission statement&lt;/a&gt;. We recognize that communities are not inclusive by default; they require deliberate attention, including an enforceable &lt;a href="https://ropensci.org/code-of-conduct"&gt;Code of Conduct&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;rOpenSci is committed to providing a safe, inclusive, welcoming, and harassment-free experience for everyone. We welcome people of all backgrounds and identities, including but not limited to gender, gender identity and expression, age, sexual orientation, disability, physical appearance, body size, race, ethnicity, religion (or lack thereof), or technology choices. We are anti-racist. We welcome anyone, no matter their technical expertise, career stage, or work sector.&lt;/p&gt;</description></item><item><title>Gather on the rOpenSci Forum</title><link>https://ropensci.org/blog/2022/01/11/ropensci-forum/</link><pubDate>Tue, 11 Jan 2022 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2022/01/11/ropensci-forum/</guid><description>
&lt;p&gt;Do you have an account on the &lt;a href="https://discuss.ropensci.org"&gt;rOpenSci forum&lt;/a&gt;?
As underlined in our &lt;a href="https://contributing.ropensci.org/resources.html#channels"&gt;contributing guide&lt;/a&gt;, our forum is where we encourage &lt;strong&gt;Q&amp;amp;A and exploration of ideas on a various range of topics&lt;/strong&gt;.
Compared to our &lt;a href="https://contributing.ropensci.org/resources.html#channels"&gt;Slack&lt;/a&gt; semi-open workspace, the forum is &lt;strong&gt;entirely open and much easier to search&lt;/strong&gt;, so a great place to gather some collaborative knowledge!
We have recently &lt;strong&gt;streamlined categories&lt;/strong&gt; so that it might be easier for you to find where to post, and what to follow.
In this post we shall present current forum categories, and ways for you to keep up-to-date with the activity without getting overwhelmed.&lt;/p&gt;</description></item><item><title>How renv restores packages from r-universe for reproducibility or production</title><link>https://ropensci.org/blog/2022/01/06/runiverse-renv/</link><pubDate>Thu, 06 Jan 2022 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2022/01/06/runiverse-renv/</guid><description>
&lt;h2&gt;
What is renv
&lt;/h2&gt;&lt;p&gt;RStudio&amp;rsquo;s &lt;a href="https://rstudio.github.io/renv/"&gt;renv&lt;/a&gt; package is a powerful dependency management toolkit for R. It allows you to create a &lt;em&gt;lockfile&lt;/em&gt; that records the exact versions of R packages used in a given project, and provides tooling to install exactly those same versions on another machine, or at a later point in time. This is very useful to create an isolated project environment for reproducibility or production purposes.&lt;/p&gt;
&lt;p&gt;The &lt;a href="https://rstudio.github.io/renv/news/index.html#renv-0150"&gt;latest version of renv (0.15.0)&lt;/a&gt; now supports restoring packages that were installed from r-universe. In this post we explain how this works, and why it has to work this way.&lt;/p&gt;</description></item><item><title>Social Coworking and Office Hours</title><link>https://ropensci.org/events/coworking-2022-01/</link><pubDate>Tue, 04 Jan 2022 19:00:00 +0000</pubDate><guid>https://ropensci.org/events/coworking-2022-01/</guid><description>
&lt;p&gt;&lt;strong&gt;Join us for 2 hours Tuesday, January 4th, 9 AM North American Pacific / 17:00 UTC for Social Coworking + Office Hours.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;We are hosting &lt;a href="https://ropensci.org/blog/2021/08/17/coworking-sessions/"&gt;Social Coworking + Office Hours&lt;/a&gt; on the first Tuesday of each month, alternating times to accommodate different parts of the world.&lt;/p&gt;
&lt;p&gt;Come for the full 2 hrs or only as long as you need!&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Meet other package developers and rOpenSci staff in Zoom&lt;/li&gt;
&lt;li&gt;Cowork independently on work related to R
&lt;ul&gt;
&lt;li&gt;Plan out that package you&amp;rsquo;ve always wanted to create&lt;/li&gt;
&lt;li&gt;Work on packages that tend to be neglected&lt;/li&gt;
&lt;li&gt;Make your packages more &lt;a href="https://ropensci.org/blog/2021/04/28/commcall-pkg-community/"&gt;contributor-friendly&lt;/a&gt; (create issues, write a road map, etc.)&lt;/li&gt;
&lt;li&gt;What ever you need to get done!&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Get answers to your questions
&lt;ul&gt;
&lt;li&gt;Ask rOpenSci staff&lt;/li&gt;
&lt;li&gt;Ask your fellow developers&lt;/li&gt;
&lt;li&gt;Discuss your work, best practices, or get advice and resources&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Answer other developers questions!&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>rOpenSci Announces $400k Award from the Chan Zuckerberg Initiative to Empower Historically Excluded Groups as Community Leaders in Scientific Open Source Projects</title><link>https://ropensci.org/blog/2021/12/20/inclusive-leadership-program/</link><pubDate>Mon, 20 Dec 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2021/12/20/inclusive-leadership-program/</guid><description>
&lt;p&gt;We are thrilled to have been awarded new funding as part of the Chan Zuckerberg Initiative &lt;a href="https://czi.co/OpenScience"&gt;Open Science program&amp;rsquo;s&lt;/a&gt; education and capacity building strategy. This $400K grant will support a new project to enable more members of historically excluded groups to participate in, benefit from, and become leaders in the R, research software engineering, and open source and open science communities.&lt;/p&gt;
&lt;p&gt;Developers in the R and open source communities are overwhelmingly white, male, from a handful of countries, primarily English-speaking, and do not use assistive technologies to participate. Research software should serve everyone in our communities. It needs to be sustainable and open and &lt;strong&gt;built by and for all groups&lt;/strong&gt;.&lt;/p&gt;</description></item><item><title>Thank You to the rOpenSci Community, 2021</title><link>https://ropensci.org/blog/2021/12/17/thank-you-2021/</link><pubDate>Fri, 17 Dec 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2021/12/17/thank-you-2021/</guid><description>
&lt;p&gt;Can you think of an rOpenSci community member that you&amp;rsquo;d like to thank?&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;A reviewer who helped you improve your package?&lt;/li&gt;
&lt;li&gt;Someone who answered your question?&lt;/li&gt;
&lt;li&gt;A community call speaker from whom you gained insight?&lt;/li&gt;
&lt;li&gt;Someone who encouraged you behind the scenes?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Consider leaving them a note in the comments below expressing your gratitude.
We often &lt;em&gt;think&lt;/em&gt; our thank yous, but &lt;em&gt;expressing&lt;/em&gt; thank yous can be incredibly meaningful.
Try to be specific.
What did they do?
What impact did their actions have?&lt;/p&gt;</description></item><item><title>Enhancing Software Peer Review with GitHub Automation</title><link>https://ropensci.org/commcalls/dec2021-automation/</link><pubDate>Tue, 02 Nov 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/commcalls/dec2021-automation/</guid><description>
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;On this call we will discuss how rOpenSci has worked with The &lt;a href="https://joss.theoj.org/"&gt;Journal of Open Source Software&lt;/a&gt; to extend JOSS’s approach of &lt;a href="https://www.arfon.org/chatops-driven-publishing"&gt;chatops-driven publishing&lt;/a&gt; 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. Chat-ops automation has been critical to JOSS’s success, and shows huge promise for automating even more tedious tasks like frequent software checks and compliance with best practices.&lt;/p&gt;</description></item><item><title>Social Coworking and Office Hours</title><link>https://ropensci.org/events/coworking-2021-12/</link><pubDate>Tue, 07 Dec 2021 03:00:00 +0000</pubDate><guid>https://ropensci.org/events/coworking-2021-12/</guid><description>
&lt;p&gt;&lt;strong&gt;Join us for 2 hours Tuesday, December 7th, 9 AM Australian Western / 1:00 UTC for Social Coworking + Office Hours.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;We are hosting &lt;a href="https://ropensci.org/blog/2021/08/17/coworking-sessions/"&gt;Social Coworking + Office Hours&lt;/a&gt; on the first Tuesday of each month, alternating times to accommodate different parts of the world.&lt;/p&gt;
&lt;p&gt;Come for the full 2 hrs or only as long as you need!&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Meet other package developers and rOpenSci staff in Zoom&lt;/li&gt;
&lt;li&gt;Cowork independently on work related to R
&lt;ul&gt;
&lt;li&gt;Plan out that package you&amp;rsquo;ve always wanted to create&lt;/li&gt;
&lt;li&gt;Work on packages that tend to be neglected&lt;/li&gt;
&lt;li&gt;Make your packages more &lt;a href="https://ropensci.org/blog/2021/04/28/commcall-pkg-community/"&gt;contributor-friendly&lt;/a&gt; (create issues, write a road map, etc.)&lt;/li&gt;
&lt;li&gt;What ever you need to get done!&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Get answers to your questions
&lt;ul&gt;
&lt;li&gt;Ask rOpenSci staff&lt;/li&gt;
&lt;li&gt;Ask your fellow developers&lt;/li&gt;
&lt;li&gt;Discuss your work, best practices, or get advice and resources&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Answer other developers questions!&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>Evaluating semi-parametric nowcasts of COVID-19 hospital admissions in Germany</title><link>https://ropensci.org/usecases/evaluating-semi-parametric-nowcasts-of-covid-19-hospital-admissions-in-germany/</link><pubDate>Tue, 30 Nov 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/evaluating-semi-parametric-nowcasts-of-covid-19-hospital-admissions-in-germany/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/targets/"&gt;&lt;code&gt;targets&lt;/code&gt;&lt;/a&gt;, &lt;a href="https://docs.ropensci.org/piggyback/"&gt;&lt;code&gt;piggyback&lt;/code&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;COVID-19 hospitalisations in Germany are released by date of positive test rather than by date of admission. This has some advantages when they are used as a tool for surveillance as these data are closer to the date of infection and so easier to link to underlying transmission dynamics and public health interventions. Unfortunately, however, when released in this way the latest data are right-censored meaning that final hospitalisations for a given day are initially underreported. This issue is often found in data sets used for the surveillance of infectious diseases and can lead to delayed or biased decision making. Fortunately, when data from a series of days is available we can estimate the level of censoring and provide estimates for the truncated hospitalisations adjusted for truncation with appropriate uncertainty. This is usually known as a nowcast.&lt;/p&gt;</description></item><item><title>rOpenSci News Digest, November 2021</title><link>https://ropensci.org/blog/2021/11/30/ropensci-news-digest-november-2021/</link><pubDate>Tue, 30 Nov 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2021/11/30/ropensci-news-digest-november-2021/</guid><description>
&lt;!-- Before sending DELETE THE INDEX_CACHE and re-knit! --&gt;
&lt;p&gt;Dear rOpenSci friends, it&amp;rsquo;s time for our monthly news roundup!&lt;/p&gt;
&lt;!-- blabla --&gt;
&lt;p&gt;You can read this post &lt;a href="https://ropensci.org/blog/2021/11/30/ropensci-news-digest-november-2021"&gt;on our blog&lt;/a&gt;.
Now let&amp;rsquo;s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;h3&gt;
Community call: @ropensci-review-bot help!
&lt;/h3&gt;&lt;p&gt;Tuesday, 07 December 2021 17:00 UTC we&amp;rsquo;ll share how we are &lt;a href="https://ropensci.org/commcalls/dec2021-automation/"&gt;&lt;strong&gt;Enhancing Software Peer Review with GitHub Automation&lt;/strong&gt;&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Speakers &lt;a href="https://www.arfon.org/"&gt;Arfon Smith&lt;/a&gt;, &lt;a href="https://ropensci.org/author/karthik-ram"&gt;Karthik Ram&lt;/a&gt;, &lt;a href="https://ropensci.org/author/ma%C3%ABlle-salmon"&gt;Maëlle Salmon&lt;/a&gt; and &lt;a href="https://ropensci.org/author/noam-ross"&gt;Noam Ross&lt;/a&gt; will discuss how rOpenSci has worked with &lt;a href="https://joss.theoj.org/"&gt;The Journal of Open Source Software (JOSS)&lt;/a&gt; to extend their approach of &lt;a href="https://www.arfon.org/chatops-driven-publishing"&gt;chatops-driven publishing&lt;/a&gt; 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, all from the comfort of a GitHub issue comment. Chat-ops automation has been critical to JOSS’s success, and shows huge promise for automating even more tedious tasks like frequent software checks and compliance with best practices. We will show how our new review bot improves the author and editor experience, &lt;strong&gt;explain how other teams can use and customize the bot&lt;/strong&gt;, and discuss how this approach can be extended to tackle other automation, code review, and reproducibility challenges.&lt;/p&gt;</description></item><item><title>RSS feeds of package updates in r-universe</title><link>https://ropensci.org/blog/2021/11/24/runiverse-badges/</link><pubDate>Wed, 24 Nov 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2021/11/24/runiverse-badges/</guid><description>
&lt;h2&gt;
Continuous deployment in r-universe
&lt;/h2&gt;&lt;p&gt;A major difference between &lt;a href="https://r-universe.dev"&gt;r-universe&lt;/a&gt; and static repositories like CRAN and BioConductor is continuous deployment: packages in r-universe are continuously built in CI and immediately deployed to our &lt;a href="https://github.com/r-universe-org/cranlike-server/"&gt;package server&lt;/a&gt;. 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.&lt;/p&gt;
&lt;p&gt;The package server also makes it relatively easy to add new functionality to expose information about R packages from the database in some other way. For example, we recently added a &lt;a href="https://ropensci.org/blog/2021/10/14/runiverse-badges/"&gt;badges API&lt;/a&gt; to display package versions and totals in the form of a small badge image that can be embedded in webpages.&lt;/p&gt;</description></item><item><title>cffr: Create a CITATION.cff File for your R Package</title><link>https://ropensci.org/blog/2021/11/23/cffr/</link><pubDate>Tue, 23 Nov 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2021/11/23/cffr/</guid><description>
&lt;!--html_preserve--&gt;
&lt;figure class="pull-right"&gt;&lt;a href="https://docs.ropensci.org/cffr/"&gt;&lt;img src="https://ropensci.org/blog/2021/11/23/cffr/logo.png"
alt="Hex sticker for the cffr package. White background with a blue outline and blue text reading &amp;#39;cffr&amp;#39; above a blue network diagram in the shape of a brain" width="150"&gt;&lt;/a&gt;
&lt;/figure&gt;
&lt;!--/html_preserve--&gt;
&lt;p&gt;A new R package, &lt;a href="https://docs.ropensci.org/cffr/"&gt;cffr&lt;/a&gt;, has been
&lt;a href="https://github.com/ropensci/cffr"&gt;developed&lt;/a&gt;,
&lt;a href="https://github.com/ropensci/software-review/issues/463"&gt;peer-reviewed&lt;/a&gt; by
rOpenSci and accepted by &lt;a href="https://CRAN.R-project.org/package=cffr"&gt;CRAN&lt;/a&gt;. This
package has a single purpose: to create a valid CITATION.cff file using the
metadata of any R package.&lt;/p&gt;
&lt;h2&gt;
CITATION.cff files and why they matter
&lt;/h2&gt;&lt;p&gt;A &lt;a href="https://citation-file-format.github.io/"&gt;Citation File Format (CFF)&lt;/a&gt; is a
plain text file with human- and machine-readable citation information for
software (and datasets)&lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt;.&lt;/p&gt;</description></item><item><title>How I Test cffr on (about) 2,000 Packages using GitHub Actions and R-universe</title><link>https://ropensci.org/blog/2021/11/23/how-i-test-cffr/</link><pubDate>Tue, 23 Nov 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2021/11/23/how-i-test-cffr/</guid><description>
&lt;p&gt;When GitHub announced &lt;a href="https://twitter.com/natfriedman/status/1420122675813441540"&gt;support for CITATION.cff
files&lt;/a&gt; I though of
creating a package that would assist R developers in this matter. I was already
using &lt;a href="https://docs.ropensci.org/codemetar/"&gt;codemetar&lt;/a&gt; for most of my packages,
so I was familiar with the creation of these kind of metadata files.&lt;/p&gt;
&lt;p&gt;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). Finally, the first working version of
&lt;a href="https://docs.ropensci.org/cffr/"&gt;cffr&lt;/a&gt; was released on September 15, 2021.&lt;/p&gt;</description></item><item><title>rOpenSci Dev Guide 0.7.0: Updates</title><link>https://ropensci.org/blog/2021/11/18/devguide-0.7.0/</link><pubDate>Thu, 18 Nov 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2021/11/18/devguide-0.7.0/</guid><description>
&lt;p&gt;rOpenSci Software Peer Review&amp;rsquo;s guidance is gathered in &lt;a href="https://devguide.ropensci.org/"&gt;an online book&lt;/a&gt; and keeps improving!
To find out what&amp;rsquo;s new in our dev guide 0.7.0, you can &lt;a href="https://devguide.ropensci.org/booknews.html"&gt;read the changelog&lt;/a&gt;,
or this blog post for more digested information.&lt;/p&gt;
&lt;h2&gt;
@ropensci-review-bot help: less TODOs, more simple commands!
&lt;/h2&gt;&lt;p&gt;A big change brought in this release is the retirement of some of our multiple TODOs for editors in favor of simple bot commands such as &lt;code&gt;@ropensci-review-bot check package&lt;/code&gt;.
Our &lt;a href="https://devguide.ropensci.org/editorguide.html"&gt;editor guide&lt;/a&gt; is now simpler!&lt;/p&gt;</description></item><item><title>How to Cite R and R Packages</title><link>https://ropensci.org/blog/2021/11/16/how-to-cite-r-and-r-packages/</link><pubDate>Tue, 16 Nov 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2021/11/16/how-to-cite-r-and-r-packages/</guid><description>
&lt;p&gt;I teach R to a lot of scientists, those that are new to science (i.e. students)
as well as more established scientists, new to R.
I find that after all their struggles of dealing with dates,
or remembering where to put the comma, they&amp;rsquo;re so grateful to actual have an analysis,
that they often forget or aren&amp;rsquo;t aware of the next steps.&lt;/p&gt;
&lt;p&gt;Many scientists don&amp;rsquo;t know that they should be citing R packages let alone R,
and, if they do know, they often struggle with how.
So here&amp;rsquo;s a short primer on why and how to get started!&lt;/p&gt;</description></item><item><title>Jeroen Ooms on The r-universe at NHS-R Conference</title><link>https://ropensci.org/events/nhsr-jeroen/</link><pubDate>Tue, 09 Nov 2021 16:25:00 +0000</pubDate><guid>https://ropensci.org/events/nhsr-jeroen/</guid><description>
&lt;p&gt;Jeroen Ooms, rOpenSci Lead Infrastructure Engineer will give a talk on &lt;a href="https://ropensci.org/r-universe/"&gt;The r-universe project&lt;/a&gt; at the &lt;a href="https://nhsrcommunity.com/nhs-r-community-conference-2021/"&gt;NHS-R 2021 virtual conference&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;NHS is the UK National Health Service and the &lt;a href="https://nhsrcommunity.com/about/"&gt;NHS-R community&lt;/a&gt; &amp;ldquo;aims to support the learning, application and exploitation of R in the NHS through workshops, video tutorials and providing a platform for discussion and sharing of developing best practice solutions to NHS problems.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://nhsrcommunity.com/wp-content/uploads/2021/10/NHS-R-Conference-Programme-D3-20211014-1.pdf"&gt;Conference program&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Social Coworking and Office Hours</title><link>https://ropensci.org/events/coworking-2021-11/</link><pubDate>Tue, 02 Nov 2021 18:00:00 +0000</pubDate><guid>https://ropensci.org/events/coworking-2021-11/</guid><description>
&lt;p&gt;&lt;strong&gt;Join us for 2 hours Tuesday, November 2nd, 9 AM Pacific / 16:00 UTC for Social Coworking + Office Hours.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;We are hosting &lt;a href="https://ropensci.org/blog/2021/08/17/coworking-sessions/"&gt;Social Coworking + Office Hours&lt;/a&gt; on the first Tuesday of each month, alternating times to accommodate different parts of the world.&lt;/p&gt;
&lt;p&gt;Come for the full 2 hrs or only as long as you need!&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Meet other package developers and rOpenSci staff in Zoom&lt;/li&gt;
&lt;li&gt;Cowork independently on work related to R
&lt;ul&gt;
&lt;li&gt;Plan out that package you&amp;rsquo;ve always wanted to create&lt;/li&gt;
&lt;li&gt;Work on packages that tend to be neglected&lt;/li&gt;
&lt;li&gt;Make your packages more &lt;a href="https://ropensci.org/blog/2021/04/28/commcall-pkg-community/"&gt;contributor-friendly&lt;/a&gt; (create issues, write a road map, etc.)&lt;/li&gt;
&lt;li&gt;What ever you need to get done!&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Get answers to your questions
&lt;ul&gt;
&lt;li&gt;Ask rOpenSci staff&lt;/li&gt;
&lt;li&gt;Ask your fellow developers&lt;/li&gt;
&lt;li&gt;Discuss your work, best practices, or get advice and resources&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Answer other developers questions!&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>Expanding Software Peer Review: Statistical Package Standards at rOpenSci</title><link>https://ropensci.org/commcalls/oct2021-statsreview02/</link><pubDate>Mon, 18 Oct 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/commcalls/oct2021-statsreview02/</guid><description>
&lt;p&gt;&lt;em&gt;This is the second in a series of 1-hour Community Calls on our &lt;a href="https://ropensci.org/software-review/"&gt;statistical software review project&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;We at rOpenSci have expanded the scope of our software peer review system to encompass explicitly statistical software. The &lt;a href="https://ropensci.org/commcalls/feb2021-statsreview/"&gt;first Community Call in this series&lt;/a&gt; covered new tools to help people prepare their software for submission. This time, we will address the bigger picture of how our community-informed development of standards for statistical packages meets a critical need of stakeholders. Noam Ross (EcoHealth Alliance and rOpenSci Software Review Lead) will catch everyone up on the project. Rebecca Killick (Lancaster University and rOpenSci Statistical Software Peer Review advisory committee) will offer insights into standardisation and the potential role our program might play in the future of statistical software and open source software in general. Juliane Manitz (EMD Serono and R Validation Hub) will offer a perspective on the use of open source software in regulated environments. Christoph Sax (cynkra) will share his experience as the first person to submit a package, &lt;a href="https://github.com/ropensci/software-review/issues/464"&gt;tsbox&lt;/a&gt;, for review and aligning his software with our standards.&lt;/p&gt;</description></item><item><title>rOpenSci News Digest, October 2021</title><link>https://ropensci.org/blog/2021/10/22/ropensci-news-digest-october-2021/</link><pubDate>Fri, 22 Oct 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2021/10/22/ropensci-news-digest-october-2021/</guid><description>
&lt;!-- Before sending DELETE THE INDEX_CACHE and re-knit! --&gt;
&lt;p&gt;Dear rOpenSci friends, it&amp;rsquo;s time for our monthly news roundup!&lt;/p&gt;
&lt;!-- blabla --&gt;
&lt;p&gt;You can read this post &lt;a href="https://ropensci.org/blog/2021/10/22/ropensci-news-digest-october-2021"&gt;on our blog&lt;/a&gt;.
Now let&amp;rsquo;s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;h3&gt;
Community call about the statistical software review project
&lt;/h3&gt;&lt;p&gt;A fantastic community call is coming up on Tuesday, 26 October 2021 18:00 UTC: &lt;a href="https://ropensci.org/commcalls/oct2021-statsreview02/"&gt;&lt;strong&gt;Expanding Software Peer Review: Statistical Package Standards at rOpenSci&lt;/strong&gt;&lt;/a&gt;!&lt;/p&gt;</description></item><item><title>Generating and customizing badges in r-universe</title><link>https://ropensci.org/blog/2021/10/14/runiverse-badges/</link><pubDate>Thu, 14 Oct 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2021/10/14/runiverse-badges/</guid><description><i><a href="https://ropensci.org/es/blog/2021/10/14/runiverse-badges/">Read it in: Español</a>.</i><i><a href="https://ropensci.org/pt/blog/2021/10/14/runiverse-badges/">Read it in: Português</a>.</i>
&lt;h2&gt;
Badges in r-universe
&lt;/h2&gt;&lt;p&gt;After &lt;a href="https://ropensci.org/blog/2021/06/22/setup-runiverse/"&gt;creating your personal universe&lt;/a&gt;, the dashboard on &lt;code&gt;https://{yourname}.r-universe.dev&lt;/code&gt; shows the version and other details for each package in your repository. We have also added a new &lt;a href="https://ropensci.r-universe.dev/ui#badges"&gt;tab&lt;/a&gt; that lists the available badges for the repository.&lt;/p&gt;
&lt;figure&gt;&lt;a href="https://ropensci.r-universe.dev/ui#badges"&gt;&lt;img src="https://ropensci.org/blog/2021/10/14/runiverse-badges/screenshot.png"&gt;&lt;/a&gt;
&lt;/figure&gt;
&lt;p&gt;Badges provide a nice way to display the status of your repository or individual packages within external webpages, such as a README file, your homepage, or your &lt;a href="https://docs.github.com/en/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme"&gt;personal&lt;/a&gt; or &lt;a href="https://docs.github.com/en/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile"&gt;organization&lt;/a&gt; profile README on GitHub.&lt;/p&gt;</description></item><item><title>Predizendo volume de eucalipto com tidymodels, XGBoost e targets</title><link>https://ropensci.org/usecases/predizendo-volume-de-eucalipto-com-tidymodels-xgboost-e-targets/</link><pubDate>Wed, 13 Oct 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/predizendo-volume-de-eucalipto-com-tidymodels-xgboost-e-targets/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/targets/"&gt;targets&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;Neste tutorial, realizei o ajuste de diversos modelos de Machine Learning para a predição do volume de madeira de Eucalyptus.
De modo geral, foi realizado o ajuste de diversos modelos, então foi feito o ajuste final e a avaliação da qualidade preditiva do melhor modelo obtido. Em seguida, realizou-se o orquestramento de todo o trabalho, a partir do pacote targets, bem como a produção automática de um relatório final com o resultado da modelagem.&lt;/p&gt;</description></item><item><title>Announcing New Software Peer Review Editors: Emily Riederer, Adam Sparks, and Jeff Hollister</title><link>https://ropensci.org/blog/2021/10/12/editors2021/</link><pubDate>Tue, 12 Oct 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2021/10/12/editors2021/</guid><description>
&lt;p&gt;We are excited to welcome Emily Riederer, Adam Sparks, and Jeff Hollister to our team of &lt;a href="https://ropensci.org/software-review/#editors"&gt;Associate Editors&lt;/a&gt; for rOpenSci &lt;a href="https://ropensci.org/software-review/"&gt;Software Peer Review&lt;/a&gt;.
They join Laura DeCicco, Julia Gustavsen, Anna Krystalli, Mauro Lepore, Karthik Ram, Noam Ross, Maëlle Salmon, and Melina Vidoni.&lt;/p&gt;
&lt;p&gt;rOpenSci has been running a rigorous and collegial software peer review system since 2015.
Editors &lt;a href="https://devguide.ropensci.org/editorguide.html"&gt;manage the review process&lt;/a&gt;, performing initial package checks, identifying reviewers, and moderating the process until the package is accepted by reviewers and transferred to rOpenSci.
To address the scope and volume of packages submitted for review, it&amp;rsquo;s critical that we have a team of editors with complementary expertise.
Adam brings his broad experience with API packages and his experience from agricultural research in academia, an international non-government organisation and government.
Emily is known for openly sharing her processes-oriented approach to development based in her experience in industry.
Jeff works hard at expanding open source tooling and skills in environmental science, particularly in government.&lt;/p&gt;</description></item><item><title>Creating historical Congressional maps with USABoundaries</title><link>https://ropensci.org/usecases/creating-historical-congressional-maps-with-usaboundaries/</link><pubDate>Sun, 10 Oct 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/creating-historical-congressional-maps-with-usaboundaries/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/USAboundaries/"&gt;USAboundaries&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;While reading a book about a futile presidential candidacy in the 1800s by Mormon leader Joseph Smith, I noticed that he proposed radically reshaping congressional apportionment rules and only assigning one House Representative per 1 million residents per state. I wanted to see what that would have done to Congress in the 1840s, and I wanted to make a map showing how many representatives each state would get under the proposed rules.&lt;/p&gt;</description></item><item><title>Social Coworking and Office Hours</title><link>https://ropensci.org/events/coworking-2021-10/</link><pubDate>Tue, 05 Oct 2021 03:00:00 +0000</pubDate><guid>https://ropensci.org/events/coworking-2021-10/</guid><description>
&lt;p&gt;&lt;strong&gt;Join us for 2 hours Tuesday, October 5th, 9 AM Australian Western / 1:00 UTC for Social Coworking + Office Hours.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;We are hosting &lt;a href="https://ropensci.org/blog/2021/08/17/coworking-sessions/"&gt;Social Coworking + Office Hours&lt;/a&gt; on the first Tuesday of each month, alternating times to accommodate different parts of the world.&lt;/p&gt;
&lt;p&gt;Come for the full 2 hrs or only as long as you need!&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Meet other package developers and rOpenSci staff in Zoom&lt;/li&gt;
&lt;li&gt;Cowork independently on work related to R
&lt;ul&gt;
&lt;li&gt;Plan out that package you&amp;rsquo;ve always wanted to create&lt;/li&gt;
&lt;li&gt;Work on packages that tend to be neglected&lt;/li&gt;
&lt;li&gt;Make your packages more &lt;a href="https://ropensci.org/blog/2021/04/28/commcall-pkg-community/"&gt;contributor-friendly&lt;/a&gt; (create issues, write a road map, etc.)&lt;/li&gt;
&lt;li&gt;What ever you need to get done!&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Get answers to your questions
&lt;ul&gt;
&lt;li&gt;Ask rOpenSci staff&lt;/li&gt;
&lt;li&gt;Ask your fellow developers&lt;/li&gt;
&lt;li&gt;Discuss your work, best practices, or get advice and resources&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Answer other developers questions!&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>Using jsonvalidate to validate the packages.json file from your personal universe</title><link>https://ropensci.org/usecases/using-jsonvalidate-to-validate-the-packages-json-file-from-your-personal-universe/</link><pubDate>Tue, 05 Oct 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/using-jsonvalidate-to-validate-the-packages-json-file-from-your-personal-universe/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/jsonvalidate/index.html"&gt;jsonvalidate&lt;/a&gt;
(and &lt;a href="https://r-universe.dev"&gt;R-universe&lt;/a&gt;)&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;Use the jsonvalidate package to validate the contents of &lt;code&gt;packages.json&lt;/code&gt; against a schema in your personal R-universe.
This can be part of a GitHub Action set up to run on pull requests to ensure you only merge correctly formatted changes.&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case*
&lt;/h4&gt;&lt;p&gt;&lt;code&gt;schema.json&lt;/code&gt;:&lt;/p&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;{
&amp;#34;$schema&amp;#34;: &amp;#34;http://json-schema.org/draft-07/schema#&amp;#34;,
&amp;#34;title&amp;#34;: &amp;#34;r-universe packages.json&amp;#34;,
&amp;#34;description&amp;#34;: &amp;#34;A packages.json file controlling the contents of your r-universe&amp;#34;,
&amp;#34;type&amp;#34;: &amp;#34;array&amp;#34;,
&amp;#34;items&amp;#34;: {
&amp;#34;type&amp;#34;: &amp;#34;object&amp;#34;,
&amp;#34;properties&amp;#34;: {
&amp;#34;package&amp;#34;: {
&amp;#34;description&amp;#34;: &amp;#34;The name of the R package&amp;#34;,
&amp;#34;type&amp;#34;: &amp;#34;string&amp;#34;
},
&amp;#34;url&amp;#34;: {
&amp;#34;description&amp;#34;: &amp;#34;The URL to the git repository with the package source code&amp;#34;,
&amp;#34;type&amp;#34;: &amp;#34;string&amp;#34;,
&amp;#34;format&amp;#34;: &amp;#34;uri&amp;#34;
},
&amp;#34;subdir&amp;#34;: {
&amp;#34;description&amp;#34;: &amp;#34;A subfolder of the repository containing the R package&amp;#34;,
&amp;#34;type&amp;#34;: &amp;#34;string&amp;#34;
},
&amp;#34;branch&amp;#34;: {
&amp;#34;description&amp;#34;: &amp;#34;The branch from which the package should be built&amp;#34;,
&amp;#34;type&amp;#34;: &amp;#34;string&amp;#34;
}
},
&amp;#34;required&amp;#34;: [&amp;#34;package&amp;#34;, &amp;#34;url&amp;#34;]
}
}
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;&lt;code&gt;.github/workflows/validate-json.yaml&lt;/code&gt;:&lt;/p&gt;</description></item><item><title>rOpenSci News Digest, September 2021</title><link>https://ropensci.org/blog/2021/09/30/ropensci-news-digest-september-2021/</link><pubDate>Thu, 30 Sep 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2021/09/30/ropensci-news-digest-september-2021/</guid><description>
&lt;!-- Before sending DELETE THE INDEX_CACHE and re-knit! --&gt;
&lt;p&gt;Dear rOpenSci friends, it&amp;rsquo;s time for our monthly news roundup!&lt;/p&gt;
&lt;!-- blabla --&gt;
&lt;p&gt;You can read this post &lt;a href="https://ropensci.org/blog/2021/09/30/ropensci-news-digest-september-2021"&gt;on our blog&lt;/a&gt;.
Now let&amp;rsquo;s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;p&gt;A first package was submitted to &lt;a href="https://ropensci.org/software-review/"&gt;rOpenSci Statistical Software Peer Review&lt;/a&gt;, two months after its &lt;a href="https://ropensci.org/blog/2021/07/23/ropensci-news-digest-july-2021/"&gt;opening&lt;/a&gt;: the &lt;a href="https://github.com/ropensci/software-review/issues/464"&gt;tsbox package&lt;/a&gt; by &lt;a href="https://github.com/christophsax"&gt;Christoph Sax&lt;/a&gt;.
We are very excited, and thankful for the opportunity to hone our new software review tooling!&lt;/p&gt;</description></item><item><title>The Story Behind rspatialdata</title><link>https://ropensci.org/blog/2021/09/28/rspatialdata/</link><pubDate>Tue, 28 Sep 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2021/09/28/rspatialdata/</guid><description>
&lt;p&gt;As two postgrad students on summer vacation but with no travel plans (during this global pandemic of course), we took up an internship at King Abdullah University of Science and Technology (KAUST) last summer and ended up collaborating on a really cool project with &lt;a href="https://www.paulamoraga.com/"&gt;Paula Moraga&lt;/a&gt;! Did we mention that we worked in Saudi Arabia, while living in Australia? All is well when we have the internet.&lt;/p&gt;
&lt;p&gt;We also ended up &lt;a href="https://www.youtube.com/watch?v=nLikORFBKgk"&gt;presenting our project at useR! 2021&lt;/a&gt;, and winning an award for the most outstanding lightning talk! So, keep reading to see how we got there!&lt;/p&gt;</description></item><item><title>ASA-BIOP 2021 conference</title><link>https://ropensci.org/events/asa-biop-mark/</link><pubDate>Fri, 24 Sep 2021 16:00:00 +0000</pubDate><guid>https://ropensci.org/events/asa-biop-mark/</guid><description>
&lt;p&gt;Abstract: rOpenSci is currently expanding its system for peer-review of R packages to include packages implementing statistical algorithms. This talk will briefly present two new tools developed for our expansion of scope, in order to assess statistical packages. The first, the &amp;ldquo;autotest&amp;rdquo; package, automatically generates and executes tests on R packages by determining the types of each input parameter for each function, and then mutating both types and values. This can be used to document and confirm the robustness of software to unexpected inputs. The second tool, the &amp;ldquo;ssr&amp;rdquo; package, allows standards compliance to be integrated directly into R package code. Developers use a roxygen-like system to annotate code to record where and how specific standards standards are addressed, as well as providing context or explanation for non-compliance. The integration of standards within the code itself enables the automatic generation of detailed, explicit, and cross-linked reports on standards compliance.&lt;/p&gt;</description></item><item><title>Using stplanr to find shortest road network distance to a TB treatment clinic from a TB patients' household.</title><link>https://ropensci.org/usecases/using-stplanr-to-find-shortest-road-network-distance-to-a-tb-treatment-clinic-from-a-tb-patients-household/</link><pubDate>Mon, 20 Sep 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/using-stplanr-to-find-shortest-road-network-distance-to-a-tb-treatment-clinic-from-a-tb-patients-household/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/stplanr/"&gt;stplanr&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;We estimated the distance from study participants’ (TB patients) households to their TB treatment initiation clinic using two approaches. The first approach was to estimate the distance based on a ‘straight line’ distance &lt;a href="https://en.wikipedia.org/wiki/Euclidean_distance"&gt;Cartesian distance&lt;/a&gt;. In the second approach, we used Blantyre urban road network downloaded from OpenStreetMap (OpenStreetMap Foundation) to calculate the shortest road network distance using the &lt;a href="http://ropensci.discourse.group/t/use-stplanr-to-find-and-plot-major-streets-of-a-city/2264"&gt;stplanr R package&lt;/a&gt;&lt;/p&gt;</description></item><item><title>How to Use System Commands in your R Script or Package</title><link>https://ropensci.org/blog/2021/09/13/system-calls-r-package/</link><pubDate>Mon, 13 Sep 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2021/09/13/system-calls-r-package/</guid><description>
&lt;p&gt;Have you ever found a command-line tool that&amp;rsquo;s perfect for getting your job done, and wanted to use it from an R script or package?
E.g. some sort of scientific software providing a specific functionality made available though a command-line interface (CLI)?&lt;/p&gt;
&lt;p&gt;In this post, we have a look at a few options for writing such CLI wrappers in R.
In particular, we compare the base R functions &lt;code&gt;system()&lt;/code&gt; and &lt;code&gt;system2()&lt;/code&gt;, the &lt;a href="https://cran.r-project.org/web/packages/sys/"&gt;sys&lt;/a&gt; package and the &lt;a href="https://cran.r-project.org/web/packages/processx/"&gt;processx&lt;/a&gt; package.&lt;/p&gt;</description></item><item><title>Social Coworking and Office Hours</title><link>https://ropensci.org/events/coworking-2021-09/</link><pubDate>Tue, 07 Sep 2021 18:00:00 +0000</pubDate><guid>https://ropensci.org/events/coworking-2021-09/</guid><description>
&lt;p&gt;&lt;strong&gt;Join us for 2 hours Tuesday, September 7th, 9 AM Pacific / 16:00 UTC for our first official Social Coworking + Office Hours event.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;We are hosting &lt;a href="https://ropensci.org/blog/2021/08/17/coworking-sessions/"&gt;Social Coworking + Office Hours&lt;/a&gt; on the first Tuesday of each month, alternating times to accommodate different parts of the world.&lt;/p&gt;
&lt;p&gt;Come for the full 2 hrs or only as long as you need!&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Meet other package developers and rOpenSci staff in Zoom&lt;/li&gt;
&lt;li&gt;Cowork independently on work related to R
&lt;ul&gt;
&lt;li&gt;Plan out that package you&amp;rsquo;ve always wanted to create&lt;/li&gt;
&lt;li&gt;Work on packages that tend to be neglected&lt;/li&gt;
&lt;li&gt;Make your packages more &lt;a href="https://ropensci.org/blog/2021/04/28/commcall-pkg-community/"&gt;contributor-friendly&lt;/a&gt; (create issues, write a road map, etc.)&lt;/li&gt;
&lt;li&gt;What ever you need to get done!&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Get answers to your questions
&lt;ul&gt;
&lt;li&gt;Ask rOpenSci staff&lt;/li&gt;
&lt;li&gt;Ask your fellow developers&lt;/li&gt;
&lt;li&gt;Discuss your work, best practices, or get advice and resources&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Answer other developers questions!&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>Slicing an image with magick for artistic effect</title><link>https://ropensci.org/usecases/slicing-an-image-with-magick-for-artistic-effect/</link><pubDate>Tue, 07 Sep 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/slicing-an-image-with-magick-for-artistic-effect/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/magick"&gt;magick&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;I used magick to slice an image and combine the tiles created to recreate the effect seen in Mario Klingemann&amp;rsquo;s work &amp;ldquo;&lt;a href="https://twitter.com/quasimondo/status/1400345208634712072"&gt;Mitosis&lt;/a&gt;&amp;rdquo;&lt;/p&gt;
&lt;h4&gt;
Image
&lt;/h4&gt;&lt;p&gt;&lt;img src="https://ropensci.org/usecases/slicing-an-image-with-magick-for-artistic-effect/slicing-an-image-with-magick-for-artistic-effect.jpeg" alt="1630860508.82944_r100|690x459"&gt;&lt;/p&gt;
&lt;h4&gt;
Code and more images
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://github.com/gkaramanis/aRtist/tree/main/mitosis"&gt;https://github.com/gkaramanis/aRtist/tree/main/mitosis&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
Field(s) of application
&lt;/h4&gt;&lt;p&gt;Art&lt;/p&gt;</description></item><item><title>rOpenSci docs are now built on r-universe</title><link>https://ropensci.org/blog/2021/09/03/runiverse-docs/</link><pubDate>Fri, 03 Sep 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2021/09/03/runiverse-docs/</guid><description>
&lt;p&gt;&lt;strong&gt;TLDR:&lt;/strong&gt; As of today, the pkgdown sites for all rOpenSci packages on our &lt;a href="https://docs.ropensci.org/"&gt;docs server&lt;/a&gt; are built on &lt;a href="https://ropensci.r-universe.dev"&gt;r-universe&lt;/a&gt;. This is an internal change; no action is required for package maintainers.&lt;/p&gt;
&lt;h2&gt;
From Jenkins to r-universe
&lt;/h2&gt;&lt;p&gt;For the past 2 years we have been using a &lt;a href="https://ropensci.org/blog/2019/06/07/ropensci-docs/"&gt;Jenkins server&lt;/a&gt; to automatically build the pkgdown sites for all rOpenSci packages, which get published on &lt;a href="https://docs.ropensci.org"&gt;https://docs.ropensci.org&lt;/a&gt;. By centralizing this process, we ensure that up-to-date documentation for all rOpenSci packages is available from a consistent URL with our personal branding, and without maintenance work for our package maintainers.&lt;/p&gt;</description></item><item><title>Bayesian Regression Analysis with Rstanarm (with GSODR for supporting data)</title><link>https://ropensci.org/usecases/bayesian-regression-analysis-with-rstanarm-with-gsodr-for-supporting-data/</link><pubDate>Thu, 02 Sep 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/bayesian-regression-analysis-with-rstanarm-with-gsodr-for-supporting-data/</guid><description>
&lt;p&gt;Spotted in the wild. GSODR was used to provide the average daily temperature in degrees Celsius and the total daily precipitation in millimetres for this blog post.&lt;/p&gt;
&lt;h4&gt;
rOpenSci package or resource used
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/GSODR/"&gt;GSODR&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;I just read the blog post, but the author used GSODR to fetch weather data to demonstrate the use of Rstanarm for Bayesian regression analysis.&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://methodmatters.github.io/steps-bayesian-rstanarm/"&gt;https://methodmatters.github.io/steps-bayesian-rstanarm/&lt;/a&gt;&lt;/p&gt;</description></item><item><title>rOpenSci News Digest, August 2021</title><link>https://ropensci.org/blog/2021/08/31/ropensci-news-digest-august-2021/</link><pubDate>Tue, 31 Aug 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2021/08/31/ropensci-news-digest-august-2021/</guid><description>
&lt;!-- Before sending DELETE THE INDEX_CACHE and re-knit! --&gt;
&lt;p&gt;Dear rOpenSci friends, it&amp;rsquo;s time for our monthly news roundup!&lt;/p&gt;
&lt;!-- blabla --&gt;
&lt;p&gt;You can read this post &lt;a href="https://ropensci.org/blog/2021/08/31/ropensci-news-digest-august-2021"&gt;on our blog&lt;/a&gt;.
Now let&amp;rsquo;s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;h3&gt;
Recordings of useR! 2021
&lt;/h3&gt;&lt;p&gt;Recordings of useR! 2021 are now available on the &lt;a href="https://user2021.r-project.org/recordings/"&gt;conference website&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;You can watch contributions by rOpenSci staff:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Jeroen Ooms&amp;rsquo; keynote talk about the &lt;a href="https://www.youtube.com/watch?v=8cv2qsZ_xZw&amp;amp;list=PL4IzsxWztPdmHoJwIVa4um44w2GMjctmP&amp;amp;index=8"&gt;&lt;strong&gt;R-universe project&lt;/strong&gt;&lt;/a&gt; (&lt;a href="https://jeroen.github.io/user2021/#1"&gt;slidedeck&lt;/a&gt;);&lt;/p&gt;</description></item><item><title>rOpenSci Introduces Monthly Social Coworking and Office Hours</title><link>https://ropensci.org/blog/2021/08/17/coworking-sessions/</link><pubDate>Tue, 17 Aug 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2021/08/17/coworking-sessions/</guid><description>
&lt;p&gt;We&amp;rsquo;re excited to announce that we&amp;rsquo;ll be hosting monthly social coworking + office hours sessions via Zoom, starting September 7th!&lt;/p&gt;
&lt;p&gt;Coworking is a great way to be productive and reduce feelings of social isolation (especially important over the last year)!&lt;/p&gt;
&lt;p&gt;These sessions will give you the opportunity to&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Meet other package developers and rOpenSci staff&lt;/li&gt;
&lt;li&gt;Cowork independently on work related to R (and perhaps focus on work that often gets neglected)&lt;/li&gt;
&lt;li&gt;Get answers to your questions&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;We will host sessions on the first Tuesday of each month, alternating times to accommodate different parts of the world.
Come for the full 2 hrs or only as long as you need!&lt;/p&gt;</description></item><item><title>rOpenSci staff at joint AOS &amp; SCO-SOC meeting 2021</title><link>https://ropensci.org/events/aos-sco2021/</link><pubDate>Fri, 06 Aug 2021 15:30:00 +0000</pubDate><guid>https://ropensci.org/events/aos-sco2021/</guid><description>
&lt;p&gt;Steffi LaZerte, rOpenSci&amp;rsquo;s Community Assistant, organized a lightning symposium &amp;ldquo;&lt;a href="https://steffilazerte.ca/presentations.html#Great-R-packages-for-Ornithologists"&gt;Great R packages for ornithologists&lt;/a&gt;&amp;rdquo; for this years joint meeting of the American Ornithological Society and Society for Canadian Ornithologists. Steffi starts the symposium rolling with a 5-min presentation, &amp;ldquo;How can ornithologists find R packages?&amp;rdquo;&lt;/p&gt;
&lt;p&gt;Mark Padgham, rOpenSci Software Research Scientist, is also contributing to this lightning symposium with a 5-min presentation on an rOpenSci package, &amp;ldquo;osmdata: Roadless areas and avian diversity&amp;rdquo;.&lt;/p&gt;</description></item><item><title>rOpenSci at Ecological Society of America ESA 2021</title><link>https://ropensci.org/events/esa2021/</link><pubDate>Fri, 06 Aug 2021 04:00:00 +0000</pubDate><guid>https://ropensci.org/events/esa2021/</guid><description>
&lt;p&gt;Steffi LaZerte, rOpenSci&amp;rsquo;s Community Assistant, and Carl Boettiger, rOpenSci Advisor, are both talking at the Ecological Society of America&amp;rsquo;s annual meeting, August 2 - August 6, 2021.&lt;/p&gt;
&lt;p&gt;Presentations will be available online for registrants to view, see live discussions scheduled below.&lt;/p&gt;
&lt;h4&gt;
&lt;strong&gt;Steffi LaZerte&lt;/strong&gt;
&lt;/h4&gt;&lt;p&gt;Title: &amp;ldquo;&lt;strong&gt;Using rOpenSci packages to access open data for ecology&lt;/strong&gt;&amp;quot;&lt;/br&gt;
Inspire Session 6: &amp;ldquo;Open Data Resources During a Global Pandemic&amp;rdquo;&lt;/br&gt;
Live Discussion: Tuesday, August 3, 2021, 11:00 AM - 12:00 PM Pacific; 18:00 UTC; &lt;a href="https://www.timeanddate.com/worldclock/converter.html?iso=20210803T180000&amp;amp;p1=1440&amp;amp;p2=224"&gt;Find your local time&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Informal package review using rOpenSci review template</title><link>https://ropensci.org/usecases/informal-package-review-using-ropensci-review-template/</link><pubDate>Wed, 04 Aug 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/informal-package-review-using-ropensci-review-template/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://devguide.ropensci.org/reviewtemplate.html"&gt;Review template&lt;/a&gt; from the &lt;a href="https://devguide.ropensci.org/"&gt;package development guide&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Bonus: gert to automatically retrieve the hash of the commit of the reviewed version (&lt;code&gt;gert::git_commit_id()&lt;/code&gt;)&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;Informal package review for teammates before submission to a journal.&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://github.com/epiforecasts/scoringutils/issues/121"&gt;https://github.com/epiforecasts/scoringutils/issues/121&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
Sector
&lt;/h4&gt;&lt;p&gt;academic&lt;/p&gt;
&lt;h4&gt;
Field(s) of application
&lt;/h4&gt;&lt;p&gt;epidemiology&lt;/p&gt;</description></item><item><title>Answering 'what colour is London?' with magick and rtweet</title><link>https://ropensci.org/usecases/answering-what-colour-is-london-with-magick-and-rtweet/</link><pubDate>Tue, 27 Jul 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/answering-what-colour-is-london-with-magick-and-rtweet/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used
&lt;/h4&gt;&lt;ul&gt;
&lt;li&gt;&lt;a href="https://docs.ropensci.org/rtweet/"&gt;rtweet&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.ropensci.org/magick/"&gt;magick&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;I used &lt;a href="https://docs.ropensci.org/rtweet/"&gt;rtweet&lt;/a&gt; to extract the images and body text (containing coordinates) from tweets by &lt;a href="https://twitter.com/londonmapbot"&gt;@londonmapbot&lt;/a&gt;, a bot that tweets satellite images of random parts of London (disclaimer: &lt;a href="https://www.rostrum.blog/2020/09/21/londonmapbot/"&gt;I made the bot&lt;/a&gt;). Then I used &lt;a href="https://docs.ropensci.org/magick/"&gt;magick&lt;/a&gt; to simplify each image to a single colour and extract its hex value. I used this information to create some visualisations of &amp;rsquo;the colour of London'.&lt;/p&gt;</description></item><item><title>The Story Behind censo2017, the First rOpenSci Package to be Reviewed in Spanish</title><link>https://ropensci.org/blog/2021/07/27/censo2017/</link><pubDate>Tue, 27 Jul 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2021/07/27/censo2017/</guid><description><i><a href="https://ropensci.org/es/blog/2021/07/27/censo2017-es/">Read it in: Español</a>.</i>
&lt;h2&gt;
Summary
&lt;/h2&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/censo2017"&gt;censo2017&lt;/a&gt; is an R package designed to
organize the &lt;a href="https://www.cepal.org/es/temas/redatam"&gt;Redatam&lt;/a&gt;&lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt; files
provided by the Chilean National Bureau of Statistics (Instituto Nacional de
Estadísticas de Chile in spanish) in DVD format&lt;sup id="fnref:2"&gt;&lt;a href="#fn:2" class="footnote-ref" role="doc-noteref"&gt;2&lt;/a&gt;&lt;/sup&gt;. This package was inspired
by &lt;a href="https://github.com/ropensci/citedb"&gt;citesdb&lt;/a&gt;
(&lt;a href="https://ropensci.org/author/noam-ross/"&gt;Noam Ross&lt;/a&gt;, 2020) and &lt;a href="https://github.com/ropensci/taxadb"&gt;taxadb&lt;/a&gt;
(&lt;a href="https://ropensci.org/autor/carl-boettiger/"&gt;Carl Boettiger&lt;/a&gt; et al, 2021).
This post is about this
package, the problem it solves, how to use it, and the fact that the package and
its review process were &lt;a href="https://github.com/ropensci/software-review/issues/414"&gt;all in
Spanish&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Investigating the drought in the Canadian prairies</title><link>https://ropensci.org/usecases/investigating-the-drought-in-the-canadian-prairies/</link><pubDate>Mon, 26 Jul 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/investigating-the-drought-in-the-canadian-prairies/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/weathercan/"&gt;weathercan&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;Much of the Canadian prairies is experiencing drought conditions (&lt;a href="https://agriculture.canada.ca/en/agriculture-and-environment/drought-watch-and-agroclimate/canadian-drought-monitor"&gt;https://agriculture.canada.ca/en/agriculture-and-environment/drought-watch-and-agroclimate/canadian-drought-monitor&lt;/a&gt;) resulting in significant wildfires and impacting agricultural production. I wanted to provide historical context for the current weather conditions.&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://github.com/alex-koiter/curiosity"&gt;https://github.com/alex-koiter/curiosity&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
Image
&lt;/h4&gt;&lt;p&gt;&lt;img src="https://ropensci.org/usecases/investigating-the-drought-in-the-canadian-prairies/investigating-the-drought-in-the-canadian-prairies.png" alt="Brandon_figs|690x212"&gt;&lt;/p&gt;
&lt;h4&gt;
Sector
&lt;/h4&gt;&lt;p&gt;academic, agriculture&lt;/p&gt;
&lt;h4&gt;
Field(s) of application
&lt;/h4&gt;&lt;p&gt;Weather, climate, agriculture, disaster&lt;/p&gt;</description></item><item><title>targets pipeline with RMarkdown to download and visualize USGS data</title><link>https://ropensci.org/usecases/targets-pipeline-with-rmarkdown-to-download-and-visualize-usgs-data/</link><pubDate>Mon, 26 Jul 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/targets-pipeline-with-rmarkdown-to-download-and-visualize-usgs-data/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/targets"&gt;targets&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;I was looking for a simple way to share code for a unique figure of cartogram bar charts related to the frequency of &amp;ldquo;ice&amp;rdquo; flags in public U.S. Geological Survey (USGS) streamgage data.&lt;/p&gt;
&lt;p&gt;I could have written a regular script but I needed the code to download a lot of data for all 50 U.S. states. These downloads can sometimes timeout and trigger you to have to start again. Due to this concern, I decided to use &lt;code&gt;targets&lt;/code&gt; to build a pipeline that could handle skipping downloads that were already successful if I needed to start again.&lt;/p&gt;</description></item><item><title>rOpenSci News Digest, July 2021</title><link>https://ropensci.org/blog/2021/07/23/ropensci-news-digest-july-2021/</link><pubDate>Fri, 23 Jul 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2021/07/23/ropensci-news-digest-july-2021/</guid><description>
&lt;!-- Before sending DELETE THE INDEX_CACHE and re-knit! --&gt;
&lt;p&gt;Dear rOpenSci friends, it&amp;rsquo;s time for our monthly news roundup!&lt;/p&gt;
&lt;!-- blabla --&gt;
&lt;p&gt;You can read this post &lt;a href="https://ropensci.org/blog/2021/07/23/ropensci-news-digest-july-2021"&gt;on our blog&lt;/a&gt;.
Now let&amp;rsquo;s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;!-- to be curated manually --&gt;
&lt;p&gt;Great news for fans of statistics and software!
rOpenSci&amp;rsquo;s peer-review system has now &lt;a href="https://ropensci.org/blog/2019/07/15/expanding-software-review/"&gt;expanded&lt;/a&gt; to include review of packages implementing statistical routines and algorithms.
We are thrilled to start this new chapter, for which we&amp;rsquo;ve developed a series of new standards and tools, and recruited a new &lt;a href="https://ropensci.org/software-review/"&gt;board of experts&lt;/a&gt; to oversee.
Authors of statistical software should begin by reading the &lt;a href="https://stats-devguide.ropensci.org"&gt;&lt;em&gt;Stats Software Dev Guide&lt;/em&gt;&lt;/a&gt;, which describes the categories of statistical software we now accept (Regression, Machine Learning, Exploratory Data Analysis, and more!), along with the procedures for preparing statistical software for peer review.
It also introduces our automation tools, such as &lt;a href="https://docs.ropensci.org/pkgcheck/"&gt;the &lt;code&gt;pkgcheck&lt;/code&gt; package&lt;/a&gt;, which confirms that statistical software is ready to be submitted for review.
Authors submitting statistical software to review should start by opening a &lt;em&gt;pre-submission inquiry&lt;/em&gt; on our main &lt;a href="https://github.com/ropensci/software-review"&gt;software review repository&lt;/a&gt;.
Inquiries are welcome well before packages are ready for submittal.
We hope authors make use of our standards and tools throughout the development process so as to make review straightforward.
To volunteer as a &lt;em&gt;reviewer&lt;/em&gt;, fill our &lt;a href="https://ropensci.org/software-reviewer"&gt;short form&lt;/a&gt;.
For any question, you can post on the &lt;a href="https://discuss.ropensci.org/c/statistical-software-peer-review/28"&gt;rOpenSci forum&lt;/a&gt; or contact the statistical software team (Mark Padgham, mark&amp;lt;at&amp;gt;ropensci.org, and Noam Ross, ross&amp;lt;at&amp;gt;ecohealthalliance.org).&lt;/p&gt;</description></item><item><title>pdftools + map to download &amp; read multiple pdfs</title><link>https://ropensci.org/usecases/pdftools-map-to-download-read-multiple-pdfs/</link><pubDate>Thu, 15 Jul 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/pdftools-map-to-download-read-multiple-pdfs/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/pdftools/"&gt;pdftools&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;other important packages: purrr and glue&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;I wrote code snippet that shows how to&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;create a list of URLs with glue::glue&lt;/li&gt;
&lt;li&gt;download multiple pdfs using purrr::walk2&lt;/li&gt;
&lt;li&gt;read them all with purrr::map &amp;amp; pdftools::pdf_text&lt;/li&gt;
&lt;/ul&gt;
&lt;h4&gt;
URL or code snippet for your use case
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://github.com/ColmexBDCV/tricks_for_librarians/blob/30e2cbb8d12d18e70906b57b1d44f0bdcf55f2a8/RCode/pdftools-y-tesseract/purrr-y-pdftools_demo.R"&gt;Github code&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
Sector
&lt;/h4&gt;&lt;p&gt;academic / non-profit&lt;/p&gt;
&lt;h4&gt;
Field(s) of application
&lt;/h4&gt;&lt;p&gt;humanities and any other field interested in downloading&lt;/p&gt;</description></item><item><title>pdftools + tesseract para extraer texto en español</title><link>https://ropensci.org/usecases/pdftools-tesseract-para-extraer-texto-en-espa-ol/</link><pubDate>Thu, 15 Jul 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/pdftools-tesseract-para-extraer-texto-en-espa-ol/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/pdftools/"&gt;pdftools&lt;/a&gt;, &lt;a href="https://docs.ropensci.org/tesseract/"&gt;tesseract&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;Convertí un texto-imagen en pdf a un texto legible para computadoras usando el OCR de Tesseract y la función de pdf_ocr_text()&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://github.com/ColmexBDCV/tricks_for_librarians/blob/e1e5a57a198e0de5e0c85215adaacfc42184b13f/RCode/pdftools-y-tesseract/pdftools-y-tesseract_demo.R#L32-L37"&gt;Código en Github&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
Sector
&lt;/h4&gt;&lt;p&gt;academic / non-profit&lt;/p&gt;
&lt;h4&gt;
Field(s) of application
&lt;/h4&gt;&lt;p&gt;humanidades ¡y cualquier otra disciplina que use pdfs!&lt;/p&gt;</description></item><item><title>New package katex: rendering math to HTML and MathML in R</title><link>https://ropensci.org/blog/2021/07/13/katex-release/</link><pubDate>Tue, 13 Jul 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2021/07/13/katex-release/</guid><description>
&lt;p&gt;A new rOpenSci package &lt;a href="https://cran.r-project.org/package=katex"&gt;katex&lt;/a&gt; is now on CRAN.
This package allows for converting latex math expressions to HTML and MathML for use in markdown documents or package documentation.&lt;/p&gt;
&lt;p&gt;The R package uses the &lt;a href="https://katex.org/docs/api.html"&gt;katex javascript library&lt;/a&gt;, but the rendering is done directly in R using the V8 engine (i.e. server-side), which eliminates the need for embedding the MathJax library into html pages.&lt;/p&gt;
&lt;h2&gt;
What it means to render server-side
&lt;/h2&gt;&lt;p&gt;To display a tex math in html we need a math typesetting library. The standard solution is to include &lt;a href="https://www.mathjax.org/"&gt;MathJax&lt;/a&gt; with the html page, which attempts to convert math to html in the browser, upon loading of the webpage.
However MathJax is quite heavy, which slows down the page, and it may not work in browsers where use of JavaScript or external libraries is restricted.&lt;/p&gt;</description></item><item><title>rOpenSci keynote, tutorial, talks, at useR!2021</title><link>https://ropensci.org/events/2021-07-05-user2021/</link><pubDate>Fri, 09 Jul 2021 20:00:00 +0000</pubDate><guid>https://ropensci.org/events/2021-07-05-user2021/</guid><description>
&lt;p&gt;&lt;strong&gt;Jeroen Ooms&lt;/strong&gt;, rOpenSci Lead Infrastructure Engineer, will give a &lt;a href="https://user2021.r-project.org/program/keynotes/"&gt;keynote talk&lt;/a&gt; about building a modern and scalable package build infrastructure, such as &lt;a href="https://ropensci.org/r-universe/"&gt;R-universe&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Maëlle Salmon&lt;/strong&gt;, Research Software Engineer with rOpenSci, will give a &lt;a href="https://user2021.r-project.org/program/tutorials/"&gt;tutorial&lt;/a&gt;, &lt;em&gt;GET better at testing your R package!&lt;/em&gt; on Wednesday, July the 7th at 9-12AM GMT+2. This tutorial is about advanced testing of R packages, with HTTP testing as a case study.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Stefanie Butland&lt;/strong&gt;, rOpenSci Community Manager, will present on rOpenSci’s Model for Managing a Federated Open Source Software Community.&lt;/p&gt;</description></item><item><title>Historical dataviz recreations with a sprinkle of magick</title><link>https://ropensci.org/usecases/historical-dataviz-recreations-with-a-sprinkle-of-magick/</link><pubDate>Sun, 04 Jul 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/historical-dataviz-recreations-with-a-sprinkle-of-magick/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/magick"&gt;magick&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;As part of &lt;a href="https://rss.org.uk/news-publication/news-publications/2021/section-group-reports/mary-eleanor-spear-dataviz-competition-for-childre/"&gt;the #CottonViz challenge from the Royal Statistical Society&lt;/a&gt;, I used {magick} to:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;create a gif that shows incrementally the steps I used to recreate &lt;a href="https://en.wikipedia.org/wiki/Mary_Eleanor_Spear"&gt;Mary Eleanor Spear&lt;/a&gt;&amp;rsquo;s original data visualisation of US cotton supplies in the 1940s, made with manual methods&lt;/li&gt;
&lt;li&gt;mimic another of Spear&amp;rsquo;s visualisations that uses &amp;lsquo;colour on the negative&amp;rsquo;, which she produced manually by &amp;lsquo;coloring negative photostat copies of charts or maps&amp;rsquo;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Functions used: &lt;code&gt;image_read()&lt;/code&gt;, &lt;code&gt;image_scale()&lt;/code&gt;, &lt;code&gt;image_animate()&lt;/code&gt;, &lt;code&gt;image_negate()&lt;/code&gt;, &lt;code&gt;image_transparent()&lt;/code&gt;, &lt;code&gt;image_background()&lt;/code&gt; and &lt;code&gt;image_write()&lt;/code&gt;.&lt;/p&gt;</description></item><item><title>Environment Canada air temperature using weathercan</title><link>https://ropensci.org/usecases/environment-canada-air-temperature-using-weathercan/</link><pubDate>Fri, 02 Jul 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/environment-canada-air-temperature-using-weathercan/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/weathercan"&gt;weathercan&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Given the recent heatwave, I was curious about plotting up a timeseries of the local Environment Canada weather stations. For this, I used the &lt;code&gt;weathercan&lt;/code&gt; package (&lt;a href="https://github.com/ropensci/weathercan"&gt;https://github.com/ropensci/weathercan&lt;/a&gt;)&lt;/p&gt;
&lt;p&gt;I&amp;rsquo;ll walk through the few lines of code that it takes to search, download, and plot the data:&lt;/p&gt;
&lt;p&gt;First, load a couple libraries:&lt;/p&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;library(dplyr)
library(ggplot2)
library(weathercan)
library(ggrepel)
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;Then, search the station IDs that have data for this calendar year and match my city name.&lt;/p&gt;</description></item><item><title>rOpenSci at useR!2021 - Presentations from Staff and Community</title><link>https://ropensci.org/blog/2021/07/02/ropensci-user2021/</link><pubDate>Fri, 02 Jul 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2021/07/02/ropensci-user2021/</guid><description>
&lt;p&gt;Are you putting together your useR!2021 conference schedule this weekend? Four rOpenSci staff and lots of community members are giving presentations and there&amp;rsquo;s something for everyone!&lt;/p&gt;
&lt;h2&gt;
Talks by rOpenSci staff
&lt;/h2&gt;&lt;p&gt;&lt;strong&gt;Jeroen Ooms&lt;/strong&gt;, Lead Infrastructure Engineer, will give a &lt;a href="https://www.conftool.org/user2021/index.php?page=browseSessions&amp;amp;form_session=34#paperID355"&gt;&lt;strong&gt;keynote talk&lt;/strong&gt;&lt;/a&gt; about &lt;a href="https://ropensci.org/r-universe/"&gt;&lt;strong&gt;the R-universe project&lt;/strong&gt;&lt;/a&gt; on Friday, July 9, 12:30PM - 1:30PM UTC / 5:30AM PDT.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Stefanie Butland&lt;/strong&gt;, Community Manager, will present on &lt;a href="https://www.conftool.org/user2021/index.php?page=browseSessions&amp;amp;form_session=8#paperID260"&gt;&lt;strong&gt;rOpenSci&amp;rsquo;s Model for Managing a Federated Open Source Software Community&lt;/strong&gt;&lt;/a&gt; on Monday, July 5, 5:05PM UTC / 10:05AM PDT.&lt;/p&gt;</description></item><item><title>How We Curate Our Monthly Newsletter</title><link>https://ropensci.org/blog/2021/06/24/news-meta/</link><pubDate>Thu, 24 Jun 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2021/06/24/news-meta/</guid><description>
&lt;p&gt;How to keep up with rOpenSci?
We agree that we&amp;rsquo;re doing so much good work that it&amp;rsquo;s hard. 😉
More seriously, we&amp;rsquo;ve been curating and sharing a news digest with our community for years because we believe it to be useful.
Over time its structure and infrastructure have evolved.
In this post we&amp;rsquo;ll share how we currently prepare content for the newsletter and send it to subscribers&amp;rsquo; mailboxes, as automatically as possible.&lt;/p&gt;</description></item><item><title>Mapping Asian elephant observations with rgbif</title><link>https://ropensci.org/usecases/mapping-asian-elephant-observations-with-rgbif/</link><pubDate>Wed, 23 Jun 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/mapping-asian-elephant-observations-with-rgbif/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/rgbif/"&gt;rgbif&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;Searched GBIF for observations of &lt;em&gt;Elephas maximus&lt;/em&gt; (Asian elephant), and used the locations for making two maps: one for the distribution as a heatmap, and one for observations themselves with a popup.&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://github.com/tts/asianelephants/blob/512456cfef6eb40e142b549d64312d6e21057baf/preparedata.R"&gt;Code&lt;/a&gt; and &lt;a href="https://ttso.shinyapps.io/asianelephants/"&gt;Shiny web app&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
Image
&lt;/h4&gt;&lt;p&gt;&lt;img src="https://ropensci.org/usecases/mapping-asian-elephant-observations-with-rgbif/mapping-asian-elephant-observations-with-rgbif.jpeg" alt="eldark.PNG|690x418"&gt;&lt;/p&gt;
&lt;h4&gt;
Sector
&lt;/h4&gt;&lt;p&gt;Other&lt;/p&gt;
&lt;h4&gt;
Field(s) of application
&lt;/h4&gt;&lt;p&gt;Ecology&lt;/p&gt;</description></item><item><title>How to create your personal CRAN-like repository on R-universe</title><link>https://ropensci.org/blog/2021/06/22/setup-runiverse/</link><pubDate>Tue, 22 Jun 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2021/06/22/setup-runiverse/</guid><description>
&lt;h2&gt;
R-universe: your personal R space
&lt;/h2&gt;&lt;p&gt;The &lt;a href="https://r-universe.dev"&gt;r-universe&lt;/a&gt; platform provides users and organizations with a personal CRAN-like repository for publishing software, rmarkdown articles, and other content that fits in an R package.&lt;/p&gt;
&lt;p&gt;The system automatically tracks registered git repositories containing R packages, builds binaries for Windows and MacOS, renders vignettes, and makes all data available through dashboards, feeds and APIs on personal subdomains, for example:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://ropensci.r-universe.dev"&gt;https://ropensci.r-universe.dev&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://ggseg.r-universe.dev"&gt;https://ggseg.r-universe.dev&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://r-spatial.r-universe.dev"&gt;https://r-spatial.r-universe.dev&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://mrc-ide.r-universe.dev"&gt;https://mrc-ide.r-universe.dev&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://feddelegrand7.r-universe.dev"&gt;https://feddelegrand7.r-universe.dev&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The initial pilot was mostly focused mainly on CRAN/rOpenSci developers, but as of last month we have opened up the system for anyone to create a personal R universe and start publishing packages.&lt;/p&gt;</description></item><item><title>rOpenSci News Digest, June 2021</title><link>https://ropensci.org/blog/2021/06/21/ropensci-news-digest-june-2021/</link><pubDate>Mon, 21 Jun 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2021/06/21/ropensci-news-digest-june-2021/</guid><description>
&lt;!-- Before sending DELETE THE INDEX_CACHE and re-knit! --&gt;
&lt;p&gt;Dear rOpenSci friends, it&amp;rsquo;s time for our monthly news roundup!&lt;/p&gt;
&lt;!-- blabla --&gt;
&lt;p&gt;You can read this post &lt;a href="https://ropensci.org/blog/2021/06/21/ropensci-news-digest-june-2021"&gt;on our blog&lt;/a&gt;.
Now let&amp;rsquo;s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;h3&gt;
R-universe
&lt;/h3&gt;&lt;p&gt;Video and resources from our past community call about &lt;a href="https://ropensci.org/commcalls/may2021-r-universe/"&gt;&lt;strong&gt;rOpenSci&amp;rsquo;s R-universe Project&lt;/strong&gt;&lt;/a&gt; were posted. The R-universe platform is a new umbrella project under which rOpenSci experiments with new ideas for improving publication and discovery of research software packages in R. In this 1-hour community call, &lt;strong&gt;Jeroen Ooms&lt;/strong&gt; explained the basic steps of setting up your own universe, and getting started with publishing packages (including experimental software, development versions, &lt;a href="https://ropensci.org/blog/2021/04/09/r-universe-articles/"&gt;research compendia&lt;/a&gt;) and articles on your &lt;a href="https://jeroen.r-universe.dev"&gt;personal subdomain&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Using rotl to create phylogenetic trees</title><link>https://ropensci.org/usecases/using-rotl-to-create-phylogenetic-trees/</link><pubDate>Sat, 12 Jun 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/using-rotl-to-create-phylogenetic-trees/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/rotl/"&gt;rotl&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;Used rotl to create a phylogenetic tree using a species scientific name and included clipart for each animal using phylopic.&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://github.com/dosullivan019/30DayChartChallenge/blob/e4f5fe3e9d6245a5a65b7d617c785781eaaa5b69/code/day16_tree.R"&gt;https://github.com/dosullivan019/30DayChartChallenge/blob/e4f5fe3e9d6245a5a65b7d617c785781eaaa5b69/code/day16_tree.R&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
Image
&lt;/h4&gt;&lt;p&gt;&lt;img src="https://ropensci.org/usecases/using-rotl-to-create-phylogenetic-trees/using-rotl-to-create-phylogenetic-trees.png" alt="image|690x371"&gt;&lt;/p&gt;
&lt;h4&gt;
Sector
&lt;/h4&gt;&lt;p&gt;other&lt;/p&gt;</description></item><item><title>Social Co-Working and Label-athon</title><link>https://ropensci.org/events/labelathon04/</link><pubDate>Fri, 11 Jun 2021 01:30:00 +0000</pubDate><guid>https://ropensci.org/events/labelathon04/</guid><description>
&lt;p&gt;We’re following up our Community Call - &lt;a href="https://ropensci.org/commcalls/apr2021-pkg-community/"&gt;Set Up Your Package to Foster a Community&lt;/a&gt; - with an experiment!&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Join us for 1.5 hours Thursday, June 10th, 5 PM Pacific / Friday June 11th 00:00 UTC for our fourth co-working “label-athon”.&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Meet other package developers and rOpenSci staff in Zoom&lt;/li&gt;
&lt;li&gt;Co-work independently, implementing some of &lt;a href="https://ropensci.org/commcalls/apr2021-pkg-community/"&gt;our recommendations&lt;/a&gt; for what you can add/modify in your own package to encourage community participation
&lt;ul&gt;
&lt;li&gt;Code of Conduct&lt;/li&gt;
&lt;li&gt;Contributing guide&lt;/li&gt;
&lt;li&gt;Roadmap and expectations&lt;/li&gt;
&lt;li&gt;Open and label issues to invite contributions&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Get answers to your questions&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;At the end of the session we’ll tweet links to your “&lt;a href="https://github.com/search?q=org%3Aropensci+label%3A%22help+wanted%22+state%3Aopen&amp;amp;type=Issues"&gt;help wanted&lt;/a&gt;” issues to help you get attention to your project.&lt;/p&gt;</description></item><item><title>Celebrating World Ocean Day rOpenSci Style</title><link>https://ropensci.org/blog/2021/06/08/world-ocean-day/</link><pubDate>Tue, 08 Jun 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2021/06/08/world-ocean-day/</guid><description>
&lt;p&gt;&lt;strong&gt;Happy &lt;a href="https://worldoceanday.org/"&gt;World Ocean Day&lt;/a&gt;!&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://worldoceanday.org/"&gt;World Ocean Day&lt;/a&gt; is a day of celebration and action to protect our shared ocean.&lt;/p&gt;
&lt;p&gt;While I already appreciate the importance of protecting sensitive ecosystems, including the ocean&lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt;, I found the idea of World Ocean Day especially touching.&lt;/p&gt;
&lt;blockquote class='blockquote text-left'&gt;
&lt;p class="mb-0"&gt;On World Ocean Day, people around our blue planet celebrate and honor our one shared ocean, that connects us all.&lt;/p&gt;
&lt;footer class="blockquote-footer"&gt;&lt;a href="https://worldoceanday.org/about/"&gt;About World Ocean Day&lt;/a&gt; &lt;/footer&gt;
&lt;/blockquote&gt;
&lt;p&gt;This year has been hard, and like many, I often feel isolated and emotionally exhausted.
The idea that we have only one ocean and it connects us is a lovely way to remember that as isolated as we may feel we&amp;rsquo;re all here on this planet together.&lt;/p&gt;</description></item><item><title>Using tabulizer to extract tabular data from daily COVID-19 reports</title><link>https://ropensci.org/usecases/using-tabulizer-to-extract-tabular-data-from-daily-covid-19-reports/</link><pubDate>Mon, 07 Jun 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/using-tabulizer-to-extract-tabular-data-from-daily-covid-19-reports/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/tabulizer"&gt;tabulizer&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;Used tabulizer to extract total cases, fatalities, hospitalizations, and tests from daily COVID-19 reports for Connecticut.&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://github.com/davebraze/ct-covid19/blob/efc3afd6e86baf8ff7454f1d6a02d3e68feb6154/locals.R#L29"&gt;https://github.com/davebraze/ct-covid19/blob/efc3afd6e86baf8ff7454f1d6a02d3e68feb6154/locals.R#L29&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
Sector
&lt;/h4&gt;&lt;p&gt;other&lt;/p&gt;</description></item><item><title>Social Co-Working and Label-athon</title><link>https://ropensci.org/events/labelathon03/</link><pubDate>Thu, 27 May 2021 17:30:00 +0000</pubDate><guid>https://ropensci.org/events/labelathon03/</guid><description>
&lt;p&gt;We’re following up our Community Call - &lt;a href="https://ropensci.org/commcalls/apr2021-pkg-community/"&gt;Set Up Your Package to Foster a Community&lt;/a&gt; - with an experiment!&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Join us for 1.5 hours Thursday, May 27th, 9 PM Pacific / 16:00 UTC for our third co-working “label-athon”.&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Meet other package developers and rOpenSci staff in Zoom&lt;/li&gt;
&lt;li&gt;Co-work independently, implementing some of &lt;a href="https://ropensci.org/commcalls/apr2021-pkg-community/"&gt;our recommendations&lt;/a&gt; for what you can add/modify in your own package to encourage community participation
&lt;ul&gt;
&lt;li&gt;Code of Conduct&lt;/li&gt;
&lt;li&gt;Contributing guide&lt;/li&gt;
&lt;li&gt;Roadmap and expectations&lt;/li&gt;
&lt;li&gt;Open and label issues to invite contributions&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Get answers to your questions&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;At the end of the session we’ll tweet links to your “&lt;a href="https://github.com/search?q=org%3Aropensci+label%3A%22help+wanted%22+state%3Aopen&amp;amp;type=Issues"&gt;help wanted&lt;/a&gt;” issues to help you get attention to your project.&lt;/p&gt;</description></item><item><title>rOpenSci's R-universe Project</title><link>https://ropensci.org/commcalls/may2021-r-universe/</link><pubDate>Tue, 06 Apr 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/commcalls/may2021-r-universe/</guid><description>
&lt;h3&gt;
Index of video and slides
&lt;/h3&gt;&lt;ul&gt;
&lt;li&gt;0:00 Stefanie Butland, Welcome and introductions&lt;/li&gt;
&lt;li&gt;3:10 Jeroen Ooms, Getting started with R-universe
&lt;ul&gt;
&lt;li&gt;3:57 What is R-universe? (&lt;a href="https://jeroen.github.io/runiverse2021/#3"&gt;slides&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;7:52 Browsing R packages in a universe (&lt;a href="https://jeroen.github.io/runiverse2021/#11"&gt;slides&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;12:05 Browsing articles in a universe (&lt;a href="https://jeroen.github.io/runiverse2021/#20"&gt;slides&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;14:07 API access to all the data! (&lt;a href="https://jeroen.github.io/runiverse2021/#25"&gt;slides&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;17:00 For whom is R universe intended? (&lt;a href="https://jeroen.github.io/runiverse2021/#30"&gt;slides&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;18:40 Example use-cases (&lt;a href="https://jeroen.github.io/runiverse2021/#32"&gt;slides&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;28:48 Global feeds connect the universes (&lt;a href="https://jeroen.github.io/runiverse2021/#40"&gt;slides&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;32:31 How to setup your own universe (&lt;a href="https://jeroen.github.io/runiverse2021/#45"&gt;slides&lt;/a&gt;)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;41:07 Karthik Ram, Big picture and context for the R-universe project&lt;/li&gt;
&lt;li&gt;42:58 Q &amp;amp; A&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;
Setting up your own R universe
&lt;/h3&gt;&lt;p&gt;Earlier this year we announced &lt;a href="https://ropensci.org/r-universe/"&gt;R-universe&lt;/a&gt;: a project by rOpenSci under which we experiment with various ideas for improving publication and discovery of research software packages in R. The platform is under heavy development, Jeroen&amp;rsquo;s &lt;a href="https://resources.rstudio.com/resources/rstudioglobal-2021/monitoring-health-and-impact-of-open-source-projects/"&gt;talk at rstudio-conf 2021&lt;/a&gt; outlines some of our ambitions for the effort.&lt;/p&gt;</description></item><item><title>rOpenSci News Digest, May 2021</title><link>https://ropensci.org/blog/2021/05/21/ropensci-news-digest-may-2021/</link><pubDate>Fri, 21 May 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2021/05/21/ropensci-news-digest-may-2021/</guid><description>
&lt;!-- Before sending DELETE THE INDEX_CACHE and re-knit! --&gt;
&lt;p&gt;Dear rOpenSci friends, it&amp;rsquo;s time for our monthly news roundup!&lt;/p&gt;
&lt;!-- blabla --&gt;
&lt;p&gt;You can read this post &lt;a href="https://ropensci.org/blog/2021/05/21/ropensci-news-digest-may-2021"&gt;on our blog&lt;/a&gt;.
Now let&amp;rsquo;s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;p&gt;We have no less than three categories of (online &amp;#x1f609;) events coming up: social co-working events, a community call, a conference with contributions from four rOpenSci staff members. &amp;#x2728;&lt;/p&gt;</description></item><item><title>Technical Debt in the Peer-Review Documentation of R Packages: a rOpenSci Case Study</title><link>https://ropensci.org/events/msr2021/</link><pubDate>Tue, 18 May 2021 04:00:00 +0000</pubDate><guid>https://ropensci.org/events/msr2021/</guid><description>
&lt;p&gt;rOpenSci Editor Melina Vidoni presents at &lt;a href="https://2021.msrconf.org/"&gt;MSR 2021&lt;/a&gt; Mining Software Repositories Conference: &lt;a href="https://www.cs.usask.ca/faculty/zadiacodabux/index.html"&gt;Zadia Codabux&lt;/a&gt;, &lt;a href="https://melvidoni.rbind.io/"&gt;Melina Vidoni&lt;/a&gt;, &lt;a href="https://cmps.ok.ubc.ca/about/contact/fatemeh-hendijani-fard/"&gt;Fatemeh Fard&lt;/a&gt; (2021). &lt;strong&gt;Technical Debt in the Peer-Review Documentation of R Packages: a rOpenSci Case Study&lt;/strong&gt;. &lt;a href="https://melvidoni.rbind.io/publication/2021-ropensci/"&gt;Preprint&lt;/a&gt;; &lt;a href="https://2021.msrconf.org/details/msr-2021-technical-papers/20/Technical-Debt-in-the-Peer-Review-Documentation-of-R-Packages-a-rOpenSci-Case-Study"&gt;Conference page&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Melina will present two additional talks:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Melina Vidoni (2021). Self-Admitted Technical Debt in R Packages: An Exploratory Study &lt;a href="https://melvidoni.rbind.io/publication/2021-rsatd/"&gt;Preprint&lt;/a&gt;; &lt;a href="https://2021.msrconf.org/details/msr-2021-technical-papers/18/Self-Admitted-Technical-Debt-in-R-Packages-An-Exploratory-Study"&gt;Conference page&lt;/a&gt;. MSR 2021&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Melina Vidoni (2020). Evaluating Unit Testing Practices in R Packages &lt;a href="https://melvidoni.rbind.io/publication/2021-rttd-icse/"&gt;Preprint&lt;/a&gt;; &lt;a href="https://conf.researchr.org/details/icse-2021/icse-2021-papers/5/Evaluating-Unit-Testing-Practices-in-R-Packages"&gt;Conference page&lt;/a&gt;. 43rd International Conference on Software Engineering ICSE 2021&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>Most tweeted words each month: a year snapshot</title><link>https://ropensci.org/usecases/most-tweeted-words-each-month-a-year-snapshot/</link><pubDate>Mon, 17 May 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/most-tweeted-words-each-month-a-year-snapshot/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/rtweet"&gt;&lt;code&gt;rtweet&lt;/code&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Also used: &lt;a href="https://gganimate.com/"&gt;&lt;code&gt;gganimate&lt;/code&gt;&lt;/a&gt;, &lt;a href="https://ggplot2.tidyverse.org/reference/ggplot.html"&gt;&lt;code&gt;ggplot&lt;/code&gt;&lt;/a&gt;, &lt;a href="https://lubridate.tidyverse.org/"&gt;&lt;code&gt;lubridate&lt;/code&gt;&lt;/a&gt;. Code adapted from Julia Silge&amp;rsquo;s and David Robinson&amp;rsquo;s twitter case study in their book &lt;a href="https://www.tidytextmining.com/twitter.html"&gt;Text Mining with R&lt;/a&gt; and a helpful &lt;a href="https://stackoverflow.com/questions/61132650/is-there-a-way-to-animate-a-word-cloud-in-r"&gt;Stackoverflow&lt;/a&gt; answer by a user named &lt;a href="https://stackoverflow.com/users/7514527/edward"&gt;Edward&lt;/a&gt; ;)&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;This was part of a final project for a course on Text Mining techniques. I analyzed the differences between three universities&amp;rsquo; main Twitter accounts: @DukeU, @NCState, @UNC. I took a year snapshot of tweets utilizing &lt;code&gt;rtweet&lt;/code&gt; and tried to find similarities and differences of what they were talking about. Covid19 was one of the key similarities, which makes sense given the year was dominated by the pandemic. You can see the progression of most frequently tweeted terms (tokenized by unigrams) by the use of &lt;code&gt;gganimate&lt;/code&gt; + &lt;code&gt;geom_text_wordcloud&lt;/code&gt;.&lt;/p&gt;</description></item><item><title>Social Co-Working and Label-athon</title><link>https://ropensci.org/events/labelathon02/</link><pubDate>Fri, 14 May 2021 01:30:00 +0000</pubDate><guid>https://ropensci.org/events/labelathon02/</guid><description>
&lt;p&gt;We’re following up our Community Call - &lt;a href="https://ropensci.org/commcalls/apr2021-pkg-community/"&gt;Set Up Your Package to Foster a Community&lt;/a&gt; - with an experiment!&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Join us for 1.5 hours Thursday, May 13th, 5 PM Pacific / Friday May 14th 00:00 UTC for our second co-working “label-athon”.&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Meet other package developers and rOpenSci staff in Zoom&lt;/li&gt;
&lt;li&gt;Co-work independently, implementing some of &lt;a href="https://ropensci.org/commcalls/apr2021-pkg-community/"&gt;our recommendations&lt;/a&gt; for what you can add/modify in your own package to encourage community participation
&lt;ul&gt;
&lt;li&gt;Code of Conduct&lt;/li&gt;
&lt;li&gt;Contributing guide&lt;/li&gt;
&lt;li&gt;Roadmap and expectations&lt;/li&gt;
&lt;li&gt;Open and label issues to invite contributions&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Get answers to your questions&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;At the end of the session we’ll tweet links to your “&lt;a href="https://github.com/search?q=org%3Aropensci+label%3A%22help+wanted%22+state%3Aopen&amp;amp;type=Issues"&gt;help wanted&lt;/a&gt;” issues to help you get attention to your project.&lt;/p&gt;</description></item><item><title>Easily analyzing tweets using rtweet</title><link>https://ropensci.org/usecases/easily-analyzing-tweets-using-rtweet/</link><pubDate>Wed, 12 May 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/easily-analyzing-tweets-using-rtweet/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://github.com/ropensci/rtweet"&gt;rtweet&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;After the #30DayChartChallenge was over on April 30th, I wanted to make a summary of the twitter activity related to my tweets on the #30DayChartChallenge. All of the data for this analysis such as the tweets and user information were retrieved using rtweet, data wrangling done using tidyverse and visualization using ggplot2 and leaflet.&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://github.com/aarora79/30DayChartChallenge/tree/main/tweets"&gt;https://github.com/aarora79/30DayChartChallenge/tree/main/tweets&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Scraping Google Play Reviews with RSelenium</title><link>https://ropensci.org/usecases/scraping-google-play-reviews-with-rselenium/</link><pubDate>Tue, 11 May 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/scraping-google-play-reviews-with-rselenium/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/RSelenium/"&gt;RSelenium&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;Used &lt;a href="https://docs.ropensci.org/RSelenium/"&gt;RSelenium&lt;/a&gt; to scrape web reviews for Instagram Lite in order to do text analysis in a future blog post. The package was used to start a remote browser, browse to Google Play, and navigate the semi-infinite scroll and button clicks to load additional reviews.&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://jlaw.netlify.app/2021/05/03/scraping-google-play-reviews-with-rselenium/"&gt;My Blog Post&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
Field(s) of application
&lt;/h4&gt;&lt;p&gt;Just for fun&lt;/p&gt;</description></item><item><title>What's New in terrainr 0.4.0?</title><link>https://ropensci.org/blog/2021/05/04/what-s-new-in-terrainr-0-4-0/</link><pubDate>Tue, 04 May 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2021/05/04/what-s-new-in-terrainr-0-4-0/</guid><description>
&lt;p&gt;terrainr version 0.4.0 is now on CRAN! This version is a relatively minor update
that shouldn&amp;rsquo;t impact most workflows, but makes some changes to improve the
logic and consistency of the package. The rest of this post runs through the
changes you can expect if you &lt;code&gt;update.packages&lt;/code&gt; any time soon!&lt;/p&gt;
&lt;h2&gt;
What&amp;rsquo;s a terrainr?
&lt;/h2&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/terrainr/"&gt;terrainr&lt;/a&gt; is an R package for the
retrieval and visualization of spatial data. It provides functions to download
elevation data and basemap tiles for points within the United States (using
public domain data from the USGS National Map), visualize them in R via ggplot2,
and process them for 3D visualization using the Unity 3D engine. You can see
&lt;a href="https://docs.ropensci.org/terrainr/"&gt;the docs and access the GitHub repo here!&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Social Label-athon</title><link>https://ropensci.org/events/labelathon01/</link><pubDate>Thu, 29 Apr 2021 19:00:00 +0000</pubDate><guid>https://ropensci.org/events/labelathon01/</guid><description>
&lt;p&gt;We’re following up our Community Call - &lt;a href="https://ropensci.org/commcalls/apr2021-pkg-community/"&gt;Set Up Your Package to Foster a Community&lt;/a&gt; - with an experiment!&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Join us for 1.5 hours Thursday, April 29, 9 AM Pacific / 16:00 UTC for our first co-working “label-athon”.&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Meet other package developers and rOpenSci staff in Zoom&lt;/li&gt;
&lt;li&gt;Work independently, implementing some of &lt;a href="https://ropensci.org/commcalls/apr2021-pkg-community/"&gt;our recommendations&lt;/a&gt; for what you can add/modify in your own package to encourage community participation
&lt;ul&gt;
&lt;li&gt;Code of Conduct&lt;/li&gt;
&lt;li&gt;Contributing guide&lt;/li&gt;
&lt;li&gt;Roadmap and expectations&lt;/li&gt;
&lt;li&gt;Open and label issues to invite contributions&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Get answers to your questions&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;At the end of the session we’ll tweet links to your “&lt;a href="https://github.com/search?q=org%3Aropensci+label%3A%22help+wanted%22+state%3Aopen&amp;amp;type=Issues"&gt;help wanted&lt;/a&gt;” issues to help you get attention to your project.&lt;/p&gt;</description></item><item><title>Set Up Your Package to Foster a Community - Community Call Summary</title><link>https://ropensci.org/blog/2021/04/28/commcall-pkg-community/</link><pubDate>Wed, 28 Apr 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2021/04/28/commcall-pkg-community/</guid><description>
&lt;p&gt;Last Thursday we held a &lt;a href="https://ropensci.org/commcalls/apr2021-pkg-community/"&gt;Community Call&lt;/a&gt; discussing how to set up a Package to Foster a Community.&lt;/p&gt;
&lt;p&gt;This call included speakers &lt;a href="https://ropensci.org/author/ma%C3%ABlle-salmon/"&gt;Maëlle Salmon&lt;/a&gt;, &lt;a href="https://ropensci.org/author/hugo-gruson"&gt;Hugo Gruson&lt;/a&gt; and &lt;a href="https://ropensci.org/author/steffi-lazerte"&gt;Steffi LaZerte&lt;/a&gt;, and was moderated by &lt;a href="https://ropensci.org/author/stefanie-butland"&gt;Stefanie Butland&lt;/a&gt;.&lt;/p&gt;
&lt;figure class="center"&gt;&lt;img src="https://ropensci.org/blog/2021/04/28/commcall-pkg-community/speakers.png"
alt="Headshots of the three speakers" width="600"&gt;
&lt;/figure&gt;
&lt;h2&gt;
Summarizing the community call
&lt;/h2&gt;&lt;p&gt;Scientific software development - and with that R packages - is a community effort. While there are often just a handful of developers maintaining an R package, the development really starts to thrive when users start to contribute.&lt;/p&gt;</description></item><item><title>Set Up Your Package to Foster a Community</title><link>https://ropensci.org/commcalls/apr2021-pkg-community/</link><pubDate>Wed, 24 Mar 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/commcalls/apr2021-pkg-community/</guid><description>
&lt;p&gt;rOpenSci puts ongoing effort into exploring and communicating how developers can best attract attention to their package (e.g. usage, citations, or feedback), or how to set up their repository to encourage the types of contributions they want. In this 1-hour community call, Maëlle Salmon, Hugo Gruson, and Steffi LaZerte will share tips and examples on how to do this!&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;What is the community of a package or project?&lt;/li&gt;
&lt;li&gt;Include a Code of Conduct&lt;/li&gt;
&lt;li&gt;What goes in your package contributing guide? Etiquette and setup&lt;/li&gt;
&lt;li&gt;Use your README to share your expectations with users and potential contributors&lt;/li&gt;
&lt;li&gt;Use issue templates&lt;/li&gt;
&lt;li&gt;Use issue labels to explicitly invite contributions (code or non-code) and user feedback&lt;/li&gt;
&lt;li&gt;Include a roadmap so potential contributors know where your package is going, what you plan to implement, and what you won’t&lt;/li&gt;
&lt;li&gt;What characteristics of a package or project make contributors keep coming back?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Come hear our best recommendations, and share your favorites. Stefanie Butland will moderate to get answers to your questions and we’ll have a collaborative notes doc to harness everyone&amp;rsquo;s collective wisdom.&lt;/p&gt;</description></item><item><title>rOpenSci News Digest, April 2021</title><link>https://ropensci.org/blog/2021/04/16/latest-ropensci-news-digest/</link><pubDate>Fri, 16 Apr 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2021/04/16/latest-ropensci-news-digest/</guid><description>
&lt;!-- Before sending DELETE THE INDEX_CACHE and re-knit! --&gt;
&lt;p&gt;Dear rOpenSci friends, it&amp;rsquo;s time for our monthly news roundup!
You can read this post &lt;a href="https://ropensci.org/blog/2021/04/16/latest-ropensci-news-digest"&gt;on our blog&lt;/a&gt;.
Now let&amp;rsquo;s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;p&gt;Are you interested in &lt;a href="https://devguide.ropensci.org/softwarereviewintro.html#whyreview"&gt;volunteering as a package reviewer&lt;/a&gt; for rOpenSci?
We have just updated our &lt;a href="https://airtable.com/shrnfDI2S9uuyxtDw"&gt;volunteering form&lt;/a&gt; to make it easier to match volunteers and packages.
It only takes a few minutes to fill the form.
Thanks to the more than 150 people who already answered, we&amp;rsquo;re very thankful for your participation!&lt;/p&gt;</description></item><item><title>Using RSelenium to scrape a paginated HTML table</title><link>https://ropensci.org/usecases/using-rselenium-to-scrape-a-paginated-html-table/</link><pubDate>Mon, 12 Apr 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/using-rselenium-to-scrape-a-paginated-html-table/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/RSelenium/"&gt;RSelenium&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;This example explains how emulate clicks can be done to navigate from elements to others in the HTML page, and a more focus point on moving from page to page in a paginated table.&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case*
&lt;/h4&gt;&lt;p&gt;Blog post &lt;a href="https://guillaumepressiat.github.io/blog/2021/04/RSelenium-paginated-tables"&gt;here&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Publishing and browsing articles on R-universe</title><link>https://ropensci.org/blog/2021/04/09/r-universe-articles/</link><pubDate>Fri, 09 Apr 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2021/04/09/r-universe-articles/</guid><description>
&lt;h2&gt;
Browsing articles on R-universe
&lt;/h2&gt;&lt;p&gt;In the past weeks we have extended the R-universe build system and front-ends with some new features for publishing &lt;em&gt;articles&lt;/em&gt;. Articles can be used for documentation of R packages, but also for other purposes, such as reports, tutorials, papers, or research compendia.
Publishing of articles in R-universe is based on the R vignette system, and we may add support for other types of articles later on.&lt;/p&gt;</description></item><item><title>Maëlle Salmon Teaches R-pkg Dev at R-Ladies East Lansing &amp; Chicago</title><link>https://ropensci.org/events/maelle-pkg-dev/</link><pubDate>Fri, 26 Mar 2021 19:00:00 +0000</pubDate><guid>https://ropensci.org/events/maelle-pkg-dev/</guid><description>
&lt;p&gt;“Develop an R package”, they said… What does this even mean?&lt;/p&gt;
&lt;p&gt;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. And how to solve the specific new challenges you will encounter! Last but not least we will discuss how to find your happy place in the world of R package development.&lt;/p&gt;</description></item><item><title>Teaching an introduction to workflow management using drake</title><link>https://ropensci.org/usecases/teaching-an-introduction-to-workflow-management-using-drake/</link><pubDate>Thu, 25 Mar 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/teaching-an-introduction-to-workflow-management-using-drake/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://github.com/ropensci/drake"&gt;&lt;code&gt;drake&lt;/code&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;In fall 2020 the &lt;a href="https://cereo.wsu.edu/"&gt;Center for Environmental Research, Education and Outreach&lt;/a&gt; at Washington State University hosted a workshop covering reproducible research techniques in R for graduate students. We wanted to cover &lt;code&gt;drake&lt;/code&gt; workflows as one day of the workshop to show the students what R-specific options there are for managing workflows. We expected that workflow management and to some extent R functions would be unfamiliar topics to many students, so the workshop day included discussion of why one would use workflow management software and some basic examples of building realistic functions. At the time that we ran the workshop I wasn&amp;rsquo;t aware of &lt;a href="https://github.com/ropensci/targets"&gt;&lt;code&gt;targets&lt;/code&gt;&lt;/a&gt;, so in the future we may repurpose this example using that package instead.&lt;/p&gt;</description></item><item><title>Latest rOpenSci News Digest</title><link>https://ropensci.org/blog/2021/03/16/ropensci-news/</link><pubDate>Tue, 16 Mar 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2021/03/16/ropensci-news/</guid><description>
&lt;p&gt;Dear rOpenSci friends, it&amp;rsquo;s time for our monthly news roundup!
Some housekeeping first:
We&amp;rsquo;ve been changing the infrastructure of our newsletter a bit so please update your RSS and JSON feeds to &lt;code&gt;https://ropensci.org/tags/newsletter/index.xml&lt;/code&gt; and &lt;code&gt;https://ropensci.org/tags/newsletter/index.json&lt;/code&gt;, respectively.
You can read this post &lt;a href="https://ropensci.org/blog/2021/03/16/ropensci-news"&gt;on our blog&lt;/a&gt;.
Now let&amp;rsquo;s dive into the activity at and around rOpenSci!&lt;/p&gt;
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;p&gt;Our R-universe project now has &lt;a href="https://ropensci.org/r-universe/"&gt;its own page on our website&lt;/a&gt;! &amp;#x1f680; The R-universe platform is a new umbrella project under which we experiment with various new ideas for improving publication and discovery of research software in R.&lt;/p&gt;</description></item><item><title>rOpenSci Statistical Software Testing and Peer Review - Community Call Summary</title><link>https://ropensci.org/blog/2021/03/09/commcall-stats/</link><pubDate>Tue, 09 Mar 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2021/03/09/commcall-stats/</guid><description>
&lt;p&gt;A week ago we held a &lt;a href="https://ropensci.org/commcalls/feb2021-statsreview/"&gt;Community Call&lt;/a&gt; discussing rOpenSci Statistical Software Testing and Peer Review.
This call included speakers &lt;a href="https://ropensci.org/author/noam-ross/"&gt;Noam Ross&lt;/a&gt;, &lt;a href="https://ropensci.org/author/mark-padgham"&gt;Mark Padgham&lt;/a&gt;, &lt;a href="https://ropensci.org/author/anna-krystalli"&gt;Anna Krystalli&lt;/a&gt;, &lt;a href="https://ropensci.org/author/alex-hayes"&gt;Alex Hayes&lt;/a&gt;, and &lt;a href="https://ropensci.org/author/john-sakaluk"&gt;John Sakaluk&lt;/a&gt;.&lt;/p&gt;
&lt;figure class="center"&gt;&lt;img src="https://ropensci.org/blog/2021/03/09/commcall-stats/speakers.png"
alt="Headshots of the moderator and four panelists" width="600"&gt;
&lt;/figure&gt;
&lt;p&gt;This post provides a ready reference and description of this community call, which introduced the system being developed for peer review of explicitly statistical software, along with a couple of the automated software tools for use by developers and reviewers of statistical software.&lt;/p&gt;</description></item><item><title>A first look at the R-universe build infrastructure</title><link>https://ropensci.org/blog/2021/03/04/r-universe-buildsystem/</link><pubDate>Thu, 04 Mar 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2021/03/04/r-universe-buildsystem/</guid><description>
&lt;h2&gt;
The R-universe build system
&lt;/h2&gt;&lt;p&gt;The R-universe system is a complex effort, consisting of numerous frontend and backend pieces that operate across various platforms. A key challenge in developing such a system is managing overall complexity by finding ways to reduce the problem into smaller, loosely coupled components, which can be thought of, and developed, somewhat independently.&lt;/p&gt;
&lt;p&gt;A lot of the early work on R-universe has gone into iterating with designs to gradually build up such a system in a way that is robust and scalable, while keeping complexity under control.&lt;/p&gt;</description></item><item><title>rOpenSci Statistical Software Testing and Peer Review</title><link>https://ropensci.org/commcalls/feb2021-statsreview/</link><pubDate>Wed, 17 Feb 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/commcalls/feb2021-statsreview/</guid><description>
&lt;p&gt;This is the first in a series of Community Calls we&amp;rsquo;ll host throughout the year on our &lt;a href="https://ropenscilabs.github.io/statistical-software-review-book/index.html"&gt;statistical software review project&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;We at rOpenSci are in the process of expanding the scope of our software peer-review system to encompass explicitly statistical software. As part of this we have developed new tools to help prepare software for submission. One of these, the &lt;a href="https://github.com/ropenscilabs/autotest"&gt;autotest package&lt;/a&gt;, implements and automates rigorous testing of all function inputs, while another, the &lt;a href="https://github.com/ropenscilabs/srr"&gt;srr package&lt;/a&gt;, enables documentation of, and reporting on, how and where code meets our sets of category-specific standards. Developers of packages to be submitted to this newly expanded system will be expected to apply both of these tools prior to submission.&lt;/p&gt;</description></item><item><title>Using terrainr to retrieve spatial data and make 3D landscape visualizations</title><link>https://ropensci.org/usecases/using-terrainr-to-retrieve-spatial-data-and-make-3d-landscape-visualizations/</link><pubDate>Mon, 01 Mar 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/using-terrainr-to-retrieve-spatial-data-and-make-3d-landscape-visualizations/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://github.com/ropensci/terrainr"&gt;terrainr&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;Visualized Mt. St. Helens in Unity, using public-domain data from the USGS entirely retrieved and pre-processed in R.&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case*
&lt;/h4&gt;&lt;pre tabindex="0"&gt;&lt;code&gt;library(terrainr)
library(sf)
library(progressr)
handlers(&amp;#34;progress&amp;#34;)
st_helens &amp;lt;- data.frame(
lat = 46.1914,
lng = -122.1956
)
st_helens &amp;lt;- st_as_sf(st_helens, coords = c(&amp;#34;lng&amp;#34;, &amp;#34;lat&amp;#34;))
st_helens &amp;lt;- st_set_crs(st_helens, 4326)
st_helens &amp;lt;- set_bbox_side_length(st_helens, 8000)
with_progress(
output_tiles &amp;lt;- get_tiles(st_helens,
services = c(&amp;#34;elevation&amp;#34;, &amp;#34;ortho&amp;#34;))
)
merged_tiles &amp;lt;- vapply(output_tiles, merge_rasters, character(1))
mapply(
function(x, y) raster_to_raw_tiles(x, &amp;#34;st_helens&amp;#34;, raw = y),
merged_tiles,
c(TRUE, FALSE)
)
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;This gets you a set of files in the format that Unity expects. You still need to import them by hand (for now&amp;hellip;) &amp;ndash; see &lt;a href="https://docs.ropensci.org/terrainr/articles/unity_instructions.html"&gt;the Unity vignette&lt;/a&gt; for more on that!&lt;/p&gt;</description></item><item><title>rOpenSci Dev Guide 0.6.0: Updates</title><link>https://ropensci.org/blog/2021/02/23/devguide-0.6.0/</link><pubDate>Tue, 23 Feb 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2021/02/23/devguide-0.6.0/</guid><description>
&lt;p&gt;rOpenSci Software Peer Review&amp;rsquo;s guidance is gathered in &lt;a href="https://devguide.ropensci.org/"&gt;an online book&lt;/a&gt; and keeps improving!
To find out what&amp;rsquo;s new in our dev guide 0.6.0, you can &lt;a href="https://devguide.ropensci.org/booknews.html"&gt;read the changelog&lt;/a&gt;,
or this blog post for more digested information.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;We have resumed activity after a break due to the COVID-19 crisis, but are being gentle with deadlines and timing, giving a lot of grace to all people involved. We&amp;rsquo;re all doing our best and rOpenSci is trying to be accommodating with schedules during this challenging period.&lt;/p&gt;</description></item><item><title>Make Your R Package Easier to Cite</title><link>https://ropensci.org/blog/2021/02/16/package-citation/</link><pubDate>Tue, 16 Feb 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2021/02/16/package-citation/</guid><description>
&lt;p&gt;Scientists rarely cite research software they use as part of a research project. As a consequence, the software and the time spent developing and maintaining it becomes an invisible scholarly contribution. Furthermore, this lack of visibility means that incentives to produce high quality, sustainable software are missing. Among many reasons why software is not cited, one is the lack of a clear citation information from package developers. In this tech note we provide some tips on how to make it really easy to cite your software.&lt;/p&gt;</description></item><item><title>coder Makes Medical Coding less Messy</title><link>https://ropensci.org/blog/2021/02/09/coder/</link><pubDate>Tue, 09 Feb 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2021/02/09/coder/</guid><description>
&lt;!--html_preserve--&gt;
&lt;figure class="pull-right"&gt;&lt;a href="https://docs.ropensci.org/coder/"&gt;&lt;img src="https://ropensci.org/blog/2021/02/09/coder/hex.png"
alt="Hex sticker for the coder package" width="150"&gt;&lt;/a&gt;
&lt;/figure&gt;
&lt;!--/html_preserve--&gt;
&lt;p&gt;A new R-package, &lt;a href="https://docs.ropensci.org/coder/"&gt;coder&lt;/a&gt;, has been &lt;a href="https://github.com/ropensci/coder"&gt;developed&lt;/a&gt;, &lt;a href="https://github.com/ropensci/software-review/issues/381"&gt;peer-reviewed&lt;/a&gt; by rOpenSci, accepted by &lt;a href="https://cran.r-project.org/package=coder"&gt;CRAN&lt;/a&gt;, and published in a paper by the Journal of Open Source Software &lt;a href="https://joss.theoj.org/papers/10.21105/joss.02916"&gt;(JOSS)&lt;/a&gt;. In this blog post, I will explain why this package might be useful for (epidemiological/medical/health care related) research.&lt;/p&gt;
&lt;h2&gt;
Clinical mess
&lt;/h2&gt;&lt;p&gt;Once upon a time, in countries not far from ours, there were MDs and nurses making up funny names for any diseases they encountered. What Dr. A called X would be recognized only as Y by his dear colleague Dr. B. X, however, was also a name used by Dr. C, but then for a completely different condition. It was a mess!&lt;/p&gt;</description></item><item><title>Mapping collaborations in Neotropical Taxonomy with refsplitr</title><link>https://ropensci.org/usecases/mapping-collaborations-in-neotropical-taxonomy-with-refsplitr/</link><pubDate>Sat, 06 Feb 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/mapping-collaborations-in-neotropical-taxonomy-with-refsplitr/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://github.com/ropensci/refsplitr"&gt;refsplitr&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;To demonstrate the importance of taxonomy for the study of Neotropical biodiversity, the authors (1) showcase selected plant groups in which in-depth taxonomic understanding has facilitated evolutionary and ecological research and (2) map the teams of collaborating scientists.&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://doi.org/10.3417/2020601"&gt;https://doi.org/10.3417/2020601&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
Image
&lt;/h4&gt;&lt;p&gt;&lt;img src="https://ropensci.org/usecases/mapping-collaborations-in-neotropical-taxonomy-with-refsplitr/mapping-collaborations-in-neotropical-taxonomy-with-refsplitr.png" alt="image|690x375"&gt;&lt;/p&gt;
&lt;h4&gt;
Sector
&lt;/h4&gt;&lt;p&gt;Academic&lt;/p&gt;
&lt;h4&gt;
Field(s) of application
&lt;/h4&gt;&lt;p&gt;Botany, Ecology, Tropical Biology, Bibliometrics, Science of Science&lt;/p&gt;</description></item><item><title>targets: Democratizing Reproducible Analysis Pipelines</title><link>https://ropensci.org/blog/2021/02/03/targets/</link><pubDate>Wed, 03 Feb 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2021/02/03/targets/</guid><description>
&lt;p&gt;&lt;a href="https://www.gnu.org/software/make/"&gt;Make&lt;/a&gt;&lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt;-like pipelines enhance the integrity, transparency, shelf life, efficiency, and scale of large analysis projects.
With pipelines, data science feels smoother and more rewarding, and the results are worthy of more trust.&lt;/p&gt;
&lt;!--html_preserve--&gt;
&lt;!-- I thought about following the blog guide's recommendation to use the Hugo shortcode for this tweet, but I feel the media and emojis are a bit much. --&gt;
&lt;blockquote class='blockquote text-left'&gt;
&lt;p class="mb-0"&gt;&amp;hellip;looking to get your project/s organised in the new year? hoping just to distract from feelings of impending doom/crushing loss of hope? I promise workflowing will make you feel better&amp;hellip; and &lt;a href="https://twitter.com/wmlandau"&gt;@wmlandau&lt;/a&gt; has made it SO EASY.&lt;/p&gt;</description></item><item><title>How rOpenSci Runs Community Calls</title><link>https://ropensci.org/blog/2021/02/02/ropensci-community-calls/</link><pubDate>Tue, 02 Feb 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2021/02/02/ropensci-community-calls/</guid><description>
&lt;p&gt;rOpenSci community calls are online events with the fundamental goal of strengthening our community. We have the additional goals of reinforcing our mission and values, informing people on technical and social topics, bringing different stakeholders’ perspectives to light, and identifying unmet needs on a topic.
Calls can include one to six speakers, or a moderated panel discussion.
They run for an hour and consist of 40 minutes of presentation and 20 minutes for questions from the audience.
Generally, our calls attract fairly large audiences&lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt; and we see significant representation from academia, government, and industry.&lt;/p&gt;</description></item><item><title>Use gert to scan all git repos in a directory</title><link>https://ropensci.org/usecases/use-gert-to-scan-all-git-repos-in-a-directory/</link><pubDate>Mon, 01 Feb 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/use-gert-to-scan-all-git-repos-in-a-directory/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;ul&gt;
&lt;li&gt;&lt;a href="https://docs.ropensci.org/gert/"&gt;gert&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;ul&gt;
&lt;li&gt;wrote a function that scans a directory looking for git repositories that may need to be pushed to (or pulled from) github&lt;/li&gt;
&lt;li&gt;this example is based on the &lt;code&gt;git_ahead_behind()&lt;/code&gt; command but it could easily generalise to other kinds of checks&lt;/li&gt;
&lt;/ul&gt;
&lt;h4&gt;
URL or code snippet
&lt;/h4&gt;&lt;ul&gt;
&lt;li&gt;&lt;a href="https://gist.github.com/djnavarro/fb1230ce1bb36d0de729829d819af256"&gt;github gist&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;</description></item><item><title>Behind the magick: updates to imagemagick and beyond</title><link>https://ropensci.org/blog/2021/01/29/magick-26/</link><pubDate>Fri, 29 Jan 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2021/01/29/magick-26/</guid><description>
&lt;p&gt;It has been &lt;a href="https://ropensci.org/technotes/2019/09/27/ropensci-docs/"&gt;a while&lt;/a&gt; since we posted an update about &lt;a href="https://docs.ropensci.org/magick/articles/intro.html"&gt;magick&lt;/a&gt;, but behind the scenes we are constantly tweaking and improving this package, which has become a very mature and complete toolkit for image processing in R.&lt;/p&gt;
&lt;p&gt;Over the past year, we did 6 CRAN releases, containing many small features and fixes, but perhaps more importantly, the package is getting betting better due to updates of the underlying ImageMagick library.&lt;/p&gt;
&lt;p&gt;As mentioned in the &lt;a href="https://cran.r-project.org/web/packages/magick/NEWS"&gt;NEWS&lt;/a&gt;, magick 2.6.0 gains support for &amp;ldquo;raw&amp;rdquo; and &amp;ldquo;heif&amp;rdquo; delegates on Windows and MacOS. The raw delegate is based on &lt;a href="https://www.libraw.org/"&gt;libraw&lt;/a&gt; which allows reading RAW files obtained from digital photo cameras. &lt;a href="https://github.com/strukturag/libheif"&gt;Heif&lt;/a&gt; is a new library that provides a set of formats for high quality (Ultra HD+) images in HEVC and AV1 format. Support for these formats was &lt;a href="https://github.com/ropensci/magick/issues/292"&gt;requested&lt;/a&gt; by users of the R magick package.&lt;/p&gt;</description></item><item><title>Learn All About HTTP Testing: Book Update</title><link>https://ropensci.org/blog/2021/01/26/http-testing-book/</link><pubDate>Tue, 26 Jan 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2021/01/26/http-testing-book/</guid><description>
&lt;p&gt;More and more R packages access resources on the web, and play crucial roles in workflows.
Examples from the &lt;a href="https://ropensci.org/packages/all/"&gt;rOpenSci suite of packages&lt;/a&gt; include &lt;a href="https://docs.ropensci.org/rromeo/"&gt;rromeo&lt;/a&gt;, &lt;a href="https://docs.ropensci.org/GSODR/"&gt;GSODR&lt;/a&gt;, &lt;a href="https://docs.ropensci.org/qualtRics/"&gt;qualtRics&lt;/a&gt;, &lt;a href="https://docs.ropensci.org/rnassqs/"&gt;rnassqs&lt;/a&gt;, and many, many others.
Like for all other packages, appropriate unit testing can make them more robust.
However, unit testing of these packages can bring special challenges: dependence of tests on a good internet connection, testing in the absence of authentication secrets, etc.
Having tests fail due to resources being down or slow, during development or on CRAN, means a time loss for everyone involved (slower development, messages from CRAN).
Although many packages accessing remote resources are well tested, there used to be a lack of resources around best practices&amp;hellip;
But now there is one great information source, our &lt;a href="https://books.ropensci.org/http-testing/"&gt;HTTP testing in R&lt;/a&gt; online book! &amp;#x1f389;&lt;/p&gt;</description></item><item><title>pdftools for extracting complex (e.g. text-wrapped/multiline) tables from pdfs</title><link>https://ropensci.org/usecases/pdftools-for-extracting-complex-e-g-text-wrapped-multiline-tables-from-pdfs/</link><pubDate>Tue, 26 Jan 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/pdftools-for-extracting-complex-e-g-text-wrapped-multiline-tables-from-pdfs/</guid><description>
&lt;p&gt;Extracting a complex table from pdf using pdftools::pdf_data. Example uses a table spread over multiple pages, and containing multiple(text-wrapped) lines per cell, and left and centre justified cell entries.&lt;/p&gt;
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/pdftools"&gt;pdftools&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;Extraction of complex tables from a pdf document, based on data extracted by pdftools::pdf_data(). Example has a table spread over multiple pages, and text wrapping across multiple lines per cell.&lt;/p&gt;</description></item><item><title>Shiny apps to search #rstudioglobal or #rstats tweets with rtweet</title><link>https://ropensci.org/usecases/shiny-apps-to-search-rstudioglobal-or-rstats-tweets-with-rtweet/</link><pubDate>Mon, 25 Jan 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/shiny-apps-to-search-rstudioglobal-or-rstats-tweets-with-rtweet/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/rtweet/"&gt;rtweet&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
Created interactive app and tutorials
&lt;/h4&gt;&lt;p&gt;I created an interactive Shiny apps for people to easily search, sort, filter, and download tweets with the #rstudioglobal or #rstats hashtags. #rstudioglobal was for the RStudio Global 2021 conference; #rstats is for any R tweet tagged with that hashtag.
I also created two tutorials for others who would like to do something similar.&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case*
&lt;/h4&gt;&lt;p&gt;rstats app: &lt;a href="http://apps.machlis.com/shiny/rstats/"&gt;http://apps.machlis.com/shiny/rstats&lt;/a&gt;
rstudioglobal app: &lt;a href="http://apps.machlis.com/shiny/rstudioglobal/"&gt;http://apps.machlis.com/shiny/rstudioglobal/&lt;/a&gt;
Basic rtweet tutorial at InfoWorld: &lt;a href="https://www.infoworld.com/article/3515712/how-to-search-twitter-with-rtweet-and-r.html"&gt;https://www.infoworld.com/article/3515712/how-to-search-twitter-with-rtweet-and-r.html&lt;/a&gt;
Bonus tutorial on turning rtweet data into a Shiny app: &lt;a href="https://www.infoworld.com/article/3516150/create-a-shiny-app-to-search-twitter-with-rtweet-and-r.html"&gt;https://www.infoworld.com/article/3516150/create-a-shiny-app-to-search-twitter-with-rtweet-and-r.html&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Using dittodb to test database queries</title><link>https://ropensci.org/usecases/using-dittodb-to-test-database-queries/</link><pubDate>Mon, 25 Jan 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/using-dittodb-to-test-database-queries/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/dittodb/"&gt;dittodb&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;I have a few functions in an internal package which basically wrap up some database queries. These are tricky to test because my CI system is not allowed to connect directly to the databases. dittodb let&amp;rsquo;s me do two things with these functions:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Test them in an automated way&lt;/li&gt;
&lt;li&gt;Have a record of what the &amp;lsquo;correct&amp;rsquo; database response looked like in case the data source changes down the road&lt;/li&gt;
&lt;/ol&gt;
&lt;h4&gt;
URL or code snippet for your use case*
&lt;/h4&gt;&lt;pre tabindex="0"&gt;&lt;code&gt;getData &amp;lt;- function(date) {
cred &amp;lt;- .getMyCredentials(&amp;#34;mydb&amp;#34;)
con &amp;lt;- DBI::dbConnect(
RPostgreSQL::PostgreSQL(),
user = cred[&amp;#34;user&amp;#34;],
password = cred[&amp;#34;password&amp;#34;],
dbname = cred[&amp;#34;dbname&amp;#34;],
host = cred[&amp;#34;host&amp;#34;],
port = cred[&amp;#34;port&amp;#34;]
)
on.exit(DBI::dbDisconnect(con))
out &amp;lt;- tbl(con, &amp;#34;my_table&amp;#34;) %&amp;gt;%
dplyr::filter(.data$date &amp;gt; local(date))
return(out)
}
dittodb::with_mock_db({
test_that(&amp;#34;getData&amp;#34;, {
results &amp;lt;- getData(&amp;#34;2010-01-01&amp;#34;)
expect_s3_class(results, &amp;#34;data.frame&amp;#34;)
expect_named(results, c(&amp;#34;date&amp;#34;, &amp;#34;value&amp;#34;, &amp;#34;state&amp;#34;))
})
})
&lt;/code&gt;&lt;/pre&gt;</description></item><item><title>Chat with rOpenSci team members at rstudio::global</title><link>https://ropensci.org/events/rstudio-ropensci/</link><pubDate>Fri, 22 Jan 2021 16:00:00 +0000</pubDate><guid>https://ropensci.org/events/rstudio-ropensci/</guid><description>
&lt;p&gt;rOpenSci is proud to be a &lt;a href="https://global.rstudio.com/student/page/40484"&gt;Community Partner&lt;/a&gt; at &lt;a href="https://global.rstudio.com/student/catalog"&gt;rstudio::global 2021&lt;/a&gt; January 21-22, 2021.&lt;/p&gt;
&lt;p&gt;Come chat with members of our team about developing high-quality R-packages for research, best practices in software peer review, the R-universe project, or building community. Ask us anything.&lt;/p&gt;
&lt;p&gt;You can find us in the conference’s &lt;a href="https://spatial.chat/s/rstudio"&gt;Spatial.Chat&lt;/a&gt; Community Partners Room at the rOpenSci table.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Jan 21st 9:20am PST; 12:20pm EST; 6:20pm CET&lt;/li&gt;
&lt;li&gt;Jan 21st 1:20pm PST; 4:20pm EST; 10:20pm CET&lt;/li&gt;
&lt;li&gt;Jan 21st 5:20pm PST; 8:20pm EST; 2:20am CET&lt;/li&gt;
&lt;li&gt;Jan 22nd 1:20am PST; 4:20am EST; 10:20am CET&lt;/li&gt;
&lt;li&gt;Jan 22nd 5:20am PST; 8:20am EST; 2:20pm CET&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Look for some of our community neighbors who will be there too, like &lt;a href="https://metadocencia.netlify.app/"&gt;MetaDocencia&lt;/a&gt;, &lt;a href="https://www.openscapes.org/"&gt;Openscapes&lt;/a&gt;, &lt;a href="https://carpentries.org/blog/2021/01/carpentries-at-rstudio-global/"&gt;The Carpentries&lt;/a&gt;, and others.&lt;/p&gt;</description></item><item><title>Monitoring health and impact of open-source projects</title><link>https://ropensci.org/events/rstudio-jeroen/</link><pubDate>Thu, 21 Jan 2021 23:20:00 +0000</pubDate><guid>https://ropensci.org/events/rstudio-jeroen/</guid><description>
&lt;p&gt;Jeroen Ooms talked about his rOpenSci work at rstudio::global 2021&lt;/p&gt;
&lt;h2&gt;
Abstract
&lt;/h2&gt;&lt;p&gt;At rOpenSci, we have come to realize that in order to help researchers get the most out of R, we need better tooling to monitor the quality, health, and impact of R packages. This applies both to our internal projects, as well as other packages in the R ecosystem. But what exactly makes a good R package?&lt;/p&gt;
&lt;p&gt;In this talk we discuss various aspects of open-source software that are not always immediately obvious, and that you may want to consider when depending on an R package. We identify several categories of indicators you could look for, ranging from the role in the dependency network, to expectations around maintenance and participation.&lt;/p&gt;</description></item><item><title>Getting and plotting weather and climate data</title><link>https://ropensci.org/usecases/getting-and-plotting-weather-and-climate-data/</link><pubDate>Thu, 21 Jan 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/getting-and-plotting-weather-and-climate-data/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/weathercan/"&gt;weathercan&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;I took my undergrad limnology class on a field trip to sample &amp;amp; characterize a local storm water retention pond in Brandon MB. Both weather and climate can provide important context when interpreting results. I used &lt;a href="https://twitter.com/steffilazerte/"&gt;Steffi&amp;rsquo;s&lt;/a&gt; &lt;a href="https://docs.ropensci.org/weathercan/"&gt;weathercan&lt;/a&gt; package to get Environment and Climate Change Canada weather &amp;amp; climate data for &lt;a href="https://twitter.com/CityBrandon/"&gt;Brandon MB&lt;/a&gt;. I plotted up this data a few different ways and as a class we discussed how to best present this data.&lt;/p&gt;</description></item><item><title>Introducing the rOpenSci Community Contributing Guide</title><link>https://ropensci.org/blog/2021/01/20/contributing-guide/</link><pubDate>Wed, 20 Jan 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2021/01/20/contributing-guide/</guid><description>
&lt;p&gt;Many people in our community actively contribute to rOpenSci projects. Many others would like to contribute but aren’t sure how to go about it.
Wanting to get involved in rOpenSci or &amp;ldquo;give back to open source&amp;rdquo; means different things to different people.
Ideally, a person should be able to find a way to contribute that meets their needs and fits our mission.
We created the &lt;a href="https://contributing.ropensci.org/"&gt;rOpenSci Community Contributing Guide&lt;/a&gt;&lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt; to make finding paths to contributing more transparent and sustainable.&lt;/p&gt;</description></item><item><title>Introducing BaseSet for mathematical sets</title><link>https://ropensci.org/blog/2021/01/19/introducing-baseset/</link><pubDate>Tue, 19 Jan 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2021/01/19/introducing-baseset/</guid><description>
&lt;p&gt;In this post I will explain the history behind &lt;a href="https://cran.r-project.org/package=BaseSet" title="BaseSet on CRAN"&gt;BaseSet&lt;/a&gt; then a brief introduction to sets, followed by showing what you can do with &lt;a href="https://docs.ropensci.org/BaseSet/"&gt;BaseSet&lt;/a&gt;.&lt;/p&gt;
&lt;h2&gt;
Brief BaseSet history
&lt;/h2&gt;&lt;p&gt;I study diseases to try to find what causes them at a research institute associated with an hospital.
Thanks to recent technological advances we can analyze many things from a single patient&amp;rsquo;s sample.
Having so much information available can be overwhelming, making it difficult to find the causes of diseases (but it is much better than not having enough information!).&lt;/p&gt;</description></item><item><title>Using ghql to analyze all my 2020 GitHub commits</title><link>https://ropensci.org/usecases/using-ghql-to-analyze-all-my-2020-github-commits/</link><pubDate>Sat, 16 Jan 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/using-ghql-to-analyze-all-my-2020-github-commits/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used
&lt;/h4&gt;&lt;ul&gt;
&lt;li&gt;&lt;a href="https://github.com/ropensci/ghql"&gt;ghql&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;I had a Twitter bot summarize my 2020 contributions on GitHub. I was a bit surprised by the high number of commits that I had made so I decided to have a look into that. I used the &lt;a href="https://docs.github.com/en/graphql"&gt;GitHub GraphQL API&lt;/a&gt; via the ghql package to first pull all the repositories I had contributed to in the past and in a second step get all my commits to those repositories. I then had a look at the &amp;ldquo;smaller commits&amp;rdquo; to check whether &amp;ldquo;~30% of my commits were 1 line diffs&amp;rdquo; which was my main hypothesis for the high number of commits (spoiler: no, only ~12%). I also had a look at the files that I changed in those small commits (using the REST API via gh).
In theory and with some tweaks (mostly adding pagination to the first step), the data collection approach via ghql should be able to give you &lt;em&gt;all&lt;/em&gt; your commits to the default branch over all repositories you have committed to. &amp;#x1f92f;&lt;/p&gt;</description></item><item><title>rOpenSci 2020 Code of Conduct Transparency Report</title><link>https://ropensci.org/blog/2021/01/07/transparency2020/</link><pubDate>Thu, 07 Jan 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2021/01/07/transparency2020/</guid><description>
&lt;p&gt;The rOpenSci community is supported by our &lt;a href="https://ropensci.org/code-of-conduct"&gt;Code of Conduct&lt;/a&gt; with a clear description of unacceptable behaviors, instructions on how to make a report, and information on how reports are handled. We, the Code of Conduct Committee, are responsible for receiving, investigating, deciding, enforcing and reporting on all reports of potential violations of our Code. We are committed to transparency with our community while upholding the privacy of victims and people who report incidents.&lt;/p&gt;</description></item><item><title>rOpenSci Code of Conduct Annual Review</title><link>https://ropensci.org/blog/2021/01/07/conduct2021/</link><pubDate>Thu, 07 Jan 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2021/01/07/conduct2021/</guid><description>
&lt;p&gt;Our community is our best asset. It’s so important to us, it’s in our &lt;a href="https://ropensci.org/about/"&gt;mission statement&lt;/a&gt;. We recognize that communities are not inclusive by default; they require deliberate attention, including an enforceable &lt;a href="https://ropensci.org/code-of-conduct"&gt;Code of Conduct&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;rOpenSci is committed to providing a safe, inclusive, welcoming, and harassment-free experience for everyone. We welcome people of all backgrounds and identities, including but not limited to gender, gender identity and expression, age, sexual orientation, disability, physical appearance, body size, race, ethnicity, religion (or lack thereof), or technology choices. We are anti-racist. We welcome anyone, no matter their technical expertise, career stage, or work sector.&lt;/p&gt;</description></item><item><title>Scraping liked posts on Twitter using rtweet</title><link>https://ropensci.org/usecases/scraping-liked-posts-on-twitter-using-rtweet/</link><pubDate>Sun, 03 Jan 2021 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/scraping-liked-posts-on-twitter-using-rtweet/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/rtweet"&gt;rtweet&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;I used rtweet to recreate a Python tutorial on scraping your liked Tweets on Twitter using R.&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://ivelasq.rbind.io/blog/get-tweet-likes/"&gt;https://ivelasq.rbind.io/blog/get-tweet-likes/&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
Field(s) of application
&lt;/h4&gt;&lt;p&gt;For fun (and being able to more easily scroll through your liked Tweets)&lt;/p&gt;</description></item><item><title>Phonetic Fieldwork and Experiments with the phonfieldwork Package for R</title><link>https://ropensci.org/blog/2020/12/22/phonfieldwork-phonetic-fieldwork-and-experiments/</link><pubDate>Tue, 22 Dec 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2020/12/22/phonfieldwork-phonetic-fieldwork-and-experiments/</guid><description>
&lt;h2&gt;
Science craft
&lt;/h2&gt;&lt;p&gt;As a field linguist, I have spent a lot of time working in villages in the Caucasus, collecting audio from speakers of indigenous languages. The processing of such data involves a lot of time-consuming tasks, so during my field trips I created my own pipeline for data collection. I wrote a number of scripts using different programming languages for automatic renaming, merging, and preannotation of files, making backups, visualizing some data, etc. My method consisted of a combination of solutions developed on the fly to solve specific, independent tasks, without thinking of the future.&lt;/p&gt;</description></item><item><title>2 Months in 2 Minutes - rOpenSci News, December 2020</title><link>https://ropensci.org/blog/2020/12/18/news-dec2020/</link><pubDate>Fri, 18 Dec 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2020/12/18/news-dec2020/</guid><description>
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;p&gt;We&amp;rsquo;re thrilled to &lt;a href="https://ropensci.org/blog/2020/10/27/editors2020/"&gt;announce three new rOpenSci Software Review Editors&lt;/a&gt;: Laura DeCicco, Julia Gustavsen, and Mauro Lepore and we released the fifth version (v0.5) of the &lt;a href="https://ropensci.org/blog/2020/10/22/devguide-0.5.0/"&gt;rOpenSci Developer Guide&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Our Community Call on The Wild World of Data Repositories took place Dec 16 with an audience of 153 people! The &lt;a href="https://ropensci.org/commcalls/dec2020-datarepos/"&gt;video will be posted&lt;/a&gt;, along with collaborative notes and resources, by Dec 21.&lt;/p&gt;
&lt;h2&gt;
Software Peer Review
&lt;/h2&gt;&lt;p&gt;2 community-contributed packages passed &lt;a href="https://ropensci.org/software-review/"&gt;software peer review&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>HTTP Testing With the Newest Release of vcr</title><link>https://ropensci.org/blog/2020/12/18/vcr-release/</link><pubDate>Fri, 18 Dec 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2020/12/18/vcr-release/</guid><description>
&lt;p&gt;A new version of &lt;a href="https://github.com/ropensci/vcr/"&gt;vcr&lt;/a&gt; was just released. See the &lt;a href="https://github.com/ropensci/vcr/releases/tag/v0.6.0"&gt;release notes&lt;/a&gt; for all the details. I want to highlight a few of the more notable changes.&lt;/p&gt;
&lt;h2&gt;
New contributor
&lt;/h2&gt;&lt;p&gt;vcr has a new author: &lt;a href="https://ropensci.org/author/ma%C3%ABlle-salmon/"&gt;Maëlle Salmon&lt;/a&gt;. She has been &lt;a href="https://github.com/ropensci/vcr/graphs/contributors"&gt;contributing to the package quite a lot lately&lt;/a&gt;, including many documentation improvements and big updates to the &lt;a href="https://books.ropensci.org/http-testing/"&gt;HTTP Testing in R&lt;/a&gt; which covers vcr in addition to some other packages.&lt;/p&gt;
&lt;h2&gt;
New serializer
&lt;/h2&gt;&lt;p&gt;vcr now has two serializer options: YAML (which we had before) and JSON (the new one). Serializing here refers to what format the HTTP request and response are put in before being written to a file. If you&amp;rsquo;re a keen observer of these two data formats, you&amp;rsquo;ll know these are not that different, with YAML a superset of JSON. The clear advantage of JSON straight away is that it avoids the common problem with vcr enabled tests on Windows platform where using YAML leads to errors due to something about the &lt;code&gt;yaml&lt;/code&gt; package. The &lt;code&gt;jsonlite&lt;/code&gt; package, which does the heavy lifting when using JSON, does not suffer from the same problems on Windows.&lt;/p&gt;</description></item><item><title>The Wild World of Data Repositories</title><link>https://ropensci.org/commcalls/dec2020-datarepos/</link><pubDate>Wed, 18 Nov 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/commcalls/dec2020-datarepos/</guid><description>
&lt;p&gt;See below for speaker bios and resources including collaborative notes from the call.&lt;/p&gt;
&lt;p&gt;There is no one-size-fits-all protocol for depositing your research data into a public repository in a way that maximizes its reuse and citation. We&amp;rsquo;ve assembled a panel that will help you understand the issues and opportunities for developing new tools and documentation.&lt;/p&gt;
&lt;p&gt;This 1-hour event, moderated by Kara Woo, includes 5 speakers and 20 minutes for Q &amp;amp; A on:&lt;/p&gt;</description></item><item><title>Donate to rOpenSci this Giving Season</title><link>https://ropensci.org/blog/2020/12/16/fundraising/</link><pubDate>Wed, 16 Dec 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2020/12/16/fundraising/</guid><description>
&lt;p&gt;The rOpenSci project is 100% supported by grants and donations. If you&amp;rsquo;re giving this season, please consider &lt;a href="https://numfocus.salsalabs.org/donate-to-ropensci/index.html"&gt;donating to rOpenSci&lt;/a&gt;. Your donations allow us to support internships, contractors, web services, and community events.&lt;/p&gt;
&lt;p&gt;We foster a culture that values open and reproducible research using shared data and reusable software. Our community in collaboration with our staff produce and maintain a vast collection of free open source software to support and accelerate scientific discovery. Hundreds of people have contributed their creativity, curiosity, smarts, and time in the last year. For a glimpse, see &lt;a href="https://ropensci.org/blog/2020/12/15/thankyou-2020/"&gt;Thank You to the rOpenSci Community, 2020&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Thank You to the rOpenSci Community, 2020</title><link>https://ropensci.org/blog/2020/12/15/thankyou-2020/</link><pubDate>Tue, 15 Dec 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2020/12/15/thankyou-2020/</guid><description>
&lt;p&gt;In a year where it has been hard to pay attention to anything not critical to our day-to-day lives, you have continued to share your time, expertise, enthusiasm, and willingness to try things with us. Our &lt;a href="https://ropensci.org/about/#team"&gt;staff&lt;/a&gt; of developers, researchers, and community builders work to create technical and social infrastructure to lower barriers to working with research data, and you, our community, continually help us push farther.&lt;/p&gt;
&lt;p&gt;On behalf of rOpenSci, thank you.&lt;/p&gt;</description></item><item><title>Using av to convert audio files for compatibility with an electronic storyteller</title><link>https://ropensci.org/usecases/using-av-to-convert-audio-files-for-compatibility-with-an-electronic-storyteller/</link><pubDate>Thu, 10 Dec 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/using-av-to-convert-audio-files-for-compatibility-with-an-electronic-storyteller/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/av"&gt;av&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;I converted tracks of stories for compatibility with my kids&amp;rsquo; electronic storyteller with R instead of having to use the manufacturer&amp;rsquo;s online web interface.&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://masalmon.eu/2020/12/10/av-storytime/"&gt;https://masalmon.eu/2020/12/10/av-storytime/&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
Sector
&lt;/h4&gt;&lt;p&gt;other&lt;/p&gt;
&lt;h4&gt;
Field(s) of application
&lt;/h4&gt;&lt;p&gt;little kids wrangling &amp;#x1f601;&lt;/p&gt;</description></item><item><title>Accessing GraphQL from R</title><link>https://ropensci.org/blog/2020/12/08/accessing-graphql-in-r/</link><pubDate>Tue, 08 Dec 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2020/12/08/accessing-graphql-in-r/</guid><description>
&lt;h3&gt;
Introduction
&lt;/h3&gt;&lt;p&gt;Few months ago, I embarked on a full stack spatial data project at work. The project kicked off amazingly, until I was almost backed to the wall when I discovered that some of the data sources were served via a GraphQL API. Before now, I haven&amp;rsquo;t worked with GraphQL. But, I have heard a lot about it and how amazing it is for querying data.&lt;/p&gt;
&lt;p&gt;GraphQL is a query language for application programming interfaces (APIs) that prioritizes giving clients exactly the data they request. It&amp;rsquo;s designed to make APIs flexible, fast and friendly. Basically, it is used to load data from a server to a client and it does this in a much more efficient manner than traditional methods and services.&lt;/p&gt;</description></item><item><title>Selecting the Best Phylogenetic Evolutionary Model</title><link>https://ropensci.org/blog/2020/12/01/mcbette-selecting-the-best-inference-model/</link><pubDate>Tue, 01 Dec 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2020/12/01/mcbette-selecting-the-best-inference-model/</guid><description>
&lt;!--html_preserve--&gt;
&lt;figure&gt;&lt;img src="https://ropensci.org/blog/2020/12/01/mcbette-selecting-the-best-inference-model/mcbette_logo.png"
alt="The mcbette logo" width="400"&gt;
&lt;/figure&gt;
&lt;!--/html_preserve--&gt;
&lt;p&gt;With this blog post, I show how to use the &lt;a href="https://docs.ropensci.org/mcbette/"&gt;mcbette&lt;/a&gt; R package
in an informal way.
A more formal introduction on mcbette
can be found in the Journal of Open Source Science &lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt;.
After introducing a concrete problem, I will show how mcbette
can be used to solve it.&lt;/p&gt;
&lt;p&gt;After discussing mcbette, I will conclude with
why I think rOpenSci is important and how enjoyable
my experiences have been so far.&lt;/p&gt;</description></item><item><title>Handling vegetation-plot information using vegtable and taxlist</title><link>https://ropensci.org/usecases/handling-vegetation-plot-information-using-vegtable-and-taxlist/</link><pubDate>Sat, 21 Nov 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/handling-vegetation-plot-information-using-vegtable-and-taxlist/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/taxlist/"&gt;taxlist&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;Brief explanation about the use of the packages &lt;code&gt;taxlist&lt;/code&gt; and &lt;code&gt;vegtable&lt;/code&gt;, the second embedding the first.
Functions used to produce descriptive statistics and especially to calculate proportions of higher level taxonomic ranks in plot observations and to count taxa are also briefly introduced.&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://kamapu.github.io/posts/2020-11-20-vegtablepress2/"&gt;https://kamapu.github.io/posts/2020-11-20-vegtablepress2/&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
Image
&lt;/h4&gt;&lt;p&gt;&lt;img src="https://ropensci.org/usecases/handling-vegetation-plot-information-using-vegtable-and-taxlist/handling-vegetation-plot-information-using-vegtable-and-taxlist.png" alt="vegtable_diagram|690x290"&gt;&lt;/p&gt;
&lt;h4&gt;
Sector
&lt;/h4&gt;&lt;p&gt;academic&lt;/p&gt;</description></item><item><title>Moving away from Travis CI</title><link>https://ropensci.org/blog/2020/11/19/moving-away-travis/</link><pubDate>Thu, 19 Nov 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2020/11/19/moving-away-travis/</guid><description>
&lt;p&gt;At rOpenSci, we encourage R package developers to take advantage of Continuous Integration services to automatically check the package on different platforms, with different versions of R. The &lt;a href="https://devguide.ropensci.org/ci.html"&gt;rOpenSci dev guide&lt;/a&gt; dedicates chapter 2 to the topic of &lt;em&gt;Continuous Integration Best Practices&lt;/em&gt;, and recommends a few common CI vendors, including &lt;a href="https://travis-ci.com/"&gt;Travis CI&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Travis CI has been a pioneer in free public CI services, and made the concept popular in the open-source community. The service started to get wide adoption in 2012, and &lt;a href="https://github.com/travis-ci/travis-build/commit/c697bb2240cfc1abb92a95f57d2e72c151104431"&gt;native support for R&lt;/a&gt; was added by Craig Citro in 2015, with more contributions from &lt;a href="https://github.com/travis-ci/travis-build/blob/master/lib/travis/build/script/r.rb#L1-L3"&gt;current maintainers&lt;/a&gt; Jim Hester and later Jeroen. In 2016 we wrote a &lt;a href="https://ropensci.org/blog/2016/07/12/travis-osx/"&gt;blog post&lt;/a&gt; about using a build-matrix in order to check your packages on multiple versions of Linux and MacOS, which is super powerful for R package development.&lt;/p&gt;</description></item><item><title>Use stplanr to find and plot major streets of a city</title><link>https://ropensci.org/usecases/use-stplanr-to-find-and-plot-major-streets-of-a-city/</link><pubDate>Wed, 18 Nov 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/use-stplanr-to-find-and-plot-major-streets-of-a-city/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/stplanr"&gt;stplanr&lt;/a&gt; package&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;&lt;em&gt;The life lines of Berlin&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;A fast way to find major streets within a city, without searching for any data on traffic amounts, street types or street width:&lt;/p&gt;
&lt;p&gt;Take random start and end points within the city and run a routing to find routes connecting the start and end points.&lt;/p&gt;
&lt;p&gt;Then aggregate the single street segments on how often they were used. You then get an image of the major city axes.&lt;/p&gt;</description></item><item><title>fulltext: Behind the Scenes</title><link>https://ropensci.org/blog/2020/11/17/fulltext-story/</link><pubDate>Tue, 17 Nov 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2020/11/17/fulltext-story/</guid><description>
&lt;p&gt;&lt;a href="https://github.com/ropensci/fulltext/"&gt;fulltext&lt;/a&gt; is a package I maintain for text-mining the scholarly literature (&lt;a href="https://docs.ropensci.org/fulltext/"&gt;package docs&lt;/a&gt;). You can search for articles, fetch article metadata and abstracts, and fetch full text of some articles. Text-mining the scholarly literature is a research tool used across disciplines. Full text of articles (entire article, not just the abstract) is the gold standard in text-mining in most cases.&lt;/p&gt;
&lt;p&gt;Over the past years the fulltext package has evolved under the hood in its approach to attempting to get full text articles for its users. The following is a walk through of the various iterations that fulltext has gone through for fetching full text of articles. I think it serves as a good demonstration of the complexity and frustration baked into the publishing industry, as well as the trade-offs of various approaches to solving problems and getting things done.&lt;/p&gt;</description></item><item><title>Installing V8 is now even easier</title><link>https://ropensci.org/blog/2020/11/12/installing-v8/</link><pubDate>Thu, 12 Nov 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2020/11/12/installing-v8/</guid><description>
&lt;p&gt;Google&amp;rsquo;s amazing &lt;a href="https://v8.dev/"&gt;V8 JavaScript/WASM engine&lt;/a&gt; is probably one of the most sophisticated open-source software libraries available today. It is used to power the computation in Google Chrome, NodeJS, and also &lt;a href="https://developers.cloudflare.com/workers/learning/how-workers-works"&gt;CloudFlare Workers&lt;/a&gt;, which make it possible to run code for your website inside the CDN edges.&lt;/p&gt;
&lt;p&gt;The R package V8 exposes this same engine in R, and has been on CRAN since 2014. It is used by many R packages to wrap JavaScript libraries, such as &lt;a href="https://docs.ropensci.org/geojsonio/"&gt;geojsonio&lt;/a&gt;, &lt;a href="https://docs.ropensci.org/jsonld/"&gt;jsonld&lt;/a&gt;, &lt;a href="https://github.com/rich-iannone/DiagrammeRsvg"&gt;DiagrammeR&lt;/a&gt;, or &lt;a href="https://davisvaughan.github.io/almanac/"&gt;almanac&lt;/a&gt;. Recently we have seen an increase in usage because the latest version of &lt;a href="https://mc-stan.org/rstan/"&gt;rstan&lt;/a&gt; now uses V8 for their parser.&lt;/p&gt;</description></item><item><title>Navigating open-source software: Ensuring you can rely on what you use</title><link>https://ropensci.org/events/nhsrconf2020/</link><pubDate>Wed, 11 Nov 2020 11:00:00 +0000</pubDate><guid>https://ropensci.org/events/nhsrconf2020/</guid><description>
&lt;p&gt;Dr Rebecca Killick, Associate Professor in the Mathematics &amp;amp; Statistics department at Lancaster University, and member of rOpenSci&amp;rsquo;s Statistical Software Peer Review committee spoke at the &lt;a href="https://nhsrcommunity.com/events/nhs-r-virtual-conference-2020/"&gt;National Health Service R (NHS-R) Community annual meeting&lt;/a&gt;. The audience included everyone from Clinicians to data managers.&lt;/p&gt;</description></item><item><title>Using Open-Access Tools (rentrez, taxize) to Find Coronaviruses, Their Genetic Sequences, and Their Hosts</title><link>https://ropensci.org/blog/2020/11/10/coronaviruses-and-hosts/</link><pubDate>Tue, 10 Nov 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2020/11/10/coronaviruses-and-hosts/</guid><description>
&lt;p&gt;Emerging viruses might be on everyone&amp;rsquo;s mind right now, but as an epidemiologist and disease ecologist I&amp;rsquo;ve always been interested in how and why pathogens move from animal hosts to humans.
The current pandemic of the disease we call COVID-19 is caused by &lt;em&gt;Severe acute respiratory syndrome (SARS) coronavirus 2&lt;/em&gt; (SARS-CoV-2), a virus that has emerged from wildlife like SARS coronavirus and Middle East respiratory syndrome (MERS) coronavirus did previously.
Although these viruses are now widely known, there are many more coronaviruses out there in nature, many of which we know little about.&lt;/p&gt;</description></item><item><title>osmdata, rnaturalearth and magick for #TidyTuesday</title><link>https://ropensci.org/usecases/osmdata-rnaturalearth-and-magick-for-tidytuesday/</link><pubDate>Fri, 06 Nov 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/osmdata-rnaturalearth-and-magick-for-tidytuesday/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/osmdata"&gt;&lt;code&gt;osmdata&lt;/code&gt;&lt;/a&gt;, &lt;a href="https://docs.ropensci.org/rnaturalearth"&gt;&lt;code&gt;rnaturalearth&lt;/code&gt;&lt;/a&gt;, &lt;a href="https://docs.ropensci.org/magick"&gt;&lt;code&gt;magick&lt;/code&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;I used these packages to create my submission for week 44 of #TidyTuesday, Canadian Wind Turbines. TidyTuesday is a weekly social visualization activity/project/challenge originating out of the R4DS and larger R community. &lt;code&gt;rnaturalearth&lt;/code&gt; provided me with an excellent map of Maritime Canada, &lt;code&gt;osmdata&lt;/code&gt; for the main highways (using simple features too!) and &lt;code&gt;magick&lt;/code&gt; for the no-fuss image cropping!&lt;/p&gt;</description></item><item><title>Announcing New Software Peer Review Editors: Laura DeCicco, Julia Gustavsen, Mauro Lepore</title><link>https://ropensci.org/blog/2020/10/27/editors2020/</link><pubDate>Tue, 27 Oct 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2020/10/27/editors2020/</guid><description>
&lt;p&gt;We are pleased to welcome Laura DeCicco, Julia Gustavsen, and Mauro Lepore to our team of &lt;a href="https://ropensci.org/software-review/#editors"&gt;Associate Editors&lt;/a&gt; for rOpenSci &lt;a href="https://ropensci.org/software-review/"&gt;Software Peer Review&lt;/a&gt;.
They join &lt;a href="https://ropensci.org/blog/2019/01/31/more_editors/"&gt;Brooke Anderson&lt;/a&gt;, &lt;a href="https://ropensci.org/blog/2018/06/22/new_editors/"&gt;Anna Krystalli&lt;/a&gt;, &lt;a href="https://ropensci.org/author/karthik-ram/"&gt;Karthik Ram&lt;/a&gt;, &lt;a href="https://ropensci.org/author/noam-ross/"&gt;Noam Ross&lt;/a&gt;, &lt;a href="https://ropensci.org/author/ma%C3%ABlle-salmon/"&gt;Maëlle Salmon&lt;/a&gt;, and &lt;a href="https://ropensci.org/blog/2019/01/31/more_editors/"&gt;Melina Vidoni&lt;/a&gt;.
&lt;a href="https://ropensci.org/blog/2018/06/22/new_editors/"&gt;Lincoln Mullen&lt;/a&gt; and &lt;a href="https://ropensci.org/author/scott-chamberlain/"&gt;Scott Chamberlain&lt;/a&gt; are now board alumni.&lt;/p&gt;
&lt;p&gt;Since 2015, rOpenSci has been running a software peer review system to combine the best of academic peer review with software review.
Having robust and reliable software tools is an important component of supporting open science and reproducible research.
Editors manage the review process, performing initial package checks, identifying reviewers, and moderating the process until the package is accepted by reviewers and transferred to rOpenSci.&lt;/p&gt;</description></item><item><title>osmdata: Rail transport network of the three largest cities in Spain</title><link>https://ropensci.org/usecases/osmdata-rail-transport-network-of-the-three-largest-cities-in-spain/</link><pubDate>Tue, 27 Oct 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/osmdata-rail-transport-network-of-the-three-largest-cities-in-spain/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;em&gt;&lt;a href="https://docs.ropensci.org/osmdata/"&gt;osmdata&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;&lt;em&gt;I combined several functions from the &lt;a href="https://docs.ropensci.org/osmdata/"&gt;osmdata&lt;/a&gt; package to download the vector data for the street grid and rail transport network of the three largest cities in Spain (Madrid, Barcelona and València) and try to produce a nice-looking plot of these cities.&lt;/em&gt;&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case*
&lt;/h4&gt;&lt;p&gt;&lt;em&gt;&lt;a href="https://github.com/GuillemSalazar/r_miscellanea/blob/72a477161e6fd5dfaad9661665cc9f38fa73060e/doc/1_osm.md"&gt;https://github.com/GuillemSalazar/r_miscellanea/blob/72a477161e6fd5dfaad9661665cc9f38fa73060e/doc/1_osm.md&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
&lt;h4&gt;
Image
&lt;/h4&gt;&lt;p&gt;&lt;img src="https://ropensci.org/usecases/osmdata-rail-transport-network-of-the-three-largest-cities-in-spain/osmdata-rail-transport-network-of-the-three-largest-cities-in-spain.jpeg" alt="1_osm|690x345"&gt;&lt;/p&gt;</description></item><item><title>R-Ladies East Lansing Meetup</title><link>https://ropensci.org/events/rladies-east-lansing/</link><pubDate>Thu, 22 Oct 2020 21:00:00 +0000</pubDate><guid>https://ropensci.org/events/rladies-east-lansing/</guid><description>
&lt;p&gt;Stefanie Butland, rOpenSci&amp;rsquo;s Community Manager, will introduce rOpenSci and our new &lt;a href="https://contributing.ropensci.org/"&gt;Contributing Guide&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Brooke Anderson, an &lt;a href="https://ropensci.org/blog/2019/01/31/more_editors/"&gt;rOpenSci Software Peer Review Editor&lt;/a&gt; (and Assistant Professor of Epidemiology and a Faculty Associate in the Department of Statistics at Colorado State University in her day job) will introduce people to our peer review process.&lt;/p&gt;
&lt;p&gt;R-Ladies East Lansing&amp;rsquo;s information on who can attend: &amp;ldquo;We encourage women and minority genders to present/lead most sessions, conversations but we have no restrictions whatsoever when it comes to membership, participation, and discussions. So, please join us and bring your R-family &amp;amp; R-friends!&amp;rdquo; More information on their &lt;a href="https://www.meetup.com/rladies-east-lansing/"&gt;Meetup page&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>rOpenSci Dev Guide 0.5.0: Updates</title><link>https://ropensci.org/blog/2020/10/22/devguide-0.5.0/</link><pubDate>Thu, 22 Oct 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2020/10/22/devguide-0.5.0/</guid><description>
&lt;p&gt;rOpenSci Software Peer Review&amp;rsquo;s guidance has been compiled in &lt;a href="https://devguide.ropensci.org/"&gt;an online book&lt;/a&gt; for more than one year now. We&amp;rsquo;ve just released its fifth version.
To find out what&amp;rsquo;s new in our dev guide 0.5.0, you can &lt;a href="https://devguide.ropensci.org/booknews.html"&gt;read the changelog&lt;/a&gt;,
or this blog post for more digested information.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;We have resumed activity after a break due to the COVID-19 crisis, but are being gentle with deadlines and timing, giving a lot of grace to all people involved. We&amp;rsquo;re all doing our best and rOpenSci is trying to be accommodating with schedules during this challenging year.&lt;/p&gt;</description></item><item><title>Searching medRxiv and bioRxiv Preprint Data</title><link>https://ropensci.org/blog/2020/10/20/searching-medrxivr-and-biorxiv-preprint-data/</link><pubDate>Tue, 20 Oct 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2020/10/20/searching-medrxivr-and-biorxiv-preprint-data/</guid><description>
&lt;h1&gt;
Background &amp;amp; motivation
&lt;/h1&gt;&lt;p&gt;&lt;a href="https://www.medrxiv.org/"&gt;medRxiv&lt;/a&gt;, as the preprint repository for papers in the medical, clinical, and related health sciences,&lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt; has become a central source of new studies related to the COVID-19 pandemic. As a result, more and more researchers have begun to include medRxiv in the list of bibliographic databases they search as part of systematic reviews, a type of study that aims to find and bring together all available evidence on a topic in order to provide a comprehensive answer to a research question.&lt;/p&gt;</description></item><item><title>2 Months in 2 Minutes - rOpenSci News, October 2020</title><link>https://ropensci.org/blog/2020/10/15/news-oct2020/</link><pubDate>Thu, 15 Oct 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2020/10/15/news-oct2020/</guid><description>
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;h4&gt;
rOpenSci at R-Ladies
&lt;/h4&gt;&lt;p&gt;Our community manager Stefanie Butland, and one of our software review editors Brooke Anderson, are speaking remotely at an &lt;a href="https://www.meetup.com/rladies-east-lansing/events/272642612/"&gt;R-Ladies East Lansing meetup&lt;/a&gt; Thursday, October 22nd. They will talk about our how to get involved in rOpenSci using our new &lt;a href="https://contributing.ropensci.org/"&gt;Contributing Guide&lt;/a&gt; as an entry point, and through participating in software review as a package author or reviewer.&lt;/p&gt;
&lt;h4&gt;
Contributing Guide Release
&lt;/h4&gt;&lt;p&gt;The purpose of our new &lt;a href="https://contributing.ropensci.org/"&gt;Contributing Guide&lt;/a&gt; is to welcome you to rOpenSci and help you recognize yourself as a potential contributor. It will help you figure out what you might gain by giving your time, expertise, and experience; match your needs with things that will help rOpenSci’s mission; and connect you with resources to help you along the way.&lt;/p&gt;</description></item><item><title>Covidpreprints.com: Automating Website Updates with the europepmc and rAltmetric Packages</title><link>https://ropensci.org/blog/2020/10/13/covidpreprints/</link><pubDate>Tue, 13 Oct 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2020/10/13/covidpreprints/</guid><description>
&lt;p&gt;At the eLife Sprint in September 2020, we revamped the &lt;a href="https://covidpreprints.com/"&gt;covidpreprints.com&lt;/a&gt; website, which aims at featuring landmark preprints on a timeline of the pandemic.&lt;/p&gt;
&lt;h2&gt;
The birth of the project
&lt;/h2&gt;&lt;p&gt;The ongoing COVID-19 pandemic has led to about 35 million confirmed cases and over a million deaths worldwide. The looming spectre of a second wave of the pandemic has spurred around-the-clock research efforts to better understand the pathology and epidemiology of the virus, in the hope of new therapies and vaccines.
And while novel scientific information about the pandemic was being shared at an unprecedented rate in the form of preprints&lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt;, it was becoming difficult to get an accurate, trustworthy record of this information.&lt;/p&gt;</description></item><item><title>ReproHack en LatinR</title><link>https://ropensci.org/events/latinr-2020/</link><pubDate>Thu, 08 Oct 2020 20:00:00 +0000</pubDate><guid>https://ropensci.org/events/latinr-2020/</guid><description>
&lt;p&gt;Miguel Alvarez (author of rOpenSci peer-reviewed package &lt;a href="https://docs.ropensci.org/taxlist"&gt;taxlist&lt;/a&gt;) and Maëlle Salmon (associate editor) will both record a short talk presenting &lt;a href="https://ropensci.org/software-review"&gt;rOpenSci Software Peer Review&lt;/a&gt; to be shown during &amp;ldquo;ReproHack en LatinR&amp;rdquo;.
Anna Krystalli (associate editor, ReproHack creator) will answer questions.&lt;/p&gt;</description></item><item><title>Hacktober? Any Month is a Good Month to Contribute to rOpenSci</title><link>https://ropensci.org/blog/2020/10/06/hacktober2020/</link><pubDate>Tue, 06 Oct 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2020/10/06/hacktober2020/</guid><description>
&lt;p&gt;The title of this post refers to Hacktoberfest, a month-long event organized annually by Digital Ocean to encourage contributions to open source projects on GitHub.
Unfortunately, this October, many maintainers are dealing with &lt;a href="https://blog.domenic.me/hacktoberfest/"&gt;spam pull requests&lt;/a&gt;.
So instead of issuing a general appeal to participate, we&amp;rsquo;re pointing you to our new &lt;a href="https://contributing.ropensci.org/"&gt;Community Contributing Guide&lt;/a&gt;&amp;rsquo;s section dedicated to our open &lt;a href="https://contributing.ropensci.org/resources.html#issues"&gt;Issues List&lt;/a&gt;.
Along with showing you how to find help wanted issues in rOpenSci packages, it provides suggestions on etiquette to maximize the chances that your effort will be appreciated by a maintainer.&lt;/p&gt;</description></item><item><title>Rectifying Hand-Drawn Marks on Maps With the mapscanner Package</title><link>https://ropensci.org/blog/2020/09/29/mapscanner/</link><pubDate>Tue, 29 Sep 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2020/09/29/mapscanner/</guid><description>
&lt;h2&gt;
mapscanner
&lt;/h2&gt;&lt;p&gt;It is sometimes easy in the midst of the cutting-edge world of unique
software development that is rOpenSci to forget that even though our
software might be freely available from anywhere in the world, access to
adequate hardware is often restricted. Restricted access to hardware is
rarely acknowledged as a reason for differing outcomes from the practice
of science in different parts of the world, yet being in a part of the
world that is relatively less financially advantaged must translate to
being relatively less able to take advantage of the abilities of
computer hardware.&lt;/p&gt;</description></item><item><title>A Twitter bot with rtweet, Mapbox and GitHub Actions</title><link>https://ropensci.org/usecases/a-twitter-bot-with-rtweet-mapbox-and-github-actions/</link><pubDate>Fri, 25 Sep 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/a-twitter-bot-with-rtweet-mapbox-and-github-actions/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/rtweet/"&gt;rtweet&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;I set up &lt;a href="https://github.com/features/actions"&gt;a GitHub Action&lt;/a&gt; that includes R code that generates random coordinates in greater London, queries &lt;a href="https://docs.mapbox.com/api/"&gt;the Mapbox API&lt;/a&gt; for a satellite image and uses &lt;a href="https://developer.twitter.com/en/docs"&gt;the Twitter API&lt;/a&gt; via &lt;a href="https://docs.ropensci.org/rtweet/"&gt;{rtweet}&lt;/a&gt; to post the image to the &lt;a href="https://twitter.com/londonmapbot"&gt;@londonmapbot&lt;/a&gt; Twitter account.&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case*
&lt;/h4&gt;&lt;ul&gt;
&lt;li&gt;&lt;a href="https://twitter.com/londonmapbot"&gt;@londonmapbot Twitter account&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.rostrum.blog/2020/09/21/londonmapbot/"&gt;blog post&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/matt-dray/londonmapbot"&gt;source code on GitHub&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h4&gt;
Image
&lt;/h4&gt;&lt;p&gt;&lt;img src="https://ropensci.org/usecases/a-twitter-bot-with-rtweet-mapbox-and-github-actions/a-twitter-bot-with-rtweet-mapbox-and-github-actions.jpeg" alt="wimbledon|690x459, 75%"&gt;&lt;/p&gt;</description></item><item><title>The treedata.table Package</title><link>https://ropensci.org/blog/2020/09/22/treedata.table/</link><pubDate>Tue, 22 Sep 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2020/09/22/treedata.table/</guid><description>
&lt;p&gt;The &lt;a href="http://r-datatable.com/"&gt;data.table&lt;/a&gt; package enables high-performance extended functionality for data tables in R. &lt;a href="https://ropensci.github.io/treedata.table/"&gt;treedata.table&lt;/a&gt; is a wrapper
for data.table for phylogenetic analyses that matches a phylogeny to the data.table, and preserves matching during data.table operations.
Using the data.table package greatly increases analysis reproducibility and the efficiency of data manipulation operations over other ways of performing similar tasks in
base R, enabling processing of larger trees and datasets.&lt;/p&gt;
&lt;h3&gt;
Why use treedata.table?
&lt;/h3&gt;&lt;p&gt;Simultaneous processing of phylogenetic trees and data remains a computationally-intensive task.
For example, processing a tree alongside a dataset of phylogenetic characters means processing much more data compared to processing the characters alone. This results in much longer processing times compared to more simple analysis with characters alone in data.table (Fig. 1A).
treedata.table provides new tools for increasing the speed and efficiency of phylogenetic data processing.
Data manipulation in treedata.table is significantly faster than in other commonly used packages such as base (&amp;gt;35%), treeplyr (&amp;gt;60%), and dplyr (&amp;gt;90%).
Additionally, treedata.table is &amp;gt;400% faster than treeplyr during the initial data/tree matching step (Fig. 1B).&lt;/p&gt;</description></item><item><title>Kontarion - a stack extending rocker/ml-verse for Bibliometric analytics</title><link>https://ropensci.org/usecases/kontarion-a-stack-extending-rocker-ml-verse-for-bibliometric-analytics/</link><pubDate>Tue, 15 Sep 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/kontarion-a-stack-extending-rocker-ml-verse-for-bibliometric-analytics/</guid><description>
&lt;p&gt;The larger use case for Kontarion is to support developing and deploying Bibliometric analytics within the KTH Royal Institute of Technology Library - a container-based platform that can be used on-prem or in the cloud.&lt;/p&gt;
&lt;h4&gt;
rOpenSci package or resource used
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/oai"&gt;oai&lt;/a&gt;, &lt;a href="https://docs.ropensci.org/rentrez"&gt;rentrez&lt;/a&gt;, &lt;a href="https://github.com/ropensci-archive/fulltext"&gt;fulltext&lt;/a&gt;, &lt;a href="https://docs.ropensci.org/europepmc"&gt;europepmc&lt;/a&gt;, &lt;a href="https://docs.ropensci.org/refsplitr"&gt;refsplitr&lt;/a&gt;, &lt;a href="https://docs.ropensci.org/rcrossref"&gt;rcrossref&lt;/a&gt;, &lt;a href="https://docs.ropensci.org/citecorp"&gt;citecorp&lt;/a&gt;, &lt;a href="https://docs.ropensci.org/roadoi"&gt;roadoi&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;Assembled a stack extending the versioned rocker-project.org docker image for ml-verse with various ROpenSci (and other) packages, to provide a containerized platform supporting Bibliometric analysis workflows.&lt;/p&gt;</description></item><item><title>Mapping scientific collaboration about the Anthropoce with refsplitr</title><link>https://ropensci.org/usecases/mapping-scientific-collaboration-about-the-anthropoce-with-refsplitr/</link><pubDate>Tue, 15 Sep 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/mapping-scientific-collaboration-about-the-anthropoce-with-refsplitr/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;Package &lt;a href="https://github.com/ropensci/refsplitr"&gt;refsplitr&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;The authors studied the location and patterns of collaboration of authors publishing research on the Anthropocene.&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://conbio.onlinelibrary.wiley.com/doi/10.1111/csp2.270"&gt;https://conbio.onlinelibrary.wiley.com/doi/10.1111/csp2.270&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
Image
&lt;/h4&gt;&lt;p&gt;&lt;img src="https://ropensci.org/usecases/mapping-scientific-collaboration-about-the-anthropoce-with-refsplitr/mapping-scientific-collaboration-about-the-anthropoce-with-refsplitr.jpeg" alt="image|460x500"&gt;&lt;/p&gt;
&lt;h4&gt;
Sector
&lt;/h4&gt;&lt;p&gt;academic&lt;/p&gt;
&lt;h4&gt;
Field(s) of application
&lt;/h4&gt;&lt;p&gt;academic publishing, conservation biology, text analysis, scientometrics, bibliometrics, science of science&lt;/p&gt;</description></item><item><title>Processing Web of Science records with refsplitr to study author gender and geography</title><link>https://ropensci.org/usecases/processing-web-of-science-records-with-refsplitr-to-study-author-gender-and-geography/</link><pubDate>Tue, 15 Sep 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/processing-web-of-science-records-with-refsplitr-to-study-author-gender-and-geography/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;Package &lt;a href="https://github.com/ropensci/refsplitr"&gt;refsplitr&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;The authors examined how author location, author gender ratios, and publication rates in myrmecology changed over three decades.&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://myrmecologicalnews.org/cms/index.php?option=com_content&amp;amp;view=category&amp;amp;id=1568&amp;amp;Itemid=435"&gt;https://myrmecologicalnews.org/cms/index.php?option=com_content&amp;amp;view=category&amp;amp;id=1568&amp;amp;Itemid=435&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
Image
&lt;/h4&gt;&lt;p&gt;&lt;img src="https://ropensci.org/usecases/processing-web-of-science-records-with-refsplitr-to-study-author-gender-and-geography/processing-web-of-science-records-with-refsplitr-to-study-author-gender-and-geography.png" alt="image|690x431"&gt;&lt;/p&gt;
&lt;h4&gt;
Sector
&lt;/h4&gt;&lt;p&gt;academic&lt;/p&gt;
&lt;h4&gt;
Field(s) of application
&lt;/h4&gt;&lt;p&gt;academic publishing, myrmecology,gender diversity, scientometrics, bibliometrics, science of science&lt;/p&gt;</description></item><item><title>covidpreprints.com using europepmc and rAltmetric</title><link>https://ropensci.org/usecases/covidpreprints-com-using-europepmc-and-raltmetric/</link><pubDate>Tue, 08 Sep 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/covidpreprints-com-using-europepmc-and-raltmetric/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://github.com/ropensci/europepmc"&gt;europepmc&lt;/a&gt;, &lt;a href="https://github.com/ropensci/rAltmetric"&gt;rAltmetric&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;&lt;code&gt;covidpreprints.com&lt;/code&gt; is a one-stop portal for the lay public and scientific community. We created &lt;code&gt;covidpreprints.com&lt;/code&gt; to promote scientific education and combat misinformation by discussing controversial scientific issues. We focus on the trend of open access in science, especially in the form of preprints, and we see it as a way to shape the growth of these trends within the scientific community.&lt;/p&gt;</description></item><item><title>Scientific Name Parsing: rgnparser and namext</title><link>https://ropensci.org/blog/2020/08/25/scientific-name-parsing/</link><pubDate>Tue, 25 Aug 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2020/08/25/scientific-name-parsing/</guid><description>
&lt;p&gt;I&amp;rsquo;m starting to tackle a few hard packages (&lt;a href="https://github.com/ropenscilabs/spplit"&gt;spplit&lt;/a&gt; and &lt;a href="https://github.com/ropenscilabs/spenv"&gt;spenv&lt;/a&gt;) having to do with integrating disparate data sources. I&amp;rsquo;ll talk here about spplit. I haven&amp;rsquo;t worked on spplit in a few years; I thought I&amp;rsquo;d make another attempt with &amp;ldquo;fresh&amp;rdquo; eyes.&lt;/p&gt;
&lt;p&gt;There are many use cases I can imagine for spplit; I&amp;rsquo;ll highlight a few. First, one may want to find literature that mentions particular scientific names (find all the journal articles that include the name &lt;em&gt;Ursus americanus&lt;/em&gt; (&lt;a href="https://www.ncbi.nlm.nih.gov/Taxonomy/Browser/wwwtax.cgi?mode=Info&amp;amp;id=9643"&gt;American black bear&lt;/a&gt;)). Second, one could extract scientific names from scientific literature to examine the different formats of scientific names used in different journals (e.g., &lt;a href="https://www.ncbi.nlm.nih.gov/Taxonomy/Browser/wwwtax.cgi?mode=Info&amp;amp;id=9606"&gt;&lt;em&gt;Homo sapiens&lt;/em&gt;&lt;/a&gt; vs. &lt;em&gt;Homo sapiens Linnaeus&lt;/em&gt; vs. &lt;em&gt;Homo sapiens Linnaeus, 1758&lt;/em&gt;). Last, you could extract the scientific names from your own manuscript before submission to check that all scientific names are properly formatted and match your preferred taxonomic reference.&lt;/p&gt;</description></item><item><title>Bar chart portraits with magick</title><link>https://ropensci.org/usecases/bar-chart-portraits-with-magick/</link><pubDate>Sun, 23 Aug 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/bar-chart-portraits-with-magick/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/magick"&gt;magick&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;I used magick to resize and convert an image to grayscale, and then to get the pixel values that represent their brightness. The values were used to make horizontal bars at the position of each pixel, with the width of the bar corresponding to reverse brightness (longer bars = brighter pixels).&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case*
&lt;/h4&gt;&lt;p&gt;Code: &lt;a href="https://github.com/gkaramanis/aRt/tree/master/split-bar"&gt;https://github.com/gkaramanis/aRt/tree/master/split-bar&lt;/a&gt;&lt;/p&gt;</description></item><item><title>2 Months in 2 Minutes - rOpenSci News, August 2020</title><link>https://ropensci.org/blog/2020/08/20/news-aug2020/</link><pubDate>Thu, 20 Aug 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2020/08/20/news-aug2020/</guid><description>
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;p&gt;Join our Community Manager &lt;a href="https://ropensci.org/author/stefanie-butland/"&gt;Stefanie Butland&lt;/a&gt; in a &lt;a href="https://2020.carpentrycon.org/schedule/#session-62"&gt;CarpentryCon @ Home fireside chat on Growing Inclusive, Computational Communities and Leaders&lt;/a&gt;. Live 90-min discussions Wed Aug 26 21h00 (2pm PDT) and Thu Aug 27 15h00 UTC (8am PDT). Other panelists over the two sessions are Abigail Cabunoc Mayes (Mozilla Foundation), Kate Hertweck (Fred Hutch Cancer Research Center), Toby Hodges (The Carpentries), Angela Li (U Chicago), Marlene Mhangami (Python Software Foundation), Naomi Penfold (eLife), and Serah Rono (The Carpentries). &lt;a href="https://docs.google.com/forms/d/e/1FAIpQLSc5bHp5nYG8XV1-WNQqZ_sm6h0T4G8Kp6M9biqbyRW1GrXNoA/viewform"&gt;Submit&lt;/a&gt; your questions for the panel before Aug 24.&lt;/p&gt;</description></item><item><title>Developing dittodb</title><link>https://ropensci.org/blog/2020/08/18/dev-dittodb/</link><pubDate>Tue, 18 Aug 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2020/08/18/dev-dittodb/</guid><description>
&lt;p&gt;This post describes a few different aspects behind the scenes of the development of &lt;a href="https://dittodb.jonkeane.com"&gt;dittodb&lt;/a&gt; which &lt;a href="https://github.com/ropensci/software-review/issues/366"&gt;recently went through&lt;/a&gt; the &lt;a href="https://ropensci.org/software-review/"&gt;rOpenSci peer review process&lt;/a&gt; and was &lt;a href="https://jonkeane.com/blog/introducing_dittodb/"&gt;released to CRAN on 24 July 2020&lt;/a&gt;.
This isn&amp;rsquo;t an introduction to the package itself (that&amp;rsquo;s &lt;a href="https://dittodb.jonkeane.com"&gt;available on dittodb&amp;rsquo;s site&lt;/a&gt;), but rather a look behind the scenes of the conceiving of the idea, the inspiration for, some of the development of, and history behind dittodb.&lt;/p&gt;
&lt;h2&gt;
The idea
&lt;/h2&gt;&lt;p&gt;The idea for dittodb came as a very practical one: at my day job I was working on an R package that interacted with our databases.
Though we could test a lot of things, we were struggling with writing good tests for our database interactions.
We could technically connect to the actual production database, but that meant that the tests were slow and depended on data that was sometimes changing&lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt;.
Worst of all: it would mean having to store our database credentials in our &lt;a href="https://en.wikipedia.org/wiki/Continuous_integration"&gt;Continuous Integration&lt;/a&gt; infrastructure.&lt;/p&gt;</description></item><item><title>Basic manipulation of GIF frames with magick</title><link>https://ropensci.org/usecases/basic-manipulation-of-gif-frames-with-magick/</link><pubDate>Thu, 13 Aug 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/basic-manipulation-of-gif-frames-with-magick/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://github.com/ropensci/magick"&gt;magick&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;I demonstrate how you can use the &lt;code&gt;magick&lt;/code&gt; package to do some basic manipulation of GIFs, such as playing it backwards, slowing some frame downs, and splicing in other frames.&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://statisticaloddsandends.wordpress.com/2020/08/06/basic-manipulation-of-gif-frames-with-magick/"&gt;Post on my blog&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
Image
&lt;/h4&gt;&lt;p&gt;&lt;img src="https://statisticaloddsandends.files.wordpress.com/2020/08/lebron4.gif?w=480&amp;amp;zoom=2" alt="nba gif"&gt;&lt;/p&gt;
&lt;h4&gt;
Sector
&lt;/h4&gt;&lt;p&gt;&lt;em&gt;List one of: academic / industry / government / non-profit / other&lt;/em&gt;&lt;/p&gt;</description></item><item><title>OSF: A Project Management Service Built for Research</title><link>https://ropensci.org/blog/2020/08/04/osf/</link><pubDate>Tue, 04 Aug 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2020/08/04/osf/</guid><description>
&lt;p&gt;&lt;a href="https://github.com/ropensci/osfr"&gt;osfr&lt;/a&gt; provides a (&lt;em&gt;hopefully&lt;/em&gt;) convenient R interface to &lt;a href="https://osf.io"&gt;OSF&lt;/a&gt; (Open Science Framework, &lt;a href="https://www.osf.io"&gt;https://www.osf.io&lt;/a&gt;), a free service for managing research developed by the &lt;a href="https://www.cos.io"&gt;Center for Open Science&lt;/a&gt; (COS).&lt;/p&gt;
&lt;p&gt;osfr completed its rOpenSci peer-review earlier this year and has been &lt;a href="https://cran.r-project.org/package=osfr"&gt;available on CRAN&lt;/a&gt; since February. Throughout its development and since its release I&amp;rsquo;ve had numerous conversations with members of the R community about OSF (and osfr), and through these interactions a couple recurring patterns emerged. First, it seems that many R users have heard of OSF but relatively few have first-hand experience with it. Second, I&amp;rsquo;m often asked how OSF compares to GitHub and whether it would even be useful for someone who already uses GitHub to manage their research.&lt;/p&gt;</description></item><item><title>Spanish and English blogs on how to use rtweet and magick</title><link>https://ropensci.org/usecases/spanish-and-english-blogs-on-how-to-use-rtweet-and-magick/</link><pubDate>Sat, 01 Aug 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/spanish-and-english-blogs-on-how-to-use-rtweet-and-magick/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://github.com/ropensci/rtweet"&gt;rtweet&lt;/a&gt;, &lt;a href="https://github.com/ropensci/magick"&gt;magick&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;I like to use &lt;code&gt;rtweet&lt;/code&gt; when I&amp;rsquo;m at conferences to look for impactful tweets and tweeters to follow or mute. I also enjoy using &lt;code&gt;magick&lt;/code&gt; to add images to figures.&lt;/p&gt;
&lt;p&gt;After a conference, I happened to sit next to two conference attendee and I showed them my R code and my analysis. They encouraged me to write a blog post about how to use this tool, so I wrote this &lt;a href="https://www.raynamharris.com/blog/sacnas_rtweet/"&gt;blog post in English&lt;/a&gt;. Then I translated the human-readable parts of the code and published the &lt;a href="https://www.raynamharris.com/blog/sacnas_rtweet_es/"&gt;blog in Spanish&lt;/a&gt;. I shared both blogs &lt;a href="https://twitter.com/raynamharris/status/1192510904828432384"&gt;on Twitter&lt;/a&gt; and they were well received.&lt;/p&gt;</description></item><item><title>Creating a self-updating GitHub README using rtweet and GitHub Actions</title><link>https://ropensci.org/usecases/creating-a-self-updating-github-readme-using-rtweet-and-github-actions/</link><pubDate>Tue, 21 Jul 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/creating-a-self-updating-github-readme-using-rtweet-and-github-actions/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://github.com/ropensci/rtweet"&gt;rtweet&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;After GitHub allows users to host their own README file on the profile page, people started to share many awesome README examples. Inspired by this &lt;a href="https://twitter.com/simonw/status/1281435464474324993"&gt;tweet&lt;/a&gt; where Simon William used it to share his updates from blogs and commits, I created a README updating my latest tweet instead of having a static one by doing the following actions:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Use rtweet to get my latest tweet.&lt;/li&gt;
&lt;li&gt;Use tweetrmd and webshot2 to turn the tweet into a screenshot.
The entire process is deployed on GitHub using GitHub Actions &lt;a href="https://github.com/malcolmbarrett/epibot"&gt;templates&lt;/a&gt; from my friend Malcolm Barrett.&lt;/li&gt;
&lt;/ol&gt;
&lt;h4&gt;
URL or code snippet for your use case*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://github.com/zhiiiyang/zhiiiyang/blob/af2921e2fe01cd59cab9138907f8da37ceabcb1d/script.R"&gt;https://github.com/zhiiiyang/zhiiiyang/blob/af2921e2fe01cd59cab9138907f8da37ceabcb1d/script.R&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Extraindo tabelas de documentos pdf em R com Tabulizer</title><link>https://ropensci.org/usecases/extraindo-tabelas-de-documentos-pdf-em-r-com-tabulizer/</link><pubDate>Mon, 20 Jul 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/extraindo-tabelas-de-documentos-pdf-em-r-com-tabulizer/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/tabulizer/"&gt;Tabulizer&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;Estava procurando dados sobre operações de Garantia da Lei e da Ordem (GLOs) no Brasil para o artigo final de uma disciplina do doutorado. Infelizmente não há muita informação disponível em série histórica, apesar do Ministério da Defesa ter contabilizado alguns dados das operações realizadas desde 1992. Eles estão disponíveis &lt;a href="https://www.gov.br/defesa/pt-br/assuntos/exercicios-e-operacoes/garantia-da-lei-e-da-ordem"&gt;aqui&lt;/a&gt;, assim com a metodologia usada para coleta-los. Maravilha, mas temos um problema: os dados não estão em planilhas prontas para gente usar, mas em pdf. Em dois pdfs, no caso. Um primeiro contendo variáveis como &lt;em&gt;data&lt;/em&gt; , &lt;em&gt;nome&lt;/em&gt; , &lt;em&gt;local&lt;/em&gt; , &lt;em&gt;missão&lt;/em&gt; e &lt;em&gt;tipo&lt;/em&gt; da operação, e um segundo contendo o seu &lt;em&gt;custo&lt;/em&gt; e o &lt;em&gt;efetivo&lt;/em&gt; empregado. Resolvi então escrever um post mostrando um pouco o processo de extração e transformação inicial dos dados.&lt;/p&gt;</description></item><item><title>CRAN Checks API News: Documentation, Notifications, and More</title><link>https://ropensci.org/blog/2020/07/16/cran-checks-docs-notifications/</link><pubDate>Thu, 16 Jul 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2020/07/16/cran-checks-docs-notifications/</guid><description>
&lt;p&gt;In October last year &lt;a href="https://ropensci.org/technotes/2019/10/09/cran-checks-api-update/"&gt;we wrote&lt;/a&gt; about the CRAN Checks API (&lt;a href="https://cranchecks.info"&gt;https://cranchecks.info&lt;/a&gt;). Since then there have been four new major items introduced: documentation, notifications, search, and a new version of the cchecks R package. First, an introduction to the API for those not familiar.&lt;/p&gt;
&lt;h2&gt;
CRAN Checks API
&lt;/h2&gt;&lt;p&gt;The CRANS checks API was born because whilst being crucial to a package&amp;rsquo;s fate on CRAN, CRAN checks results were not available in a machine readable format, contrary to checks from continuous integration services.
Indeed, CRAN checks results are only distributed as HTML pages.
Therefore CRAN checks API&amp;rsquo;s goal is to provide data from CRAN checks in a format that&amp;rsquo;s easier to work with from code.&lt;/p&gt;</description></item><item><title>Community Captioning of rOpenSci Community Calls</title><link>https://ropensci.org/blog/2020/07/15/subtitles/</link><pubDate>Wed, 15 Jul 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2020/07/15/subtitles/</guid><description>
&lt;p&gt;Webinars and community calls are a great way to gather many people to discuss a specific topic, without the logistic hurdles of in-person events. But whether online or in-person, to reach the broadest audience, all events should work towards greater accessibility. In particular, it is difficult for people who are deaf or hard of hearing to follow the conversation because of low quality video hindering lip reading, or for non-native speakers because of low quality sound.&lt;/p&gt;</description></item><item><title>Maintaining an R Package - Community Call Summary</title><link>https://ropensci.org/blog/2020/07/14/commcall-maintaining-pkg/</link><pubDate>Tue, 14 Jul 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2020/07/14/commcall-maintaining-pkg/</guid><description>
&lt;p&gt;In March we held a &lt;a href="https://ropensci.org/commcalls/2020-03-18/"&gt;Community Call&lt;/a&gt; discussing the maintenance of R packages.
This call included a &lt;a href="https://speakerdeck.com/juliasilge/maintaining-an-r-package"&gt;starting presentation&lt;/a&gt; by &lt;a href="https://ropensci.org/author/julia-silge/"&gt;Julia Silge&lt;/a&gt; followed by a discussion featuring panelists with a wide &lt;a href="https://ropensci.org/blog/2020/03/04/commcall-mar2020/#speakers"&gt;variety of backgrounds&lt;/a&gt;: &lt;a href="https://ropensci.org/author/elin-waring"&gt;Elin Waring&lt;/a&gt;, &lt;a href="https://ropensci.org/author/erin-grand"&gt;Erin Grand&lt;/a&gt;, &lt;a href="https://ropensci.org/author/leonardo-collado-torres"&gt;Leonardo Collado-Torres&lt;/a&gt; and &lt;a href="https://ropensci.org/author/scott-chamberlain"&gt;Scott Chamberlain&lt;/a&gt;.&lt;/p&gt;
&lt;figure class="center"&gt;&lt;img src="https://ropensci.org/blog/2020/07/14/commcall-maintaining-pkg/speakers.png"
alt="Headshots of the moderator and four panelists" width="800"&gt;
&lt;/figure&gt;
&lt;p&gt;The rOpenSci Package Maintenance Community Call was my (Janani&amp;rsquo;s) first Community Call and I loved it.
For R/software-dev newbies, learning the right terminology/lingo/vocabulary is everything.
It can take a few dozen blog posts and many hours of reading before beginners get to the &amp;lsquo;aha&amp;rsquo; moment of &amp;lsquo;oh, these are the terms I need to use to search for what I&amp;rsquo;m thinking!&amp;rsquo;.
As there are many online resources out there, the default expectation is that one can search for and learn almost everything provided one knows the right keywords.
There&amp;rsquo;s nothing like hearing a lively technical banter of experts to pick up the vernacular that one can easily build upon.
The first-hand tips and tricks, do&amp;rsquo;s and don&amp;rsquo;ts, personal anecdotes of what worked beautifully and what crashed terribly, offered by years of experience are yet unmatched in bringing newbies into speaking the community&amp;rsquo;s language.
That is the precise gap filled in by the timely and helpful rOpenSci Package Maintenance Community Call!&lt;/p&gt;</description></item><item><title>rOpenSci Ozunconf19</title><link>https://ropensci.org/events/2019-12-11-ozunconf19/</link><pubDate>Fri, 10 Jul 2020 17:00:00 +0000</pubDate><guid>https://ropensci.org/events/2019-12-11-ozunconf19/</guid><description>
&lt;p&gt;Watch &lt;a href="https://ozunconf19.ropensci.org/"&gt;https://ozunconf19.ropensci.org/&lt;/a&gt; for updates&lt;/p&gt;</description></item><item><title>useR! 2020</title><link>https://ropensci.org/events/2020-07-09-user/</link><pubDate>Thu, 09 Jul 2020 20:00:00 +0000</pubDate><guid>https://ropensci.org/events/2020-07-09-user/</guid><description>
&lt;p&gt;Two members of our team will give talks at &lt;a href="https://user2020.r-project.org/"&gt;useR! 2020&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>A better way to manage your Github personal access tokens</title><link>https://ropensci.org/blog/2020/07/07/github-pat/</link><pubDate>Tue, 07 Jul 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2020/07/07/github-pat/</guid><description>
&lt;p&gt;We have been working hard behind the scenes on the upcoming release of our new git package named &lt;a href="https://docs.ropensci.org/gert"&gt;gert&lt;/a&gt;, a joint effort from rOpenSci and the Tidyverse team. One of the main features of gert is the out-of-the-box authentication mechanism, which is provided via the new &lt;a href="https://docs.ropensci.org/credentials/articles/intro.html"&gt;credentials&lt;/a&gt; package.&lt;/p&gt;
&lt;p&gt;Among other things, the credentials package makes it possible to save and load https authentication details from the &lt;a href="https://git-scm.com/docs/gitcredentials"&gt;git credential store&lt;/a&gt;, which is part of the official command-line git. Thereby credentials are automatically shared between command line git and the gert package, while safely stored by your operating system&amp;rsquo;s preferred password manager.&lt;/p&gt;</description></item><item><title>Filtering pdfs using RegEx in their body</title><link>https://ropensci.org/usecases/filtering-pdfs-using-regex-in-their-body/</link><pubDate>Thu, 25 Jun 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/filtering-pdfs-using-regex-in-their-body/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/pdftools/"&gt;pdftools&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;I used pdftools to scan a large number of pdfs from a folder, and then stringr::str_which() to search the body of each pdf for any RegEx expression you want. Pdfs with matching RegEx expressions are saved in a new folder of your choosing.&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case*
&lt;/h4&gt;&lt;p&gt;pdf_selector&amp;lt;-function(file_folder,new_folder,search_pattern){
library(pdftools)
library(tidyverse)
setwd(file_folder)
dir.create(new_folder)
filenames&amp;lt;-list.files(file_folder,pattern=&amp;quot;*.pdf&amp;quot;,full.names=TRUE)
pdfs&amp;lt;-lapply(filenames,pdf_text)%&amp;gt;%
lapply(paste,sep=&amp;quot; &amp;ldquo;,collapse=&amp;rdquo; &amp;ldquo;)
l&amp;lt;-lapply(pdfs,str_which,pattern=search_pattern)%&amp;gt;%
as.logical()%&amp;gt;%
replace_na(FALSE)
sapply(filenames[l],file.copy,to=new_folder)
}&lt;/p&gt;</description></item><item><title>Using qualtRics to study the effect of COVID-19 on scientists</title><link>https://ropensci.org/usecases/using-qualtrics-to-study-the-effect-of-covid-19-on-scientists/</link><pubDate>Sun, 21 Jun 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/using-qualtrics-to-study-the-effect-of-covid-19-on-scientists/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://github.com/ropensci/qualtRics"&gt;qualtRics&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Used in the workflow for analyzing a survey about how scientists have been affected by the COVID-19 pandemic&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;This also inspired a blog post with some tips for working with data collected through Qualtrics&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h4&gt;
URL or code snippet for your use case*
&lt;/h4&gt;&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href="https://arxiv.org/abs/2005.11358"&gt;Quantifying the Immediate Effects of the COVID-19 Pandemic on Scientists&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href="https://wytham.rbind.io/post/qualtrics-workflow/"&gt;Blog post on Qualtrics workflow&lt;/a&gt;&lt;/p&gt;</description></item><item><title>2 Months in 2 Minutes - rOpenSci News, June 2020</title><link>https://ropensci.org/blog/2020/06/18/news-jun2020/</link><pubDate>Thu, 18 Jun 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2020/06/18/news-jun2020/</guid><description>
&lt;h2&gt;
rOpenSci HQ
&lt;/h2&gt;&lt;p&gt;The rOpenSci team, together with ten expert community members, put together a post: &lt;a href="https://ropensci.org/blog/2020/05/19/covid-19-open-data/"&gt;When Field or Lab Work is not an Option - Leveraging Open Data Resources for Remote Research&lt;/a&gt;. We highlighted examples of how specific collections of packages are being used right now in fields as varied as archaeology and climate science and compiled a table of &amp;gt; 100 rOpenSci packages for access to open data.&lt;/p&gt;
&lt;h2&gt;
Software Peer Review
&lt;/h2&gt;&lt;p&gt;&lt;a href="https://ropensci.org/software-review/"&gt;Software peer review&lt;/a&gt; is accepting submissions again, after a pause to reduce the load on reviewers and editors in light of the COVID-19 crisis.&lt;/p&gt;</description></item><item><title>Using DataPackageR to create data package Pandemic Papers with Chris Knox</title><link>https://ropensci.org/usecases/using-datapackager-to-create-data-package-pandemic-papers-with-chris-knox/</link><pubDate>Wed, 17 Jun 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/using-datapackager-to-create-data-package-pandemic-papers-with-chris-knox/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/DataPackageR/"&gt;DataPackageR&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;Used DataPackageR to create a data package of the New Zealand Government&amp;rsquo;s released &lt;a href="https://covid19.govt.nz/resources/key-documents-and-legislation/proactive-release/"&gt;Covid-19 document dump&lt;/a&gt; available as searchable plain text.&lt;/p&gt;
&lt;p&gt;Use case from &lt;strong&gt;&lt;a href="https://twitter.com/vizowl/status/1265876658508054529"&gt;from Chris Knox&amp;rsquo;s tweet&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case
&lt;/h4&gt;&lt;p&gt;Output: &lt;a href="https://github.com/nzherald/pandemicpapers"&gt;Pandemic Papers Data Package GitHub&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
Sector
&lt;/h4&gt;&lt;p&gt;Other&lt;/p&gt;
&lt;h4&gt;
Field(s) of application
&lt;/h4&gt;&lt;p&gt;Journalism&lt;/p&gt;</description></item><item><title>Testing an API wrapper with webmockr and vcr</title><link>https://ropensci.org/usecases/testing-an-api-wrapper-with-webmockr-and-vcr/</link><pubDate>Tue, 09 Jun 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/testing-an-api-wrapper-with-webmockr-and-vcr/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/webmockr/"&gt;webmockr&lt;/a&gt; and &lt;a href="https://docs.ropensci.org/vcr/"&gt;vcr&lt;/a&gt; with the &lt;a href="https://books.ropensci.org/http-testing/"&gt;HTTP testing book&lt;/a&gt;. A question on rOpenSci discourse helped me discover the tools.&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;I tested the dev.to api wrapper I wrote. I used webmockr to create stubs to the apis, and vcr to record the API response to a local disk for testing purposes. I wrote it up &lt;a href="https://dev.to/daveparr/testing-my-dev-to-api-package-with-testthat-webmockr-and-vcr-2dgm"&gt;here&lt;/a&gt;.&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case*
&lt;/h4&gt;&lt;p&gt;My code is &lt;a href="https://github.com/DaveParr/dev.to.ol"&gt;on GitHub&lt;/a&gt;&lt;/p&gt;</description></item><item><title>US lawmakers on Twitter during a pandemic: some corpus linguistics methods</title><link>https://ropensci.org/usecases/us-lawmakers-on-twitter-during-a-pandemic-some-corpus-linguistics-methods/</link><pubDate>Tue, 09 Jun 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/us-lawmakers-on-twitter-during-a-pandemic-some-corpus-linguistics-methods/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/rtweet/"&gt;rtweet&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;A short course in computational-corpus linguistics. A look at how US lawmakers have been tweeting about things COVID-19 since March. Semantic spaces, network graphs, and some politicization of COVID-concepts &amp;ndash; for good measure. ++Techniques for working with multi-word expressions in text analytic workflows.&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://www.jtimm.net/2020/05/26/corp-comp-ling-covid19/"&gt;https://www.jtimm.net/2020/05/26/corp-comp-ling-covid19/&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
Image
&lt;/h4&gt;&lt;p&gt;&lt;img src="https://ropensci.org/usecases/us-lawmakers-on-twitter-during-a-pandemic-some-corpus-linguistics-methods/us-lawmakers-on-twitter-during-a-pandemic-some-corpus-linguistics-methods.png" alt="unnamed-chunk-28-1|583x500"&gt;&lt;/p&gt;
&lt;h4&gt;
Sector
&lt;/h4&gt;&lt;p&gt;Academic&lt;/p&gt;</description></item><item><title>Create a time-lapse video using av package</title><link>https://ropensci.org/usecases/create-a-time-lapse-video-using-av-package/</link><pubDate>Mon, 08 Jun 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/create-a-time-lapse-video-using-av-package/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://ropensci.org/packages/"&gt;av&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;I took a series of photos with my DSLR and a tripod using an intervalometer.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Exposure Time:&lt;/strong&gt; 13s&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Aperture Value:&lt;/strong&gt; F8&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;ISO:&lt;/strong&gt; 100&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Then it was employed &lt;a href="https://twitter.com/hashtag/rstats?src=hashtag_click"&gt;#rstats&lt;/a&gt; to create the time-lapse, without install another software. The &lt;a href="https://twitter.com/hashtag/av?src=hashtag_click"&gt;#av&lt;/a&gt; package facilitates this work. This is my window view in Santa Maria-Brazil. Car lights painting the night during COVID-19 times.&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case*
&lt;/h4&gt;&lt;p&gt;&lt;em&gt;Here you can find the code&lt;/em&gt;
&lt;a href="https://github.com/MauricioCely/time-lapse"&gt;https://github.com/MauricioCely/time-lapse&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Scrape an image from DeepZoom with R and magick, recomposing a single image from multiple tiles</title><link>https://ropensci.org/usecases/scrape-an-image-from-deepzoom-with-r-and-magick-recomposing-a-single-image-from-multiple-tiles/</link><pubDate>Mon, 08 Jun 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/scrape-an-image-from-deepzoom-with-r-and-magick-recomposing-a-single-image-from-multiple-tiles/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/magick"&gt;magick&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://en.wikipedia.org/wiki/Deep_Zoom"&gt;DeepZoom&lt;/a&gt; allows webmasters to display high resolution images in an online viewer. It mostly discourages downlading the original high resolution images to your local drive. Magick combined with rvest can be used to get these images nevertheless with the help of R.&lt;/p&gt;
&lt;p&gt;Full code for doing so is presented on &lt;a href="https://ourednik.info/maps/2020/05/26/scrape-an-image-from-deepzoom-with-r-and-magick-recomposing-a-single-image-from-multiple-tiles/"&gt;my blog on mapping and data mining&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;In the core of the code, I use the &lt;a href="https://cran.r-project.org/web/packages/magick/vignettes/intro.html"&gt;magick R package&lt;/a&gt; to recompose the whole image from the tiles. This in two embedded for-loops. The recomposing magic happens in the line&lt;/p&gt;</description></item><item><title>Superior svg graphics rendering in R, and why it matters</title><link>https://ropensci.org/blog/2020/05/28/rsvg2/</link><pubDate>Thu, 28 May 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2020/05/28/rsvg2/</guid><description>
&lt;p&gt;This week we released a major new version of the &lt;a href="https://cran.r-project.org/web/packages/rsvg/index.html"&gt;rsvg&lt;/a&gt; package on CRAN. This package provides R bindings to &lt;a href="https://developer.gnome.org/rsvg/stable/"&gt;librsvg2&lt;/a&gt; which is a powerful system library for rendering svg images into bitmaps that can be displayed, or use for further processing in for example the &lt;a href="https://docs.ropensci.org/magick"&gt;magick&lt;/a&gt; package.&lt;/p&gt;
&lt;p&gt;The biggest change in this release is the R package on Windows and MacOS now includes the latest librsvg 2.48.4. This is a major upgrade; the librsvg2 rendering engine has been &lt;a href="https://people.gnome.org/~federico/blog/css-in-librsvg-is-now-in-rust.html"&gt;completely rewritten&lt;/a&gt; in Rust &lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt; using components from &lt;a href="https://research.mozilla.org/servo-engines/"&gt;Mozilla Servo&lt;/a&gt;. This has resulted in major improvements in quality and performance, and we have gained full support for css styling.&lt;/p&gt;</description></item><item><title>Detecting the Effects of Sustained Glacier Wastage on Streamflow in Variably Glacierized Catchments (Using tidyhydat)</title><link>https://ropensci.org/usecases/detecting-the-effects-of-sustained-glacier-wastage-on-streamflow-in-variably-glacierized-catchments-using-tidyhydat/</link><pubDate>Mon, 25 May 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/detecting-the-effects-of-sustained-glacier-wastage-on-streamflow-in-variably-glacierized-catchments-using-tidyhydat/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://github.com/ropensci/tidyhydat"&gt;tidyhydat&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did &lt;del&gt;you&lt;/del&gt; they do?
&lt;/h4&gt;&lt;p&gt;This study focused on the effects of glacier melt on streamflow in the Canadian portion of the Columbia River headwaters over the period 1977 to 2017. Between 1985 and 2013, glacier coverage decreased by up to 2% of catchment area for the 35 study catchments. The analyses suggest that glacier-melt reductions have exacerbated a regional climate-driven trend to decreased August streamflow contributions from unglacierized areas.&lt;/p&gt;</description></item><item><title>Using {drake} for machine learning</title><link>https://ropensci.org/usecases/using-drake-for-machine-learning/</link><pubDate>Fri, 22 May 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/using-drake-for-machine-learning/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/drake"&gt;drake&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;I elaborated on how I use {drake} to create machine learning products end-to-end, using it in combination of the R package structure.&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://edwinth.github.io/blog/drake-ml/"&gt;https://edwinth.github.io/blog/drake-ml/&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
Sector
&lt;/h4&gt;&lt;p&gt;industry&lt;/p&gt;</description></item><item><title>When Field or Lab Work is not an Option - Leveraging Open Data Resources for Remote Research</title><link>https://ropensci.org/blog/2020/05/19/covid-19-open-data/</link><pubDate>Tue, 19 May 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2020/05/19/covid-19-open-data/</guid><description>
&lt;p&gt;The COVID-19 pandemic has dramatically impacted all of our lives in a very short period of time.
Spring and summer are usually very busy as students prepare to go the field to engage in various data collection efforts.
The pandemic has also disrupted these carefully planned activities as travel is suspended and local and remote field stations have closed indefinitely.
A lost field season can be a major setback for a dissertation timeline and students will have to improvise.
One promising opportunity to continue research efforts during these unprecedented times is taking advantage of the massive amounts of open scientific data that are freely available.
Open data can form the basis of a review, synthesis, or new research.&lt;/p&gt;</description></item><item><title>bomrang with a third party package, stationaRy, to get hourly weather data and clifro to plot wind roses</title><link>https://ropensci.org/usecases/bomrang-with-a-third-party-package-stationary-to-get-hourly-weather-data-and-clifro-to-plot-wind-roses/</link><pubDate>Sun, 17 May 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/bomrang-with-a-third-party-package-stationary-to-get-hourly-weather-data-and-clifro-to-plot-wind-roses/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/bomrang/"&gt;bomrang&lt;/a&gt;, &lt;a href="https://docs.ropensci.org/clifro/"&gt;clifro&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;We had an issue with an on-site weather station where the wind-vane was not properly calibrated. So we opted to use BOM data to check wind directions during the rainfall events in which we were measuring fungal spore dispersal to make sure the wind was blowing roughly in the direction of our trap plants.&lt;/p&gt;
&lt;p&gt;We used bomrang&amp;rsquo;s &lt;code&gt;sweep_for_stations()&lt;/code&gt; to identify stations within a given radius of a site where we had research plots to then download hourly weather data using the &lt;a href="https://cran.r-project.org/package=stationaRy"&gt;stationaRy package&lt;/a&gt; (bomrang does not offer hourly weather data).&lt;/p&gt;</description></item><item><title>Package for downloading shapefiles using piggyback</title><link>https://ropensci.org/usecases/package-for-downloading-shapefiles-using-piggyback/</link><pubDate>Mon, 11 May 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/package-for-downloading-shapefiles-using-piggyback/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/piggyback/"&gt;piggyback&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;I created a package called {leaidr} to use facilitate the download and use of U.S. school district shapefiles. The shapefile is over GitHub&amp;rsquo;s allowed limit of 100MB. Originally, I tried to use GitHub LFS as a way to upload the file. Unfortunately, GitHub LFS is not reproducible in that when others download the package, they wouldn&amp;rsquo;t be able to access the file.&lt;/p&gt;</description></item><item><title>A Roundup of R Tools for Handling BibTeX</title><link>https://ropensci.org/blog/2020/05/07/rmd-citations/</link><pubDate>Thu, 07 May 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2020/05/07/rmd-citations/</guid><description>
&lt;p&gt;Our website is based on Markdown content rendered with Hugo.
Markdown content is in some cases knit from R Markdown, but with &lt;a href="https://bookdown.org/yihui/blogdown/output-format.html"&gt;less functionality than if one rendered R Markdown to html as in the blogdown default&lt;/a&gt;.
In particular, we cannot use the usual BibTex + CSL + Pandoc-citeproc &lt;a href="https://github.com/rstudio/distill/issues/45"&gt;dance&lt;/a&gt; to handle a bibliography.
Thankfully, using the rOpenSci package RefManageR, we can still make our own bibliography from a BibTeX file without formatting references by hand.
In this post we shall present our custom workflow for inserting citations, as well as more mainstream tools.&lt;/p&gt;</description></item><item><title>Visualize covid19 cases using rnaturalearth package</title><link>https://ropensci.org/usecases/visualize-covid19-cases-using-rnaturalearth-package/</link><pubDate>Tue, 05 May 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/visualize-covid19-cases-using-rnaturalearth-package/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;rnaturalearth&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;I created several R dataset packages for tracking the covid19 virus in different geographic locations (Italy, Switzerland, etc.). To help users create choropleth maps with a minimum effort I added for each dataset (when applicable) a column with the corresponding region/province naming convention used in the &lt;strong&gt;rnaturaleath&lt;/strong&gt; package. The goal is to enable a seamless merge of the data with the geospatial data available in the package with the &lt;code&gt;ne_state&lt;/code&gt; function.&lt;/p&gt;</description></item><item><title>{drake} at Queensland Fire and Emergency Services</title><link>https://ropensci.org/usecases/drake-at-queensland-fire-and-emergency-services/</link><pubDate>Mon, 04 May 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/drake-at-queensland-fire-and-emergency-services/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://github.com/ropensci/drake"&gt;drake&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;I wrote a blog post detailing how my team of 4 data scientists at Queensland Fire and Emergency Services sets up our R projects with &lt;code&gt;{drake}&lt;/code&gt;. I also talk a little bit about how it facilitates colloboration and debugging.&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://milesmcbain.xyz/the-drake-post/"&gt;https://milesmcbain.xyz/the-drake-post/&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
Sector
&lt;/h4&gt;&lt;p&gt;Government&lt;/p&gt;
&lt;h4&gt;
Field(s) of application
&lt;/h4&gt;&lt;p&gt;Sofware Engineering&lt;/p&gt;</description></item><item><title>Highlights of Hugo Code Highlighting</title><link>https://ropensci.org/blog/2020/04/30/code-highlighting/</link><pubDate>Thu, 30 Apr 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2020/04/30/code-highlighting/</guid><description>
&lt;p&gt;Thanks to a quite overdue update of Hugo on our build system&lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt;, our website can now harness the full power of Hugo code highlighting for Markdown-based content.
What&amp;rsquo;s code highlighting apart from the reason behind a tongue-twister in this post title?
In this post we shall explain how Hugo&amp;rsquo;s code highlighter, &lt;a href="https://github.com/alecthomas/chroma"&gt;Chroma&lt;/a&gt;, helps you prettify your code (i.e. &lt;em&gt;syntax highlighting&lt;/em&gt;), and accentuate parts of your code (i.e. &lt;em&gt;line highlighting&lt;/em&gt;).&lt;/p&gt;
&lt;h3&gt;
Make your code look pretty
&lt;/h3&gt;&lt;p&gt;If you notice and appreciate the difference between&lt;/p&gt;</description></item><item><title>Using taxadb to query taxonomic information in ecology projects</title><link>https://ropensci.org/usecases/using-taxadb-to-query-taxonomic-information-in-ecology-projects/</link><pubDate>Mon, 27 Apr 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/using-taxadb-to-query-taxonomic-information-in-ecology-projects/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/taxadb/"&gt;taxadb&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://gavinmasterson.netlify.app/post/taxadb/"&gt;https://gavinmasterson.netlify.app/post/taxadb/&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
Image
&lt;/h4&gt;&lt;p&gt;&lt;img src="https://ropensci.org/usecases/using-taxadb-to-query-taxonomic-information-in-ecology-projects/using-taxadb-to-query-taxonomic-information-in-ecology-projects.png" alt="image|638x350"&gt;&lt;/p&gt;
&lt;h4&gt;
Sector
&lt;/h4&gt;&lt;p&gt;academic&lt;/p&gt;
&lt;h4&gt;
Field(s) of application
&lt;/h4&gt;&lt;p&gt;ecology, conservation, evolutionary biology, species distribution modeling&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;I used the {taxadb} package to verify taxonomic information for two ecology-related projects. In the second case, I compared taxonomic identifications from 2006 with the current information for those species to identify changes in name and/or status..&lt;/p&gt;</description></item><item><title>Miscellaneous Wisdom about R Markdown &amp; Hugo Gained from Work on our Website</title><link>https://ropensci.org/blog/2020/04/23/rmd-learnings/</link><pubDate>Thu, 23 Apr 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2020/04/23/rmd-learnings/</guid><description>
&lt;p&gt;Whilst &lt;a href="https://ropensci.org/blog/2020/04/07/bookdown-learnings/"&gt;working on the blog guide&lt;/a&gt;, &lt;a href="https://ropensci.org/authors/stefanie-butland/"&gt;Stefanie Butland&lt;/a&gt; and I consolidated knowledge we had already gained, but it was also the opportunity to up our Rmd/Hugo technical game.
Our website uses Hugo but not blogdown&lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt; to render posts: every post is based on an .md file that is either written directly or knit from an .Rmd file.
We wanted to provide clear guidance for both options, and to stick to the well-documented Hugo way of e.g. inserting figures.
We also wanted to provide post contributors with an as smooth as possible workflow to create a new post.
Working on this mission, unsurprisingly we learned a lot, and why not share our newly acquired technical know-how?
In this post I shall go through four things we learned about Rmd/Hugo, while trying to provide context about the &lt;em&gt;why&lt;/em&gt; of our using them.&lt;/p&gt;</description></item><item><title>Animated generative art with magick</title><link>https://ropensci.org/usecases/animated-generative-art-with-magick/</link><pubDate>Tue, 21 Apr 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/animated-generative-art-with-magick/</guid><description>
&lt;p&gt;This use case for {&lt;a href="https://docs.ropensci.org/magick/"&gt;magick&lt;/a&gt;} was inspired by the &amp;lsquo;ashtree&amp;rsquo; algorithm by Danielle Navarro. I thought it would be really nice to show the organic growth of the trees. The tree itself is a result of a branching process, an excellent example for some simple generative art using functional programming. The animation can be admired &lt;a href="https://twitter.com/analythium/status/1251004527609708545"&gt;here&lt;/a&gt;.&lt;/p&gt;
&lt;h4&gt;
rOpenSci package or resource used
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/magick/"&gt;magick&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://gist.github.com/psolymos/f0f8132ee03b6f7f03e275473b355b8e"&gt;https://gist.github.com/psolymos/f0f8132ee03b6f7f03e275473b355b8e&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Automatic Code Cleaning in R with Rclean</title><link>https://ropensci.org/blog/2020/04/21/rclean/</link><pubDate>Tue, 21 Apr 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2020/04/21/rclean/</guid><description>
&lt;blockquote&gt;
&lt;p&gt;Leave the code cleaner than you found it.&lt;/p&gt;
&lt;p&gt;&amp;ndash; R.C. Martin in &lt;em&gt;Clean Code&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;The R language has become very popular among scientists and analysts
because it enables the rapid development of software and empowers
scientific investigation. However, regardless of the language used,
data analysis is usually complicated. Because of various project
complexities and time constraints, analytical software often reflects
these challenges. &amp;ldquo;What did I measure? What analyses are relevant to
the study? Do I need to transform the data? What&amp;rsquo;s the function for the
analysis I want to run?&amp;rdquo; Although many researchers see the value in
learning to write software, the time investment for learning a
programming language alone is still exceedingly high for many, let
alone also learning software best practices. The downside to the rapid
spread of data science is that learning to create good software takes
a back-seat to just writing code that will get the job &amp;ldquo;done&amp;rdquo; leading
to issues with transparency and software that is highly unstable
(i.e. buggy and not reproducible).&lt;/p&gt;</description></item><item><title>2 Months in 2 Minutes - rOpenSci News, April 2020</title><link>https://ropensci.org/blog/2020/04/17/news-apr2020/</link><pubDate>Fri, 17 Apr 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2020/04/17/news-apr2020/</guid><description>
&lt;h3&gt;
rOpenSci HQ
&lt;/h3&gt;&lt;ul&gt;
&lt;li&gt;The recording, collaborative notes and links to community discussion and resources are up for our latest &lt;a href="https://ropensci.org/commcalls/2020-03-18/"&gt;Community Call on Maintaining an R package&lt;/a&gt;. Panel moderated by Julia Silge included Elin Waring, Erin Grand, Leonardo Collado-Torres, and Scott Chamberlain.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt; &lt;/p&gt;
&lt;h3&gt;
Software Peer Review
&lt;/h3&gt;&lt;p&gt;1 staff-contributed package passed &lt;a href="https://ropensci.org/software-review/"&gt;software peer review&lt;/a&gt;.&lt;/p&gt;
&lt;!---- alphabetical order. For link to package, use 1) https://docs.ropensci.org/pkgname when docs are rendered without errors or bad links to images or 2) to the source code page e.g. https://github.com/ropensci/grainchanger when docs page has errors
----&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;a href="https://docs.ropensci.org/parzer/"&gt;parzer&lt;/a&gt;&lt;/strong&gt; - Parse messy geographic coordinates. Author: &lt;a href="https://ropensci.org/author/scott-chamberlain/"&gt;Scott Chamberlain&lt;/a&gt;; Reviewers: &lt;a href="https://github.com/brunj7"&gt;Julien Brun&lt;/a&gt;, &lt;a href="https://github.com/mvickm"&gt;María Victoria Munafó&lt;/a&gt;; Read the &lt;a href="https://github.com/ropensci/onboarding/issues/341"&gt;Review&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;em&gt;On March 16, we paused new submissions for software peer review for 30 days (possibly longer) in the interest of reducing load on reviewers and editors in light of the COVID-19 crisis.&lt;/em&gt;&lt;/p&gt;</description></item><item><title>Extracting eBird Data from a Polygon</title><link>https://ropensci.org/blog/2020/04/16/ebird-polygon/</link><pubDate>Thu, 16 Apr 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2020/04/16/ebird-polygon/</guid><description>
&lt;p&gt;One of the first things I took on when I started at the Cornell Lab of Ornithology was creating the &lt;a href="https://cornelllabofornithology.github.io/auk/"&gt;auk R package&lt;/a&gt; for accessing eBird data. The entire eBird dataset can be downloaded as a massive text file, called the eBird Basic Dataset (EBD), and auk pulls out manageable chunks of the dataset based on various spatial, temporal, or taxonomic filters. I&amp;rsquo;m often asked &amp;ldquo;how do I extract data from within a polygon?&amp;rdquo; (usually &amp;ldquo;polygon&amp;rdquo; is replaced by &amp;ldquo;shapefile&amp;rdquo;, but I try to avoid that word since there&amp;rsquo;s &lt;a href="http://switchfromshapefile.org/"&gt;good reasons to stop using shapefiles&lt;/a&gt;). Rather than answer these questions individually, I thought I&amp;rsquo;d do a quick post about how to do this with auk. Note that, at the time of posting, this requires auk version 0.4.1 or higher, which can be installed with:&lt;/p&gt;</description></item><item><title>Use of crul's retry sub-routine in an API package</title><link>https://ropensci.org/usecases/use-of-crul-s-retry-sub-routine-in-an-api-package/</link><pubDate>Thu, 16 Apr 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/use-of-crul-s-retry-sub-routine-in-an-api-package/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/crul"&gt;&lt;code&gt;crul&lt;/code&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case*
&lt;/h4&gt;&lt;p&gt;&lt;em&gt;Link to a blog post, a gist, or an academic paper, or provide some code inline&lt;/em&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href="https://github.com/ropensci/ropenaq/pull/50"&gt;PR in &lt;code&gt;ropenaq&lt;/code&gt;&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href="https://blog.r-hub.io/2020/04/07/retry-wheel/"&gt;Post on the R-hub blog about retry sub-routines in &lt;code&gt;crul&lt;/code&gt; and &lt;code&gt;httr&lt;/code&gt;, and (not) re-inventing the wheel when developing R packages&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h4&gt;
Sector
&lt;/h4&gt;&lt;p&gt;&lt;em&gt;List one of: academic / industry / government / non-profit / other&lt;/em&gt;&lt;/p&gt;</description></item><item><title>rOpenSci Dev Guide 0.4.0: Updates</title><link>https://ropensci.org/blog/2020/04/14/devguide-release/</link><pubDate>Tue, 14 Apr 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2020/04/14/devguide-release/</guid><description>
&lt;p&gt;rOpenSci Software Peer Review&amp;rsquo;s guidance has been compiled in &lt;a href="https://devguide.ropensci.org/"&gt;an online book&lt;/a&gt; for more than one year now. We&amp;rsquo;ve just released its fourth version.
To find out what&amp;rsquo;s new in our dev guide 0.4.0, you can &lt;a href="https://devguide.ropensci.org/booknews.html"&gt;read the changelog&lt;/a&gt;,
or this blog post for more digested information.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Note that, as indicated in the &lt;a href="https://github.com/ropensci/software-review"&gt;README of the software review repo&lt;/a&gt;, in the interest of reducing load on reviewers and editors as we manage the COVID-19 crisis, rOpenSci is temporarily pausing new submissions for software peer review for 30 days (and possibly longer). Please check back &lt;a href="https://github.com/ropensci/software-review"&gt;in the software review repository&lt;/a&gt; again after 17 April for updates. In this period new submissions will not be handled, nor new reviewers assigned. Reviews and responses to reviews will be handled on a ‘best effort’ basis, but no follow-up reminders will be sent.&lt;/p&gt;</description></item><item><title>{Magick}ally Visualize Historical Google Maps Traffic Data</title><link>https://ropensci.org/usecases/magick-ally-visualize-historical-google-maps-traffic-data/</link><pubDate>Fri, 10 Apr 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/magick-ally-visualize-historical-google-maps-traffic-data/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/magick/"&gt;magick&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://e.olamijuwon.com/how-to-magickally-visualize-historical-google-maps-traffic-data/"&gt;https://e.olamijuwon.com/how-to-magickally-visualize-historical-google-maps-traffic-data/&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
Image
&lt;/h4&gt;&lt;p&gt;&lt;img src="https://ropensci.org/usecases/magick-ally-visualize-historical-google-maps-traffic-data/magick-ally-visualize-historical-google-maps-traffic-data.jpeg" alt="CapeTown - 30March|581x500"&gt;&lt;/p&gt;
&lt;h4&gt;
Sector
&lt;/h4&gt;&lt;p&gt;Other&lt;/p&gt;
&lt;h4&gt;
Field(s) of application
&lt;/h4&gt;&lt;p&gt;Social sciences&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;I used {magick} in combination with {googleway} package to visualize historical road traffic in three major cities in South Africa. This exercise was motivated by the increased need to evaluate compliance with social distancing as many African countries enforce full/partial lock down in the wake of COVID-19. Unfortunately, Google Maps does not provide historical traffic data beyond traffic information on a typical (specified) day and time.&lt;/p&gt;</description></item><item><title>10 Things We Learned in Creating the Blog Guide with bookdown</title><link>https://ropensci.org/blog/2020/04/07/bookdown-learnings/</link><pubDate>Tue, 07 Apr 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2020/04/07/bookdown-learnings/</guid><description>
&lt;p&gt;After soliciting, reviewing, and publishing over 100 blog posts and tech notes by rOpenSci community members, we have created the &lt;a href="https://blogguide.ropensci.org/"&gt;rOpenSci Blog Guide for Authors and Editors&lt;/a&gt; to address many frequently asked questions and frequently given suggestions.&lt;/p&gt;
&lt;p&gt;Technically, we structured the content as a bookdown gitbook. It was Stef&amp;rsquo;s first foray into the glorious process of publishing a book with bookdown, and Maëlle&amp;rsquo;s second&lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt;. And oh, we learned a lot.&lt;/p&gt;
&lt;h2&gt;
Stef (first-timer)
&lt;/h2&gt;&lt;h3&gt;
1. How to collaborate across timezones
&lt;/h3&gt;&lt;p&gt;There is a 9-hour time difference between Maëlle and me for most of the year. I&amp;rsquo;m in Kamloops, Canada and Maëlle is in Nancy, France. Since so much of this is new to me, text-based explanations from Maëlle via Slack usually boggled my mind. It helped immensely to have a weekly 30-minute meeting (8:30am for Stef and 5:30pm for Maëlle) with agenda and notes in a shared google doc. We would talk through our approaches and priorities and Maëlle would coach me in new-to-me tools.&lt;/p&gt;</description></item><item><title>pdftools for parsing tables from many .pdfs</title><link>https://ropensci.org/usecases/pdftools-for-parsing-tables-from-many-pdfs/</link><pubDate>Tue, 31 Mar 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/pdftools-for-parsing-tables-from-many-pdfs/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://github.com/ropensci/pdftools"&gt;&lt;code&gt;pdftools&lt;/code&gt;&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case*
&lt;/h4&gt;&lt;ul&gt;
&lt;li&gt;&lt;a href="https://github.com/jthomasmock/pdftools-guide"&gt;Link to GitHub repo&lt;/a&gt;
&lt;ul&gt;
&lt;li&gt;Has all the code and raw PDFs for users to test out themselves&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;a href="https://jthomasmock.github.io/pdftools-guide/#scraping_complex_tables_from_pdfs_with_pdf_tools"&gt;Vignette/Webpage with example code run&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h4&gt;
Image
&lt;/h4&gt;&lt;p&gt;Raw example of the PDF table from the TTB. Notice there are inconsistent spaces between the table columns.&lt;/p&gt;
&lt;p&gt;&lt;img src="https://ropensci.org/usecases/pdftools-for-parsing-tables-from-many-pdfs/pdftools-for-parsing-tables-from-many-pdfs.png" alt=""&gt;&lt;/p&gt;
&lt;h4&gt;
Sector
&lt;/h4&gt;&lt;p&gt;Finance, econometrics&lt;/p&gt;
&lt;h4&gt;
Field(s) of application
&lt;/h4&gt;&lt;p&gt;Forecasting, finance, econometrics, but really could be used for anything!&lt;/p&gt;</description></item><item><title>Searching Microsoft Academic &amp; extracting the metadata</title><link>https://ropensci.org/usecases/searching-microsoft-academic-extracting-the-metadata/</link><pubDate>Fri, 27 Mar 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/searching-microsoft-academic-extracting-the-metadata/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/microdemic/"&gt;microdemic&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;My exercise comprise a piece of code that can help to search the articles and extract the metdata from Microsoft Academic. The example is limited with only one query type.
&lt;a href="https://github.com/ropensci/microdemic"&gt;microdemic&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://rpubs.com/alexeilutay/covid_coverage2"&gt;COVID March publications &lt;/a&gt;&lt;/p&gt;
&lt;p&gt;The query consists of the words (terms) and the publication date range. Number of results were received via ma_calchist, the records were extracted by 100 with ma_evaluate.
The guy who learned me to test this was &lt;a href="https://twitter.com/DarrinEide"&gt;Darrin Eide&lt;/a&gt;&lt;/p&gt;</description></item><item><title>parzer: Parse Messy Geographic Coordinates</title><link>https://ropensci.org/blog/2020/03/19/parzer/</link><pubDate>Thu, 19 Mar 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2020/03/19/parzer/</guid><description>
&lt;p&gt;&lt;a href="https://github.com/ropensci/parzer"&gt;parzer&lt;/a&gt; is a new package for handling messy geographic coordinates.
The first version is now on CRAN, with binaries coming soon hopefully (see
note about installation below). The package recently &lt;a href="https://github.com/ropensci/onboarding/issues/341"&gt;completed rOpenSci
review&lt;/a&gt;.&lt;/p&gt;
&lt;h2&gt;
parzer motivation
&lt;/h2&gt;&lt;p&gt;The idea for this package started with a tweet from &lt;a href="https://ropensci.org/author/noam-ross/"&gt;Noam Ross&lt;/a&gt;
(&lt;a href="https://twitter.com/noamross/status/1070733367522590721"&gt;https://twitter.com/noamross/status/1070733367522590721&lt;/a&gt;) about 15 months ago.&lt;/p&gt;
&lt;p&gt;The idea being that sometimes you have geographic coordinates in a messy
format, or in many different formats, etc. You can think of it as being
the package for geographic coordinates that &lt;a href="https://cloud.r-project.org/web/packages/lubridate/"&gt;lubridate&lt;/a&gt; is for dates.&lt;/p&gt;</description></item><item><title>Maintaining an R Package</title><link>https://ropensci.org/commcalls/2020-03-18/</link><pubDate>Wed, 18 Mar 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/commcalls/2020-03-18/</guid><description/></item><item><title>satRday Neuchâtel</title><link>https://ropensci.org/events/satrday-neuchatel/</link><pubDate>Sat, 14 Mar 2020 08:00:00 +0000</pubDate><guid>https://ropensci.org/events/satrday-neuchatel/</guid><description>
&lt;p&gt;Mark Padgham, rOpenSci Software Research Scientist, is giving a talk at &lt;a href="https://neuchatel2020.satrdays.org/"&gt;satRday Neuchâtel&lt;/a&gt;. Community member and package maintainer, Sina Rüeger, is one of the organizers.&lt;/p&gt;
&lt;p&gt;This is a remote conference. Free with registration.&lt;/p&gt;</description></item><item><title>Supercharge your GitHub Actions Experience with tic</title><link>https://ropensci.org/blog/2020/03/13/tic-ghactions/</link><pubDate>Fri, 13 Mar 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2020/03/13/tic-ghactions/</guid><description>
&lt;p&gt;&lt;a href="https://en.wikipedia.org/wiki/Continuous_integration"&gt;&amp;ldquo;Continuous Integration&amp;rdquo;&lt;/a&gt; (CI) has become a standard for proper software development.
Checking the integrity of software after changes have been made is essential to ensure its proper functionality.
Also, CI helps catch problems introduced by dependencies early when executed on a regular basis (usually done via scheduled &lt;a href="https://tecadmin.net/crontab-in-linux-with-20-examples-of-cron-schedule/"&gt;CRON&lt;/a&gt; runs).&lt;/p&gt;
&lt;p&gt;Multiple professional providers exist (&lt;a href="https://travis-ci.com/"&gt;Travis CI&lt;/a&gt;, &lt;a href="https://www.appveyor.com/"&gt;AppVeyor CI&lt;/a&gt;, &lt;a href="https://circleci.com/"&gt;Circle CI&lt;/a&gt;, etc.) which offer CI services to the public.
Most services offer limited free build contingents for open-source projects.
However, it has not been easy for the R community to jump on the train right away as most providers did not support the R language natively on their side.
Therefore, the R community started to create their own configurations to quickly automate the checking of R packages on &lt;a href="https://travis-ci.com/"&gt;Travis CI&lt;/a&gt;.
In fact, the first commit of the official &lt;code&gt;r.rb&lt;/code&gt; build script was made on &lt;a href="https://github.com/travis-ci/travis-build/commit/c697bb2240cfc1abb92a95f57d2e72c151104431"&gt;Feb 1st 2015 by Craig Citro&lt;/a&gt;.
Since then 21 unique contributors have maintained this configuration under the meta-lead of &lt;a href="https://github.com/jimhester"&gt;Jim Hester&lt;/a&gt; and &lt;a href="https://github.com/jeroen"&gt;Jeroen Ooms&lt;/a&gt; which allowed many thousands of R package maintainers to jump onto the train.&lt;/p&gt;</description></item><item><title>Community Call - Maintaining an R Package</title><link>https://ropensci.org/blog/2020/03/04/commcall-mar2020/</link><pubDate>Wed, 04 Mar 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2020/03/04/commcall-mar2020/</guid><description>
&lt;p&gt;For this Community Call, we&amp;rsquo;re trying something different. We&amp;rsquo;ll start with a short talk by &lt;a href="#speakers"&gt;&lt;strong&gt;Julia Silge&lt;/strong&gt;&lt;/a&gt;, then spend most of the time on Q &amp;amp; A with &lt;a href="#speakers"&gt;four panelists&lt;/a&gt; - &lt;strong&gt;Elin Waring&lt;/strong&gt;, &lt;strong&gt;Erin Grand&lt;/strong&gt;, &lt;strong&gt;Leonardo Collado-Torres&lt;/strong&gt;, and &lt;strong&gt;Scott Chamberlain&lt;/strong&gt; - moderated by Julia.&lt;/p&gt;
&lt;p&gt;Our panelists bring a wide range of perspectives so there&amp;rsquo;s something for everyone. Collectively, they have experience developing and maintaining passion-project packages, very popular packages, too many packages on CRAN, packages on Bioconductor, and taking over maintenance (and changing things!) of a package developed by someone else.&lt;/p&gt;</description></item><item><title>opentripplanner: Fast and Easy Multimodal Trip Planning in R with OpenTripPlanner</title><link>https://ropensci.org/blog/2020/02/25/opentripplanner/</link><pubDate>Tue, 25 Feb 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2020/02/25/opentripplanner/</guid><description>
&lt;p&gt;With services like Google Maps, finding the fastest route from A to B has become quick, cheap, and easy. Not just for driving but walking, cycling and public transport too. But in the field of transport studies, we often want not only a single route, but thousands or millions of routes. This is where we hit a problem for services such as Google or the &lt;a href="https://openrouteservice.org/"&gt;Open Route Service&lt;/a&gt;, that usually only allow a limited number of free routes per day (typically around 1000). So routing is either very time consuming or expensive. Another problem is that we may not be interested in the current travel options, but how those options may change in the future. Such as, after a new bridge has been built or a new bus timetable has been introduced. Therefore, researchers can find it useful to run their own routing services where they have more control and can produce as many routes as necessary.&lt;/p&gt;</description></item><item><title>rOpenSci's Leadership in #rstats Culture</title><link>https://ropensci.org/blog/2020/02/21/ropensci-leadership/</link><pubDate>Fri, 21 Feb 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2020/02/21/ropensci-leadership/</guid><description>
&lt;p&gt;&lt;em&gt;At their closing keynote at the 2020 RStudio Conference, Hilary Parker and Roger Peng mentioned that they hatched the idea for their excellent &lt;a href="http://nssdeviations.com/"&gt;Not So Standard Deviations podcast&lt;/a&gt; following their reunion at the &lt;a href="https://unconf15.ropensci.org/"&gt;2015 rOpenSci unconf, (&amp;ldquo;runconf15&amp;rdquo;)&lt;/a&gt;. That statement went straight to my heart because it pin-pointed how I had been feeling throughout the week of RStudio Conference that I had been unable to name. At rstudio::conf, I was surrounded by so many of the incredible people I had met at that very same runconf15. These folks are visionaries and leaders, founding and leading global efforts in open source software and inclusive culture, and the fact that they were all together at a small event convened by rOpenSci holds great significance. I am so honored to know this community, and to consider them allies and friends. The RStudio Conference (&amp;ldquo;rstudio::conf&amp;rdquo;), a conference with 2400 people, felt cozy with their presence and with the visible efforts they have led to make R and beyond a welcoming, innovative space. In a follow-up to an earlier &lt;a href="https://ropensci.org/blog/2020/02/04/rstudioconf-2020/"&gt;blog summary of rstudio::conf(2020)&lt;/a&gt;, here I want to reflect on how important runconf15 was, and how truly unique and gamechanging rOpenSci is.&lt;/em&gt;&lt;/p&gt;</description></item><item><title>2 Months in 2 Minutes - rOpenSci News, February 2020</title><link>https://ropensci.org/blog/2020/02/20/news-feb2020/</link><pubDate>Thu, 20 Feb 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2020/02/20/news-feb2020/</guid><description>
&lt;h3&gt;
rOpenSci HQ
&lt;/h3&gt;&lt;ul&gt;
&lt;li&gt;On behalf of rOpenSci, thank you to everyone who has contributed their creativity, curiosity, smarts, and time in the last year. Read our &lt;a href="https://ropensci.org/blog/2019/12/23/thankyou/"&gt;Thank You, 2019&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;
Software Peer Review
&lt;/h3&gt;&lt;p&gt;3 community-contributed packages passed &lt;a href="https://ropensci.org/software-review/"&gt;software peer review&lt;/a&gt;.&lt;/p&gt;
&lt;!---- alphabetical order. For link to package, use 1) https://docs.ropensci.org/pkgname when docs are rendered without errors or bad links to images or 2) to the source code page e.g. https://github.com/ropensci/grainchanger when docs page has errors
----&gt;
&lt;p&gt;&lt;strong&gt;&lt;a href="https://docs.ropensci.org/osfr/"&gt;osfr&lt;/a&gt;&lt;/strong&gt; - R Interface to OSF. Author: &lt;a href="https://github.com/aaronwolen"&gt;Aaron Wolen&lt;/a&gt;; Reviewers: &lt;a href="https://github.com/HeidiSeibold"&gt;Heidi Seibold&lt;/a&gt;, &lt;a href="https://ropensci.org/authors/carl-boettiger/"&gt;Carl Boettiger&lt;/a&gt;; Read the &lt;a href="https://github.com/ropensci/onboarding/issues/279"&gt;Review&lt;/a&gt;&lt;/p&gt;</description></item><item><title>pdftools for parsing .pdf from a URL - public data mining</title><link>https://ropensci.org/usecases/pdftools-for-parsing-pdf-from-a-url-public-data-mining/</link><pubDate>Sat, 15 Feb 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/pdftools-for-parsing-pdf-from-a-url-public-data-mining/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://github.com/ropensci/pdftools"&gt;pdftools&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case*
&lt;/h4&gt;&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-r" data-lang="r"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nf"&gt;library&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;httr&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="c1"&gt;# will be use to make HTML GET and POST requests&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nf"&gt;library&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;rvest&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="c1"&gt;# will be used to parse HTML&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nf"&gt;library&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;tidyverse&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="c1"&gt;# data munge&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nf"&gt;library&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;pdftools&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="c1"&gt;# parse pdf&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# |- data ----&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nf"&gt;library&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;httr&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="c1"&gt;# will be use to make HTML GET and POST requests&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nf"&gt;library&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;rvest&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="c1"&gt;# will be used to parse HTML&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nf"&gt;library&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;tidyverse&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="c1"&gt;# data munge&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nf"&gt;library&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;pdftools&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="c1"&gt;# parse pdf&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# |- data ----&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="n"&gt;url&lt;/span&gt; &lt;span class="o"&gt;&amp;lt;-&lt;/span&gt; &lt;span class="s"&gt;&amp;#34;https://www.bsee.gov/guidance-and-regulations/guidance/safety-alerts-programs&amp;#34;&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="n"&gt;r&lt;/span&gt; &lt;span class="o"&gt;&amp;lt;-&lt;/span&gt; &lt;span class="nf"&gt;GET&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;url&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="n"&gt;raw_tbl&lt;/span&gt; &lt;span class="o"&gt;&amp;lt;-&lt;/span&gt; &lt;span class="n"&gt;r&lt;/span&gt; &lt;span class="o"&gt;%&amp;gt;%&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="nf"&gt;content&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt; &lt;span class="o"&gt;%&amp;gt;%&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="nf"&gt;html_node&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s"&gt;&amp;#34;table&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;%&amp;gt;%&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="nf"&gt;html_table&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt; &lt;span class="o"&gt;%&amp;gt;%&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="nf"&gt;as_tibble&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt; &lt;span class="o"&gt;%&amp;gt;%&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="n"&gt;janitor&lt;/span&gt;&lt;span class="o"&gt;::&lt;/span&gt;&lt;span class="nf"&gt;clean_names&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="n"&gt;raw_tbl&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# |- munge ----&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="n"&gt;normalize_title&lt;/span&gt; &lt;span class="o"&gt;&amp;lt;-&lt;/span&gt; &lt;span class="kr"&gt;function&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;title&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="n"&gt;title&lt;/span&gt; &lt;span class="o"&gt;%&amp;gt;%&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="nf"&gt;tolower&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt; &lt;span class="o"&gt;%&amp;gt;%&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="nf"&gt;str_replace_all&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s"&gt;&amp;#34;\\b\\s\\b&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s"&gt;&amp;#34;\\-&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;%&amp;gt;%&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="nf"&gt;str_remove_all&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s"&gt;&amp;#34;\\s&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="n"&gt;clean_tbl&lt;/span&gt; &lt;span class="o"&gt;&amp;lt;-&lt;/span&gt; &lt;span class="n"&gt;raw_tbl&lt;/span&gt; &lt;span class="o"&gt;%&amp;gt;%&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="nf"&gt;mutate&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;norm_url&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nf"&gt;map_chr&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;title&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;normalize_title&lt;/span&gt;&lt;span class="p"&gt;))&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="n"&gt;clean_tbl&lt;/span&gt;&lt;span class="o"&gt;$&lt;/span&gt;&lt;span class="n"&gt;norm_url[[1]]&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="n"&gt;base_url&lt;/span&gt; &lt;span class="o"&gt;&amp;lt;-&lt;/span&gt; &lt;span class="s"&gt;&amp;#34;https://www.bsee.gov/sites/bsee.gov/files/safety-alerts//&amp;#34;&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="n"&gt;ReadPDF&lt;/span&gt; &lt;span class="o"&gt;&amp;lt;-&lt;/span&gt; &lt;span class="kr"&gt;function&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;base_url&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;pdf_url&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="n"&gt;pdf_url&lt;/span&gt; &lt;span class="o"&gt;&amp;lt;-&lt;/span&gt; &lt;span class="n"&gt;glue&lt;/span&gt;&lt;span class="o"&gt;::&lt;/span&gt;&lt;span class="nf"&gt;glue&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;base_url&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="n"&gt;pdf_url&lt;/span&gt;&lt;span class="p"&gt;},&lt;/span&gt; &lt;span class="s"&gt;&amp;#34;.pdf&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="nf"&gt;print&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;pdf_url&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="c1"&gt;# pdftools time!&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="nf"&gt;pdf_text&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;pdf_url&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="n"&gt;SafeReadPDF&lt;/span&gt; &lt;span class="o"&gt;&amp;lt;-&lt;/span&gt; &lt;span class="nf"&gt;possibly&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;ReadPDF&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="kc"&gt;NA&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nf"&gt;SafeReadPDF&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;base_url&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;clean_tbl&lt;/span&gt;&lt;span class="o"&gt;$&lt;/span&gt;&lt;span class="n"&gt;norm_url[[1]]&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;h4&gt;
Image
&lt;/h4&gt;&lt;p&gt;&lt;img src="https://ropensci.org/usecases/pdftools-for-parsing-pdf-from-a-url-public-data-mining/pdftools-for-parsing-pdf-from-a-url-public-data-mining.gif" alt="pdftools-demo|690x351"&gt;&lt;/p&gt;</description></item><item><title>taxadb: A High-Performance Local Taxonomic Database Interface</title><link>https://ropensci.org/blog/2020/02/13/taxadb/</link><pubDate>Thu, 13 Feb 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2020/02/13/taxadb/</guid><description>
&lt;p&gt;Dealing with taxonomic inconsistencies within and across datasets is a fundamental challenge of ecology and evolutionary biology. Accounting for species synonyms, taxa splitting and unification is especially important as aggregation of data across time and different data sources becomes increasingly common. One potentially powerful approach for addressing these issues is to resolve scientific names to taxonomic identifiers that follow a consistent taxonomic concept. In such a workflow, data from one of the many taxonomic providers (e.g. Integrated Taxonomic Information System &lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt;, Catalogue of Life &lt;sup id="fnref:2"&gt;&lt;a href="#fn:2" class="footnote-ref" role="doc-noteref"&gt;2&lt;/a&gt;&lt;/sup&gt;, National Center for Biological Information &lt;sup id="fnref:3"&gt;&lt;a href="#fn:3" class="footnote-ref" role="doc-noteref"&gt;3&lt;/a&gt;&lt;/sup&gt;) is integrated with biodiversity datasets to identify an accepted ID for each name. Multiple tools exist to facilitate this workflow, including R&amp;rsquo;s taxize package &lt;sup id="fnref:4"&gt;&lt;a href="#fn:4" class="footnote-ref" role="doc-noteref"&gt;4&lt;/a&gt;&lt;/sup&gt;, which provides an API interface to taxonomic databases. However, due to the nature of API queries which are slow, limited in scope, and dependent on the current state of the database, it remains difficult to resolve names to a taxonomic authority in quick, reproducible way. taxadb seeks to address these issues using a new approach for interfacing with taxonomic data via a local database of taxonomic providers.&lt;/p&gt;</description></item><item><title>osmdata use case: Wall Art</title><link>https://ropensci.org/usecases/osmdata-use-case-wall-art/</link><pubDate>Thu, 06 Feb 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/osmdata-use-case-wall-art/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/osmdata"&gt;osmdata&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case*
&lt;/h4&gt;&lt;p&gt;This &lt;a href="https://github.com/deanmarchiori/culburra"&gt;github repository&lt;/a&gt; by Dean Marchiori&lt;/p&gt;
&lt;h4&gt;
Image
&lt;/h4&gt;&lt;p&gt;&lt;img src="https://ropensci.org/usecases/osmdata-use-case-wall-art/osmdata-use-case-wall-art.jpeg" alt=""&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;Dean Marchiori used the &lt;a href="https://docs.ropensci.org/osmdata/"&gt;&lt;code&gt;osmdata&lt;/code&gt; package&lt;/a&gt; to create a striking image which he printed and hung on a wall. His code to reproduce the image is contained with the &lt;a href="https://github.com/deanmarchiori/culburra"&gt;github repository&lt;/a&gt; file &lt;a href="https://github.com/deanmarchiori/culburra/blob/1dbf32edec17438b20e444a3b3722fd6c61feb5f/culburra.Rmd"&gt;&lt;code&gt;culburra.Rmd&lt;/code&gt;&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>The Fun of Building Things and the Challenge of Learning - the rOpenSci OzUnconf 2019</title><link>https://ropensci.org/blog/2020/02/05/ozunconf19/</link><pubDate>Wed, 05 Feb 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2020/02/05/ozunconf19/</guid><description>
&lt;p&gt;It was the best of times, it was the worst of times.&lt;/p&gt;
&lt;p&gt;Dickens might have meant it figuratively, but in the case of the rOpenSci OzUnconf 2019, we mean it literally. Set to the backdrop of a &lt;a href="https://en.wikipedia.org/wiki/2019%E2%80%9320_Australian_bushfire_season"&gt;national emergency that is still ongoing&lt;/a&gt; from 11-13 December, our participants came from across Australia as well as New Zealand, Japan, India and Indonesia.&lt;/p&gt;
&lt;p&gt;An rOpenSci unconference (unconf) is about building - building software, tools, but more importantly &lt;em&gt;community&lt;/em&gt;. It operates on the premise that we all belong.&lt;/p&gt;</description></item><item><title>Working with audio in R using av</title><link>https://ropensci.org/blog/2020/02/03/av-audio/</link><pubDate>Mon, 03 Feb 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2020/02/03/av-audio/</guid><description>
&lt;p&gt;The latest version of the rOpenSci &lt;a href="https://docs.ropensci.org/av"&gt;av package&lt;/a&gt; includes some useful new tools for working with audio data. We have added functions for reading, cutting, converting, transforming, and plotting audio data in any popular audio / video format (mp3, mkv, aac, etc).&lt;/p&gt;
&lt;p&gt;The functionality can either be used by itself, or to prepare audio data for further analysis in R using other packages. We hope this clears an important hurdle to use R for research on speech, music, and &lt;a href="https://youtu.be/F8Zt3mYlOqU"&gt;whale mating calls&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>tabulizer for parsing block-text from .pdf</title><link>https://ropensci.org/usecases/tabulizer-for-parsing-block-text-from-pdf/</link><pubDate>Sat, 01 Feb 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/tabulizer-for-parsing-block-text-from-pdf/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://github.com/ropensci/tabulizer"&gt;tabulizer&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case*
&lt;/h4&gt;&lt;p&gt;Goal: extract certain block of data from different sections of the .pdf&lt;/p&gt;
&lt;p&gt;Strategy: use split-apply-combine approach via &lt;code&gt;locate_areas()&lt;/code&gt; (to get box coordinates of sections of interest) and then &lt;code&gt;extract_tables()&lt;/code&gt; to get the data with the section.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;code&gt;locate_areas()&lt;/code&gt; demo&lt;/strong&gt;
&lt;img src="https://ropensci.org/usecases/tabulizer-for-parsing-block-text-from-pdf/tabulizer-for-parsing-block-text-from-pdf.gif" alt="tabulizer-demo|601x500"&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Code snippet&lt;/strong&gt;&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-r" data-lang="r"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# |- fxn ----&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# data munge function for map() later&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="n"&gt;CleanHeader&lt;/span&gt; &lt;span class="o"&gt;&amp;lt;-&lt;/span&gt; &lt;span class="kr"&gt;function&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;tbl&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="n"&gt;tbl&lt;/span&gt; &lt;span class="o"&gt;%&amp;gt;%&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="n"&gt;tidyr&lt;/span&gt;&lt;span class="o"&gt;::&lt;/span&gt;&lt;span class="nf"&gt;pivot_longer&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="n"&gt;cols&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;idx&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;%&amp;gt;%&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="n"&gt;dplyr&lt;/span&gt;&lt;span class="o"&gt;::&lt;/span&gt;&lt;span class="nf"&gt;group_by&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;name&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;%&amp;gt;%&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="n"&gt;dplyr&lt;/span&gt;&lt;span class="o"&gt;::&lt;/span&gt;&lt;span class="nf"&gt;filter&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;value&lt;/span&gt; &lt;span class="o"&gt;!=&lt;/span&gt; &lt;span class="s"&gt;&amp;#34;&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;%&amp;gt;%&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="n"&gt;dplyr&lt;/span&gt;&lt;span class="o"&gt;::&lt;/span&gt;&lt;span class="nf"&gt;summarise&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;value&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nf"&gt;paste0&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;value&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;collapse&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="s"&gt;&amp;#34;:&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;))&lt;/span&gt; &lt;span class="o"&gt;%&amp;gt;%&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="n"&gt;tidyr&lt;/span&gt;&lt;span class="o"&gt;::&lt;/span&gt;&lt;span class="nf"&gt;separate&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;value&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nf"&gt;c&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s"&gt;&amp;#34;cat&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s"&gt;&amp;#34;data&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;),&lt;/span&gt; &lt;span class="n"&gt;sep&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="s"&gt;&amp;#34;:&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;extra&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="s"&gt;&amp;#34;merge&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;%&amp;gt;%&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="n"&gt;dplyr&lt;/span&gt;&lt;span class="o"&gt;::&lt;/span&gt;&lt;span class="nf"&gt;mutate_at&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nf"&gt;vars&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;data&lt;/span&gt;&lt;span class="p"&gt;),&lt;/span&gt; &lt;span class="n"&gt;stringr&lt;/span&gt;&lt;span class="o"&gt;::&lt;/span&gt;&lt;span class="n"&gt;str_remove&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s"&gt;&amp;#34;:&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;%&amp;gt;%&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="n"&gt;dplyr&lt;/span&gt;&lt;span class="o"&gt;::&lt;/span&gt;&lt;span class="nf"&gt;select&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;cat&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;data&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# |- data ----&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="n"&gt;file&lt;/span&gt; &lt;span class="o"&gt;&amp;lt;-&lt;/span&gt; &lt;span class="s"&gt;&amp;#34;./ropensci_white.pdf&amp;#34;&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# get the box coordinates via interactive selection; this info is then used in extract_tables() area args&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nf"&gt;locate_areas&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;file&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;pages&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="m"&gt;1&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# extract data&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="n"&gt;header_raw&lt;/span&gt; &lt;span class="o"&gt;&amp;lt;-&lt;/span&gt; &lt;span class="nf"&gt;extract_tables&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;f&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;pages&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="m"&gt;1&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="n"&gt;area&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nf"&gt;list&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nf"&gt;c&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="m"&gt;74&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="m"&gt;88&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="m"&gt;128&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="m"&gt;522&lt;/span&gt;&lt;span class="p"&gt;)),&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="n"&gt;guess&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="kc"&gt;FALSE&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# data munge; data/application specific&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="n"&gt;header_raw[[1]]&lt;/span&gt; &lt;span class="o"&gt;%&amp;gt;%&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="n"&gt;tibble&lt;/span&gt;&lt;span class="o"&gt;::&lt;/span&gt;&lt;span class="nf"&gt;as_tibble&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt; &lt;span class="o"&gt;%&amp;gt;%&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="n"&gt;janitor&lt;/span&gt;&lt;span class="o"&gt;::&lt;/span&gt;&lt;span class="nf"&gt;remove_empty&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s"&gt;&amp;#34;cols&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;%&amp;gt;%&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="n"&gt;dplyr&lt;/span&gt;&lt;span class="o"&gt;::&lt;/span&gt;&lt;span class="nf"&gt;mutate&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;idx&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nf"&gt;cumsum&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;stringr&lt;/span&gt;&lt;span class="o"&gt;::&lt;/span&gt;&lt;span class="nf"&gt;str_detect&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;V1&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s"&gt;&amp;#34;Section Marker&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;)))&lt;/span&gt; &lt;span class="o"&gt;%&amp;gt;%&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="n"&gt;dlpyr&lt;/span&gt;&lt;span class="o"&gt;::&lt;/span&gt;&lt;span class="nf"&gt;group_split&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;idx&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;%&amp;gt;%&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="n"&gt;purrr&lt;/span&gt;&lt;span class="o"&gt;::&lt;/span&gt;&lt;span class="nf"&gt;map_dfr&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;CleanHeader&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;h4&gt;
Image
&lt;/h4&gt;&lt;p&gt;Sample .pdf where coloured boxes represent sections of interest to extract data from.&lt;/p&gt;</description></item><item><title>Accessing, wrangling and plotting global weather data (for free!)</title><link>https://ropensci.org/usecases/accessing-wrangling-and-plotting-global-weather-data-for-free/</link><pubDate>Thu, 30 Jan 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/accessing-wrangling-and-plotting-global-weather-data-for-free/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/rnoaa/"&gt;rnoaa&lt;/a&gt;, &lt;a href="https://docs.ropensci.org/lawn/"&gt;lawn&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://www.ecologi.st/post/weather/"&gt;https://www.ecologi.st/post/weather/&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
Image
&lt;/h4&gt;&lt;p&gt;&lt;em&gt;&lt;img src="https://ropensci.org/usecases/accessing-wrangling-and-plotting-global-weather-data-for-free/accessing-wrangling-and-plotting-global-weather-data-for-free.png" alt="pretty_ghcnd-1|689x492"&gt;&lt;/em&gt;&lt;/p&gt;
&lt;h4&gt;
Sector
&lt;/h4&gt;&lt;p&gt;academic&lt;/p&gt;
&lt;h4&gt;
Field(s) of application
&lt;/h4&gt;&lt;p&gt;ecology, climatology, meteorology&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;Search, extract, wrangle and plot weather data from NOAA&amp;rsquo;s archives using South Africa as a use case. This is particularly valuable for South Africa because our national weather service charges for their data. Thanks @sckottie and others that have contributed to these packages!&lt;/p&gt;</description></item><item><title>Call BEAST2 for Bayesian evolutionary analysis from R</title><link>https://ropensci.org/blog/2020/01/28/babette/</link><pubDate>Tue, 28 Jan 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2020/01/28/babette/</guid><description>
&lt;p&gt;&lt;a href="https://docs.ropensci.org/babette/"&gt;babette&lt;/a&gt; &lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt; is a package to work with BEAST2 &lt;sup id="fnref:2"&gt;&lt;a href="#fn:2" class="footnote-ref" role="doc-noteref"&gt;2&lt;/a&gt;&lt;/sup&gt;,
a software platform for Bayesian evolutionary analysis from R.&lt;/p&gt;
&lt;p&gt;babette is a spin-off of my own academic research.
As a PhD I work on models of diversification: mathematical descriptions
of how species form new species. Instead of working on a species'
individuals, I work on species as evolutionary lineages.
A good way to show the evolutionary relationships between species
are phylogenies. For example, this is a phylogeny, with four species,
eloquently named &amp;lsquo;1&amp;rsquo;, &amp;lsquo;2&amp;rsquo;, &amp;lsquo;3&amp;rsquo; and &amp;lsquo;4&amp;rsquo;:&lt;/p&gt;</description></item><item><title>mapping the location of biogeography researchers with `refsplitr`</title><link>https://ropensci.org/usecases/mapping-the-location-of-biogeography-researchers-with-refsplitr/</link><pubDate>Tue, 28 Jan 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/mapping-the-location-of-biogeography-researchers-with-refsplitr/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used
&lt;/h4&gt;&lt;p&gt;package &lt;a href="https://github.com/ropensci/refsplitr"&gt;refsplitr&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
URL for use case
&lt;/h4&gt;&lt;p&gt;Eichhorn, M. P, Baker, K., &amp;amp; Griffiths, M. (2019). Steps towards decolonising biogeography. &lt;em&gt;Frontiers of Biogeography&lt;/em&gt; . &lt;a href="http://dx.doi.org/10.21425/F5FBG44795"&gt;http://dx.doi.org/10.21425/F5FBG44795&lt;/a&gt; Retrieved from &lt;a href="https://escholarship.org/uc/item/2k00787j"&gt;https://escholarship.org/uc/item/2k00787j&lt;/a&gt;.&lt;/p&gt;
&lt;h4&gt;
Image
&lt;/h4&gt;&lt;p&gt;An image from the authors&amp;rsquo; &lt;a href="https://treesinspace.com/2020/01/23/decolonise-biogeography/"&gt;blog post&lt;/a&gt; about the paper; the map of author locations was generated with &lt;code&gt;refsplitr&lt;/code&gt;
&lt;img src="https://ropensci.org/usecases/mapping-the-location-of-biogeography-researchers-with-refsplitr/mapping-the-location-of-biogeography-researchers-with-refsplitr.png" alt="image|441x500"&gt;.&lt;/p&gt;
&lt;h4&gt;
Sector
&lt;/h4&gt;&lt;p&gt;academic&lt;/p&gt;
&lt;h4&gt;
Field(s) of application
&lt;/h4&gt;&lt;p&gt;biogeography, ecology, bibliometrics, scientometrics&lt;/p&gt;</description></item><item><title>rOpenSci 2019 Code of Conduct Transparency Report</title><link>https://ropensci.org/blog/2020/01/16/transparency2019/</link><pubDate>Thu, 16 Jan 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2020/01/16/transparency2019/</guid><description>
&lt;p&gt;In January 2019, we &lt;a href="https://ropensci.org/blog/2019/01/14/conduct/"&gt;announced&lt;/a&gt; the release of rOpenSci&amp;rsquo;s &lt;a href="https://ropensci.org/code-of-conduct"&gt;Code of Conduct version 2.0&lt;/a&gt;. This includes a named Committee, greater detail about unacceptable behaviors, instructions on how to make a report, and information on how reports are handled. We are committed to transparency with our community while upholding of victims and people who report incidents.&lt;/p&gt;
&lt;p&gt;Our Code of Conduct applies to all people participating in the rOpenSci community, including rOpenSci staff and leadership. It applies to all modes of interaction online including GitHub project repositories, the rOpenSci discussion forum, Slack, Community Calls, and in person at rOpenSci-hosted events or events officially endorsed by rOpenSci, including social gatherings affiliated with an event.&lt;/p&gt;</description></item><item><title>rOpenSci Code of Conduct Annual Review</title><link>https://ropensci.org/blog/2020/01/16/conduct/</link><pubDate>Thu, 16 Jan 2020 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2020/01/16/conduct/</guid><description>
&lt;p&gt;One year ago, we released our &lt;a href="https://ropensci.org/blog/2019/01/14/conduct/"&gt;new Code of Conduct&lt;/a&gt;. At that time, the Code of Conduct Committee (authors of this post) agreed to do an annual review of the text, reporting form, and our internal guidelines.&lt;/p&gt;
&lt;p&gt;We have made one change to the Code of Conduct text. Because some people who have experienced abuse prefer not to label themselves as a victim, in &amp;ldquo;We are committed to transparency with our community while upholding the privacy of victims&amp;rdquo; we edited to &amp;ldquo;&amp;hellip; upholding the privacy of victims and people who report incidents&amp;rdquo;.&lt;/p&gt;</description></item><item><title>Thank You, 2019</title><link>https://ropensci.org/blog/2019/12/23/thankyou/</link><pubDate>Mon, 23 Dec 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/12/23/thankyou/</guid><description>
&lt;p&gt;We mean it.&lt;/p&gt;
&lt;p&gt;On behalf of rOpenSci, thank you to everyone who has contributed their creativity, curiosity, smarts, and time in the last year. We are fortunate to have paid &lt;a href="https://ropensci.org/about/#team"&gt;staff&lt;/a&gt; who work to build technical and social infrastructure to lower barriers to working with research data. But it is our community, built on trust, that binds us together and helps us see who we are working for.&lt;/p&gt;
&lt;p&gt;Many people have submitted their R packages for software peer review (31)&lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt;, reviewed those packages (~60), contributed some code or documentation to a package (117 people made their first code contribution to rOpenSci this year), (co-)authored a &lt;a href="https://ropensci.org/archive/"&gt;blog post or tech note&lt;/a&gt; about their package or an rOpenSci resource (48 authors), shared a &lt;a href="https://discuss.ropensci.org/c/usecases/"&gt;use case&lt;/a&gt; to help package authors see how their work is being used and help other users imagine how they can apply it (26 people), attended a &lt;a href="https://ropensci.org/commcalls/"&gt;Community Call&lt;/a&gt; (331 people in 23 countries), cited our software (306 citations of 122 packages), asked or answered questions, explored project ideas, or gave us a generous shoutout in a talk, a post, or on Twitter.&lt;/p&gt;</description></item><item><title>Want to Intern with rOpenSci’s Community Manager?</title><link>https://ropensci.org/blog/2019/12/23/community-intern/</link><pubDate>Mon, 23 Dec 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/12/23/community-intern/</guid><description>
&lt;p&gt;Want to get some hands-on insights into running an open source community? Here’s an opportunity to work with me, rOpenSci’s Community Manager, on some non-code &lt;a href="https://ropensci.org/community/"&gt;community-related work&lt;/a&gt;. I am looking for someone to work 1 day a week for 12 to 14 weeks.&lt;/p&gt;
&lt;p&gt;Working alongside rOpenSci’s Community Manager, Stefanie Butland, you will use guidelines and checklists to help run some of our established programs like our &lt;a href="https://ropensci.org/blog/"&gt;Blog&lt;/a&gt; and &lt;a href="https://ropensci.org/commcalls/"&gt;Community Calls&lt;/a&gt;. Tasks include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Reviewing and editing community-contributed blog posts via Git and GitHub, publishing them to our &lt;a href="https://github.com/ropensci/roweb2"&gt;website&lt;/a&gt;, and drafting and scheduling tweets to promote them&lt;/li&gt;
&lt;li&gt;Publishing information on upcoming Community Calls to the rOpenSci website, promoting them through multiple channels, and post-Call video editing&lt;/li&gt;
&lt;li&gt;Monitoring social media for use cases of rOpenSci packages or resources, encouraging people to share those in our &lt;a href="https://discuss.ropensci.org/c/usecases/"&gt;public forum&lt;/a&gt;, and scheduling tweets to promote them&lt;/li&gt;
&lt;li&gt;Drafting and scheduling tweets when an rOpenSci package is featured in RViews Top 40, highlighted in R-Weekly monthly news, or similar digests&lt;/li&gt;
&lt;li&gt;Sharing your opinions with us on how we can improve any of these&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Who are you?&lt;/strong&gt; You are familiar with R communities, understand that it’s &lt;em&gt;people&lt;/em&gt; that make software, and you have a sense of community building with a “what’s it like to be you” perspective. You have a working knowledge of Git and GitHub, are skilled in written and spoken communication, grammar, and editing in English and are comfortable communicating on Twitter.&lt;/p&gt;</description></item><item><title>2 Months in 2 Minutes - rOpenSci News, December 2019</title><link>https://ropensci.org/blog/2019/12/20/news-dec2019/</link><pubDate>Fri, 20 Dec 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/12/20/news-dec2019/</guid><description>
&lt;p&gt; &lt;/p&gt;
&lt;h3&gt;
rOpenSci HQ
&lt;/h3&gt;&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;rOpenSci Announces a &lt;a href="https://ropensci.org/blog/2019/11/06/scientific-package-ecosystem/"&gt;New $896k Award&lt;/a&gt; From The Gordon and Betty Moore Foundation to Improve the Scientific Package Ecosystem for R.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;We’re excited to announce a new member of our team! &lt;a href="https://ropensci.org/blog/2019/12/03/mark-padgham/"&gt;Introducing Mark Padgham&lt;/a&gt;, rOpenSci’s new Software Research Scientist&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href="https://ropensci.org/blog/2019/11/25/numfocus-awards/"&gt;NumFOCUS recognizes Melina Vidoni and Will Landau&lt;/a&gt; for their contributions to rOpenSci.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Videos, speaker&amp;rsquo;s slides, resources and collaborative notes from our Community Call on &lt;a href="https://ropensci.org/commcalls/2019-12-05/"&gt;Testing in R&lt;/a&gt; are posted.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;What would &lt;strong&gt;you&lt;/strong&gt; like to hear about in an rOpenSci Community Call? We are &lt;a href="https://github.com/ropensci-org/community-calls"&gt;soliciting your emoji-votes and new ideas&lt;/a&gt; for Community Call topics and speakers.&lt;/p&gt;</description></item><item><title>We cleaned our website URLs with R!</title><link>https://ropensci.org/blog/2019/12/19/urls-tidying/</link><pubDate>Thu, 19 Dec 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/12/19/urls-tidying/</guid><description>
&lt;p&gt;Last year we reported on &lt;a href="https://ropensci.org/technotes/2018/09/05/commonmark/"&gt;the joy of using commonmark and xml2 to parse
Markdown content, like the source of this website built with
Hugo&lt;/a&gt;, in particular &lt;a href="https://ropensci.org/technotes/2018/09/05/commonmark/#urls-parsing"&gt;to extract
links&lt;/a&gt;,
at the time merely to count them. How about we go a bit further and use
the same approach to find links to be fixed? In this tech note we shall
report our experience using R to find broken/suboptimal links and fix
them.&lt;/p&gt;</description></item><item><title>HTTP testing in R: overview of tools and new features</title><link>https://ropensci.org/blog/2019/12/11/http-testing/</link><pubDate>Wed, 11 Dec 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/12/11/http-testing/</guid><description>
&lt;p&gt;Testing is a crucial component to any software package. Testing makes sure
that your code does what you expect it to do; and importantly, makes it safer to make
changes moving forward because a good test suite will tell you if a change has broken
existing functionality. Our recent &lt;a href="https://ropensci.org/commcalls/2019-12-05/"&gt;community call on testing&lt;/a&gt; is a nice
place to get started with testing.&lt;/p&gt;
&lt;p&gt;One way to make testing even harder is through including HTTP requests. This adds
complexity for many reasons:&lt;/p&gt;</description></item><item><title>How to precompute package vignettes or pkgdown articles</title><link>https://ropensci.org/blog/2019/12/08/precompute-vignettes/</link><pubDate>Sun, 08 Dec 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/12/08/precompute-vignettes/</guid><description><i><a href="https://ropensci.org/es/blog/2019/12/08/precompute-vignettes/">Read it in: Español</a>.</i><i><a href="https://ropensci.org/pt/blog/2019/12/08/precompute-vignettes/">Read it in: Português</a>.</i>
&lt;p&gt;As of earlier this year, we are now &lt;a href="https://ropensci.org/technotes/2019/06/07/ropensci-docs/"&gt;automatically building&lt;/a&gt; binaries and pkgdown documentation for &lt;a href="https://docs.ropensci.org"&gt;all rOpenSci packages&lt;/a&gt;. One issue we encountered is that some packages include vignettes that require some special tools/data/credentials, which are unavailable on generic build servers.&lt;/p&gt;
&lt;p&gt;This post explains how to include such vignettes and articles in your package.&lt;/p&gt;
&lt;h2&gt;
On package vignettes
&lt;/h2&gt;&lt;p&gt;By default, R automatically recreates vignettes during &lt;code&gt;R CMD check&lt;/code&gt; or when generating pkgdown sites by running all R code. This is useful because it provides some extra testing of your code and ensures that documentation is reproducible. However, sometimes it is not a good idea to run the code on every build server, every time. For example:&lt;/p&gt;</description></item><item><title>Last Night, Testing Saved my Life</title><link>https://ropensci.org/commcalls/2019-12-05/</link><pubDate>Wed, 04 Dec 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/commcalls/2019-12-05/</guid><description>
&lt;p&gt;To the uninitiated, software testing may seem variously boring, daunting or bogged down in obscure terminology. However, it has the potential to be enormously useful for people developing software at any level of expertise, and can often be put into practice with relatively little effort.&lt;/p&gt;
&lt;p&gt;Our 1-hour Call will include two speakers and at least 20 minutes for Q &amp;amp; A.&lt;/p&gt;
&lt;p&gt;As someone with a background in science, not software engineering, Steffi LaZerte will share her experiences using automated testing in R to ensure that packages do what they&amp;rsquo;re supposed to do, on all the operating systems they&amp;rsquo;re supposed to do it on, and that they handle weird stuff gracefully.&lt;/p&gt;</description></item><item><title>Introducing Mark Padgham, rOpenSci’s new Software Research Scientist</title><link>https://ropensci.org/blog/2019/12/03/mark-padgham/</link><pubDate>Tue, 03 Dec 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/12/03/mark-padgham/</guid><description>
&lt;p&gt;We’re thrilled to be introducing a new member of our team. Mark Padgham has joined rOpenSci as a Software Research Scientist working full-time from Münster, Germany. Mark will play a key role in research and development of statistical software standards and expanding our efforts in software peer review, enabled by &lt;a href="https://ropensci.org/blog/2019/07/15/expanding-software-review/"&gt;new funding&lt;/a&gt; from the Sloan Foundation. He will work closely with &lt;a href="https://ropensci.org/authors/noam-ross/"&gt;Noam Ross&lt;/a&gt;, rOpenSci Leadership team member, and Scientist at EcoHealth Alliance and &lt;a href="https://ropensci.org/authors/karthik-ram/"&gt;Karthik Ram&lt;/a&gt;, rOpenSci Project Lead.&lt;/p&gt;</description></item><item><title>Batch image manipulation using magick</title><link>https://ropensci.org/usecases/batch-image-manipulation-using-magick/</link><pubDate>Tue, 26 Nov 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/batch-image-manipulation-using-magick/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/magick/"&gt;magick&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://github.com/roryspanton/batch-magick"&gt;https://github.com/roryspanton/batch-magick&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
Sector
&lt;/h4&gt;&lt;p&gt;Any&lt;/p&gt;
&lt;h4&gt;
Field(s) of application
&lt;/h4&gt;&lt;p&gt;Cognitive psychology - or anything else with images!&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;I used magick in conjunction with functions from purrr (tidyverse) to manipulate and convert multiple images concisely and efficiently. This simple framework allows the user to read any number of images in magick supported formats, perform the same magick manipulations on all of them, and export them as different file types (if desired), with neat file names. This automates the potentially long and tedious process of performing the same manipulation on large sets of images.&lt;/p&gt;</description></item><item><title>rnassqs: accessing USDA agricultural data via API</title><link>https://ropensci.org/blog/2019/11/26/rnassqs/</link><pubDate>Tue, 26 Nov 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/11/26/rnassqs/</guid><description>
&lt;p&gt;The United States Deparment of Agriculture National Agricultural
Statistics Service (&lt;a href="https://www.nass.usda.gov/"&gt;USDA-NASS&lt;/a&gt;) provides a wide range of agricultural
data that includes animal, crop, demographic, economic, and
environmental measures across a number of geographies and time periods.
This data is available by direct download or queriable via the
&lt;a href="https://quickstats.nass.usda.gov/"&gt;Quick Stats&lt;/a&gt; interface. While
the Quick Stats tool puts a large amount of data into the hands
of users, the interface can be frustrating, especially when trying
to access more than 50,000 records or hoping to automate downloading
data when new data is released. I developed
&lt;a href="https://ropensci.github.io/rnassqs/"&gt;rnassqs&lt;/a&gt; as a solution to
these frustrations. rnassqs provides a simple R interface for
the Quick Stats API. By iterating over a set of parameters,
R users can make processing NASS data reproducible and automated.&lt;/p&gt;</description></item><item><title>Analyzing invoice data from Elsevier relative to hybrid open access</title><link>https://ropensci.org/usecases/analyzing-invoice-data-from-elsevier-relative-to-hybrid-open-access/</link><pubDate>Mon, 25 Nov 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/analyzing-invoice-data-from-elsevier-relative-to-hybrid-open-access/</guid><description>
&lt;h4&gt;
Package or resource used
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/rcrossref/"&gt;rcrossref&lt;/a&gt;, &lt;a href="https://docs.ropensci.org/crminer/"&gt;crminer&lt;/a&gt;, &lt;a href="https://docs.ropensci.org/tabulizer/"&gt;tabulizer&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;URL or code snippet for your use case&lt;/strong&gt;*
&lt;a href="https://subugoe.github.io/scholcomm_analytics/posts/elsevier_invoice/"&gt;https://subugoe.github.io/scholcomm_analytics/posts/elsevier_invoice/&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Sector&lt;/strong&gt;
Academic&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Field(s) of application&lt;/strong&gt;
Scholarly Communications Analytics, Open Access Monitoring, Licensing in Libraries&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;What did you do?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;I used several rOpenSci packages to mine Elsevier full-texts for invoice data relative to open access articles in hybrid journals. Such evidence is critical to keep track of funding streams for open access publications. Academic publishers rarely make publication fee spending for hybrid journals transparent. Surprisingly, Elsevier is a notable exception sharing this data.&lt;/p&gt;</description></item><item><title>NumFOCUS recognizes Melina Vidoni and Will Landau for their contributions to rOpenSci</title><link>https://ropensci.org/blog/2019/11/25/numfocus-awards/</link><pubDate>Mon, 25 Nov 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/11/25/numfocus-awards/</guid><description>
&lt;p&gt;rOpenSci thrives because of volunteer contributions from community members - submitting and reviewing R packages, serving as editors for software peer review, writing blog posts, sharing information about packages and resources, contributing code and documentation and answering others&amp;rsquo; questions. Recently our fiscal sponsor, NumFOCUS, gave us an opportunity to nominate two contributors for recognition at the NumFOCUS annual summit. Sometimes all we can do is publicly express our gratitude for the people who help make our software robust and sustainable, and make our community a welcoming place that adds value to people&amp;rsquo;s experiences.&lt;/p&gt;</description></item><item><title>workloopR: Analysis of work loops and other data from muscle physiology experiments in R</title><link>https://ropensci.org/blog/2019/11/14/workloopr-release/</link><pubDate>Thu, 14 Nov 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/11/14/workloopr-release/</guid><description>
&lt;p&gt;Studies of muscle physiology often rely on closed-source, proprietary software for not only recording data but also for data wrangling and analyses. Although specialized software might be necessary to record data from highly-specialized equipment, data wrangling and analyses should be free from this constraint. It&amp;rsquo;s becoming more common for researchers to provide code along with published papers (but usually as Matlab scripts&amp;hellip;ugh), but it is still typical for most analyses to be performed with code that stays in-house. Even worse is when some of the steps are carried out in a non-reproducible way, like needing to click and drag sliders across a screen (&lt;em&gt;by hand!!&lt;/em&gt;) to select a data range of interest.&lt;/p&gt;</description></item><item><title>Community Call - Last Night, Testing Saved my Life</title><link>https://ropensci.org/blog/2019/11/12/commcall-dec2019/</link><pubDate>Tue, 12 Nov 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/11/12/commcall-dec2019/</guid><description>
&lt;p&gt;To the uninitiated, software testing may seem variously boring, daunting or bogged down in obscure terminology. However, it has the potential to be enormously useful for people developing software at any level of expertise, and can often be put into practice with relatively little effort.&lt;/p&gt;
&lt;p&gt;Our 1-hour Call will include two speakers and at least 20 minutes for Q &amp;amp; A.&lt;/p&gt;
&lt;p&gt;As someone with a background in science, not software engineering, &lt;a href="#speakers"&gt;&lt;strong&gt;Steffi LaZerte&lt;/strong&gt;&lt;/a&gt; will share her experiences using automated testing in R to ensure that packages do what they&amp;rsquo;re supposed to do, on all the operating systems they&amp;rsquo;re supposed to do it on, and that they handle weird stuff gracefully.&lt;/p&gt;</description></item><item><title>ERDDAP servers use case: tidync and rerddap</title><link>https://ropensci.org/usecases/erddap-servers-use-case-tidync-and-rerddap/</link><pubDate>Thu, 07 Nov 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/erddap-servers-use-case-tidync-and-rerddap/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://github.com/ropensci/rerddap"&gt;rerddap&lt;/a&gt; and &lt;a href="https://github.com/ropensci/tidync"&gt;tidync&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case*
&lt;/h4&gt;&lt;p&gt;Original Post: &lt;a href="https://twitter.com/u_ribo/status/1191685777660362752"&gt;https://twitter.com/u_ribo/status/1191685777660362752&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Source Code: &lt;a href="https://github.com/uribo/30DayMapChallenge/blob/45283ace68005542bcfa6a35c2a6910500c5f4fc/day5.R"&gt;https://github.com/uribo/30DayMapChallenge/blob/45283ace68005542bcfa6a35c2a6910500c5f4fc/day5.R&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
Image
&lt;/h4&gt;&lt;p&gt;&lt;img src="https://ropensci.org/usecases/erddap-servers-use-case-tidync-and-rerddap/erddap-servers-use-case-tidync-and-rerddap.jpeg" alt="day05_sst|690x246"&gt;&lt;/p&gt;
&lt;h4&gt;
Field(s) of application
&lt;/h4&gt;&lt;p&gt;data visualization, spatial&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;NOAA SST observation data was searched and acquired with {rerddap}, and netCDF format files were processed and visualized with {tidync}.&lt;/p&gt;</description></item><item><title>rOpenSci Announces a New Award From The Gordon and Betty Moore Foundation to Improve the Scientific Package Ecosystem for R</title><link>https://ropensci.org/blog/2019/11/06/scientific-package-ecosystem/</link><pubDate>Wed, 06 Nov 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/11/06/scientific-package-ecosystem/</guid><description>
&lt;p&gt;Today we are pleased to announce that we have received new funding from the &lt;a href="https://www.moore.org/initiative-strategy-detail?initiativeId=data-driven-discovery"&gt;Gordon and Betty Moore Foundation&lt;/a&gt;. The $894k grant will help us improve infrastructure for R packages and enable us to move towards a &lt;em&gt;science first&lt;/em&gt; package ecosystem for the R community. You may have already noticed some developments on this front when we announced &lt;a href="https://ropensci.org/technotes/2019/06/07/ropensci-docs/"&gt;our automated documentation server&lt;/a&gt; back in June. Over the coming months we plan to roll out more tools and services to make it easier to maintain and distribute packages while capturing the impact of such work.&lt;/p&gt;</description></item><item><title>tidync: scientific array data from NetCDF in R</title><link>https://ropensci.org/blog/2019/11/05/tidync/</link><pubDate>Tue, 05 Nov 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/11/05/tidync/</guid><description>
&lt;p&gt;In May 2019 version 0.2.0 of &lt;a href="https://docs.ropensci.org/tidync/"&gt;tidync&lt;/a&gt; was approved by rOpenSci and accepted to CRAN. Here we provide a &lt;a href="#overview"&gt;quick overview&lt;/a&gt; of the typical workflow with some pseudo-code for the main functions in tidync. This overview is enough to read if you just want to try out the package on your own data. The tidync package is focussed on &lt;em&gt;efficient data extraction&lt;/em&gt; for developing your own software, and this somewhat long post takes the time to explain the concepts in detail.&lt;/p&gt;</description></item><item><title>Reproducible CV using rorcid</title><link>https://ropensci.org/usecases/reproducible-cv-using-rorcid/</link><pubDate>Sat, 02 Nov 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/reproducible-cv-using-rorcid/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://cran.r-project.org/web/packages/rorcid/index.html"&gt;rorcid&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
Sector
&lt;/h4&gt;&lt;p&gt;Public relations&lt;/p&gt;
&lt;h4&gt;
Field
&lt;/h4&gt;&lt;p&gt;Reproducible science&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;A curriculum vitae is really a set of lists. It would be fantastic to have a reproducible CV that capitalizes on R to re-populate works to a table. I examined the capacity of rorcid as a mechanism to scrape works from my ORCID profile, tidy a bit include filter to papers only for now, and then pull that table into an R Markdown and knit out a clean CV to pdf. Seems like a viable strategy. I co-tested wosr as an alternative. &lt;a href="https://cran.r-project.org/web/packages/wosr/index.html"&gt;https://cran.r-project.org/web/packages/wosr/index.html&lt;/a&gt;
Numerous advantages to rorcid package.&lt;/p&gt;</description></item><item><title>(Re)introducing skimr v2 - A year in the life of an open source R project</title><link>https://ropensci.org/blog/2019/10/29/skimrv2/</link><pubDate>Tue, 29 Oct 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/10/29/skimrv2/</guid><description>
&lt;p&gt;&lt;a href="https://www.youtube.com/watch?v=-LzdKH1naok"&gt;Theme song: &lt;em&gt;PSA&lt;/em&gt; by Jay-Z&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;We announced the testing version of skimr v2 on
&lt;a href="https://github.com/ropensci/skimr/issues/341"&gt;June 19, 2018&lt;/a&gt;. After more than a
year of (admittedly intermittent) work, we’re thrilled to be able to say that
the package is ready to go to CRAN. So, what happened over the last year? And
why are we so excited for v2?&lt;/p&gt;
&lt;h3&gt;
Wait, what is a “skimr”?
&lt;/h3&gt;&lt;p&gt;skimr is an R package for summarizing your data. It extends tidyverse packages,
and dplyr in particular, so that you can get a broad set of summary statistics
with a single function call. You can install a pre-release version from the
package&amp;rsquo;s &lt;a href="https://github.com/ropensci/skimr"&gt;GitHub repo&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>tidyhydat and weathercan webinar</title><link>https://ropensci.org/usecases/tidyhydat-and-weathercan-webinar/</link><pubDate>Tue, 29 Oct 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/tidyhydat-and-weathercan-webinar/</guid><description>
&lt;p&gt;I hope this is approximately what is intended here:&lt;/p&gt;
&lt;h4&gt;
Package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://github.com/ropensci/tidyhydat"&gt;tidyhydat&lt;/a&gt;, &lt;a href="https://github.com/ropensci/weathercan"&gt;weathercan&lt;/a&gt;, &lt;a href="https://github.com/ropensci/Hydrology"&gt;hydrology task view&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://cwra.org/en/introduction-to-r-webinar/"&gt;https://cwra.org/en/introduction-to-r-webinar/&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
Sector
&lt;/h4&gt;&lt;p&gt;government presented; academic and industry attendants&lt;/p&gt;
&lt;h4&gt;
Field(s) of application
&lt;/h4&gt;&lt;p&gt;hydrology, meteorology&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;I gave a 2 hours webinar for water professionals illustrating how one might use the tidyhydat and weathercan packages.&lt;/p&gt;</description></item><item><title>rmangal: making ecological networks easily accessible</title><link>https://ropensci.org/blog/2019/10/21/rmangal/</link><pubDate>Mon, 21 Oct 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/10/21/rmangal/</guid><description>
&lt;p&gt;In early September, the version 2.0.0 of &lt;a href="https://ropensci.github.io/rmangal/"&gt;rmangal&lt;/a&gt; was approved by
rOpenSci, four weeks later it made it to CRAN. Following-up on our experience we
detail below the reasons why we wrote rmangal, why we submitted our package to
rOpenSci and how the peer review improved our package.&lt;/p&gt;
&lt;h3&gt;
Mangal, a database for ecological networks
&lt;/h3&gt;&lt;p&gt;Ecological networks are defined as a set of species populations (the nodes of
the network) connected through ecological interactions (the edges). Interactions
are ecological processes in which one species affects another. Although
predation is probably the most known and documented interaction, other less
noticeable associations are just as essential to ecosystem functioning. For
instance, a mammal that unintentionally disperses viable seeds attached to its
fur might help plants to thrive. All of these interactions occur simultaneously,
shaping ecosystem functioning and making them as complex as they are
fascinating.&lt;/p&gt;</description></item><item><title>2 Months in 2 Minutes - rOpenSci News, October 2019</title><link>https://ropensci.org/blog/2019/10/17/news-oct2019/</link><pubDate>Thu, 17 Oct 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/10/17/news-oct2019/</guid><description>
&lt;h3&gt;
rOpenSci HQ
&lt;/h3&gt;&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;What would &lt;strong&gt;you&lt;/strong&gt; like to hear about in an rOpenSci Community Call? We are soliciting your &amp;ldquo;votes&amp;rdquo; and new ideas for Community Call topics and speakers. Find out how you can influence us by checking out our new &lt;a href="https://github.com/ropensci-org/community-calls"&gt;Community Calls repository&lt;/a&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Videos, speaker&amp;rsquo;s slides, resources and collaborative notes from our Community Call on &lt;a href="https://ropensci.org/commcalls/2019-09-24/"&gt;Reproducible Workflows at Scale with drake&lt;/a&gt; are posted.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Help wanted! We encourage rOpenSci package authors to help us help you get more contributors to your package. If you label an issue “help wanted” (no hyphen or emojis), those issues can be found in a &lt;a href="https://github.com/search?q=org%3Aropensci+label%3A%22help+wanted%22+state%3Aopen&amp;amp;type=Issues"&gt;search of the rOpenSci organization&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>What are Your Use Cases for rOpenSci Tools and Resources?</title><link>https://ropensci.org/blog/2019/10/15/use-cases/</link><pubDate>Tue, 15 Oct 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/10/15/use-cases/</guid><description>
&lt;p&gt;We want to know how &lt;strong&gt;you&lt;/strong&gt; use &lt;a href="https://ropensci.org/packages/"&gt;rOpenSci packages&lt;/a&gt; and resources so we can give them, their developers, and your examples more visibility.&lt;/p&gt;
&lt;p&gt;It’s valuable to both users and developers of a package to see how it has been used “in the wild”. This goes a long way to encouraging people to keep up development knowing there are others who appreciate and build on their work. This also helps people imagine how they might use a package to address their research question, and provides some code to give them a head-start.&lt;/p&gt;</description></item><item><title>cran checks API: an update</title><link>https://ropensci.org/blog/2019/10/09/cran-checks-api-update/</link><pubDate>Wed, 09 Oct 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/10/09/cran-checks-api-update/</guid><description>
&lt;p&gt;If you have an R package on CRAN, you probably know about CRAN checks. Each package on CRAN, that is not archived on CRAN&lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt;, has a checks page, like this one for &lt;code&gt;ropenaq&lt;/code&gt;:
&lt;a href="https://cloud.r-project.org/web/checks/check_results_ropenaq.html"&gt;https://cloud.r-project.org/web/checks/check_results_ropenaq.html&lt;/a&gt;&lt;/p&gt;
&lt;figure&gt;&lt;img src="https://ropensci.org/img/blog-images/2019-10-09-cran-checks-api-update/cranchecks.png"&gt;
&lt;/figure&gt;
&lt;p&gt;The table above is results of running R CMD CHECK on the package on a combination of different operating systems, R versions and compilers. CRAN maintainers presumably use these as a basis for getting in touch with maintainers when these checks are failing.&lt;/p&gt;</description></item><item><title>rOpenSci Dev Guide 0.3.0: Updates</title><link>https://ropensci.org/blog/2019/10/08/dev-guide-update-fall19/</link><pubDate>Tue, 08 Oct 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/10/08/dev-guide-update-fall19/</guid><description>
&lt;p&gt;As &lt;a href="https://ropensci.org/blog/2019/02/01/software-review-news/"&gt;announced in February&lt;/a&gt;, we now have &lt;a href="https://devguide.ropensci.org/"&gt;an online book&lt;/a&gt; containing all things related to rOpenSci software review. Our goal is to update it approximately quarterly - it&amp;rsquo;s time to present the third version. You can &lt;a href="https://devguide.ropensci.org/booknews.html"&gt;read the changelog&lt;/a&gt; or this blog post to find out what&amp;rsquo;s new in our dev guide 0.3.0!&lt;/p&gt;
&lt;h2&gt;
Updates to our policies and guidance
&lt;/h2&gt;&lt;h3&gt;
Scope
&lt;/h3&gt;&lt;p&gt;We&amp;rsquo;ve introduced an important change for anyone thinking of submitting a package. We ask authors to select a category in our &lt;a href="https://devguide.ropensci.org/policies.html#aims-and-scope"&gt;Aims and Scope&lt;/a&gt; under which to submit. We found that the &amp;ldquo;reproducibility&amp;rdquo; category was confusing, as almost any R package can be related to reproducibility. We split &amp;ldquo;reproducibility&amp;rdquo; into four new categories that fit the narrower topics it previously included. They are:&lt;/p&gt;</description></item><item><title>Academic CV using {vitae}, {scholar} to pull papers, and {tic} for building on Travis.</title><link>https://ropensci.org/usecases/academic-cv-using-vitae-scholar-to-pull-papers-and-tic-for-building-on-travis/</link><pubDate>Thu, 03 Oct 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/academic-cv-using-vitae-scholar-to-pull-papers-and-tic-for-building-on-travis/</guid><description>
&lt;h4&gt;
Package or resource used*
&lt;/h4&gt;&lt;p&gt;{vitae} and &lt;a href="https://github.com/ropensci/tic"&gt;{tic}&lt;/a&gt; - both rOpenSci Labs (and excellent).&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case*
&lt;/h4&gt;&lt;p&gt;Code: &lt;a href="https://github.com/seabbs/cv"&gt;https://github.com/seabbs/cv&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
Image
&lt;/h4&gt;&lt;p&gt;&lt;img src="https://ropensci.org/usecases/academic-cv-using-vitae-scholar-to-pull-papers-and-tic-for-building-on-travis/academic-cv-using-vitae-scholar-to-pull-papers-and-tic-for-building-on-travis.png" alt="15|586x500,100%"&gt;&lt;/p&gt;
&lt;p&gt;Link: &lt;a href="https://samabbott.co.uk/cv/cv.pdf"&gt;https://samabbott.co.uk/cv/cv.pdf&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
Sector
&lt;/h4&gt;&lt;p&gt;Academic&lt;/p&gt;
&lt;h4&gt;
Field(s) of application
&lt;/h4&gt;&lt;p&gt;Anything requiring a CV with publications.&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;Academic CV built using R - updated automatically from &lt;a href="https://scholar.google.com/citations?user=GqZm90IAAAAJ&amp;amp;hl=en"&gt;Google Scholar&lt;/a&gt; each week. See &lt;a href="https://www.samabbott.co.uk/cv/cv.pdf"&gt;here&lt;/a&gt; for the full rendered CV. All other data stored as .csv&amp;rsquo;s so can be updated on GitHub without touching the code or main document.&lt;/p&gt;</description></item><item><title>Can {drake} RAP? Promoting {drake} for pipeline management in UK government</title><link>https://ropensci.org/usecases/can-drake-rap-promoting-drake-for-pipeline-management-in-uk-government/</link><pubDate>Wed, 02 Oct 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/can-drake-rap-promoting-drake-for-pipeline-management-in-uk-government/</guid><description>
&lt;h4&gt;
Package or resource used
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/drake"&gt;drake&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case*
&lt;/h4&gt;&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.rostrum.blog/2019/07/23/can-drake-rap/"&gt;Blog post&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/matt-dray/drake-egg-rap"&gt;GitHub demo repo&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/matt-dray/drake-egg-rap/blob/a34e1e9ae9d589ef4580203a9dc7763068036689/docs/drake-presentation.pdf"&gt;Presentation about {drake} and the demo&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.rostrum.blog/2019/08/25/holepunch-drake/"&gt;Bonus blog post about launching the demo repo in Binder via Karthik Ram&amp;rsquo;s {holepunch} package&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h4&gt;
Image
&lt;/h4&gt;&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.rostrum.blog/post/2019-07-22-can-drake-rap_files/hall-of-fame.jpeg"&gt;&amp;lsquo;Drake hall of fame&amp;rsquo;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.rostrum.blog/post/2019-07-22-can-drake-rap_files/demo-report-page-short.png"&gt;Output from demo example&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.rostrum.blog/post/2019-07-22-can-drake-rap_files/dependency-outdated-static.png"&gt;Simple &lt;code&gt;drake_vis_graph()&lt;/code&gt; output showing targets that are out of date&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h4&gt;
Sector
&lt;/h4&gt;&lt;p&gt;Government&lt;/p&gt;
&lt;h4&gt;
Field(s) of application
&lt;/h4&gt;&lt;p&gt;National statistics publications&lt;/p&gt;</description></item><item><title>drake use case involving fires!</title><link>https://ropensci.org/usecases/drake-use-case-involving-fires/</link><pubDate>Fri, 27 Sep 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/drake-use-case-involving-fires/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/drake/"&gt;drake&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;ul&gt;
&lt;li&gt;&lt;a href="https://github.com/aedobbyn/nyc-fires"&gt;repo&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://aedobbyn.github.io/nyc-fires/index.html#1"&gt;slides&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/aedobbyn/nyr-2019"&gt;similar talk at NYR 2019&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h4&gt;
About
&lt;/h4&gt;&lt;p&gt;This pipeline uses &lt;a href="https://ropenscilabs.github.io/drake-manual/"&gt;&lt;code&gt;drake&lt;/code&gt;&lt;/a&gt; to pull tweets from the Twitter API and extract info on where fires are happening in New York City. It illustrates &lt;code&gt;drake&lt;/code&gt;&amp;rsquo;s &amp;ldquo;what gets done stays done&amp;rdquo; motto.&lt;/p&gt;</description></item><item><title>Updates to the rOpenSci image suite: magick, tesseract, and av</title><link>https://ropensci.org/blog/2019/09/27/ropensci-docs/</link><pubDate>Fri, 27 Sep 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/09/27/ropensci-docs/</guid><description>
&lt;p&gt;Image processing is one of the core focus areas of rOpenSci. Over the last few months we have released several major upgrades to core packages in our imaging suite, including &lt;a href="https://docs.ropensci.org/magick"&gt;magick&lt;/a&gt;, &lt;a href="https://docs.ropensci.org/tesseract"&gt;tesseract&lt;/a&gt;, and &lt;a href="https://docs.ropensci.org/av"&gt;av&lt;/a&gt;. This post highlights a few cool new features.&lt;/p&gt;
&lt;h2&gt;
Magick 2.2
&lt;/h2&gt;&lt;p&gt;The &lt;a href="https://docs.ropensci.org/magick"&gt;magick&lt;/a&gt; package is one of the most powerful packages for image processing in R. It interfaces to the ImageMagick C++ API and can takes advantage of several other R packages providing imaging functionality in R. Version 2.1 and 2.2 include a lot of small fixes and new features: the &lt;a href="https://cran.r-project.org/web/packages/magick/NEWS"&gt;NEWS&lt;/a&gt; file has the full list of changes.&lt;/p&gt;</description></item><item><title>Reproducible workflows at scale with drake</title><link>https://ropensci.org/commcalls/2019-09-24/</link><pubDate>Tue, 24 Sep 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/commcalls/2019-09-24/</guid><description>
&lt;h2&gt;
NA
&lt;/h2&gt;</description></item><item><title>citecorp: working with open citations</title><link>https://ropensci.org/blog/2019/09/17/citecorp/</link><pubDate>Tue, 17 Sep 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/09/17/citecorp/</guid><description>
&lt;p&gt;citecorp is a new (hit CRAN in late August) R package for working with data from the
&lt;a href="https://opencitations.net/corpus"&gt;OpenCitations Corpus&lt;/a&gt; (OCC).
&lt;a href="https://opencitations.net/"&gt;OpenCitations&lt;/a&gt;, run by David Shotton and Silvio Peroni,
houses the OCC, an open repository of scholarly citation data
under the very open &lt;a href="https://creativecommons.org/publicdomain/zero/1.0/"&gt;CC0 license&lt;/a&gt;. The &lt;a href="https://i4oc.org/"&gt;I4OC (Initiative for Open Citations)&lt;/a&gt;
is a collaboration between many parties, with the aim of promoting &amp;ldquo;unrestricted
availability of scholarly citation data&amp;rdquo;. Citation data is available through Crossref,
and available in R via our packages &lt;a href="https://github.com/ropensci/rcrossref"&gt;rcrossref&lt;/a&gt;, &lt;a href="https://github.com/ropensci/fulltext"&gt;fulltext&lt;/a&gt; and &lt;a href="https://github.com/ropensci/crminer"&gt;crminer&lt;/a&gt;.
Citation data is also available via the &lt;a href="https://opencitations.net/corpus"&gt;OCC&lt;/a&gt;; and this OCC data is now
available in R through the new package citecorp.&lt;/p&gt;</description></item><item><title>Use rnaturalearth to get a background map in sf format for plotting with ggplot</title><link>https://ropensci.org/usecases/use-rnaturalearth-to-get-a-background-map-in-sf-format-for-plotting-with-ggplot/</link><pubDate>Tue, 10 Sep 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/use-rnaturalearth-to-get-a-background-map-in-sf-format-for-plotting-with-ggplot/</guid><description>
&lt;p&gt;Sometimes you just need some points on map. You have lat/lon points, where are you going to get a nice background map that you can plot in R, using ggplot2 and geom_sf? R natural earth!&lt;/p&gt;
&lt;h4&gt;
Package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://github.com/ropensci/rnaturalearth"&gt;rnaturalearth&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://gist.github.com/arvi1000/13eda3ad39ed89e9e196c720864b25af"&gt;https://gist.github.com/arvi1000/13eda3ad39ed89e9e196c720864b25af&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
Image
&lt;/h4&gt;&lt;p&gt;&lt;img src="https://ropensci.org/usecases/use-rnaturalearth-to-get-a-background-map-in-sf-format-for-plotting-with-ggplot/use-rnaturalearth-to-get-a-background-map-in-sf-format-for-plotting-with-ggplot.png" alt=""&gt;&lt;/p&gt;
&lt;h4&gt;
Field(s) of application
&lt;/h4&gt;&lt;p&gt;&lt;em&gt;e.g. data visualization&lt;/em&gt;&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;&lt;em&gt;Plotted some points on a basemap, applied a map projection&lt;/em&gt;&lt;/p&gt;</description></item><item><title>Converting MedDRA Terminology to Linked Data using rdflib</title><link>https://ropensci.org/usecases/converting-meddra-terminology-to-linked-data-using-rdflib/</link><pubDate>Fri, 06 Sep 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/converting-meddra-terminology-to-linked-data-using-rdflib/</guid><description>
&lt;p&gt;As part of the &lt;a href="https://www.phuse.eu/"&gt;PhUSE&lt;/a&gt; project &lt;a href="https://github.com/phuse-org/CTDasRDF"&gt;Going Translational with Linked Data (GoTWLD)&lt;/a&gt; we use the &lt;strong&gt;rdflib&lt;/strong&gt; package to translate MedDRA terminology to Linked Data as RDF Triples.&lt;/p&gt;
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://github.com/ropensci/rdflib"&gt;rdflib&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
Use Case URL
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://github.com/phuse-org/MedDRAasRDF/blob/37992ea830c835705481db3deb894246641e00dd/doc/MedDRAConversion.md"&gt;MedDRA Terminology Conversion to RDF&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
Image
&lt;/h4&gt;&lt;p&gt;&lt;img src="https://ropensci.org/usecases/converting-meddra-terminology-to-linked-data-using-rdflib/converting-meddra-terminology-to-linked-data-using-rdflib.png" alt="MedDRA-ProgramFlow-medDRAReadAsc|630x500"&gt;&lt;/p&gt;
&lt;h4&gt;
Sector
&lt;/h4&gt;&lt;p&gt;Pharmaceutical, Biotech, Medical/Healthcare&lt;/p&gt;
&lt;h4&gt;
Field(s) of application
&lt;/h4&gt;&lt;p&gt;Medical terminology coding including Adverse Events. Biomedical research, Pharmaceutical industry.&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;Used an ontology-based approach to convert the multiple hierarchical ASCii files to a unified Linked Data Graph representation. MedDRA terminology files are under license, but the conversion R scripts are freely available to anyone who wishes to convert their MedDRA coding to Linked Data.&lt;/p&gt;</description></item><item><title>UCSCXenaTools: Retrieve Gene Expression and Clinical Information from UCSC Xena for Survival Analysis</title><link>https://ropensci.org/blog/2019/09/06/ucscxenatools-surv/</link><pubDate>Fri, 06 Sep 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/09/06/ucscxenatools-surv/</guid><description>
&lt;p&gt;The &lt;a href="https://xenabrowser.net/"&gt;UCSC Xena platform&lt;/a&gt; provides an unprecedented resource for public omics data from big projects like &lt;a href="https://www.cancer.gov/about-nci/organization/ccg/research/structural-genomics/tcga"&gt;The Cancer Genome Atlas (TCGA)&lt;/a&gt;, however, it is hard
for users to incorporate multiple datasets or data types, integrate the selected data with
popular analysis tools or homebrewed code, and reproduce analysis procedures. To address this issue, we developed an R package UCSCXenaTools for enabling data retrieval, analysis integration and reproducible research for omics data from the UCSC Xena platform&lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt;.&lt;/p&gt;</description></item><item><title>Using pdftools, tabulizer, and writexl to simplify business information handling workflow</title><link>https://ropensci.org/usecases/using-pdftools-tabulizer-and-writexl-to-simplify-business-information-handling-workflow/</link><pubDate>Tue, 27 Aug 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/using-pdftools-tabulizer-and-writexl-to-simplify-business-information-handling-workflow/</guid><description>
&lt;p&gt;Providing a script for a workflow to liberate the contents of PDFs&lt;/p&gt;
&lt;h4&gt;
Packages used
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://github.com/ropensci/pdftools"&gt;pdftools&lt;/a&gt;, &lt;a href="https://github.com/ropensci/tabulizer"&gt;tabulizer&lt;/a&gt;, &lt;a href="https://github.com/ropensci/writexl"&gt;writexl&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
Code Snippet
&lt;/h4&gt;&lt;p&gt;They have a script which, when they hit the source button, opens a select file dialog box and they pick the pdf, then it saves a word document with the full text, and an excel file of one sheet per table, in the same directory. they also have the option of coming on some R courses I regularly run if they want to start working with the information inside of R.&lt;/p&gt;</description></item><item><title>Using rOpenSci Software Peer Review Guidelines for Teaching</title><link>https://ropensci.org/blog/2019/08/27/software-peer-review-guidelines-for-teaching/</link><pubDate>Tue, 27 Aug 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/08/27/software-peer-review-guidelines-for-teaching/</guid><description>
&lt;h3&gt;
Teaching collaborative software development
&lt;/h3&gt;&lt;p&gt;In the &lt;a href="https://ubc-mds.github.io/about/"&gt;University of British Columbia&amp;rsquo;s Master of Data Science program&lt;/a&gt; one of the courses we teach is called &lt;a href="https://github.com/UBC-MDS/DSCI_524_collab-sw-dev"&gt;Collaborative Software Development, DSCI 524&lt;/a&gt;. In this course we focus on teaching how to exploit practices from collaborative software development techniques in data scientific workflows. This includes appropriate use of the software life cycle, unit testing and continuous integration, as well as packaging code for use by others.&lt;/p&gt;</description></item><item><title>Introducing Open Forensic Science in R</title><link>https://ropensci.org/blog/2019/08/20/forensic-science/</link><pubDate>Tue, 20 Aug 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/08/20/forensic-science/</guid><description>
&lt;p&gt;The free online book &lt;a href="https://sctyner.github.io/OpenForSciR/"&gt;&lt;em&gt;Open Forensic Science in R&lt;/em&gt;&lt;/a&gt; was created to foster open science practices in the forensic science community. It is comprised of eight chapters: an introduction and seven chapters covering different areas of forensic science: the validation of DNA interpretation systems, firearms analysis of bullets and casings, latent fingerprints, shoe outsole impressions, trace glass evidence, and decision-making in forensic identification tasks. The chapters of &lt;em&gt;Open Forensic Science in R&lt;/em&gt; have the same five sections: Introduction, Data, R Package(s), Drawing Conclusions, and Case Study. There is R code throughout the chapter to guide the reader along in an analysis, and the case study walks the reader through solving a forensic science problem in R, from reading the data to answering a specific question such as, &amp;ldquo;Were these two bullets fired by the same gun?&amp;rdquo;&lt;/p&gt;</description></item><item><title>Using rorcid to generate a website CV</title><link>https://ropensci.org/usecases/using-rorcid-to-generate-a-website-cv/</link><pubDate>Tue, 20 Aug 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/using-rorcid-to-generate-a-website-cv/</guid><description>
&lt;p&gt;I use rOpenSci&amp;rsquo;s &lt;strong&gt;rorcid&lt;/strong&gt; package to generate my CV for my academic website. Prior to building the website, I run a &lt;a href="https://github.com/noamross/noamross.net/blob/018ec3915dced73a7a66ea56d0ee270efc6e3bac/scripts/get-orcid-data.R"&gt;script&lt;/a&gt; with rorcid that downloads my publications, education, and work history, combines them with some additional annotation data, and saves them as YAML files. These are used by the Hugo site generator to generate my CV.&lt;/p&gt;
&lt;h4&gt;
Package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;strong&gt;rorcid&lt;/strong&gt;: &lt;a href="https://github.com/ropensci/rorcid"&gt;https://github.com/ropensci/rorcid&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://www.noamross.net/vitae/"&gt;https://www.noamross.net/vitae/&lt;/a&gt;&lt;/p&gt;</description></item><item><title>2 Months in 2 Minutes - rOpenSci News, August 2019</title><link>https://ropensci.org/blog/2019/08/15/news-aug2019/</link><pubDate>Thu, 15 Aug 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/08/15/news-aug2019/</guid><description>
&lt;h3&gt;
rOpenSci HQ
&lt;/h3&gt;&lt;ul&gt;
&lt;li&gt;rOpenSci &lt;a href="https://ropensci.org/blog/2019/07/15/expanding-software-review/"&gt;received a $678K award&lt;/a&gt; from the Sloan Foundation to expand Software Peer Review.&lt;/li&gt;
&lt;li&gt;&lt;a href="https://ropensci.org/blog/2019/07/18/ropensci-hiring/"&gt;We are hiring&lt;/a&gt; for a new position in statistical software testing and peer review.&lt;/li&gt;
&lt;li&gt;Join our next &lt;a href="https://ropensci.org/blog/2019/08/08/commcall-sep2019/"&gt;Community Call on Reproducible Workflows at Scale with drake&lt;/a&gt; September 24th.&lt;/li&gt;
&lt;li&gt;Videos, speakers&amp;rsquo; slides, resources and collaborative notes from our Community Calls on &lt;a href="https://ropensci.org/commcalls/2019-06-28/"&gt;Involving Multilingual Communities&lt;/a&gt; and &lt;a href="https://ropensci.org/commcalls/2019-07-30/"&gt;Reproducible Research with R&lt;/a&gt; are posted.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;
Software Peer Review
&lt;/h3&gt;&lt;p&gt;5 community-contributed packages passed &lt;a href="https://ropensci.org/software-review/"&gt;software peer review&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Synthesizing population time-series data from the USA Long Term Ecological Research Network</title><link>https://ropensci.org/blog/2019/08/13/popler/</link><pubDate>Tue, 13 Aug 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/08/13/popler/</guid><description>
&lt;h3&gt;
Introduction
&lt;/h3&gt;&lt;p&gt;The availability of large quantities of freely available data is revolutionizing the world of ecological research. Open data maximizes the opportunities to perform comparative analyses and meta-analyses. Such synthesis efforts will increasingly exploit &amp;ldquo;population data&amp;rdquo;, which we define here as time series of population abundance. Such population data plays a central role in testing ecological theory and guiding management decisions. One of the richest sources of open access population data is the &lt;a href="https://lternet.edu/"&gt;USA Long Term Ecological Research (LTER) Network&lt;/a&gt;. However, LTER data presents the drawback common to all ecological time-series: extreme heterogeneity derived from differences in sampling designs.
We experienced this heterogeneity first hand, upon embarking on our own comparative analysis of population data. Specifically, we noticed that heterogeneities in sampling design made datasets hard to compare, and therefore hard to search and analyze.&lt;/p&gt;</description></item><item><title>Community Call - Reproducible Workflows at Scale with drake</title><link>https://ropensci.org/blog/2019/08/08/commcall-sep2019/</link><pubDate>Thu, 08 Aug 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/08/08/commcall-sep2019/</guid><description>
&lt;p&gt;Ambitious workflows in R, such as machine learning analyses, can be difficult to manage. A single round of computation can take several hours to complete, and routine updates to the code and data tend to invalidate hard-earned results. You can enhance the maintainability, hygiene, speed, scale, and reproducibility of such projects with the drake R package. drake resolves the dependency structure of your analysis pipeline, skips tasks that are already up to date, executes the rest with optional distributed computing, and organizes the output so you rarely have to think about data files. This talk demonstrates how to create and maintain a realistic machine learning project using drake-powered automation.&lt;/p&gt;</description></item><item><title>Use of R package review guidelines in independent manuscript review</title><link>https://ropensci.org/usecases/use-of-r-package-review-guidelines-in-independent-manuscript-review/</link><pubDate>Thu, 08 Aug 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/use-of-r-package-review-guidelines-in-independent-manuscript-review/</guid><description>
&lt;h4&gt;
Package or resource used
&lt;/h4&gt;&lt;p&gt;rOpenSci &lt;a href="https://devguide.ropensci.org/"&gt;package development guide book&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://ropensci.org/blog/2019/04/18/wild-standards/"&gt;https://ropensci.org/blog/2019/04/18/wild-standards/&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
Image
&lt;/h4&gt;&lt;p&gt;&lt;img src="https://ropensci.org/usecases/use-of-r-package-review-guidelines-in-independent-manuscript-review/use-of-r-package-review-guidelines-in-independent-manuscript-review.jpeg" alt="sRKKrJ0|690x343"&gt;&lt;/p&gt;
&lt;h4&gt;
Sector
&lt;/h4&gt;&lt;p&gt;academic&lt;/p&gt;
&lt;h4&gt;
Field(s) of application
&lt;/h4&gt;&lt;p&gt;academic manuscript review&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;Quoted from Hao Ye @hye in the &lt;a href="https://ropensci.org/blog/2019/04/18/wild-standards/"&gt;blog post&lt;/a&gt;:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;When I was asked to review the code for the pavo 2.0 manuscript&lt;a href="https://ropensci.org/blog/2019/04/18/wild-standards/#fn:1"&gt;1&lt;/a&gt;, I had an initial moment of panic – I had no experience doing formal code review. Luckily, I knew that rOpenSci had a set of reviewing guidelines, and that a few MEE Applications papers had used them. The same guidelines are also used by the &lt;a href="https://joss.theoj.org/"&gt;Journal of Open Source Software&lt;/a&gt; (JOSS). Although this submission wasn’t flagged for rOpenSci review, I didn’t see a conflict with using their guidelines for my task.&lt;/p&gt;</description></item><item><title>Teaching how to create high quality R packages</title><link>https://ropensci.org/usecases/teaching-how-to-create-high-quality-r-packages/</link><pubDate>Mon, 05 Aug 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/teaching-how-to-create-high-quality-r-packages/</guid><description>
&lt;h4&gt;
Package or resource used*
&lt;/h4&gt;&lt;p&gt;rOpenSci &lt;a href="https://ropensci.github.io/dev_guide/"&gt;package development guide book&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://github.com/UBC-MDS/DSCI_524_collab-sw-dev"&gt;https://github.com/UBC-MDS/DSCI_524_collab-sw-dev&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
Sector
&lt;/h4&gt;&lt;p&gt;academic&lt;/p&gt;
&lt;h4&gt;
Field(s) of application
&lt;/h4&gt;&lt;p&gt;Data Science&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;the &lt;a href="https://ubc-mds.github.io/about/"&gt;University of British Columbia&amp;rsquo;s Master of Data Science program&lt;/a&gt; one of the courses we teach is called &lt;a href="https://github.com/UBC-MDS/DSCI_524_collab-sw-dev"&gt;DSCI 524 Collaborative Software Development&lt;/a&gt;. In this course, students have to work in teams of 3-4 to create a R package (among other things). One of the resources we recommend the students use for this is the &lt;a href="https://devguide.ropensci.org/"&gt;rOpenSci Packages: Development, Maintenance, and Peer Review&lt;/a&gt; guide. In particular, we encourage the students to go through the &lt;a href="https://devguide.ropensci.org/reviewtemplate.html"&gt;Review template&lt;/a&gt; in the appendix of that guide before they hand in their R package for final grading. Instructors and Teaching Assistants for this course also use this &lt;a href="https://devguide.ropensci.org/reviewtemplate.html"&gt;Review template&lt;/a&gt; to help give both formative feedback and guide summative assessment.&lt;/p&gt;</description></item><item><title>Reproducible Research with R</title><link>https://ropensci.org/commcalls/2019-07-30/</link><pubDate>Tue, 30 Jul 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/commcalls/2019-07-30/</guid><description/></item><item><title>rOpenSci Hiring for New Position in Statistical Software Testing and Peer Review</title><link>https://ropensci.org/blog/2019/07/18/ropensci-hiring/</link><pubDate>Thu, 18 Jul 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/07/18/ropensci-hiring/</guid><description>
&lt;p&gt;Are you passionate about statistical methods and software? If so we would love for you to join our team to dig deep into the world of statistical software packages. You’ll develop standards for evaluating and reviewing statistical tools, publish, and work closely with an international team of experts to set up a new software review system.&lt;/p&gt;
&lt;p&gt;We are seeking a creative, dedicated, and collaborative software research scientist to support a two-year project in launching a new software peer-review initiative. The software research scientist will work on the &lt;a href="https://ropensci.org/blog/2019/07/15/expanding-software-review/"&gt;Sloan Foundation supported rOpenSci project&lt;/a&gt;, with &lt;a href="https://ropensci.org/about/#team"&gt;rOpenSci staff&lt;/a&gt; and a statistical methods editorial board. They will research and develop standards and review guidelines for statistical software, publish findings, and develop R software to test packages against those standards. The software research scientist will work with staff and the board to collaborate broadly with the statistical and software communities to gather input, refine and promote the standards, and recruit editors and peer reviewers. The candidate must be self-motivated, proactive, collaborative and comfortable working openly and reproducibly with a broad online community.&lt;/p&gt;</description></item><item><title>Promoting R and rOpenSci packages in UK local government</title><link>https://ropensci.org/usecases/promoting-r-and-ropensci-packages-in-uk-local-government/</link><pubDate>Wed, 17 Jul 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/promoting-r-and-ropensci-packages-in-uk-local-government/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://github.com/ropensci-archive/ropenaq"&gt;ropenaq&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
Description
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://www.trafford.gov.uk"&gt;Trafford Council&amp;rsquo;s&lt;/a&gt; &lt;a href="https://www.trafforddatalab.io/"&gt;Trafford Data Lab&lt;/a&gt; are publishing &lt;a href="https://twitter.com/search?q=%23rstats"&gt;#rstats&lt;/a&gt; &lt;a href="https://www.trafforddatalab.io/recipes/"&gt;recipes&lt;/a&gt; for local government colleagues. The aim of the project is to embed an analytical workflow across UK local government that encourages openness, reproducibility and collaboration by promoting the use of R. We&amp;rsquo;ve used and plan to use a number of rOpenSci packages in the recipes including &lt;a href="https://cran.r-project.org/web/packages/ropenaq/index.html"&gt;ropenaq&lt;/a&gt; and &lt;a href="https://cran.r-project.org/web/packages/fingertipsR/index.html"&gt;fingertipsR&lt;/a&gt;. These particular packages provide an intuitive way of retrieving open data within R without the need to familiarise yourself with often complex APIs.&lt;/p&gt;</description></item><item><title>Querying linked data to improve public services</title><link>https://ropensci.org/usecases/querying-linked-data-to-improve-public-services/</link><pubDate>Wed, 17 Jul 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/querying-linked-data-to-improve-public-services/</guid><description>
&lt;h4&gt;
Package used
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/ghql/"&gt;ghql&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case
&lt;/h4&gt;&lt;ul&gt;
&lt;li&gt;&lt;a href="http://www.trafforddatalab.io/opengovintelligence/documentation/scan_README.html"&gt;App documentation&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://vimeo.com/311452398"&gt;App video tutorial&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/traffordDataLab/opengovintelligence/tree/master/apps/scan"&gt;App source code&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/Swirrl/cubiql/wiki/Querying-a-GraphQL-client-for-linked-data-using-R"&gt;GitHub wiki on using ghql&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://www.opengovintelligence.eu/pilots-individual/trafford/"&gt;Project description on OpenGovIntelligence project page&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://medium.com/@traffordDataLab/improving-the-discoverability-of-worklessness-data-b91bf28e6fd6"&gt;Medium post on Trafford Worklessness pilot&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://theodi.org/projects-services/projects/public-service-delivery-case-studies#1557761403632-1e730194-ee1d"&gt;Write-up by Open Data Institute&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;The &lt;a href="https://docs.ropensci.org/ghql/"&gt;ghql&lt;/a&gt; package was used to retrieve open data held in a triple store that was queryable with &lt;a href="https://github.com/Swirrl/cubiql"&gt;CubiQL&lt;/a&gt;, a &lt;a href="https://graphql.org/"&gt;GraphQL&lt;/a&gt; service. The data was visualised in a &lt;a href="https://shiny.rstudio.com/"&gt;Shiny&lt;/a&gt; application that formed part of a suite of apps used in the &lt;a href="http://www.trafforddatalab.io/opengovintelligence/"&gt;Trafford Workless Pilot&lt;/a&gt;. The pilot was part of the EU funded Horizon 2020 &lt;a href="http://www.opengovintelligence.eu/"&gt;OpenGovIntelligence&lt;/a&gt; project that used linked data to improve public services.&lt;/p&gt;</description></item><item><title>Using fingertipsR for public health data in UK local government</title><link>https://ropensci.org/usecases/using-fingertipsr-for-public-health-data-in-uk-local-government/</link><pubDate>Wed, 17 Jul 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/using-fingertipsr-for-public-health-data-in-uk-local-government/</guid><description>
&lt;h4&gt;
Package used
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://github.com/ropensci/fingertipsR"&gt;fingertipsR&lt;/a&gt; by Sebastian Fox&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case
&lt;/h4&gt;&lt;ol&gt;
&lt;li&gt;&lt;a href="https://www.trafforddatalab.io/recipes/importing_data/fingertips.html"&gt;Download local authority values for the alcohol related admissions indicator&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://medium.com/@traffordDataLab/public-health-data-at-your-fingertips-d17523664d19"&gt; Public health data at your fingertips - rate of antidepressant prescribing&lt;/a&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;h4&gt;
Image
&lt;/h4&gt;&lt;p&gt;&lt;img src="https://ropensci.org/usecases/using-fingertipsr-for-public-health-data-in-uk-local-government/using-fingertipsr-for-public-health-data-in-uk-local-government.png" alt="fingertipsr-trafford-usecase|690x476"&gt;&lt;/p&gt;
&lt;h4&gt;
Sector
&lt;/h4&gt;&lt;p&gt;government&lt;/p&gt;
&lt;h4&gt;
Field(s) of application
&lt;/h4&gt;&lt;p&gt;public health&lt;/p&gt;</description></item><item><title>Aggregating spatial data with the grainchanger package</title><link>https://ropensci.org/blog/2019/07/16/grainchanger/</link><pubDate>Tue, 16 Jul 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/07/16/grainchanger/</guid><description>
&lt;p&gt;The &lt;a href="https://docs.ropensci.org/grainchanger/"&gt;grainchanger&lt;/a&gt; package provides functionality for data aggregation to a coarser resolution via moving-window or direct methods.&lt;/p&gt;
&lt;h3&gt;
Why do we need new methods for data aggregation?
&lt;/h3&gt;&lt;p&gt;As landscape ecologists and macroecologists, we often need to aggregate data in order to harmonise datasets. In doing so, we often lose a lot of information about the spatial structure and environmental heterogeneity of data measured at finer resolution.&lt;/p&gt;
&lt;p&gt;The issues around scale disconnects are both conceptual and practical:&lt;/p&gt;</description></item><item><title>rOpenSci Announces $678K Award from the Sloan Foundation to Expand Software Peer Review</title><link>https://ropensci.org/blog/2019/07/15/expanding-software-review/</link><pubDate>Mon, 15 Jul 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/07/15/expanding-software-review/</guid><description>
&lt;p&gt;We’re delighted to announce that we have received new funding from the &lt;a href="https://sloan.org/"&gt;Alfred P. Sloan Foundation&lt;/a&gt;. The $678K grant, awarded through the Foundation&amp;rsquo;s Data &amp;amp; Computational Research program, will be used to expand our efforts in software peer review.&lt;/p&gt;
&lt;p&gt;Software peer review has become a core part of rOpenSci, helping improve scientific software quality, drive best engineering practices into scientific communities, and building community and collaboration through open, constructive reviews. We&amp;rsquo;re excited to expand our work in this important area. Here&amp;rsquo;s what we&amp;rsquo;ll be doing in the next two years with this support:&lt;/p&gt;</description></item><item><title>Community Call - Reproducible Research with R</title><link>https://ropensci.org/blog/2019/07/11/commcall-jul2019/</link><pubDate>Thu, 11 Jul 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/07/11/commcall-jul2019/</guid><description>
&lt;p&gt;Our 1-hour Call on Reproducible Research with R will include three speakers and 20 minutes for Q &amp;amp; A.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://ropensci.org/authors/ben-marwick/"&gt;&lt;strong&gt;Ben Marwick&lt;/strong&gt;&lt;/a&gt; will introduce you to a &lt;a href="https://research-compendium.science/"&gt;research compendium&lt;/a&gt;, which accompanies, enhances, or is a scientific publication providing data, code, and documentation for reproducing a scientific workflow.&lt;/p&gt;
&lt;p&gt;From &lt;a href="https://ropensci.org/authors/karthik-ram/"&gt;&lt;strong&gt;Karthik Ram&lt;/strong&gt;&lt;/a&gt; you will learn about &lt;a href="https://karthik.github.io/holepunch/"&gt;holepunch&lt;/a&gt;, an R package that will take any GitHub repo with R scripts and R markdown files and quickly turn it in into a free, live RStudio server where anyone can run your code!&lt;/p&gt;</description></item><item><title>Chat with rOpenSci Contributors at useR!2019</title><link>https://ropensci.org/blog/2019/07/08/user2019/</link><pubDate>Mon, 08 Jul 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/07/08/user2019/</guid><description>
&lt;p&gt;Three members of the rOpenSci team - Scott Chamberlain, Jenny Bryan, and Rich FitzJohn - as well as many community members will give talks at &lt;a href="http://www.user2019.fr/"&gt;useR!2019&lt;/a&gt;. Many other package authors, maintainers, reviewers and unconf participants will be there too. Don&amp;rsquo;t hesitate to ask them about rOpenSci &lt;a href="https://ropensci.org/packages/"&gt;packages&lt;/a&gt;, &lt;a href="https://ropensci.org/software-review/"&gt;software peer review&lt;/a&gt;, &lt;a href="https://ropensci.org/community/"&gt;community&lt;/a&gt;, or just say hello if you&amp;rsquo;re looking for a friendly face.&lt;/p&gt;
&lt;p&gt;We&amp;rsquo;ve listed their talks for you. Search the &lt;a href="https://connect.rstudioservices.com/content/331/user2019-schedule.html"&gt;schedule&lt;/a&gt; for details.&lt;/p&gt;
&lt;h3&gt;
Wednesday, July 10
&lt;/h3&gt;&lt;p&gt;&lt;a href="https://ropensci.org/authors/julia-stewart-lowndes/"&gt;&lt;strong&gt;Julia Stewart Lowndes&lt;/strong&gt;&lt;/a&gt; Keynote! R for better science in less time&lt;/p&gt;</description></item><item><title>Using bomrang to correlate weather conditions to sorghum stalk rot (charcoal rot)</title><link>https://ropensci.org/usecases/using-bomrang-to-correlate-weather-conditions-to-sorghum-stalk-rot-charcoal-rot/</link><pubDate>Mon, 01 Jul 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/using-bomrang-to-correlate-weather-conditions-to-sorghum-stalk-rot-charcoal-rot/</guid><description>
&lt;h4&gt;
Package or resource used
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/bomrang/"&gt;bomrang&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case
&lt;/h4&gt;&lt;p&gt;Full article: &lt;a href="https://communities.grdc.com.au/field-crop-diseases/sorghum-disease-survey/"&gt;https://communities.grdc.com.au/field-crop-diseases/sorghum-disease-survey/&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Code gist: &lt;a href="https://gist.github.com/adamhsparks/23d6266f4a2b5f19f9edef6970f0364a"&gt;https://gist.github.com/adamhsparks/23d6266f4a2b5f19f9edef6970f0364a&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
Image
&lt;/h4&gt;&lt;p&gt;&lt;img src="https://ropensci.org/usecases/using-bomrang-to-correlate-weather-conditions-to-sorghum-stalk-rot-charcoal-rot/using-bomrang-to-correlate-weather-conditions-to-sorghum-stalk-rot-charcoal-rot.png" alt="Image_1|690x375"&gt;&lt;/p&gt;
&lt;h4&gt;
Sector
&lt;/h4&gt;&lt;p&gt;academic&lt;/p&gt;
&lt;h4&gt;
Field(s) of application
&lt;/h4&gt;&lt;p&gt;botanical epidemiology, plant pathology, agronomy&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;I used &lt;code&gt;bomrang&lt;/code&gt;&amp;rsquo;s &lt;a href="https://docs.ropensci.org/bomrang/articles/bomrang.html#using-get_historical"&gt;&lt;code&gt;get_historical()&lt;/code&gt;&lt;/a&gt; to fetch weather data, rainfall and temperature, for four stations in Queensland and New South Wales to create a climogram to illustrate how rainfall seemingly affected the distribution of sorghum charcoal rot (&lt;em&gt;Macrophomina phaseolina&lt;/em&gt;) during the summer season of 2018/19. The article was published online as a part of the &lt;a href="https://communities.grdc.com.au/field-crop-diseases/"&gt;GRDC Communities Field Crops Diseases&lt;/a&gt; blog.&lt;/p&gt;</description></item><item><title>Involving Multilingual Communities</title><link>https://ropensci.org/commcalls/2019-06-28/</link><pubDate>Fri, 28 Jun 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/commcalls/2019-06-28/</guid><description/></item><item><title>2 Months in 2 Minutes - rOpenSci News, June 2019</title><link>https://ropensci.org/blog/2019/06/20/news-jun2019/</link><pubDate>Thu, 20 Jun 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/06/20/news-jun2019/</guid><description>
&lt;h3&gt;
rOpenSci HQ 👨🏽‍💻👩🏼‍💻 🏗️
&lt;/h3&gt;&lt;ul&gt;
&lt;li&gt;Join our next &lt;a href="https://ropensci.org/commcalls/2019-06-28/"&gt;Community Call on Involving Multilingual Communities&lt;/a&gt; June 28th.&lt;/li&gt;
&lt;li&gt;Video of our &lt;a href="https://ropensci.org/commcalls/2019-05-07/"&gt;Community Call on Security for R&lt;/a&gt; is up, with a long list of resources.&lt;/li&gt;
&lt;li&gt;Our Community Manager, Stefanie Butland, spoke at R-Ladies Seattle and Fred Hutch about rOpenSci, Learning R, and Building Community May 22nd.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;
Software Peer Review ✔
&lt;/h3&gt;&lt;p&gt;6 community-contributed packages passed &lt;a href="https://ropensci.org/software-review/"&gt;software peer review&lt;/a&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://docs.ropensci.org/nbaR/"&gt;nbaR&lt;/a&gt; - R Package Client for the Netherlands Biodiversity API
&lt;ul&gt;
&lt;li&gt;Author: &lt;a href="https://github.com/hettling"&gt;Hannes Hettling&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Issue: &lt;a href="https://github.com/ropensci/onboarding/issues/257"&gt;ropensci/onboarding#257&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Reviewers:
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://github.com/DomBennett"&gt;Dom Bennett&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/mbjoseph"&gt;Max Joseph&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.ropensci.org/git2rdata/"&gt;git2rdata&lt;/a&gt; - Store and Retrieve Data.frames in a Git Repository
&lt;ul&gt;
&lt;li&gt;Author: &lt;a href="https://github.com/ThierryO"&gt;Thierry Onkelinx&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Issue: &lt;a href="https://github.com/ropensci/onboarding/issues/263"&gt;ropensci/onboarding#263&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Reviewers:
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://github.com/jennybc"&gt;Jenny Bryan&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/brodieG"&gt;Brodie Gaslam&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.ropensci.org/citesdb/"&gt;citesdb&lt;/a&gt; - A high-performance database of shipment-level CITES trade data
&lt;ul&gt;
&lt;li&gt;Author: &lt;a href="https://github.com/noamross"&gt;Noam Ross&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Issue: &lt;a href="https://github.com/ropensci/onboarding/issues/292"&gt;ropensci/onboarding#292&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Reviewers:
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://github.com/pachamaltese"&gt;pachamaltese&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/xavi-rp"&gt;Xavier Rotllan-Puig&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.ropensci.org/MtreeRing/"&gt;MtreeRing&lt;/a&gt; - A Shiny Application for Automatic Measurements of Tree-Ring Widths on Digital Images
&lt;ul&gt;
&lt;li&gt;Author: &lt;a href="https://github.com/JingningShi"&gt;Jingning Shi&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Issue: &lt;a href="https://github.com/ropensci/onboarding/issues/287"&gt;ropensci/onboarding#287&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Reviewers:
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://github.com/bhive01"&gt;Brandon Hurr&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/rorynolan"&gt;Rory Nolan&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.ropensci.org/rromeo/"&gt;rromeo&lt;/a&gt; - An R Client for SHERPA/RoMEO API
&lt;ul&gt;
&lt;li&gt;Author: &lt;a href="https://github.com/Rekyt"&gt;Matthias Grenié&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Issue: &lt;a href="https://github.com/ropensci/onboarding/issues/285"&gt;ropensci/onboarding#285&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Reviewers:
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://github.com/ottlngr"&gt;Philipp Ottolinger&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/brunaw"&gt;Bruna Wundervald&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.ropensci.org/tidync/"&gt;tidync&lt;/a&gt; - A Tidy Approach to &amp;lsquo;NetCDF&amp;rsquo; Data Exploration and Extraction
&lt;ul&gt;
&lt;li&gt;Author: &lt;a href="https://github.com/mdsumner"&gt;Michael Sumner&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Issue: &lt;a href="https://github.com/ropensci/onboarding/issues/174"&gt;ropensci/onboarding#174&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Reviewers:
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://github.com/timcdlucas"&gt;Tim Lucas&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/Nowosad"&gt;Jakub Nowosad&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;em&gt;Consider &lt;a href="https://devguide.ropensci.org/softwarereviewintro.html"&gt;submitting your package&lt;/a&gt; or &lt;a href="https://devguide.ropensci.org/softwarereviewintro.html#whyreview"&gt;volunteering to review&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;</description></item><item><title>Community Call - Involving Multilingual Communities</title><link>https://ropensci.org/blog/2019/06/13/commcall-jun2019/</link><pubDate>Thu, 13 Jun 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/06/13/commcall-jun2019/</guid><description>
&lt;p&gt;rOpenSci’s community is increasingly international and multilingual. While we have operated primarily in English, we now receive submissions of packages from authors whose primary language is not. As we expand our community in this way, we want to learn from the experience of other organizations. How can we manage our peer-review process and open-source projects to be welcoming to non-native English speakers?&lt;/p&gt;
&lt;p&gt;Our guest speakers will include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Rayna Harris, who has co-led work with &lt;a href="https://carpentries.org/"&gt;The Carpentries&lt;/a&gt; in internationalization of curricula.&lt;/li&gt;
&lt;li&gt;Emilio Bruna, who as editor-in-chief of &lt;a href="https://onlinelibrary.wiley.com/journal/17447429"&gt;Biotropica&lt;/a&gt;, manages a journal with a heavily tropical-country audience and authorship base.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The call will be moderated by Melina Vidoni, an associate editor for rOpenSci &lt;a href="https://ropensci.org/software-review/"&gt;software peer review&lt;/a&gt;. There will be 20 minutes for Q &amp;amp; A following the presentations.&lt;/p&gt;</description></item><item><title>Taking over maintenance of a software package</title><link>https://ropensci.org/blog/2019/06/12/taking-over-maint/</link><pubDate>Wed, 12 Jun 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/06/12/taking-over-maint/</guid><description>
&lt;p&gt;Software is maintained by people. While software can in theory live on indefinitely, to do so requires people. People change jobs, move locations, retire, and unfortunately die sometimes. When a software maintainer can no longer maintain a package, what happens to the software?&lt;/p&gt;
&lt;p&gt;Because of the fragility of people in software, in an ideal world a piece of software should have as many maintainers as possible. Increasing maintainers increases the so-called &lt;a href="https://en.wikipedia.org/wiki/Bus_factor"&gt;bus factor&lt;/a&gt;. A lower number of maintainers means fewer people have to get hit by a bus to then have no maintainers.&lt;/p&gt;</description></item><item><title>Introducing the new rOpenSci docs server</title><link>https://ropensci.org/blog/2019/06/07/ropensci-docs/</link><pubDate>Fri, 07 Jun 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/06/07/ropensci-docs/</guid><description>
&lt;p&gt;As part of our continuous effort to improve rOpenSci infrastructure, we are rolling out a new service to automatically build and host documentation for all rOpenSci packages.&lt;/p&gt;
&lt;p&gt;&lt;img src="https://ropensci.org/blog/2019/06/07/ropensci-docs/r68Ukiw.png" alt="drakedocs"&gt;&lt;/p&gt;
&lt;p&gt;The webpages are generated using the popular &lt;a href="https://pkgdown.r-lib.org/"&gt;pkgdown&lt;/a&gt; system with our &lt;a href="https://github.com/ropensci/rotemplate"&gt;rOpenSci template&lt;/a&gt;, and get automatically published on &lt;a href="https://docs.ropensci.org/"&gt;https://docs.ropensci.org/&lt;/a&gt;. Some examples:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://docs.ropensci.org/drake/"&gt;https://docs.ropensci.org/drake/&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.ropensci.org/magick/"&gt;https://docs.ropensci.org/magick/&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.ropensci.org/writexl/"&gt;https://docs.ropensci.org/writexl/&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.ropensci.org/stplanr/"&gt;https://docs.ropensci.org/stplanr/&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.ropensci.org/osmdata/"&gt;https://docs.ropensci.org/osmdata/&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.ropensci.org/visdat/"&gt;https://docs.ropensci.org/visdat/&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.ropensci.org/tesseract/"&gt;https://docs.ropensci.org/tesseract/&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;We intend this to become the central place to find documentation for rOpenSci packages. We are still rolling this out so not all packages are there yet, but the majority is online now.&lt;/p&gt;</description></item><item><title>get_clean_obs R Function (searching, pulling and cleaning citizen science records from iNaturalist and GBIF)</title><link>https://ropensci.org/usecases/get-clean-obs-r-function-searching-pulling-and-cleaning-citizen-science-records-from-inaturalist-and-gbif/</link><pubDate>Thu, 06 Jun 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/get-clean-obs-r-function-searching-pulling-and-cleaning-citizen-science-records-from-inaturalist-and-gbif/</guid><description>
&lt;p&gt;An R function that leverages the rgbif and spocc packages to search for, pull down, combine and clean records of a single species (with lat/lon bounding boxes). A continuing work in progress, but hopefully useful for folks interested in pulling records from these sources. It also has some (slow, but tricky) work arounds when querying large numbers (up to 200k) from these sources.&lt;/p&gt;
&lt;h4&gt;
Package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://github.com/ropensci/spocc"&gt;spocc&lt;/a&gt;, &lt;a href="https://ropensci.github.io/rgbif/"&gt;rgbif&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://github.com/keatonwilson/insect_migration/blob/ec66ff976155fd75982dce0ebf42644077127b53/scripts/get_clean_obs_function.R"&gt;https://github.com/keatonwilson/insect_migration/blob/ec66ff976155fd75982dce0ebf42644077127b53/scripts/get_clean_obs_function.R&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Access Publisher Copyright &amp; Self-Archiving Policies via the 'SHERPA/RoMEO' API</title><link>https://ropensci.org/blog/2019/06/04/rromeo/</link><pubDate>Tue, 04 Jun 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/06/04/rromeo/</guid><description>
&lt;p&gt;We&amp;rsquo;ve been following rOpenSci&amp;rsquo;s work for a long time, and we use several packages on a daily basis for our scientific projects, especially &lt;a href="https://github.com/ropensci/taxize/"&gt;taxize&lt;/a&gt; to clean species names, &lt;a href="https://github.com/ropensci/rredlist/"&gt;rredlist&lt;/a&gt; to extract species IUCN statuses or [treeio](many probs with this post) to work with phylogenetic trees.
rOpensci is a perfect incarnation of a vibrant and diverse community where people learn and develop new ideas, especially regarding scientific packages.
We&amp;rsquo;ve also noticed how much the thorough review process improves the quality of the packages that join the rOpenSci ecosystem.
And while we were admiring the dynamics of rOpenSci community, we started to wonder how we could contribute to this ecosystem.
And this is how we started our quest to find a project that could fit rOpenSci goals while at the same time teach us new skills.&lt;/p&gt;</description></item><item><title>osmdata use case: Bicycle network analysis of Auckland</title><link>https://ropensci.org/usecases/osmdata-use-case-bicycle-network-analysis-of-auckland/</link><pubDate>Thu, 30 May 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/osmdata-use-case-bicycle-network-analysis-of-auckland/</guid><description>
&lt;h4&gt;
Package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://ropensci.github.io/osmdata/index.html"&gt;osmdata&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://kimnewzealand.github.io/2019/04/08/bike-network/"&gt;Spatial Bike Network Analysis in Auckland&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
Sector
&lt;/h4&gt;&lt;p&gt;Other&lt;/p&gt;
&lt;h4&gt;
Field(s) of application
&lt;/h4&gt;&lt;p&gt;transport and planning&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;I used the osmdata package to retrieve and analyse Open Street Map (OSM) bike data given the flurry of bike route construction in Auckland. I also compared to the bike counter data provided by Auckland Transport to visualise our bike networks.&lt;/p&gt;</description></item><item><title>Using bib2df to parse the R Journal archives</title><link>https://ropensci.org/usecases/using-bib2df-to-parse-the-r-journal-archives/</link><pubDate>Wed, 29 May 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/using-bib2df-to-parse-the-r-journal-archives/</guid><description>
&lt;h4&gt;
Package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/bib2df/"&gt;bib2df&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://blog.r-hub.io/2019/05/29/keep-up-with-cran/"&gt;https://blog.r-hub.io/2019/05/29/keep-up-with-cran/&lt;/a&gt;&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-r" data-lang="r"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="n"&gt;journal&lt;/span&gt; &lt;span class="o"&gt;&amp;lt;-&lt;/span&gt; &lt;span class="n"&gt;bib2df&lt;/span&gt;&lt;span class="o"&gt;::&lt;/span&gt;&lt;span class="nf"&gt;bib2df&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s"&gt;&amp;#34;https://journal.r-project.org/archive/RJournal.bib&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="n"&gt;knitr&lt;/span&gt;&lt;span class="o"&gt;::&lt;/span&gt;&lt;span class="nf"&gt;kable&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt; &lt;span class="n"&gt;journal&lt;/span&gt;&lt;span class="nf"&gt;[grepl&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s"&gt;&amp;#34;CRAN&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;journal&lt;/span&gt;&lt;span class="o"&gt;$&lt;/span&gt;&lt;span class="n"&gt;TITLE&lt;/span&gt;&lt;span class="p"&gt;),&lt;/span&gt; &lt;span class="nf"&gt;c&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s"&gt;&amp;#34;TITLE&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s"&gt;&amp;#34;MONTH&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s"&gt;&amp;#34;YEAR&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s"&gt;&amp;#34;URL&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="n"&gt;]&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;h4&gt;
Sector
&lt;/h4&gt;&lt;p&gt;other&lt;/p&gt;
&lt;h4&gt;
Field(s) of application
&lt;/h4&gt;&lt;p&gt;R package development&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;I used bib2df to parse the bibliography file containing information about all previous articles of the R Journal, to then filter articles whose title contained the word &amp;ldquo;CRAN&amp;rdquo;, since I wanted to see how often the CRAN team had published articles giving updates on their policies and processes.&lt;/p&gt;</description></item><item><title>ramlegacy: a package for RAM Legacy Database</title><link>https://ropensci.org/blog/2019/05/28/ramlegacy/</link><pubDate>Tue, 28 May 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/05/28/ramlegacy/</guid><description>
&lt;h2&gt;
Introduction
&lt;/h2&gt;&lt;p&gt;ramlegacy is a new R package to download, cache and read in all the different versions of the &lt;a href="https://www.ramlegacy.org/"&gt;RAM Legacy Stock Assessment Database&lt;/a&gt;, a public database containing stock assessment results of commercially exploited marine populations from around the world. The package accomplishes all this by:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Providing a function &lt;code&gt;download_ramlegacy()&lt;/code&gt;, to download all the available versions of the RAM Database and cache them on the user’s computer in a location provided by the &lt;a href="https://cran.r-project.org/web/packages/rappdirs/index.html"&gt;rappdirs&lt;/a&gt; package. This way once a version has been downloaded it doesn’t need to be re-downloaded for subsequent analysis.&lt;/li&gt;
&lt;li&gt;Supporting reading in specified tables or all tables from a cached version of the database through the function &lt;code&gt;load_ramlegacy()&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Providing a function &lt;code&gt;ram_dir()&lt;/code&gt; to view the path of the rappdirs location where the downloaded database was cached.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The primary motivation behind developing the caching behavior of the package was to save the user time and effort spent in re-downloading different versions of the database as part of any future analysis.&lt;/p&gt;</description></item><item><title>rodev: helpers for rOpenSci package authors</title><link>https://ropensci.org/blog/2019/05/21/rodev/</link><pubDate>Tue, 21 May 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/05/21/rodev/</guid><description>
&lt;p&gt;We strive for high quality in &lt;a href="https://ropensci.org/packages/"&gt;our suite of packages&lt;/a&gt;, in practice via a &lt;a href="https://ropensci.org/software-review/"&gt;system of software peer review&lt;/a&gt;, and via &lt;a href="https://devguide.ropensci.org/"&gt;packaging guidelines that keep growing&lt;/a&gt;. There is therefore a risk of increasing the workload of package authors, who already have a lot on their plate. To avoid that, when explaining how to do things in our dev guide, we recommend existing automated tools to authors.&lt;/p&gt;
&lt;p&gt;Inspired by &lt;a href="https://usethis.r-lib.org/"&gt;the usethis package&lt;/a&gt;, we&amp;rsquo;ve started work on our specific helpers for rOpenSci package authors, &lt;a href="https://docs.ropensci.org/rodev/"&gt;rodev&lt;/a&gt;. In this note, we&amp;rsquo;ll present some of the helpers it contains at the moment, and ask for your feedback as an rOpenSci package author.&lt;/p&gt;</description></item><item><title>rcrossref for #TidyTuesday</title><link>https://ropensci.org/usecases/rcrossref-for-tidytuesday/</link><pubDate>Fri, 17 May 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/rcrossref-for-tidytuesday/</guid><description>
&lt;h4&gt;
Package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://github.com/ropensci/rcrossref"&gt;rcrossref&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://twitter.com/jakekaupp/status/1129202271789748234"&gt;https://twitter.com/jakekaupp/status/1129202271789748234&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
Sector
&lt;/h4&gt;&lt;p&gt;Other&lt;/p&gt;
&lt;h4&gt;
Field(s) of application
&lt;/h4&gt;&lt;p&gt;Bibliometrics&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;In week 20 of #TidyTuesday, a #rstats community exercise around cleaning and visualizing data, I used rcrossref to get the citation counts for Nobel Prize winners (DOI was present in the dataset) and visualized the citation patterns by author and Nobel category (Chemistry, Physics and Medicine)&lt;/p&gt;</description></item><item><title>rOpenSci Dev Guide 0.2.0: Updates Inside and Out</title><link>https://ropensci.org/blog/2019/05/16/dev-guide-update/</link><pubDate>Thu, 16 May 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/05/16/dev-guide-update/</guid><description>
&lt;p&gt;As announced in &lt;a href="https://ropensci.org/blog/2019/02/01/software-review-news/"&gt;our recent post about updates to our Software Peer Review system&lt;/a&gt;, all our package development, review and maintenance is available as &lt;a href="https://devguide.ropensci.org/"&gt;an online book&lt;/a&gt;. Our goal is to update it approximately quarterly so it&amp;rsquo;s already time to present its second official version! You can &lt;a href="https://devguide.ropensci.org/booknews.html"&gt;read the changelog&lt;/a&gt; or this blog post to find out what&amp;rsquo;s new in our dev guide 0.2.0!&lt;/p&gt;
&lt;h2&gt;
A more legit and accessible book
&lt;/h2&gt;&lt;p&gt;Let&amp;rsquo;s start with very exciting news, the dev guide now has a cover, designed by Oz Locke from &lt;a href="https://www.lockecreatives.com/"&gt;Locke Creatives&lt;/a&gt;!&lt;/p&gt;</description></item><item><title>POWER to the People</title><link>https://ropensci.org/blog/2019/05/14/nasapower/</link><pubDate>Tue, 14 May 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/05/14/nasapower/</guid><description>
&lt;p&gt;NASA generates and provides heaps of data to the scientific community. Not all
of it is looking out at the stars. Some of it is looking back at us here on
Earth. NASA’s Earth science program observes, understands and models the
Earth system&lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt;. We can use these data to discover how our Earth is changing,
to better predict change, and to understand the consequences for life on Earth.&lt;/p&gt;
&lt;p&gt;The Earth science program includes the
&lt;a href="https://power.larc.nasa.gov/"&gt;Prediction of Worldwide Energy Resource (POWER)&lt;/a&gt;
project, which was initiated to improve upon the current renewable energy data
set and to create new data sets from new satellite systems. The POWER project
targets three user communities: 1) Renewable Energy (SSE), 2) Sustainable
Buildings (SB) and 3) Agroclimatology (AG)&lt;sup id="fnref1:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt; and covers 140+ different
parameters.&lt;/p&gt;</description></item><item><title>Can rainfall be a useful predictor of epidemic risk across temporal and...</title><link>https://ropensci.org/usecases/can-rainfall-be-a-useful-predictor-of-epidemic-risk-across-temporal-and/</link><pubDate>Fri, 10 May 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/can-rainfall-be-a-useful-predictor-of-epidemic-risk-across-temporal-and/</guid><description>
&lt;h4&gt;
rOpenSci package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://github.com/ropensci/nasapower"&gt;nasapower&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
URL
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://speakerdeck.com/emdelponte/can-rainfall-be-a-useful-predictor-of-epidemic-risk-across-temporal-and-spatial-scales?slide=23"&gt;https://speakerdeck.com/emdelponte/can-rainfall-be-a-useful-predictor-of-epidemic-risk-across-temporal-and-spatial-scales?slide=23&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
Sector
&lt;/h4&gt;&lt;p&gt;Academic&lt;/p&gt;
&lt;h4&gt;
Field(s) of application
&lt;/h4&gt;&lt;p&gt;Plant disease epidemiology, risk mapping, rainfall monitoring&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;I used the package, with the help of its maintainer @adamhsparks, to download rainfall data for specific time periods matching the pre- and early-season of period of soybean growth in Brazil. It will be further used to explore associations between rainfall and patterns of dispersal of a fungal disease of soybean over large region across years.&lt;/p&gt;</description></item><item><title>Open Trade Statistics</title><link>https://ropensci.org/blog/2019/05/09/tradestatistics/</link><pubDate>Thu, 09 May 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/05/09/tradestatistics/</guid><description>
&lt;h3&gt;
Introduction
&lt;/h3&gt;&lt;p&gt;&lt;a href="https://tradestatistics.io"&gt;Open Trade Statistics&lt;/a&gt; (OTS) was created with the intention to lower the barrier to working with international economic trade data. It includes a public API, a dashboard, and an R package for data retrieval.&lt;/p&gt;
&lt;p&gt;The project started when I was affected by the fact that many Latin American Universities have limited or no access to the &lt;a href="https://comtrade.un.org/"&gt;United Nations Commodity Trade Statistics Database&lt;/a&gt; (UN COMTRADE).&lt;/p&gt;
&lt;p&gt;There are alternatives to COMTRADE, for example the &lt;a href="http://www.cepii.fr/CEPII/en/bdd_modele/presentation.asp?id=1"&gt;Base Pour L&amp;rsquo;Analyse du Commerce International&lt;/a&gt; (BACI) constitutes an improvement over COMTRADE as it is constructed using the raw data and a method that reconciles the declarations of the exporter and the importer. The main problem with BACI is that you need UN COMTRADE institutional access to download their datasets.&lt;/p&gt;</description></item><item><title>Security for R</title><link>https://ropensci.org/commcalls/2019-05-07/</link><pubDate>Tue, 07 May 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/commcalls/2019-05-07/</guid><description/></item><item><title>Using drake to power a new soil respiration database</title><link>https://ropensci.org/usecases/using-drake-to-power-a-new-soil-respiration-database/</link><pubDate>Sat, 04 May 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/using-drake-to-power-a-new-soil-respiration-database/</guid><description>
&lt;h4&gt;
Package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://github.com/ropensci/drake"&gt;drake&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://github.com/bpbond/cosore/blob/6b96bf9afbc3cb8e995c4b1e65b7c6af78bdc82f/README.md"&gt;https://github.com/bpbond/cosore/blob/6b96bf9afbc3cb8e995c4b1e65b7c6af78bdc82f/README.md&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
Image
&lt;/h4&gt;&lt;p&gt;&lt;img src="https://ropensci.org/usecases/using-drake-to-power-a-new-soil-respiration-database/using-drake-to-power-a-new-soil-respiration-database.png" alt="26%20PM|346x499"&gt;&lt;/p&gt;
&lt;h4&gt;
Sector
&lt;/h4&gt;&lt;p&gt;Academic&lt;/p&gt;
&lt;h4&gt;
Field(s) of application
&lt;/h4&gt;&lt;p&gt;Earth sciences, climate change, ecology&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;Earth system scientists increasingly use online data repositories to store, synthesize, and perform meta-analyses of e.g. forest growth, plant characteristics, and land-atmosphere energy fluxes (see for example &lt;a href="https://ameriflux.lbl.gov"&gt;Ameriflux&lt;/a&gt;). No such database exists for &lt;em&gt;continuous soil respiration&lt;/em&gt;, the land-to-atmosphere CO2 flux measured continuously by automated systems around the world, however. This is the gap my nascent &lt;code&gt;cosore&lt;/code&gt; package aims to fill. &lt;code&gt;drake&lt;/code&gt; provides the infrastructure for tracking out-of-date soil respiration datasets contributed by authors; efficiently rebuilding them into a single, standardized form; and verifying reproducibility.&lt;/p&gt;</description></item><item><title>qualtRics: the Stack Overflow Developer Survey</title><link>https://ropensci.org/usecases/qualtrics-the-stack-overflow-developer-survey/</link><pubDate>Wed, 01 May 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/qualtrics-the-stack-overflow-developer-survey/</guid><description>
&lt;h4&gt;
rOpenSci package used
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://ropensci.github.io/qualtRics/"&gt;qualtRics&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
Use case
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://insights.stackoverflow.com/survey/2019"&gt;Stack Overflow Developer Survey 2019 results&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
Image
&lt;/h4&gt;&lt;p&gt;&lt;img src="https://ropensci.org/usecases/qualtrics-the-stack-overflow-developer-survey/qualtrics-the-stack-overflow-developer-survey.png" alt="tech_network-1|500x500,75%"&gt;&lt;/p&gt;
&lt;h4&gt;
Sector
&lt;/h4&gt;&lt;p&gt;industry&lt;/p&gt;
&lt;h4&gt;
Field(s) of application
&lt;/h4&gt;&lt;p&gt;surveys&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;As the data scientist who worked on both planning and analyzing Stack Overflow&amp;rsquo;s annual survey, I used qualtRics to access the almost 90,000 responses to our survey. Using qualtRics made our workflow more reproducible and simpler.&lt;/p&gt;</description></item><item><title>Relaunching the qualtRics package</title><link>https://ropensci.org/blog/2019/04/30/qualtrics-relaunch/</link><pubDate>Tue, 30 Apr 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/04/30/qualtrics-relaunch/</guid><description>
&lt;p&gt;rOpenSci is one of the first organizations in the R community I ever interacted with, when I participated in the &lt;a href="https://juliasilge.com/blog/i-went-to-ropensci/"&gt;2016 rOpenSci unconf&lt;/a&gt;. I have since &lt;a href="https://ropensci.org/software-review/"&gt;reviewed several rOpenSci packages&lt;/a&gt; and been so happy to be connected to this community, but I have never submitted or maintained a package myself. All that changed when I heard the call for a new maintainer for the &lt;a href="https://github.com/ropensci/qualtRics"&gt;qualtRics&lt;/a&gt; package. &amp;ldquo;IT&amp;rsquo;S GO TIME,&amp;rdquo; I thought. 😎&lt;/p&gt;
&lt;p&gt;&lt;a href="https://www.qualtrics.com/"&gt;Qualtrics&lt;/a&gt; is an online survey and data collection software platform. Qualtrics is used across many domains in both academia and industry for online surveys and research, including by me at my day job as a data scientist at &lt;a href="https://stackoverflow.com/"&gt;Stack Overflow&lt;/a&gt;. While users can manually download survey responses from Qualtrics through a browser, importing this data into R is then cumbersome. The qualtRics R package implements the retrieval of survey data using the Qualtrics API and aims to reduce the pre-processing steps needed in analyzing such surveys. This package has been a huge help to me in my real day-to-day work, and I have been so grateful for the excellent work of the package&amp;rsquo;s original authors, including the previous maintainer &lt;a href="https://jasperginn.io/"&gt;Jasper Ginn&lt;/a&gt;. This package is currently the only package on CRAN that offers functionality like this for Qualtrics&amp;rsquo; API, and is included in the official Qualtrics API documentation.&lt;/p&gt;</description></item><item><title>conditionz: control how many times conditions are thrown</title><link>https://ropensci.org/blog/2019/04/24/conditionz/</link><pubDate>Wed, 24 Apr 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/04/24/conditionz/</guid><description>
&lt;p&gt;conditionz is a new (just on CRAN today) R package for controlling how many times conditions are thrown.&lt;/p&gt;
&lt;p&gt;This package arises from an annoyance in another set of packages I maintain: The &lt;a href="https://github.com/ropensci/brranching"&gt;brranching&lt;/a&gt; package uses
the &lt;a href="https://github.com/ropensci/taxize"&gt;taxize&lt;/a&gt; package internally, calling it’s function &lt;code&gt;taxize::tax_name()&lt;/code&gt;. The &lt;code&gt;taxize::tax_name()&lt;/code&gt; function
throws useful messages to the user if their API key is not found, and gives them instructions
on how to find it. However, the user does not have to get an API key. If they don’t they then get subjected to
lots of repeats of the same message.&lt;/p&gt;</description></item><item><title>Join, split, and compress PDF files with pdftools</title><link>https://ropensci.org/blog/2019/04/24/pdftools-22/</link><pubDate>Wed, 24 Apr 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/04/24/pdftools-22/</guid><description>
&lt;p&gt;Last month we released a new version of &lt;a href="https://cran.r-project.org/package=pdftools"&gt;pdftools&lt;/a&gt; and a new companion package &lt;a href="https://cran.r-project.org/package=qpdf"&gt;qpdf&lt;/a&gt; for working with pdf files in R. This release introduces the ability to perform pdf transformations, such as splitting and combining pages from multiple files. Moreover, the &lt;code&gt;pdf_data()&lt;/code&gt; function which was &lt;a href="https://ropensci.org/technotes/2018/12/14/pdftools-20/"&gt;introduced in pdftools 2.0&lt;/a&gt; is now available on all major systems.&lt;/p&gt;
&lt;h2&gt;
Split and Join PDF files
&lt;/h2&gt;&lt;p&gt;It is now possible to split, join, and compress pdf files with pdftools. For example the &lt;code&gt;pdf_subset()&lt;/code&gt; function creates a new pdf file with a selection of the pages from the input file:&lt;/p&gt;</description></item><item><title>When Standards Go Wild - Software Review for a Manuscript</title><link>https://ropensci.org/blog/2019/04/18/wild-standards/</link><pubDate>Thu, 18 Apr 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/04/18/wild-standards/</guid><description>
&lt;p&gt; &lt;/p&gt;
&lt;h2&gt;
&lt;img src="stefanie-butland.jpg" alt="Stefanie Butland" style="margin: 0px 10px; width: 75px;" align="left"&gt; Stefanie Butland, &lt;em&gt;rOpenSci Community Manager&lt;/em&gt;
&lt;/h2&gt;&lt;p&gt;Some things are just irresistible to a community manager – PhD student Hugo Gruson’s recent tweets definitely fall into that category.&lt;/p&gt;
&lt;figure&gt;&lt;img src="https://ropensci.org/blog/2019/04/18/wild-standards/sRKKrJ0.png"
alt="Pavo tweets"&gt;
&lt;/figure&gt;
&lt;p&gt;I was surprised and intrigued to see an example of our software peer review guidelines being used in a manuscript review, independent of our &lt;a href="https://ropensci.org/blog/2017/11/29/review-collaboration-mee/"&gt;formal collaboration&lt;/a&gt; with the journal &lt;a href="https://besjournals.onlinelibrary.wiley.com/journal/2041210x"&gt;Methods in Ecology and Evolution (MEE)&lt;/a&gt;. This is exactly the kind of thing rOpenSci is working to enable by developing a good set of practices that broadly apply to research software.&lt;/p&gt;</description></item><item><title>Get tweet status ID from CrossRef Event Data with crevents</title><link>https://ropensci.org/usecases/get-tweet-status-id-from-crossref-event-data-with-crevents/</link><pubDate>Fri, 12 Apr 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/get-tweet-status-id-from-crossref-event-data-with-crevents/</guid><description>
&lt;h4&gt;
Package or resource used
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://github.com/ropensci/crevents/"&gt;crevents&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://github.com/tts/aaltoced/blob/b617ec401473cfe7928723e8f2d68be8fa4945ea/getdata.R#L36-L45"&gt;https://github.com/tts/aaltoced/blob/b617ec401473cfe7928723e8f2d68be8fa4945ea/getdata.R#L36-L45&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
Sector
&lt;/h4&gt;&lt;p&gt;Academic&lt;/p&gt;
&lt;h4&gt;
Field(s) of application
&lt;/h4&gt;&lt;p&gt;Bibliometrics, altmetrics&lt;/p&gt;
&lt;h4&gt;
What did you do?
&lt;/h4&gt;&lt;p&gt;I built a &lt;a href="https://ttso.shinyapps.io/aaltoced/"&gt;Shiny web app&lt;/a&gt; on those recent publications of our university that have been tweeted by their DOI. For this, I first queried CrossRef Event Data with crevents, extracted the tweet status id&amp;rsquo;s from the result, and then fetched the tweet text and other info with &lt;a href="https://cran.r-project.org/package=rtweet"&gt;rtweet&lt;/a&gt;. For the whole story, see &lt;a href="https://blogs.aalto.fi/suoritin/2019/04/10/everyday-altmetrics/"&gt;my blog post&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Community Call - Security for R</title><link>https://ropensci.org/blog/2019/04/09/commcall-may2019/</link><pubDate>Tue, 09 Apr 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/04/09/commcall-may2019/</guid><description>
&lt;p&gt;&amp;ldquo;Security&amp;rdquo; can be a daunting, scary, and (frankly) quite often a very boring topic. BUT!, we promise that this Community Call on May 7th will be informative, engaging, and enlightening (or, at least not boring)!&lt;/p&gt;
&lt;p&gt;Applying security best practices is essential not only for developers or sensitive data storage but also for the everyday R user installing R packages, contributing to open source, working with APIs or remote servers. However, keeping up-to-date with security best practices and applying them meticulously requires significant effort and is difficult without expert knowledge. On this Call you’ll hear about how the &lt;code&gt;ropsec&lt;/code&gt; package can help &lt;em&gt;you&lt;/em&gt; and you&amp;rsquo;ll learn the inner secrets of maintaining confidentiality, integrity, and availability throughout all your data science workflows.&lt;/p&gt;</description></item><item><title>Getting your toes wet in R: Hydrology, meteorology, and more</title><link>https://ropensci.org/blog/2019/04/02/hydrology-task-view/</link><pubDate>Tue, 02 Apr 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/04/02/hydrology-task-view/</guid><description>
&lt;h3&gt;
Importance of Hydrology
&lt;/h3&gt;&lt;p&gt;Given that liquid water is &lt;a href="https://www.amnh.org/explore/science-topics/water-and-life-on-earth"&gt;essential to life on Earth&lt;/a&gt;, water research cuts across numerous disciplines including hydrology, meteorology, geography, climate science, engineering, ecology, and more. Numerous R packages have emerged from this diversity of approaches, and we recently gathered many of them into a new rOpenSci &lt;a href="https://github.com/ropensci/Hydrology"&gt;task view&lt;/a&gt; which we broadly titled &amp;lsquo;Hydrology&amp;rsquo; and published to &lt;a href="https://CRAN.R-project.org/view=Hydrology"&gt;CRAN&lt;/a&gt;. Our intent is to be exhaustive and compile R packages to access, model, and summarise information related to the movement of water across the Earth&amp;rsquo;s landscape. We hope to contribute to a &lt;a href="https://www.hydrol-earth-syst-sci-discuss.net/hess-2019-50/"&gt;nascent community of hydrological R users&lt;/a&gt; and develop an infrastructure of packages that provide a comprehensive toolkit for water practitioners who use R as their preferred computational analysis tool. Making sense of water data is critical to understanding the response of landscapes to a changing climate. Consolidating water-related packages will promote their usage and discovery and ultimately facilitate reproducible workflows for water research. Since this is a new task view, it serves our purpose to evaluate the current &lt;em&gt;State of Hydrology&lt;/em&gt; in R and look at the interdependency of hydrology packages relative to some better known collections of packages in the general R ecosystem.&lt;/p&gt;</description></item><item><title>rgbif: get a little or a *lot* of occurrence data</title><link>https://ropensci.org/usecases/rgbif-get-a-little-or-a-lot-of-occurrence-data/</link><pubDate>Tue, 02 Apr 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/rgbif-get-a-little-or-a-lot-of-occurrence-data/</guid><description>
&lt;p&gt;This use case was presented by &lt;a href="https://www.zoology.ubc.ca/~turner/KGTurner/"&gt;Kathryn Turner&lt;/a&gt; as part of a &lt;a href="https://ropensci.org/commcalls/2019-03-27/"&gt;Community Call on Research Applications of rOpenSci Taxonomy and Biodiversity Tools&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
Package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://github.com/ropensci/rgbif"&gt;rgbif&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://gist.github.com/kgturner/f44a9dc6e3417794ed1f433a96a2cc7a"&gt;Code example&lt;/a&gt; to download occurrence data from &lt;a href="https://www.gbif.org/"&gt;GBIF&lt;/a&gt; for a handful of species, and scaling up to several thousand&lt;/p&gt;
&lt;p&gt;Paper: &lt;a href="https://www.biorxiv.org/content/10.1101/493270v1"&gt;&amp;ldquo;Occurrence data tells us about abiotic tolerances&amp;rdquo;&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
Field(s) of application
&lt;/h4&gt;&lt;p&gt;ecology&lt;/p&gt;</description></item><item><title>Rencontre scientifique, URFIST de Bordeaux</title><link>https://ropensci.org/events/2019-03-29-urfist-bordeaux/</link><pubDate>Fri, 29 Mar 2019 14:40:00 +0000</pubDate><guid>https://ropensci.org/events/2019-03-29-urfist-bordeaux/</guid><description>
&lt;p&gt;Our software engineer and associate editor Maëlle Salmon will give an invited talk about rOpenSci &lt;a href="https://ropensci.org/software-review"&gt;Software Peer Review&lt;/a&gt;, in French, at the &lt;a href="https://sygefor.reseau-urfist.fr/#/training/7705/8525/7338a781b57bf45847c702bfd05b2a80"&gt;&amp;ldquo;Repenser la robustesse et la fiabilité en recherche : les chercheurs face à la crise de la reproductibilité&amp;rdquo; scientific meeting&lt;/a&gt; organized by &lt;a href="http://weburfist.univ-bordeaux.fr/"&gt;URFIST de Bordeaux&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>taxize: Understanding how seafood mislabelling misrepresents the conservation status of the fish on your plate</title><link>https://ropensci.org/usecases/taxize-understanding-how-seafood-mislabelling-misrepresents-the-conservation-status-of-the-fish-on-your-plate/</link><pubDate>Fri, 29 Mar 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/taxize-understanding-how-seafood-mislabelling-misrepresents-the-conservation-status-of-the-fish-on-your-plate/</guid><description>
&lt;p&gt;This use case was presented by &lt;a href="http://www.margaretsiple.com/"&gt;Margaret Siple&lt;/a&gt; as part of a &lt;a href="https://ropensci.org/commcalls/2019-03-27/"&gt;Community Call on Research Applications of rOpenSci Taxonomy and Biodiversity Tools&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
Package used
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://github.com/ropensci/taxize"&gt;taxize&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
Links to use case
&lt;/h4&gt;&lt;ul&gt;
&lt;li&gt;&lt;a href="https://mcsiple.github.io/rOpenSciExample.html"&gt;Code example&lt;/a&gt;: Given genus names, retrieve family names and Given a list of species names, get their IUCN status&lt;/li&gt;
&lt;li&gt;&lt;a href="https://onlinelibrary.wiley.com/doi/full/10.1111/conl.12328"&gt;Paper&lt;/a&gt;: Financial and Ecological Implications of Global Seafood Mislabeling&lt;/li&gt;
&lt;/ul&gt;
&lt;h4&gt;
Image
&lt;/h4&gt;&lt;p&gt;&lt;img src="https://ropensci.org/usecases/taxize-understanding-how-seafood-mislabelling-misrepresents-the-conservation-status-of-the-fish-on-your-plate/taxize-understanding-how-seafood-mislabelling-misrepresents-the-conservation-status-of-the-fish-on-your-plate.png" alt="59%20PM|648x500,75%"&gt;&lt;/p&gt;</description></item><item><title>rBiodiversidata</title><link>https://ropensci.org/usecases/rbiodiversidata/</link><pubDate>Thu, 28 Mar 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/rbiodiversidata/</guid><description>
&lt;p&gt;This are scripts used for the Biodiversidata Project that are useful for:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Retrieving Conservation Status and Population Trend (IUCN).&lt;/li&gt;
&lt;li&gt;Checking Species Names.&lt;/li&gt;
&lt;li&gt;Retrieving Taxonomic Information for a Species.&lt;/li&gt;
&lt;/ol&gt;
&lt;h4&gt;
Package or resource used
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://github.com/ropensci/rredlist"&gt;rredlist&lt;/a&gt;, &lt;a href="https://github.com/ropensci/taxize"&gt;taxize&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://github.com/bienflorencia/rBiodiversidata"&gt;https://github.com/bienflorencia/rBiodiversidata&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
Sector
&lt;/h4&gt;&lt;p&gt;University of Lincoln, UK&lt;/p&gt;
&lt;h4&gt;
Field(s) of application
&lt;/h4&gt;&lt;p&gt;ecology, conservation&lt;/p&gt;</description></item><item><title>Research Applications of rOpenSci Taxonomy and Biodiversity Tools</title><link>https://ropensci.org/commcalls/2019-03-27/</link><pubDate>Wed, 27 Mar 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/commcalls/2019-03-27/</guid><description/></item><item><title>weathercan: Exploring extreme weather events in my neighbourhood</title><link>https://ropensci.org/usecases/weathercan-exploring-extreme-weather-events-in-my-neighbourhood/</link><pubDate>Wed, 27 Mar 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/weathercan-exploring-extreme-weather-events-in-my-neighbourhood/</guid><description>
&lt;h4&gt;
rOpenSci Package used
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://ropensci.github.io/weathercan/"&gt;weathercan&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
Use Case &amp;ndash; Blog Posts in GitHub
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://github.com/stephhazlitt/some-assembly-required/blob/1eec5cc92cf7fd7b69d24d47cc52c0bd0a9a9e0b/R/fence/fence.md"&gt;Weather with &lt;code&gt;weathercan&lt;/code&gt;&lt;/a&gt;
&lt;em&gt;and&lt;/em&gt;
&lt;a href="https://github.com/stephhazlitt/some-assembly-required/blob/1eec5cc92cf7fd7b69d24d47cc52c0bd0a9a9e0b/R/fence/wind_direction.md"&gt;When You Miss the Target&lt;/a&gt;
&lt;em&gt;and&lt;/em&gt;
&lt;a href="https://github.com/stephhazlitt/some-assembly-required/blob/1eec5cc92cf7fd7b69d24d47cc52c0bd0a9a9e0b/R/fence/wind_coord.R"&gt;a script with a final, better datavis option&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
Images
&lt;/h4&gt;&lt;p&gt;&lt;img src="https://ropensci.org/usecases/weathercan-exploring-extreme-weather-events-in-my-neighbourhood/weathercan-exploring-extreme-weather-events-in-my-neighbourhood.png" alt="wind_coord_facet_plot|690x483"&gt;&lt;/p&gt;</description></item><item><title>Linking phylogenetic and geographic data using rotl and rgbif</title><link>https://ropensci.org/usecases/linking-phylogenetic-and-geographic-data-using-rotl-and-rgbif/</link><pubDate>Fri, 22 Mar 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/usecases/linking-phylogenetic-and-geographic-data-using-rotl-and-rgbif/</guid><description>
&lt;h4&gt;
Package or resource used*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://docs.ropensci.org/rotl"&gt;rotl&lt;/a&gt;, &lt;a href="https://docs.ropensci.org/rgbif"&gt;rgbif&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
URL or code snippet for your use case*
&lt;/h4&gt;&lt;p&gt;&lt;a href="https://mctavishlab.github.io/BIO144/labs/rotl-rgbif.html"&gt;https://mctavishlab.github.io/BIO144/labs/rotl-rgbif.html&lt;/a&gt;&lt;/p&gt;
&lt;h4&gt;
Image
&lt;/h4&gt;&lt;p&gt;&lt;img src="https://ropensci.org/usecases/linking-phylogenetic-and-geographic-data-using-rotl-and-rgbif/linking-phylogenetic-and-geographic-data-using-rotl-and-rgbif.png" alt="phylomap|617x494"&gt;&lt;/p&gt;
&lt;h4&gt;
Field(s) of application
&lt;/h4&gt;&lt;p&gt;evolution, ecology&lt;/p&gt;</description></item><item><title>drake transformed</title><link>https://ropensci.org/blog/2019/03/18/drake-700/</link><pubDate>Mon, 18 Mar 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/03/18/drake-700/</guid><description>
&lt;p&gt;Version 7.0.0 of &lt;a href="https://github.com/ropensci/drake"&gt;&lt;code&gt;drake&lt;/code&gt;&lt;/a&gt; just arrived on &lt;a href="https://cran.r-project.org/"&gt;CRAN&lt;/a&gt;, and it is faster and easier to use than previous releases.&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-r" data-lang="r"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nf"&gt;install.packages&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s"&gt;&amp;#34;drake&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;h2&gt;
Recap
&lt;/h2&gt;&lt;p&gt;Data analysis can be slow. A round of scientific computation can take several minutes, hours, or even days to complete. After it finishes, if you update your code or data, your hard-earned results may no longer be valid. How much of that valuable output can you keep, and how much do you need to update? How much runtime must you endure all over again?&lt;/p&gt;</description></item><item><title>Community Call - Research Applications of rOpenSci Taxonomy and Biodiversity Tools</title><link>https://ropensci.org/blog/2019/03/11/commcall-mar2019/</link><pubDate>Mon, 11 Mar 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/03/11/commcall-mar2019/</guid><description>
&lt;p&gt;Our next Community Call, on March 27th, aims to help people learn about using rOpenSci&amp;rsquo;s R packages to access and analyze taxonomy and biodiversity data, and to recognize the breadth and depth of their applications. We also aim to learn from the discussion how we might improve these tools. Presentations will start with an introduction to the topic and details on some specific packages and we&amp;rsquo;ll hear from several people about their &amp;ldquo;use cases in the wild&amp;rdquo;.&lt;/p&gt;</description></item><item><title>handlr: convert among citation formats</title><link>https://ropensci.org/blog/2019/02/27/handlr-release/</link><pubDate>Wed, 27 Feb 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/02/27/handlr-release/</guid><description>
&lt;p&gt;Citations are a crucial piece of scholarly work. They hold metadata on each scholarly work, including what people were involved, what year the work was published, where it was published, and more. The links between citations facilitate insight into many questions about scholarly work.&lt;/p&gt;
&lt;p&gt;Citations come in &lt;a href="https://github.com/datacite/bolognese#features"&gt;many different formats&lt;/a&gt; including BibTex, RIS, JATS, and many more. This is not to be confused with &lt;a href="https://citationstyles.org/"&gt;citation styles&lt;/a&gt; such as APA vs. MLA and so on.&lt;/p&gt;</description></item><item><title>stats19: a package for road safety research</title><link>https://ropensci.org/blog/2019/02/26/stats19/</link><pubDate>Tue, 26 Feb 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/02/26/stats19/</guid><description>
&lt;h4&gt;
Introduction
&lt;/h4&gt;&lt;p&gt;&lt;code&gt;stats19&lt;/code&gt; is a new R package enabling access to and working with
Great Britain’s official road traffic casualty database,
&lt;a href="https://data.gov.uk/dataset/cb7ae6f0-4be6-4935-9277-47e5ce24a11f/road-safety-data"&gt;STATS19&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;We started the package in late 2018 following three main motivations:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;The release of the 2017 road crash statistics, which showed
worsening road safety in some areas, increasing the importance of
making the data more accessible.&lt;/li&gt;
&lt;li&gt;The realisation that many researchers were writing ad hoc code to
clean the data, with a huge amount of duplicated (wasted) effort and
potential for mistakes to lead to errors in the labelling of the
data (more on that below).&lt;/li&gt;
&lt;li&gt;An understanding of the concept of ‘modularity’ in software design,
following the &lt;a href="https://en.wikipedia.org/wiki/Unix_philosophy"&gt;Unix
philosophy&lt;/a&gt; that
programs should ‘do one thing and do it well’. This realisation has
led to code inside the rOpenSci-hosted package
&lt;a href="https://github.com/ropensci/stplanr"&gt;&lt;code&gt;stplanr&lt;/code&gt;&lt;/a&gt; being split-out
into two separate packages:
&lt;a href="https://github.com/Robinlovelace/cyclestreets"&gt;&lt;code&gt;cyclestreets&lt;/code&gt;&lt;/a&gt; and
&lt;a href="https://github.com/ropensci/stats19"&gt;&lt;code&gt;stats19&lt;/code&gt;&lt;/a&gt;.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;We have a wider motivation: we want the roads to be safer. By making
data on the nature of road crashes more publicly accessible to inform policy,
we hope this package saves lives.&lt;/p&gt;</description></item><item><title>Bugfix release for the ssh package</title><link>https://ropensci.org/blog/2019/02/22/ssh-04/</link><pubDate>Fri, 22 Feb 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/02/22/ssh-04/</guid><description>
&lt;p&gt;The ssh package provides a native ssh client for R. You can connect to a remote server over SSH to transfer files via SCP, setup a secure tunnel, or run a command or script on the host while streaming stdout and stderr directly to the client. The &lt;a href="https://cran.r-project.org/web/packages/ssh/vignettes/intro.html"&gt;intro vignette&lt;/a&gt; provides a brief introduction.&lt;/p&gt;
&lt;p&gt;This week &lt;a href="https://cran.r-project.org/package=ssh"&gt;version 0.4&lt;/a&gt; has been released, so you can install it directly from CRAN:&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-r" data-lang="r"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nf"&gt;install.packages&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s"&gt;&amp;#34;ssh&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;The &lt;a href="https://cran.r-project.org/web/packages/ssh/NEWS"&gt;NEWS&lt;/a&gt; file shows that this is mostly a bugfix release:&lt;/p&gt;</description></item><item><title>DataONE webinar</title><link>https://ropensci.org/events/2019-02-12-dataone/</link><pubDate>Tue, 12 Feb 2019 10:00:00 +0000</pubDate><guid>https://ropensci.org/events/2019-02-12-dataone/</guid><description>
&lt;h3&gt;
rOpenSci: high quality research software for reproducible data science
&lt;/h3&gt;&lt;p&gt;Two members of our team - Karthik Ram and Scott Chamberlain - will present at the monthly DataONE webinar. They will cover our peer review process for scientific software and highlight a few of our flagship packages with use cases and examples.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Time&lt;/strong&gt;: 9 am Pacific; &lt;a href="https://www.timeanddate.com/worldclock/fixedtime.html?msg=rOpenSci+DataONE+webinar&amp;amp;iso=20190212T09&amp;amp;p1=1050&amp;amp;ah=1"&gt;Find your timezone&lt;/a&gt;
&lt;/br&gt;
&lt;a href="https://www.dataone.org/webinars/ropensci-high-quality-research-software-reproducible-data-science"&gt;Registration required&lt;/a&gt; (free)&lt;/p&gt;</description></item><item><title>Community Call Follow-up - Governance of Open Source Research Software Organizations</title><link>https://ropensci.org/blog/2019/02/12/governance/</link><pubDate>Tue, 12 Feb 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/02/12/governance/</guid><description>
&lt;p&gt;We tend to know a good open source research software project when we see it: The code is well-documented, users contribute back to the project, the software is licensed and citable, and the community interacts and co-produces in a healthy, productive fashion. The academic literature &lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt; and community discourse &lt;sup id="fnref:2"&gt;&lt;a href="#fn:2" class="footnote-ref" role="doc-noteref"&gt;2&lt;/a&gt;&lt;/sup&gt; around research software development offer insight into how to promote the technical best-practices needed to produce some of these project attributes; however, the management of non-technical, social components of software projects are less visible and therefore less often discussed in best-practice pieces. In a &lt;a href="https://ropensci.org/commcalls/2018-12-18/"&gt;recent community call&lt;/a&gt;, I discussed some of these components through the lens of &lt;a href="https://ropensci.org/blog/2017/10/06/sholler-plan/"&gt;my research&lt;/a&gt; on open source research software project governance.&lt;/p&gt;</description></item><item><title>A Major Upgrade of the V8 package</title><link>https://ropensci.org/blog/2019/02/11/v8-20/</link><pubDate>Mon, 11 Feb 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/02/11/v8-20/</guid><description>
&lt;p&gt;This week &lt;a href="https://cran.r-project.org/package=V8"&gt;version 2.0 of the V8 package&lt;/a&gt; has been released to CRAN. Go get it now!&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-r" data-lang="r"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nf"&gt;install.packages&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s"&gt;&amp;#34;V8&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;The V8 package provides an embedded JavaScript engine that can be used inside of R. You can use it interactively as a JavaScript console, but it is mostly useful for wrapping JavaScript libraries in R packages. Some cool examples include &lt;a href="https://cran.r-project.org/web/packages/jsonld/index.html"&gt;jsonld&lt;/a&gt;, &lt;a href="https://cran.r-project.org/web/packages/jsonvalidate/index.html"&gt;jsonvalidate&lt;/a&gt;, and &lt;a href="https://cran.r-project.org/web/packages/daff/index.html"&gt;daff&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;This major and much anticipated upgrade brings a new version of the JavaScript engine, effectively upgrading the JavaScript language. This opens up a lot of new possibilities, but it can also introduce some subtle behavioral changes, so read on carefully.&lt;/p&gt;</description></item><item><title>rOpenSci Software Peer Review: Still Improving</title><link>https://ropensci.org/blog/2019/02/01/software-review-news/</link><pubDate>Fri, 01 Feb 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/02/01/software-review-news/</guid><description>
&lt;p&gt;rOpenSci&amp;rsquo;s &lt;a href="https://ropensci.org/packages/"&gt;suite of packages&lt;/a&gt; is comprised of contributions from staff engineers and the wider R community, bringing considerable diversity of skills, expertise and experience to bear on the suite. How do we ensure that every package is held to a high standard? That&amp;rsquo;s where our software review system comes into play: packages contributed by the community undergo a &lt;strong&gt;transparent, constructive, non adversarial and open review process&lt;/strong&gt;. For that process relying mostly on &lt;strong&gt;volunteer work&lt;/strong&gt;, &lt;em&gt;&lt;a href="https://devguide.ropensci.org/softwarereviewintro.html#associateditors"&gt;associate editors&lt;/a&gt;&lt;/em&gt; manage the incoming flow and ensure progress of submissions; &lt;em&gt;authors&lt;/em&gt; create, submit and improve their package; &lt;em&gt;&lt;a href="https://devguide.ropensci.org/#reviewers"&gt;reviewers&lt;/a&gt;&lt;/em&gt;, two per submission, examine the software code and user experience.&lt;/p&gt;</description></item><item><title>Announcing new software peer review editors: Melina Vidoni and Brooke Anderson</title><link>https://ropensci.org/blog/2019/01/31/more_editors/</link><pubDate>Thu, 31 Jan 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/01/31/more_editors/</guid><description>
&lt;p&gt;We are pleased to welcome Brooke Anderson and Melina Vidoni to our team of &lt;a href="https://devguide.ropensci.org/softwarereviewintro.html#associateditors"&gt;Associate Editors&lt;/a&gt; for rOpenSci &lt;a href="https://ropensci.org/software-review/"&gt;Software Peer Review&lt;/a&gt;. They join Scott Chamberlain, Anna Krystalli, Lincoln Mullen, Karthik Ram, Noam Ross and Maëlle Salmon. With the addition of Brooke and Melina, our editorial board now includes four women and four men, located in North America, South America and Europe.&lt;/p&gt;
&lt;p&gt;Our open Software Peer Review system for community-contributed R tools is a key component of &lt;a href="https://ropensci.org/about/"&gt;our mission&lt;/a&gt; to create technical infrastructure that lowers barriers to working with data sources on the web. Editors manage the review process, performing initial package checks, identifying reviewers, and moderating the process until the package is accepted by reviewers and transferred to rOpenSci. The number of packages submitted for review has increased every year, resulting in an increased &lt;a href="https://ropensci.org/blog/2018/05/03/onboarding-is-work/#work-done-by-editors"&gt;workload for Editors&lt;/a&gt; and the need to expand the team.&lt;/p&gt;</description></item><item><title>Interacting with The Demographic and Health Surveys (DHS) Program data</title><link>https://ropensci.org/blog/2019/01/29/rdhs/</link><pubDate>Tue, 29 Jan 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/01/29/rdhs/</guid><description>
&lt;p&gt;There seem to be a lot of ways to write about your R package, and rather than have
to decide on what to focus on I thought I&amp;rsquo;d write a little bit about everything.
To begin with I thought it best to describe what problem &lt;code&gt;rdhs&lt;/code&gt; tries to solve,
why it was developed and how I came to be involved in this project. I then give a
brief overview of what the package can do, before continuing to
describe how writing my first proper package and the rOpenSci
review process was. Lastly I wanted to share a couple of things that I learnt along
the way. These are not very clever or difficult things,
but rather things that were difficult to Google, which now I think about it should probably
be the best metric for a difficult problem.&lt;/p&gt;</description></item><item><title>ConectaR</title><link>https://ropensci.org/events/conectar/</link><pubDate>Fri, 25 Jan 2019 10:00:00 +0000</pubDate><guid>https://ropensci.org/events/conectar/</guid><description>
&lt;p&gt;Our software engineer Maëlle Salmon will give a keynote talk about rOpenSci at the &lt;a href="https://www.conectar2019.org/"&gt;ConectaR 2019 conference&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>wateRinfo - Downloading tidal data to understand the behaviour of a migrating eel</title><link>https://ropensci.org/blog/2019/01/22/waterinfo-tidal-eel/</link><pubDate>Tue, 22 Jan 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/01/22/waterinfo-tidal-eel/</guid><description>
&lt;blockquote&gt;
&lt;p&gt;Do you know what that sound is, Highness? Those are the Shrieking Eels — if you don&amp;rsquo;t believe me, just wait. They always grow louder when they&amp;rsquo;re about to feed on human flesh. If you swim back now, I promise, no harm will come to you. I doubt you will get such an offer from the Eels.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Vizzini, &lt;a href="https://youtu.be/KGcat9tGZVU"&gt;The Princess Bride&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;European eels (&lt;a href="https://en.wikipedia.org/wiki/Anguilla_anguilla"&gt;&lt;em&gt;Anguilla anguilla&lt;/em&gt;&lt;/a&gt;) have it tough. Not only are they depicted as monsters in movies, they are &lt;a href="https://doi.org/10.2305/IUCN.UK.2014-1.RLTS.T60344A45833138.en"&gt;critically endangered&lt;/a&gt; in real life. One of the many aspects that is contributing to their decline is the reduced connectivity between their freshwater and marine habitats. Eels are catadromous: they live in freshwater, but migrate to the Sargasso Sea to spawn, a route that is blocked by numerous human structures (shipping locks, sluices, pumping stations, etc.). &lt;a href="http://www.marinebiology.ugent.be/node/68491"&gt;Pieterjan Verhelst&lt;/a&gt; studies the impact of these structures on the behaviour of eels, making use of the &lt;a href="https://lifewatch.be/en/fish-acoustic-receiver-network"&gt;fish acoustic receiver network&lt;/a&gt; that was established as part of the Belgian LifeWatch observatory. This animated video gives a quick introduction to his research and the receiver network:&lt;/p&gt;</description></item><item><title>rstudio::conf</title><link>https://ropensci.org/events/2019-01-15-rstudioconf/</link><pubDate>Tue, 15 Jan 2019 08:00:00 +0000</pubDate><guid>https://ropensci.org/events/2019-01-15-rstudioconf/</guid><description>
&lt;p&gt;Two members of our team will attend &lt;a href="https://www.cvent.com/events/rstudio-conf-austin/event-summary-dd6d75526f3c4554b67c4de32aeffb47.aspx"&gt;rstudio::conf&lt;/a&gt;, chat with them if you have questions about rOpenSci.&lt;/p&gt;
&lt;h3&gt;
A guide to modern reproducible data science
&lt;/h3&gt;&lt;p&gt;&lt;strong&gt;Karthik Ram&lt;/strong&gt; (Tidyverse-ext, session 1)&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Have you ever had a challenging time cloning someone&amp;rsquo;s data analysis repo and easily re-running the analysis without fiddling with missing packages, mismatched versions, external dependencies, unavailable data or a whole host of other issues? Would you like your own work to be reproducible where someone else can access your data, code, workflow, models and provenance and easily re-create your results without consulting you? Then this is the talk for you. You&amp;rsquo;ll learn about creating custom computing environments that can be shared and instantly with remote users, packaging small to medium data inside and outside packages, and creating simple to complex workflows to track the provenance of your results.&lt;/em&gt;&lt;/p&gt;</description></item><item><title>rOpenSci's new Code of Conduct</title><link>https://ropensci.org/blog/2019/01/14/conduct/</link><pubDate>Mon, 14 Jan 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/01/14/conduct/</guid><description>
&lt;p&gt;We are pleased to announce the release of our &lt;a href="https://ropensci.org/code-of-conduct"&gt;new Code of Conduct&lt;/a&gt;. rOpenSci&amp;rsquo;s community is our best asset and it&amp;rsquo;s important that we put strong mechanisms in place before we have to act on a report.&lt;/p&gt;
&lt;p&gt;As before, our Code applies equally to members of the rOpenSci team and to anyone from the community at large participating in in-person or online activities.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;What&amp;rsquo;s new?&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;A Code of Conduct Committee: Stefanie Butland (rOpenSci Community Manager), Scott Chamberlain (rOpenSci Co-founder and Technical Lead) and Kara Woo (independent community member). We are responsible for receiving, investigating, deciding, enforcing and reporting on all reports of potential violations of our Code.&lt;/li&gt;
&lt;li&gt;Greater detail about acceptable and unacceptable behaviors&lt;/li&gt;
&lt;li&gt;Clear instructions on how to make a report&lt;/li&gt;
&lt;li&gt;Information on how reports will be handled&lt;/li&gt;
&lt;li&gt;A commitment to transparency with our community while upholding the privacy of victims&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Our new Code of Conduct has been influenced by and adapted from many sources including the &lt;a href="https://youtu.be/nizfHxg8y3o"&gt;Open Source and Feelings&lt;/a&gt; talk by &lt;a href="https://lifeofaudrey.com/"&gt;Audrey Eschright&lt;/a&gt;, the R Consortium Community Diversity and Inclusion Working Group&amp;rsquo;s draft &lt;a href="https://github.com/RConsortium/RCDI-WG/tree/master/conduct"&gt;Code of Conduct&lt;/a&gt;, the &lt;a href="https://geekfeminism.wikia.com/wiki/Community_anti-harassment/Policy"&gt;Geek Feminism anti-harassment policy&lt;/a&gt;, our own Community Call, &lt;a href="https://ropensci.org/blog/2016/12/21/commcallv12-review-coc/"&gt;How do I create a Code of Conduct for my event/lab/codebase?&lt;/a&gt;, incident reporting forms from &lt;a href="https://numfocus.org/code-of-conduct"&gt;NumFOCUS&lt;/a&gt; &amp;amp; &lt;a href="https://github.com/jupyter/governance/blob/master/conduct/code_of_conduct.md"&gt;Jupyter&lt;/a&gt;, and perhaps most importantly, by community members from whom we learn so much.&lt;/p&gt;</description></item><item><title>vitae: Dynamic CVs with R Markdown</title><link>https://ropensci.org/blog/2019/01/10/vitae/</link><pubDate>Thu, 10 Jan 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/01/10/vitae/</guid><description>
&lt;h3&gt;
Why vitae?
&lt;/h3&gt;&lt;div class="float-left"&gt;&lt;figure class="m-0"&gt;&lt;img src="PeFoXDy.png"
alt="vitae logo"ZgotmplZ
ZgotmplZ
ZgotmplZ
ZgotmplZ
style=" object-fit: cover; object-position: center; height: 250px; width: 250px; margin-right: 15px"
/&gt;
&lt;p&gt;
&lt;p&gt;The process of maintaining a CV can be tedious. It&amp;rsquo;s a task I often forget about - that is until someone requests it and I find that my latest is woefully out of date. To make matters worse, these professional updates often need repeating across variety of sites (such as ORCID and LinkedIn).&lt;/p&gt;</description></item><item><title>An even better rOpenSci website with Hugo</title><link>https://ropensci.org/blog/2019/01/09/hugo/</link><pubDate>Wed, 09 Jan 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/01/09/hugo/</guid><description>
&lt;p&gt;A bit more than one year ago, rOpenSci &lt;a href="https://twitter.com/rOpenSci/status/925036483383148545"&gt;launched its new website design&lt;/a&gt;, by the designer &lt;a href="https://www.marulango.com/"&gt;Maru Lango&lt;/a&gt;. Not only did the website appearance change (for the better!), but the underlying framework too. &lt;a href="https://ropensci.org"&gt;ropensci.org&lt;/a&gt; is powered by &lt;a href="https://gohugo.io/"&gt;Hugo&lt;/a&gt;, like &lt;a href="https://CRAN.R-project.org/package=blogdown"&gt;&lt;code&gt;blogdown&lt;/code&gt;&lt;/a&gt;! Over the last few months, we&amp;rsquo;ve made the best of this framework, hopefully improving your browsing experience (and trapping you into binge reading). In this note, we&amp;rsquo;ll go over the main developments, as well as give some Hugo tips.&lt;/p&gt;</description></item><item><title>Continuing to Grow Community Together at ozunconf, 2018</title><link>https://ropensci.org/blog/2019/01/08/ozunconf18/</link><pubDate>Tue, 08 Jan 2019 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2019/01/08/ozunconf18/</guid><description>
&lt;p&gt;&lt;img src="https://ropensci.org/img/blog-images/2019-01-08-ozunconf/melb-logo.png" alt=""&gt;&lt;/p&gt;
&lt;p&gt;In late November 2018, we ran the &lt;a href="https://ozunconf18.ropensci.org"&gt;third annual rOpenSci ozunconf&lt;/a&gt;. This is the sibling rOpenSci unconference, held in Australia. We ran the first ozunconf &lt;a href="https://ropensci.org/blog/2016/06/16/au-unconf"&gt;in Brisbane&lt;/a&gt; in 2016, and the second &lt;a href="https://ropensci.org/blog/2017/10/31/ozunconf2017"&gt;in Melbourne&lt;/a&gt; in 2017.&lt;/p&gt;
&lt;p&gt;&lt;img src="https://ropensci.org/img/blog-images/2019-01-08-ozunconf/adam-anna-sarah.jpeg" alt=""&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Photos taken by Ajay from &lt;a href="https://www.fotoholics.org/"&gt;Fotoholics&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;As usual, before the unconf, we started discussion on &lt;a href="https://github.com/ropensci/ozunconf18/issues"&gt;GitHub issue threads&lt;/a&gt;,
and the excitement was building with the number of issues.&lt;/p&gt;
&lt;p&gt;The day before the unconf we ran &amp;ldquo;Day 0 training&amp;rdquo; - an afternoon explaining R packages and GitHub. This aimed to show people how to create an R package, set it up with version control with git, then put it on GitHub, and share it with others. The idea behind delivering this course was not necessarily to have people become experts in R package development and GitHub. Instead, it aimed to gently introduce the ideas and concepts of R packages and GitHub, so that people can hit the ground running over the next two days.&lt;/p&gt;</description></item><item><title>Spelling 2.0: Improved Markdown and RStudio Support</title><link>https://ropensci.org/blog/2018/12/20/spelling-20/</link><pubDate>Thu, 20 Dec 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/12/20/spelling-20/</guid><description>
&lt;p&gt;We have released updates for the rOpenSci text analysis tools. This technote will highlight some of the major improvements in the &lt;a href="https://github.com/ropensci/spelling#readme"&gt;spelling&lt;/a&gt; package and also the underlying &lt;a href="https://cloud.r-project.org/web/packages/hunspell/vignettes/intro.html"&gt;hunspell&lt;/a&gt; package, which provides the spelling engine for the spelling package.&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-r" data-lang="r"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nf"&gt;install.packages&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s"&gt;&amp;#34;spelling&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Update to the latest versions to use these cool new features!&lt;/p&gt;
&lt;h2&gt;
Automatic Checking of README and NEWS files
&lt;/h2&gt;&lt;p&gt;Users that are already using &lt;em&gt;spelling&lt;/em&gt; on their packages might discover a few new typos! The new version of spelling now also checks the &lt;code&gt;readme.md&lt;/code&gt; and &lt;code&gt;news.md&lt;/code&gt; and &lt;code&gt;index.md&lt;/code&gt; files in your package root directory.&lt;/p&gt;</description></item><item><title>Governance strategies for open source research software projects</title><link>https://ropensci.org/commcalls/2018-12-18/</link><pubDate>Tue, 18 Dec 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/commcalls/2018-12-18/</guid><description/></item><item><title>rcites - The story behind the package</title><link>https://ropensci.org/blog/2018/12/18/accessing-cites-data/</link><pubDate>Tue, 18 Dec 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/12/18/accessing-cites-data/</guid><description>
&lt;h3&gt;
The Ecology Hackathon
&lt;/h3&gt;&lt;p&gt;Almost one year ago now, ecologists filled a room for the &lt;a href="https://methodsblog.com/2018/01/23/ecology-hackathon/"&gt;“Ecology Hackathon: Developing R Packages for Accessing, Synthesizing and Analyzing Ecological Data”&lt;/a&gt; that was co-organised by rOpenSci Fellow, &lt;a href="https://twitter.com/_nickgolding_"&gt;Nick Golding&lt;/a&gt; and &lt;a href="https://besjournals.onlinelibrary.wiley.com/journal/2041210x"&gt;Methods in Ecology and Evolution&lt;/a&gt;. This hackathon was part of the “Ecology Across Borders” Joint Annual Meeting 2017 of &lt;a href="https://www.britishecologicalsociety.org/"&gt;BES&lt;/a&gt;, &lt;a href="https://www.gfoe.org/en"&gt;GfÖ&lt;/a&gt;, &lt;a href="http://www.necov.org/"&gt;NecoV&lt;/a&gt;, and &lt;a href="https://www.europeanecology.org/"&gt;EEF&lt;/a&gt; in Ghent. At different tables, different people joined each other to work on different ideas to implement as R packages. At our table, we were around ten people that more or less did not know anything about what we aimed for. We barely knew each other and nobody had clear expectations, just the desire of learning more about R packages. We were interested in a common idea posted as a &lt;a href="https://github.com/ropensci/wishlist/issues/29"&gt;wishlist&lt;/a&gt; in the rOpenSci community: building an R package to interact with &lt;a href="https://cites.org/"&gt;CITES&lt;/a&gt; and its &lt;a href="https://speciesplus.net"&gt;Speciesplus database&lt;/a&gt;. CITES (the Convention on International Trade in Endangered Species of Wild Fauna and Flora) is an international agreement between governments and provides key information to ensure that international trade in specimens of wild animals and plants does not threaten their survival. At 10 am, nobody had a clear idea on where to start. By 6 pm, we had a functional prototype of the &lt;code&gt;rcites&lt;/code&gt; package, which was really rewarding and gave motivation to follow up on the package development. We did great team-work, met new researchers, and learned a bunch of new stuff. This was definitely a successful hackathon!&lt;/p&gt;</description></item><item><title>Pdftools 2.0: powerful pdf text extraction tools</title><link>https://ropensci.org/blog/2018/12/14/pdftools-20/</link><pubDate>Fri, 14 Dec 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/12/14/pdftools-20/</guid><description>
&lt;p&gt;A new version of pdftools has been released to CRAN. Go get it while it&amp;rsquo;s hot:&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-r" data-lang="r"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nf"&gt;install.packages&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s"&gt;&amp;#34;pdftools&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;This version has two major improvements: low level text extraction and encoding improvements.&lt;/p&gt;
&lt;h2&gt;
About PDF textboxes
&lt;/h2&gt;&lt;p&gt;A pdf document may seem to contain paragraphs or tables in a viewer, but this is not actually true. PDF is a &lt;em&gt;printing format&lt;/em&gt;: a page consists of a series of unrelated lines, bitmaps, and textboxes with a given size, position and content. Hence a table in a pdf file is really just a large unordered set of lines and words that are nicely visually positioned. This makes sense for printing, but makes extracting text or data from a pdf file extremely difficult.&lt;/p&gt;</description></item><item><title>Generating reasonable starting trees for complex phylogenetic analyses</title><link>https://ropensci.org/blog/2018/12/11/treestartr/</link><pubDate>Tue, 11 Dec 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/12/11/treestartr/</guid><description>
&lt;p&gt;I never really thought I would write an R package. I use R pretty casually. Then, this year, I was invited to participate during the last week of the &lt;a href="http://www.analytical.palaeobiology.de/"&gt;Analytical Paleobiology short course&lt;/a&gt;, an intensive month-long experience in quantitative paleontology. I was thrilled to be invited. But I got a slight sinking feeling in my stomach when I realized all the materials were in R.&lt;/p&gt;
&lt;p&gt;And so I, a Pythonista, decided I would spend some of my maternity leave writing R packages to try to blend in with students who had spent the month living and breathing R.&lt;/p&gt;</description></item><item><title>Community Call - Governance strategies for open source research software projects</title><link>https://ropensci.org/blog/2018/12/05/commcall-dec2018/</link><pubDate>Wed, 05 Dec 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/12/05/commcall-dec2018/</guid><description>
&lt;p&gt;🎤 Dan Sholler, rOpenSci Postdoctoral Fellow&lt;/p&gt;
&lt;p&gt;🕘 Tuesday, December 18, 2018, 10-11AM PST; 7-8PM CET (&lt;a href="https://www.timeanddate.com/worldclock/fixedtime.html?iso=20181218T10&amp;amp;p1=791&amp;amp;ah=1&amp;amp;msg=governance-strategies-for-open-source-research-software-projects"&gt;find your timezone&lt;/a&gt;)&lt;/p&gt;
&lt;p&gt;☎️ &lt;a href="https://ropensci.org/commcalls"&gt;Details for joining the Community Call&lt;/a&gt;. Everyone is welcome. No RSVP needed.&lt;/p&gt;
&lt;p&gt;Researchers use open source software for the capabilities it provides, such as streamlined data access and analysis and interoperability with other pieces of the scientific computing ecosystem. For most complex software, generating these technical capabilities requires building and governing a community via sound management practices, activities that are often less visible than code contributions and other software development work. And unless the initial developers commit to doing all the needed work for a long time, a community needs to develop to sustain the software, and in many cases, to determine where the software should go. In this call, we’ll pull back the cover on some of the non-technical work that goes into building and sustaining a software project by highlighting the governance challenges projects face and the strategies they use to overcome them.&lt;/p&gt;</description></item><item><title>Detecting spatiotemporal groups in relocation data with spatsoc</title><link>https://ropensci.org/blog/2018/12/04/spatsoc/</link><pubDate>Tue, 04 Dec 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/12/04/spatsoc/</guid><description>
&lt;p&gt;&lt;a href="https://github.com/ropensci/spatsoc"&gt;spatsoc&lt;/a&gt; is an R package written by Alec Robitaille, Quinn Webber and Eric Vander Wal of the Wildlife Evolutionary Ecology Lab (&lt;a href="https://weel.gitlab.io"&gt;WEEL&lt;/a&gt;) at Memorial University of Newfoundland. It is the lab&amp;rsquo;s first R package and was recently accepted through the rOpenSci onboarding process with a big thanks to reviewers &lt;a href="https://github.com/pmnatural"&gt;Priscilla Minotti&lt;/a&gt; and &lt;a href="https://github.com/FilipeamTeixeira"&gt;Filipe Teixeira&lt;/a&gt;, and editor &lt;a href="https://github.com/lmullen"&gt;Lincoln Mullen&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;code&gt;spatsoc&lt;/code&gt; started as a single function (what would eventually become &lt;code&gt;group_pts&lt;/code&gt;) written by Alec in 2017 to help answer some of the questions that Quinn and Eric were asking about how animal social structure is related to spatial processes. These ideas were originally proposed by Quinn and Eric in their recent review paper &lt;sup&gt;&lt;a href="#ref1"&gt;1&lt;/a&gt;&lt;/sup&gt;. After our ideas were published, we began using this early function to determine when GPS collared caribou (&lt;em&gt;Rangifer tarandus&lt;/em&gt;) in Newfoundland were recorded within 50 m of one another, within 5 minutes. This spatiotemporal grouping allowed us to build and analyze social association networks with &lt;a href="https://sites.google.com/site/drfarine/r-packages/asnipe"&gt;&lt;code&gt;asnipe&lt;/code&gt;&lt;/a&gt; and &lt;a href="https://igraph.org/r/"&gt;&lt;code&gt;igraph&lt;/code&gt;&lt;/a&gt;. Using animal telemetry data with social network analysis allowed us to draw new insights from a long term movement dataset.&lt;/p&gt;</description></item><item><title>rnoaa: new data sources and NCDC units</title><link>https://ropensci.org/blog/2018/12/04/rnoaa-update/</link><pubDate>Tue, 04 Dec 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/12/04/rnoaa-update/</guid><description>
&lt;p&gt;We&amp;rsquo;ve just released a new version of &lt;a href="https://github.com/ropensci/rnoaa"&gt;rnoaa&lt;/a&gt; with A LOT of changes. Check out
the &lt;a href="https://github.com/ropensci/rnoaa/releases/tag/v0.8.0"&gt;release notes&lt;/a&gt;
for a complete list of changes.&lt;/p&gt;
&lt;p&gt;We&amp;rsquo;ll highlight a few things in this post:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;New data sources in the package&lt;/li&gt;
&lt;li&gt;NCDC units added to the output of &lt;code&gt;ncdc()&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Links:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;rnoaa source code: &lt;a href="https://github.com/ropensci/rnoaa"&gt;https://github.com/ropensci/rnoaa&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;rnoaa on CRAN: &lt;a href="https://cran.rstudio.com/web/packages/rnoaa/"&gt;https://cran.rstudio.com/web/packages/rnoaa/&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;
Installation
&lt;/h2&gt;&lt;p&gt;Install the lastest from CRAN&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-r" data-lang="r"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nf"&gt;install.packages&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s"&gt;&amp;#34;rnoaa&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Some binaries are not up yet on CRAN - you can also install from GitHub:&lt;/p&gt;</description></item><item><title>restez: Query GenBank locally</title><link>https://ropensci.org/blog/2018/12/03/restez/</link><pubDate>Mon, 03 Dec 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/12/03/restez/</guid><description>
&lt;h2&gt;
What is &lt;code&gt;restez&lt;/code&gt;?
&lt;/h2&gt;&lt;p&gt;R packages for interacting with the National Center for Biotechnology Information (NCBI) have, to-date, depended on &lt;a href="https://en.wikipedia.org/wiki/Application_programming_interface"&gt;API&lt;/a&gt; query calls via &lt;a href="https://www.ncbi.nlm.nih.gov/search/"&gt;NCBI&amp;rsquo;s Entrez&lt;/a&gt;.
For computational analyses that require the automated look-up of reams of biological sequence data, piecemeal querying via bandwith-limited requests is evidently not ideal. These queries are not only slow, but they depend on network connections and the remote server&amp;rsquo;s consistent behaviour. Additionally, users who make very large requests over extended periods of time run the risk of being blocked.&lt;/p&gt;</description></item><item><title>Community Call Summary - Code Review in the Lab</title><link>https://ropensci.org/blog/2018/11/29/codereview/</link><pubDate>Thu, 29 Nov 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/11/29/codereview/</guid><description>
&lt;p&gt;Although there are increasing incentives and pressures for researchers to share code (even for projects that are not essentially computational), practices vary widely and standards are mostly non-existent. The practice of &lt;em&gt;reviewing&lt;/em&gt; code then falls to researchers and research groups before publication. With that in mind, rOpenSci hosted a &lt;a href="https://discuss.ropensci.org/t/how-do-you-review-code-that-accompanies-a-research-project-or-paper-help-ropensci-plan-a-community-call"&gt;discussion thread&lt;/a&gt; and a &lt;a href="https://ropensci.org/commcalls/2018-10-16/"&gt;community call&lt;/a&gt; to bring together different researchers for a conversation about current practices, and challenges in reviewing code in the lab.&lt;/p&gt;</description></item><item><title>Co-localization analysis of fluorescence microscopy images</title><link>https://ropensci.org/blog/2018/11/27/colocr/</link><pubDate>Tue, 27 Nov 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/11/27/colocr/</guid><description>
&lt;p&gt;A few months ago, I wasn&amp;rsquo;t sure what to expect when looking at fluorescence microscopy images in published papers. I looked at the accompanying graph to understand the data or the point the authors were trying to make. Often, the graph represents one or more measures of the so-called co-localization, but I couldn’t figure out how to interpret them. It turned out; reading the images is simple. Cells are simultaneously stained by two dyes (say, red and green) for two different proteins. The color turns yellow in the merged image when the two proteins localize in proximity.&lt;/p&gt;</description></item><item><title>Checklist Recipe - How we created a template to standardize species data</title><link>https://ropensci.org/blog/2018/11/20/checklist-recipe/</link><pubDate>Tue, 20 Nov 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/11/20/checklist-recipe/</guid><description>
&lt;p&gt;Imagine you are a fish ecologist who compiled a list of fish species for your country. 🐟&lt;/p&gt;
&lt;p&gt;Your list could be useful to others, so you publish it as a supplementary file to an article or in a research repository. That is fantastic, but it might be difficult for others to discover your list or combine it with other lists of species. Luckily there&amp;rsquo;s a better way to publish species lists: as a standardized checklist that can be harvested and processed by the Global Biodiversity Information Facility (GBIF). We created a documented template to do that in R, which recently won the &lt;a href="https://www.gbif.org/news/4TuHBNfycgO4GEMOKkMi4u/six-winners-top-the-2018-ebbe-nielsen-challenge"&gt;GBIF Ebbe Nielsen Challenge&lt;/a&gt;. In this post we explain how we did that and highlight some of the tools we discovered along the way.&lt;/p&gt;</description></item><item><title>Working with images in R</title><link>https://ropensci.org/commcalls/2018-11-15/</link><pubDate>Thu, 15 Nov 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/commcalls/2018-11-15/</guid><description/></item><item><title>The Antarctic/Southern Ocean rOpenSci community</title><link>https://ropensci.org/blog/2018/11/13/antarctic/</link><pubDate>Tue, 13 Nov 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/11/13/antarctic/</guid><description>
&lt;h3&gt;
Antarctic/Southern Ocean science and rOpenSci
&lt;/h3&gt;&lt;p&gt;Collaboration and reproducibility are &lt;a href="https://doi.org/10.1038/d41586-018-05369-6"&gt;fundamental to Antarctic and Southern Ocean science&lt;/a&gt;, and the value of data to Antarctic science has long been promoted. The &lt;a href="https://www.ats.aq/e/ats.htm"&gt;Antarctic Treaty&lt;/a&gt; (which came into force in 1961) included the provision that scientific observations and results from Antarctica should be openly shared. The high cost and difficulty of acquisition means that data tend to be re-used for different studies once collected. Further, there are many common data requirement themes (e.g. sea ice information is useful to a wide range of activities, from voyage planning through to ecosystem modelling). Support for Antarctic data management is well established. The SCAR-COMNAP Joint Committee on Antarctic Data Management was established in 1997 and remains active &lt;a href="https://www.scar.org/data-products/scadm/"&gt;as a SCAR Standing Commitee&lt;/a&gt; today.&lt;/p&gt;</description></item><item><title>Tesseract 4 is here! State of the art OCR in R!</title><link>https://ropensci.org/blog/2018/11/06/tesseract-40/</link><pubDate>Tue, 06 Nov 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/11/06/tesseract-40/</guid><description>
&lt;p&gt;Last week Google and friends released the new major version of their OCR system: &lt;a href="https://github.com/tesseract-ocr/tesseract/releases"&gt;Tesseract 4&lt;/a&gt;. This release builds upon 2+ years of hard work and has completely overhauled the internal OCR engine. From the &lt;a href="https://github.com/tesseract-ocr/tesseract/wiki/TrainingTesseract-4.00"&gt;tesseract wiki&lt;/a&gt;:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Tesseract 4.0 includes a new neural network-based recognition engine that delivers significantly higher accuracy (on document images) than the previous versions, in return for a significant increase in required compute power. On complex languages however, it may actually be faster than base Tesseract.&lt;/p&gt;</description></item><item><title>Sharing the Recipe for rOpenSci's Unconf Ice Breaker</title><link>https://ropensci.org/blog/2018/11/01/icebreaker/</link><pubDate>Thu, 01 Nov 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/11/01/icebreaker/</guid><description>
&lt;p&gt;While many people groan at the thought of participating in a group ice breaker activity, we&amp;rsquo;ve gotten consistent feedback from people who have been to recent rOpenSci unconferences.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Best ice breaker ever!&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;We&amp;rsquo;ve had lots of requests for a detailed description of how we do it. This post shares our recipe, including a script you can adapt, a reflection on its success, examples of how others have used it, and some tips to remember. Let us know in the comments if you&amp;rsquo;ve used or adapted it!&lt;/p&gt;</description></item><item><title>Community Call - Working with images in R</title><link>https://ropensci.org/blog/2018/10/24/commcall-nov2018/</link><pubDate>Wed, 24 Oct 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/10/24/commcall-nov2018/</guid><description>
&lt;p&gt;rOpenSci&amp;rsquo;s software engineer / postdoc Jeroen Ooms will explain what images are, under the hood, and showcase several &lt;a href="https://ropensci.org/packages/"&gt;rOpenSci packages&lt;/a&gt; that form a modern toolkit for working with images in R, including &lt;a href="https://github.com/ropenscilabs/opencv"&gt;opencv&lt;/a&gt;, &lt;a href="https://github.com/ropensci/av"&gt;av&lt;/a&gt;, &lt;a href="https://github.com/ropensci/tesseract"&gt;tesseract&lt;/a&gt;, &lt;a href="https://github.com/ropensci/magick"&gt;magick&lt;/a&gt; and &lt;a href="https://github.com/ropensci/pdftools"&gt;pdftools&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;🕘 Thursday, November 15, 2018, 10-11AM PST; 7-8PM CET (&lt;a href="https://www.timeanddate.com/worldclock/fixedtime.html?msg=rOpenSci+Community+Call+-+Working+with+images+in+R&amp;amp;iso=20181115T10&amp;amp;p1=791&amp;amp;ah=1"&gt;find your timezone&lt;/a&gt;)&lt;/p&gt;
&lt;p&gt;☎️ Find all details for joining the call on our &lt;a href="https://communitycalls.ropensci.org/#next-call"&gt;Community Calls page&lt;/a&gt;.
Everyone is welcome. No RSVP needed.&lt;/p&gt;
&lt;figure&gt;&lt;img src="https://ropensci.org/img/blog-images/2018-10-24-commcall-nov2018/ropensci-magick.png"
alt="Magick: quantize, histogram"&gt;
&lt;/figure&gt;
&lt;h4&gt;
Agenda
&lt;/h4&gt;&lt;ol&gt;
&lt;li&gt;Welcome (Stefanie Butland, rOpenSci Community Manager, 5 min)&lt;/li&gt;
&lt;li&gt;Working with images in R (Jeroen Ooms, 35 min)&lt;/li&gt;
&lt;li&gt;Q &amp;amp; A (20 min)&lt;/li&gt;
&lt;/ol&gt;
&lt;h4&gt;
Abstract
&lt;/h4&gt;&lt;p&gt;Images in various forms are used for numerous applications across scientific disciplines. Whether you are observing through satellite or microscope, looking at MRI scans or petri dishes, trying to find patterns or abnormalities, the data is in the image. Unfortunately the tools for working with images are traditionally highly fragmented by field, and often narrow in scope. At rOpenSci we are working on a suite of general purpose packages based on powerful c/c++ libraries. These provide an extensible and interoperable foundation for working with images in R, which can be used to implement domain specific-methods. This talk gives a taste of things we can currently do with images in R, and highlights some of the ongoing developments and challenges.&lt;/p&gt;</description></item><item><title>Code Review in the Lab, or ... How do you review code that accompanies a research project or paper?</title><link>https://ropensci.org/commcalls/2018-10-16/</link><pubDate>Tue, 16 Oct 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/commcalls/2018-10-16/</guid><description/></item><item><title>pubchunks: extract parts of scholarly XML articles</title><link>https://ropensci.org/blog/2018/10/16/pubchunks/</link><pubDate>Tue, 16 Oct 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/10/16/pubchunks/</guid><description>
&lt;p&gt;&lt;a href="https://github.com/ropensci/pubchunks"&gt;pubchunks&lt;/a&gt; is a package grown out of the &lt;a href="https://github.com/ropensci/fulltext"&gt;fulltext&lt;/a&gt; package. &lt;code&gt;fulltext&lt;/code&gt;
provides a single interface to many sources of full text scholarly articles. As
part of the user flow in &lt;code&gt;fulltext&lt;/code&gt; there is an extraction step where &lt;code&gt;fulltext::chunks()&lt;/code&gt;
pulls parts of articles out of XML format article files.&lt;/p&gt;
&lt;p&gt;As part of making &lt;code&gt;fulltext&lt;/code&gt; more maintainable and focused on simply fetching articles,
and realizing that pulling out bits of structured XML files is a more general problem,
we broke out &lt;code&gt;pubchunks&lt;/code&gt; into a separate package. &lt;code&gt;fulltext::ft_chunks()&lt;/code&gt; and
&lt;code&gt;fulltext::ft_tabularize()&lt;/code&gt; will eventually be removed and we&amp;rsquo;ll point users to
&lt;code&gt;pubchunks&lt;/code&gt;.&lt;/p&gt;</description></item><item><title>Parsing Metadata with R - A Package Story</title><link>https://ropensci.org/blog/2018/10/09/jstor/</link><pubDate>Tue, 09 Oct 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/10/09/jstor/</guid><description>
&lt;p&gt;Every R package has its story. Some packages are written by experts, some by
novices. Some are developed quickly, others were long in the making. This is the
story of &lt;code&gt;jstor&lt;/code&gt;, a package which I developed during my time as a student of
sociology, working in a research project on the scientific elite within
sociology. Writing the package has taught me many things (more on that later)
and it is deeply gratifying to see, that others find the package useful.&lt;/p&gt;</description></item><item><title>Distinguish yourself in CRAN person() with ORCID</title><link>https://ropensci.org/blog/2018/10/08/orcid/</link><pubDate>Mon, 08 Oct 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/10/08/orcid/</guid><description>
&lt;p&gt;Proper identification of individuals is crucial for acknowledging and
studying their scientific work, be it journal articles or pieces of
software. In this tech note, one year after CRAN started supporting
ORCIDs, we shall explain why and how to use unique author identifiers in
DESCRIPTION files.&lt;/p&gt;
&lt;h2&gt;
Why use ORCIDs on CRAN?
&lt;/h2&gt;&lt;p&gt;When analyzing the authorship of CRAN packages, one can look at authors’
names and email addresses. Names can be written with and without quotes,
email addresses change, which makes it all tricky as &lt;a href="https://blog.revolutionanalytics.com/2018/03/the-most-prolific-package-maintainers-on-cran.html"&gt;noted by David
Smith when he looked for the most prolific CRAN
authors&lt;/a&gt;
(notice our very own Scott Chamberlain and Jeroen Ooms in that
scoreboard by the way?). Besides, several people can have the same name!&lt;/p&gt;</description></item><item><title>The av Package: Production Quality Video in R</title><link>https://ropensci.org/blog/2018/10/06/av-release/</link><pubDate>Sat, 06 Oct 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/10/06/av-release/</guid><description>
&lt;p&gt;At rOpenSci we are developing on a suite of packages that expose powerful graphics and imaging libraries in R. Our latest addition is &lt;a href="https://github.com/ropensci/av#readme"&gt;av&lt;/a&gt; &amp;ndash; a new package for working with audio/video based on the &lt;a href="https://www.ffmpeg.org/"&gt;FFmpeg&lt;/a&gt; AV libraries. This ambitious new project will become the video counterpart of the &lt;a href="https://cloud.r-project.org/web/packages/magick/vignettes/intro.html"&gt;magick&lt;/a&gt; package which we use for working with images.&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-r" data-lang="r"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nf"&gt;install.packages&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s"&gt;&amp;#34;av&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="n"&gt;av&lt;/span&gt;&lt;span class="o"&gt;::&lt;/span&gt;&lt;span class="nf"&gt;av_demo&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;The package can be installed directly from CRAN and includes a test function &lt;code&gt;av_demo()&lt;/code&gt; which generates a demo video from random histograms.&lt;/p&gt;</description></item><item><title>Community Call - Code Review in the Lab, or ... How do you review code that accompanies a research project?</title><link>https://ropensci.org/blog/2018/10/05/commcall-oct2018/</link><pubDate>Fri, 05 Oct 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/10/05/commcall-oct2018/</guid><description>
&lt;p&gt;Do you have code that accompanies a research project or manuscript? How do you review and archive that code before you submit a paper? Our next Community Call will present different perspectives on this hot topic, with plenty of time for Q&amp;amp;A.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;What&amp;rsquo;s the culture of the group around feedback and code collaboration?&lt;/li&gt;
&lt;li&gt;What are the use cases?&lt;/li&gt;
&lt;li&gt;What are some practices that can adopted?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;🕘 Tuesday, October 16th, 9-10 AM PDT (&lt;a href="https://www.timeanddate.com/worldclock/fixedtime.html?msg=rOpenSci+Community+Call&amp;amp;iso=20181016T09&amp;amp;p1=791&amp;amp;ah=1"&gt;find your timezone&lt;/a&gt;)&lt;/p&gt;</description></item><item><title>outcomerate: Transparent Communication of Quality in Social Surveys</title><link>https://ropensci.org/blog/2018/10/02/outcomerate/</link><pubDate>Tue, 02 Oct 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/10/02/outcomerate/</guid><description>
&lt;h4&gt;
Background
&lt;/h4&gt;&lt;p&gt;Surveys are ubiquitous in the social sciences, and the best of them are meticulously planned out. Statisticians often decide on a sample size based on a theoretical design, and then proceed to inflate this number to account for &amp;ldquo;sample losses&amp;rdquo;. This ensures that the desired sample size is achieved, even in the presence of non-response. Factors that reduce the pool of interviews include participant refusals, inability to contact respondents, deaths, and frame inaccuracies.&lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt; The more non-response, the more a study becomes open to criticism about its veracity.&lt;/p&gt;</description></item><item><title>tinkr: editing Markdown documents using XML tools</title><link>https://ropensci.org/blog/2018/10/01/tinkr/</link><pubDate>Mon, 01 Oct 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/10/01/tinkr/</guid><description>
&lt;p&gt;Remember our recent post showing that &lt;a href="https://ropensci.org/technotes/2018/09/05/commonmark/"&gt;one can wrangle Markdown files
programmatically without regex&lt;/a&gt;? That
tech note showed how to convert Markdown bodies to XML in order to
extract information from them. Now, this post goes one step further and
presents &lt;a href="https://github.com/ropenscilabs/tinkr"&gt;&lt;code&gt;tinkr&lt;/code&gt;&lt;/a&gt;, a package for
converting .md and .Rmd files to XML, editing them, and… &lt;strong&gt;writing them
back as Markdown&lt;/strong&gt;!&lt;/p&gt;
&lt;h2&gt;
General tinkr workflow
&lt;/h2&gt;&lt;p&gt;The goal of &lt;code&gt;tinkr&lt;/code&gt; is to convert Markdown files to XML and back to
allow their editing with &lt;code&gt;xml2&lt;/code&gt; (XPath!) instead of numerous complicated
regular expressions. The XML represents the full Markdown &lt;a href="https://en.wikipedia.org/wiki/Abstract_syntax_tree"&gt;syntax tree
(or AST)&lt;/a&gt;. &lt;a href="https://www.w3schools.com/xml/xpath_intro.asp"&gt;If new
to XPath refer to this great
intro&lt;/a&gt;. The package
offers two functions, &lt;code&gt;to_xml()&lt;/code&gt; and &lt;code&gt;to_md()&lt;/code&gt;.&lt;/p&gt;</description></item><item><title>Mapping the 2018 East Africa floods from space with smapr</title><link>https://ropensci.org/blog/2018/09/25/smapr/</link><pubDate>Tue, 25 Sep 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/09/25/smapr/</guid><description>
&lt;p&gt;Hundreds of thousands of people in east Africa have been displaced and hundreds have died as a result of torrential rains which ended a drought but saturated soils and engorged rivers, resulting in extreme flooding in 2018.
This post will explore these events using the R package &lt;code&gt;smapr&lt;/code&gt;, which provides access to global satellite-derived soil moisture data collected by the NASA &lt;a href="https://smap.jpl.nasa.gov/"&gt;Soil Moisture Active-Passive (SMAP) mission&lt;/a&gt; and abstracts away some of the complexity associated with finding, acquiring, and working with the &lt;a href="https://portal.hdfgroup.org/pages/viewpage.action?pageId=48804287"&gt;HDF5&lt;/a&gt; files that contain the observations (shout out to &lt;a href="https://github.com/ldecicco-USGS"&gt;Laura DeCicco&lt;/a&gt; and &lt;a href="https://github.com/marcosci"&gt;Marco Sciaini&lt;/a&gt; for reviewing &lt;code&gt;smapr&lt;/code&gt;, and &lt;a href="https://github.com/noamross"&gt;Noam Ross&lt;/a&gt; for editing in the rOpenSci onboarding process).
We will focus on Somalia and Kenya, two of the hardest hit countries.
We&amp;rsquo;ll also lean on another rOpenSci package, &lt;code&gt;rnoaa&lt;/code&gt;, to link precipitation to soil moisture.&lt;/p&gt;</description></item><item><title>Chat with the rOpenSci team at upcoming meetings</title><link>https://ropensci.org/blog/2018/09/21/ropensci-at-meetings/</link><pubDate>Fri, 21 Sep 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/09/21/ropensci-at-meetings/</guid><description>
&lt;p&gt;You can find members of the rOpenSci team at various meetings and workshops around the world. Come say &amp;lsquo;hi&amp;rsquo;, learn about how our software &lt;a href="https://ropensci.org/packages/"&gt;packages&lt;/a&gt; can enable your research, or about our process for open peer software &lt;a href="https://ropensci.org/software-review/"&gt;review and onboarding&lt;/a&gt;, how you can get connected with the &lt;a href="https://ropensci.org/community/"&gt;community&lt;/a&gt; or tell us how we can help you do open and reproducible research.&lt;/p&gt;</description></item><item><title>Building Reproducible Data Packages with DataPackageR</title><link>https://ropensci.org/blog/2018/09/18/datapackager/</link><pubDate>Tue, 18 Sep 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/09/18/datapackager/</guid><description>
&lt;p&gt;Sharing data sets for collaboration or publication has always been challenging, but it’s become increasingly problematic as complex and high dimensional data sets have become ubiquitous in the life sciences. Studies are large and time consuming; data collection takes time, data analysis is a moving target, as is the software used to carry it out.&lt;/p&gt;
&lt;p&gt;In the vaccine space (&lt;a href="https://www.fredhutch.org/en/research/divisions/vaccine-infectious-disease-division/research/biostatistics-bioinformatics-and-epidemiology.html"&gt;where I work&lt;/a&gt;) we analyze collections of high-dimensional immunological data sets from a variety of different technologies (RNA sequencing, cytometry, multiplexed antibody binding, and others). These data often arise from clinical trials and can involve tens to hundreds of subjects. The data are analyzed by teams of researchers with a diverse variety of goals.&lt;/p&gt;</description></item><item><title>What have these birds been studied for? Querying science outputs with R</title><link>https://ropensci.org/blog/2018/09/11/birds-science/</link><pubDate>Tue, 11 Sep 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/09/11/birds-science/</guid><description>
&lt;p&gt;In the &lt;a href="https://ropensci.org/blog/2018/08/21/birds-radolfzell/"&gt;second post of the series where we obtained data from
eBird&lt;/a&gt; we
determined what birds were observed in the county of Constance, and we
complemented this knowledge with some taxonomic and trait information in
&lt;a href="https://ropensci.org/blog/2018/09/04/birds-taxo-traits/"&gt;the fourth post of the
series&lt;/a&gt;. Now,
we could be curious about the occurrence of these birds in &lt;em&gt;scientific
work&lt;/em&gt;. In this post, we will query the scientific literature and an open
scientific data repository for species names: what have these birds been
studied for? Read on if you want to learn how to use R packages allowing
to do so!&lt;/p&gt;</description></item><item><title>All the Badges One Can Earn: Parsing Badges of CRAN Packages READMEs</title><link>https://ropensci.org/blog/2018/09/10/github-badges/</link><pubDate>Mon, 10 Sep 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/09/10/github-badges/</guid><description>
&lt;p&gt;A while ago we
&lt;a href="https://github.com/ropensci/software-review/issues/130"&gt;onboarded&lt;/a&gt; an
exciting package, &lt;a href="https://github.com/ropensci/codemetar/"&gt;&lt;code&gt;codemetar&lt;/code&gt;&lt;/a&gt;
by &lt;a href="https://ropensci.org/about/#team"&gt;Carl Boettiger&lt;/a&gt;. &lt;code&gt;codemetar&lt;/code&gt; is an R specific
information collector and parser for the &lt;a href="https://github.com/codemeta"&gt;CodeMeta
project&lt;/a&gt;. In particular, &lt;code&gt;codemetar&lt;/code&gt; can
digest metadata about an R package in order to fill &lt;a href="https://codemeta.github.io/terms/"&gt;the terms
recognized by CodeMeta&lt;/a&gt;. This means
extracting information from DESCRIPTION but also from e.g. continuous
integration&lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt; badges in the README! In this note, we’ll take advantage
of &lt;code&gt;codemetar::extract_badges&lt;/code&gt; function to explore the diversity of
badges worn by the READMEs of CRAN packages.&lt;/p&gt;</description></item><item><title>In praise of Commonmark: wrangle (R)Markdown files without regex</title><link>https://ropensci.org/blog/2018/09/05/commonmark/</link><pubDate>Wed, 05 Sep 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/09/05/commonmark/</guid><description>
&lt;p&gt;You might have read &lt;a href="https://ropensci.org/blog/2018/05/10/onboarding-social-weather/"&gt;my blog post analyzing the social weather of
rOpenSci
onboarding&lt;/a&gt;,
based on a text analysis of GitHub issues. I extracted text out of
Markdown-formatted threads with regular expressions. I basically
hammered away at the issues using tools I was familiar with until it
worked! Now I know there’s a much better and cleaner way, that I’ll
present in this note. Read on if you want to extract insights about
text, code, links, etc. from R Markdown reports, Hugo website sources,
GitHub issues… without writing messy and smelly code!&lt;/p&gt;</description></item><item><title>What are these birds? Complement occurrence data with taxonomy and traits information</title><link>https://ropensci.org/blog/2018/09/04/birds-taxo-traits/</link><pubDate>Tue, 04 Sep 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/09/04/birds-taxo-traits/</guid><description>
&lt;p&gt;Thanks to the &lt;a href="https://ropensci.org/blog/2018/08/21/birds-radolfzell/"&gt;second post of the series where we obtained data from
eBird&lt;/a&gt; we know
what birds were observed in the county of Constance. Now, not all
species’ names mean a lot to me, and even if they did, there are a lot
of them. In this post, we shall use rOpenSci’s packages accessing
taxonomy and trait data in order to summarize some characteristics of
the birds’ population of the county: armed with scientific and common
names of birds, we have access to plenty of open data!&lt;/p&gt;</description></item><item><title>What's this bird? Classify old natural history drawings with R</title><link>https://ropensci.org/blog/2018/08/28/birds-ocr/</link><pubDate>Tue, 28 Aug 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/08/28/birds-ocr/</guid><description>
&lt;p&gt;In this new post, we’re taking a break from modern birding data in &lt;a href="https://ropensci.org/tags/birder"&gt;our
birder’s series&lt;/a&gt;… let’s explore
gorgeous drawings from a natural history collection! Armed with
rOpenSci’s packages binding powerful C++ libraries and open taxonomy
data, how much information can we automatically extract from images?
Maybe not much, but we’ll at least have explored image manipulation,
optical character recognition (OCR), language detection, taxonomic name
resolution with rOpenSci’s packages.&lt;/p&gt;
&lt;h2&gt;
Free natural history images and appropriate R tooling!
&lt;/h2&gt;&lt;p&gt;A long time ago I had bookmarked the &lt;a href="https://www.flickr.com/people/biodivlibrary/"&gt;Flickr account of the Biodiversity
Heritage Library (BHL)&lt;/a&gt;.
So many beautiful images of biodiversity, moreover free to use! In
particular, I &lt;a href="https://www.flickr.com/photos/biodivlibrary/sets/72157694191194992"&gt;downloaded all pictures from one of the Birds of
Australia
albums&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>rgbif: seven years of GBIF in R</title><link>https://ropensci.org/blog/2018/08/22/rgbif-seven-years/</link><pubDate>Wed, 22 Aug 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/08/22/rgbif-seven-years/</guid><description>
&lt;p&gt;&lt;a href="https://github.com/ropensci/rgbif"&gt;rgbif&lt;/a&gt; was seven years old yesterday!&lt;/p&gt;
&lt;h2&gt;
What is rgbif?
&lt;/h2&gt;&lt;p&gt;&lt;code&gt;rgbif&lt;/code&gt; gives you access to data from the Global Biodiversity Information Facility (&lt;a href="https://www.gbif.org/"&gt;GBIF&lt;/a&gt;) via their API.&lt;/p&gt;
&lt;p&gt;A samping of use cases covered in &lt;code&gt;rgbif&lt;/code&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Search for datasets&lt;/li&gt;
&lt;li&gt;Get metrics on usage of datasets&lt;/li&gt;
&lt;li&gt;Get metadata about organizations providing data to GBIF&lt;/li&gt;
&lt;li&gt;Search taxonomic names&lt;/li&gt;
&lt;li&gt;Get quick taxonomic name suggestions&lt;/li&gt;
&lt;li&gt;Search occurrences by taxonomic name/country/collector/etc.&lt;/li&gt;
&lt;li&gt;Download occurrences by taxonomic name/country/collector/etc.&lt;/li&gt;
&lt;li&gt;Fetch raster maps to quickly visualize large scale biodiversity&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;
History
&lt;/h2&gt;&lt;p&gt;Our first commit on &lt;code&gt;rgbif&lt;/code&gt; was on &lt;a href="https://github.com/ropensci/rgbif/commit/9042246555151240a5136ccf7530d0524bfb1cb5"&gt;2011-08-26&lt;/a&gt;, uneventfully adding an empty README:&lt;/p&gt;</description></item><item><title>What birds are observed near Radolfzell? Bird occurrence data in R</title><link>https://ropensci.org/blog/2018/08/21/birds-radolfzell/</link><pubDate>Tue, 21 Aug 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/08/21/birds-radolfzell/</guid><description>
&lt;p&gt;Thanks to the &lt;a href="https://ropensci.org/blog/2018/08/14/where-to-bird/"&gt;first post of the
series&lt;/a&gt; we know
where to observe birds near Radolfzell’s Max Planck Institute for
Ornithology, so we could go and do that! Or we can stay behind our
laptops and take advantage of &lt;a href="https://ebird.org/home"&gt;eBird&lt;/a&gt;, a
fantastic bird sightings aggregator! As explained by Matt Strimas-Mackey
in &lt;a href="https://ropensci.org/blog/2018/08/07/auk/"&gt;his recent blog post&lt;/a&gt;,
“The eBird database currently contains over 500 million records of bird
sightings, spanning every country and over 98% of species, making it an
extremely valuable resource for bird research and conservation.”.&lt;/p&gt;</description></item><item><title>Mongolite 2.0: GridFS, connection pooling, and more</title><link>https://ropensci.org/blog/2018/08/14/mongolite-20/</link><pubDate>Tue, 14 Aug 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/08/14/mongolite-20/</guid><description>
&lt;p&gt;This week version 2.0 of the mongolite package has been released to CRAN. Major new features in this release include support for MongoDB 4.0, GridFS, running database commands, and connection pooling.&lt;/p&gt;
&lt;p&gt;Mongolite is primarily an easy-to-use client to get data in and out of MongoDB. However it supports increasingly many advanced features like aggregation, indexing, map-reduce, streaming, encryption, and enterprise authentication. The &lt;a href="https://jeroen.github.io/mongolite/"&gt;mongolite user manual&lt;/a&gt; provides a great introduction with details and worked examples.&lt;/p&gt;</description></item><item><title>Where to go observe birds in Radolfzell? An answer with R and open data</title><link>https://ropensci.org/blog/2018/08/14/where-to-bird/</link><pubDate>Tue, 14 Aug 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/08/14/where-to-bird/</guid><description>
&lt;p&gt;This post is the 1st post of a series showcasing various rOpenSci
packages as if Maëlle were a birder trying to make the most of R in
general and rOpenSci in particular. Although the series use cases will
mostly feature &lt;em&gt;birds&lt;/em&gt;, it’ll be the occasion to highlight rOpenSci’s
packages that are more widely applicable, so read on no matter what your
field is! Moreoever, each post should stand on its own.&lt;/p&gt;</description></item><item><title>phylotaR: Retrieve Orthologous Sequences from GenBank</title><link>https://ropensci.org/blog/2018/08/08/phylotar/</link><pubDate>Wed, 08 Aug 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/08/08/phylotar/</guid><description>
&lt;p&gt;In this technote I will outline what phylotaR was developed for, how to install it and how to run it with some simple examples.&lt;/p&gt;
&lt;h2&gt;
What is phylotaR?
&lt;/h2&gt;&lt;p&gt;In any phylogenetic analysis it is important to identify sequences that share the same &lt;a href="https://en.wikipedia.org/wiki/Sequence_homology#Orthology"&gt;orthology&lt;/a&gt; &amp;ndash; homologous sequences separated by speciation events. This is often performed by simply searching an online sequence repository using sequence labels. Relying solely on sequence labels, however, can miss sequences that have either not been labelled, have unanticipated names or have been mislabelled.&lt;/p&gt;</description></item><item><title>Extracting and Processing eBird Data</title><link>https://ropensci.org/blog/2018/08/07/auk/</link><pubDate>Tue, 07 Aug 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/08/07/auk/</guid><description>
&lt;figure class="center"&gt;&lt;img src="https://ropensci.org/img/blog-images/2018-08-07-auk/auk.png"
alt="auk hex sticker" width="300"&gt;
&lt;/figure&gt;
&lt;p&gt;&lt;a href="https://www.ebird.org"&gt;eBird&lt;/a&gt; is an online tool for recording bird
observations. The eBird database currently contains over 500 million
records of bird sightings, spanning every country and nearly every bird
species, making it an extremely valuable resource for bird research and
conservation. These data can be used to map the distribution and
abundance of species, and assess how species’ ranges are changing over
time. This dataset is available for download as a text file; however,
this file is huge (over 180 GB!) and, therefore, poses some unique
challenges. In particular, it isn’t possible to import and manipulate
the full dataset in R. Working with these data typically requires
filtering them to a smaller subset of desired observations before
reading into R. This filtering is most efficiently done using AWK, a
Unix utility and programming language for processing column formatted
text data. The &lt;code&gt;auk&lt;/code&gt; package acts as a front end for AWK, allowing users
to filter eBird data before import into R, and provides tools to perform
some important pre-processing of the data. Them name of this package
comes from the happy coincidence that the command line tool
&lt;a href="https://www.gnu.org/software/gawk/manual/gawk.html"&gt;AWK&lt;/a&gt;, upon which
the package is based, is pronounced the same as
&lt;a href="https://en.wikipedia.org/wiki/Auk"&gt;auk&lt;/a&gt;, the family of sea birds also
known as Alcids.&lt;/p&gt;</description></item><item><title>A package for dimensionality reduction of large data</title><link>https://ropensci.org/blog/2018/08/01/umapr/</link><pubDate>Wed, 01 Aug 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/08/01/umapr/</guid><description>
&lt;p&gt;&lt;img src="img/blog-images/2018-08-01-umapr/multiple_algorithms_cancer.png" alt="Comparing UMAP to other algorithms"&gt;&lt;/p&gt;
&lt;h2&gt;
Motivation
&lt;/h2&gt;&lt;blockquote&gt;
&lt;p&gt;Note: Recently, two new UMAP R packages have appeared. These new packages provide more features than umapr does and they are more actively developed. These packages are:
&lt;a href="https://github.com/tkonopka/umap"&gt;&lt;code&gt;umap&lt;/code&gt;&lt;/a&gt;, which provides the same Python wrapping function as umapr and also an R implementation, removing the need for the Python version to be installed. It is available on CRAN.
&lt;a href="https://github.com/jlmelville/uwot"&gt;&lt;code&gt;uwot&lt;/code&gt;&lt;/a&gt;, which also provides an R implementation, removing the need for the Python version to be installed.&lt;/p&gt;</description></item><item><title>rOpenSci Educators Collaborative: How Can We Develop a Community of Innovative R Educators?</title><link>https://ropensci.org/blog/2018/07/26/educollab-community/</link><pubDate>Thu, 26 Jul 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/07/26/educollab-community/</guid><description>
&lt;p&gt;&lt;strong&gt;tl;dr&lt;/strong&gt;: we propose three calls to action:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Share your curricular materials in the open.&lt;/li&gt;
&lt;li&gt;Participate in the rOpenSci Education profile series.&lt;/li&gt;
&lt;li&gt;Discuss with us how you want to be involved in &lt;a href="https://github.com/ropenscilabs/rOpenSciEd"&gt;rOpenSci Educators’ Collaborative&lt;/a&gt;.&lt;/li&gt;
&lt;/ol&gt;
&lt;hr&gt;
&lt;p&gt;In previous posts in this series, we identified challenges that individual instructors typically face when teaching science with R, and shared characteristics of effective educational resources to help address these challenges. However, the toughest challenges that educators in this area face are human, rather than technological. Our shared experiences highlight the need for a strong community of innovative R educators. However, this community is currently not well-connected or easily discoverable.&lt;/p&gt;</description></item><item><title>rOpenSci Educators Collaborative: What Educational Resources Work Well and Why?</title><link>https://ropensci.org/blog/2018/07/25/educollab-resources/</link><pubDate>Wed, 25 Jul 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/07/25/educollab-resources/</guid><description>
&lt;p&gt;In the first post of this series, we sketched out some of the common challenges faced by educators who teach with R across scientific domains. In this post, we delve into what makes a &amp;ldquo;good&amp;rdquo; educational resource for teaching science with R.&lt;/p&gt;
&lt;figure class="center"&gt;&lt;img src="https://ropensci.org/img/blog-images/2018-07-24-educollab-challenges/educollab-logo.png"
alt="educollab hashtags"&gt;
&lt;/figure&gt;
&lt;p&gt;For instructors teaching sciences with R, there are a number of open educational resources that they can reuse, tailor to their own teaching style, or use to inspire them in creating their own materials. Some examples:&lt;/p&gt;</description></item><item><title>rOpenSci Educators Collaborative: What Are The Challenges When Teaching Science With R?</title><link>https://ropensci.org/blog/2018/07/24/educollab-challenges/</link><pubDate>Tue, 24 Jul 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/07/24/educollab-challenges/</guid><description>
&lt;p&gt;&lt;figure&gt;&lt;img src="https://ropensci.org/img/blog-images/2018-07-24-educollab-challenges/educollab-logo.png"
alt="educollab hashtags"&gt;
&lt;/figure&gt;
Educators who teach science using R tend to face common pedagogical problems, regardless of their scientific domain. Yet instructors who teach with R often feel isolated at their institutions. They may be the only ones in their departments to teach using R. Even if there are others, the culture of collaboration around teaching is generally impoverished, unlike the rich culture of collaboration around research. In this three-part series of blog posts, participants at the &lt;a href="https://unconf18.ropensci.org/"&gt;rOpenSci 2018 unconf&lt;/a&gt; briefly survey the state of teaching science with R.&lt;/p&gt;</description></item><item><title>Gifski on CRAN: the fastest GIF encoder in the universe</title><link>https://ropensci.org/blog/2018/07/23/gifski-release/</link><pubDate>Mon, 23 Jul 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/07/23/gifski-release/</guid><description>
&lt;p&gt;The &lt;a href="https://cloud.r-project.org/web/packages/gifski/index.html"&gt;gifski&lt;/a&gt; package which was demonstrated in May at &lt;a href="https://2018.erum.io/"&gt;eRum 2018&lt;/a&gt; in Budapest is now on CRAN. Gifski is a simple but powerful package which can hopefully take away an important performance bottleneck for generating animated graphics in R.&lt;/p&gt;
&lt;h2&gt;
What is Gifski
&lt;/h2&gt;&lt;p&gt;Gifski is a multi-threaded high-quality GIF encoder written in Rust. It can create animated GIF images with thousands of colors per frame and do so much faster than other software. The &lt;a href="https://gif.ski/"&gt;Gifski Website&lt;/a&gt; has more technical details and beautiful examples.&lt;/p&gt;</description></item><item><title>What's inside? pkginspector provides helpful tools for inspecting package contents</title><link>https://ropensci.org/blog/2018/07/17/pkginspector/</link><pubDate>Tue, 17 Jul 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/07/17/pkginspector/</guid><description>
&lt;figure class="center"&gt;&lt;img src="img/blog-images/2018-07-17-pkginspector/pkginspector_hex_sticker.png"
alt="pkginspector hex sticker" width="300"&gt;
&lt;/figure&gt;
&lt;p&gt;R packages are widely used in science, yet the code behind them often does not come under scrutiny. To address this lack, rOpenSci has been a pioneer in developing a peer review process for R packages. The goal of &lt;a href="https://github.com/ropenscilabs/pkginspector/"&gt;&lt;code&gt;pkginspector&lt;/code&gt;&lt;/a&gt; is to help that process by providing a means to better understand the internal structure of R packages. It offers tools to analyze and visualize the relationship among functions within a package, and to report whether or not functions&amp;rsquo; interfaces are consistent. If you are reviewing an R package (maybe your own!), &lt;a href="https://github.com/ropenscilabs/pkginspector/"&gt;&lt;code&gt;pkginspector&lt;/code&gt;&lt;/a&gt; is for you.&lt;/p&gt;</description></item><item><title>phylogram: dendrograms for evolutionary analysis</title><link>https://ropensci.org/blog/2018/07/12/phylogram/</link><pubDate>Thu, 12 Jul 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/07/12/phylogram/</guid><description>
&lt;p&gt;Evolutionary biologists are increasingly using R for building,
editing and visualizing phylogenetic trees.
The reproducible code-based workflow and comprehensive array of tools
available in packages such as &lt;a href="http://ape-package.ird.fr/"&gt;ape&lt;/a&gt;,
&lt;a href="https://github.com/KlausVigo/phangorn"&gt;phangorn&lt;/a&gt; and
&lt;a href="http://blog.phytools.org/"&gt;phytools&lt;/a&gt; make R an ideal platform for
phylogenetic analysis.
Yet the many different tree formats are not well integrated,
as pointed out in a recent
&lt;a href="https://ropensci.org/blog/2018/05/17/treeio/"&gt;post&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;The standard data structure for phylogenies in R is the &amp;ldquo;phylo&amp;rdquo;
object, a memory efficient, matrix-based tree representation.
However, non-biologists have tended to use a tree structure
called the &amp;ldquo;dendrogram&amp;rdquo;, which is a deeply nested list with
node properties defined by various attributes stored at each level.
While certainly not as memory efficient as the matrix-based format,
dendrograms are versatile and intuitive to manipulate, and hence
a large number of analytical and visualization functions exist
for this object type. A good example is the
&lt;a href="https://github.com/talgalili/dendextend"&gt;dendextend&lt;/a&gt; package,
which features an impressive range of options for editing dendrograms
and plotting publication-quality trees.&lt;/p&gt;</description></item><item><title>Exploring ways to address gaps in maternal-child health research</title><link>https://ropensci.org/blog/2018/07/05/mchtoolbox/</link><pubDate>Thu, 05 Jul 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/07/05/mchtoolbox/</guid><description>
&lt;p&gt;It’s easy to come to a conference and feel intimidated by the wealth of knowledge and expertise of other attendees. As Ellen Ullman, a software engineer and writer describes,&lt;/p&gt;
&lt;blockquote class='blockquote text-left'&gt;
&lt;p class="mb-0"&gt;I was aware at all times that I had only islands of knowledge separated by darkness; that I was surrounded by chasms of not-knowing, into one of which I was certain to fall.&lt;/p&gt;
&lt;footer class="blockquote-footer"&gt;Ellen Ullman in &lt;cite title="Source Title"&gt;Life in Code: A Personal History of Technology. (2017)&lt;/cite&gt;&lt;/footer&gt;
&lt;/blockquote&gt;
&lt;p&gt;One of the best ways to start feeling less intimidated is to start talking to others. Ullman continues,&lt;/p&gt;</description></item><item><title>A package for tidying nested lists</title><link>https://ropensci.org/blog/2018/06/26/roomba/</link><pubDate>Tue, 26 Jun 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/06/26/roomba/</guid><description>
&lt;p&gt;Data == knowledge! Much of the data we use, whether it be from
government repositories, social media, GitHub, or e-commerce sites comes
from public-facing APIs. The quantity of data available is truly
staggering, but munging JSON output into a format that is easily
analyzable in R is an equally staggering undertaking. When JSON is
turned into an R object, it usually becomes a deeply nested list riddled
with missing values that is difficult to untangle into a tidy format.
Moreover, every API presents its own challenges; code you&amp;rsquo;ve written to
clean up data from GitHub isn&amp;rsquo;t necessarily going to work on Twitter
data, as each API spews data out in its own unique, headache-inducing
nested list structure. To ease and generalize this process, &lt;a href="https://github.com/ropensci/unconf18/issues/24"&gt;Amanda
Dobbyn proposed&lt;/a&gt; an
&lt;a href="https://ropensci.org/blog/2018/06/05/unconf18/"&gt;unconf18&lt;/a&gt; project for a general API response tidier! Welcome &lt;code&gt;roomba&lt;/code&gt;,
our first stab at easing the process of tidying nested lists!&lt;/p&gt;</description></item><item><title>Announcing new software review editors: Anna Krystalli and Lincoln Mullen</title><link>https://ropensci.org/blog/2018/06/22/new_editors/</link><pubDate>Fri, 22 Jun 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/06/22/new_editors/</guid><description>
&lt;p&gt;Part of rOpenSci&amp;rsquo;s mission is to create technical infrastructure in the form of carefully vetted R software tools that lower barriers to working with data sources on the web. Our open peer software review system for community-contributed tools is a key component of this. As the rOpenSci community grows and more package authors submit their work for peer review, we need to expand our editorial board to maintain a speedy process. As our &lt;a href="https://ropensci.org/blog/2018/05/03/onboarding-is-work/#work-done-by-editors"&gt;recent post&lt;/a&gt; shows, package submissions have grown every year since we started this experiment, and we see no reason they will slow down!&lt;/p&gt;</description></item><item><title>Chat with the rOpenSci team at upcoming meetings</title><link>https://ropensci.org/blog/2018/06/19/ropensci-at-meetings/</link><pubDate>Tue, 19 Jun 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/06/19/ropensci-at-meetings/</guid><description>
&lt;p&gt;You can find members of the rOpenSci team at various meetings and workshops around the world. Come say &amp;lsquo;hi&amp;rsquo;, learn about how our software &lt;a href="https://ropensci.org/packages/"&gt;packages&lt;/a&gt; can enable your research, or about our process for open peer software &lt;a href="https://ropensci.org/software-review/"&gt;review and onboarding&lt;/a&gt;, how you can get connected with the &lt;a href="https://ropensci.org/community/"&gt;community&lt;/a&gt; or tell us how we can help you do open and reproducible research.&lt;/p&gt;</description></item><item><title>Exploring European attitudes and behaviours using the European Social Survey</title><link>https://ropensci.org/blog/2018/06/14/essurvey/</link><pubDate>Thu, 14 Jun 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/06/14/essurvey/</guid><description>
&lt;!-- # see for blogpost https://github.com/ropensci/roweb2#contributing-a-blog-post --&gt;
&lt;h2&gt;
Introduction
&lt;/h2&gt;&lt;p&gt;I never thought that I&amp;rsquo;d be programming software in my career. I started
using R a little over 2 years now and it&amp;rsquo;s been one of the most important
decisions in my career. Secluded in a small academic office with no one
to discuss/interact about my new hobby, I started searching the web for
tutorials and packages. After getting to know how amazing and nurturing
the R community is, it made me want to become a data scientist. So I set
out to do it. Throughout the journey I repeatedly found myself using
the &lt;a href="https://www.europeansocialsurvey.org/"&gt;European Social Survey&lt;/a&gt; (ESS from now on), a
really neat dataset that collects information on attitudes, beliefs and
behaviour patterns of diverse populations in more than thirty European
nations since 2002.&lt;/p&gt;</description></item><item><title>The ssh Package: Secure Shell (SSH) Client for R</title><link>https://ropensci.org/blog/2018/06/12/ssh-02/</link><pubDate>Tue, 12 Jun 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/06/12/ssh-02/</guid><description>
&lt;p&gt;Have you ever needed to connect to a remote server over SSH to transfer files via SCP or to setup a secure tunnel, and wished you could do so from R itself? The new rOpenSci &lt;a href="https://cran.r-project.org/web/packages/ssh/index.html"&gt;ssh&lt;/a&gt; package provides a native ssh client in R allows you to do that and even more, like running a command or script on the host while streaming stdout and stderr directly to the client. The package is based on &lt;a href="https://www.libssh.org/"&gt;libssh&lt;/a&gt;, a powerful C library implementing the SSH protocol.&lt;/p&gt;</description></item><item><title>Unconf18 projects 4: umapr, greta, roomba, proxy-bias-vignette, http caching</title><link>https://ropensci.org/blog/2018/06/08/unconf_recap_4/</link><pubDate>Fri, 08 Jun 2018 22:35:23 +0000</pubDate><guid>https://ropensci.org/blog/2018/06/08/unconf_recap_4/</guid><description>
&lt;p&gt;For the fourth and last day of project recaps from &lt;a href="https://ropensci.org/tags/unconf18/"&gt;this year&amp;rsquo;s unconf&lt;/a&gt;, here is an overview of the next five projects. (Full set of project recaps: &lt;a href="https://ropensci.org/blog/2018/06/05/unconf_recap_1/"&gt;recap 1&lt;/a&gt;, &lt;a href="https://ropensci.org/blog/2018/06/06/unconf18_recap_2/"&gt;recap 2&lt;/a&gt;, &lt;a href="https://ropensci.org/blog/2018/06/07/unconf_recap_3/"&gt;recap 3&lt;/a&gt;, &lt;a href="https://ropensci.org/blog/2018/06/08/unconf_recap_4/"&gt;recap 4&lt;/a&gt;.)&lt;/p&gt;
&lt;p&gt;In the spirit of exploration and experimentation at rOpenSci unconferences, these projects are not necessarily finished products or in scope for rOpenSci packages.&lt;/p&gt;
&lt;p&gt; &lt;/p&gt;
&lt;h2&gt;
&lt;code&gt;umapr&lt;/code&gt;
&lt;/h2&gt;&lt;p&gt;&lt;strong&gt;Summary:&lt;/strong&gt; &lt;code&gt;umapr&lt;/code&gt; wraps the Python implementation of UMAP to make the algorithm accessible from within R, leveraging &lt;a href="https://cran.r-project.org/web/packages/reticulate/index.html"&gt;&lt;code&gt;reticulate&lt;/code&gt;&lt;/a&gt; to interface with Python. Uniform Manifold Approximation and Projection (UMAP) is a non-linear dimensionality reduction algorithm. It is similar to t-SNE but computationally more efficient.&lt;/p&gt;</description></item><item><title>.rprofile: Julia Silge</title><link>https://ropensci.org/blog/2018/06/08/rprofile-julia-silge/</link><pubDate>Fri, 08 Jun 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/06/08/rprofile-julia-silge/</guid><description>
&lt;div class="float-left"&gt;&lt;figure class="m-0"&gt;&lt;img src="https://ropensci.org/img/blog-images/2018-06-08-rprofile-julia-silge/julia-silge.jpg"
alt="Julia Silge"ZgotmplZ
ZgotmplZ
style=" object-fit: cover; object-position: center; height: 250px; width: 250px; margin-right: 15px"
/&gt;
&lt;p&gt;
&lt;em&gt;Dr. Julia Silge [@juliasilge on Twitter] is a data scientist at Stack Overflow. We talked about why R brings Julia joy, her path to a career in data science and what it was like to co-write a book for O&amp;rsquo;Reilly Media. This interview occurred on February 3, 2018 at the RStudio Conference in San Diego.&lt;/em&gt;
&lt;/p&gt;
&lt;/figure&gt;
&lt;/div&gt;
&lt;div style="clear: both;"&gt;&lt;/div&gt;
&lt;hr&gt;
&lt;p&gt;KO: What is your name, job title, and how long have you been using R?&lt;/p&gt;</description></item><item><title>Unconf18 projects 3: jobstatus, motifator, QcodeR, opencv, trackmd</title><link>https://ropensci.org/blog/2018/06/07/unconf_recap_3/</link><pubDate>Thu, 07 Jun 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/06/07/unconf_recap_3/</guid><description>
&lt;p&gt;For day 3 of project recaps from &lt;a href="https://ropensci.org/tags/unconf18/"&gt;this year&amp;rsquo;s unconf&lt;/a&gt;, here is an overview of the next five projects. Stay tuned for the last recap tomorrow. (Full set of project recaps: &lt;a href="https://ropensci.org/blog/2018/06/05/unconf_recap_1/"&gt;recap 1&lt;/a&gt;, &lt;a href="https://ropensci.org/blog/2018/06/06/unconf18_recap_2/"&gt;recap 2&lt;/a&gt;, &lt;a href="https://ropensci.org/blog/2018/06/07/unconf_recap_3/"&gt;recap 3&lt;/a&gt;, &lt;a href="https://ropensci.org/blog/2018/06/08/unconf_recap_4/"&gt;recap 4&lt;/a&gt;.)&lt;/p&gt;
&lt;p&gt;In the spirit of exploration and experimentation at rOpenSci unconferences, these projects are not necessarily finished products or in scope for rOpenSci packages.&lt;/p&gt;
&lt;p&gt;Let&amp;rsquo;s dive into today&amp;rsquo;s 5 projects in focus!&lt;/p&gt;
&lt;h2&gt;
jobstatus
&lt;/h2&gt;&lt;p&gt;&lt;img src="https://ropensci.org/img/blog-images/2018-06-07-unconf18_recap_3/jobstatus.gif" alt="jobstatus in action"&gt;&lt;/p&gt;</description></item><item><title>Unconf18 projects 2: middlechild, defender, ropsec, keybase</title><link>https://ropensci.org/blog/2018/06/06/unconf18_recap_2/</link><pubDate>Wed, 06 Jun 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/06/06/unconf18_recap_2/</guid><description><i><a href="https://ropensci.org/es/blog/2018/06/06/unconf18_recap_2/">Read it in: Español</a>.</i>
&lt;p&gt;As part of our series summarizing all projects from &lt;a href="https://ropensci.org/blog/2018/06/05/unconf18/"&gt;this year&amp;rsquo;s unconf&lt;/a&gt; I&amp;rsquo;m excited to dive into all the security related offerings from this year. (Full set of project recaps: &lt;a href="https://ropensci.org/blog/2018/06/05/unconf_recap_1/"&gt;recap 1&lt;/a&gt;, &lt;a href="https://ropensci.org/blog/2018/06/06/unconf18_recap_2/"&gt;recap 2&lt;/a&gt;, &lt;a href="https://ropensci.org/blog/2018/06/07/unconf_recap_3/"&gt;recap 3&lt;/a&gt;, &lt;a href="https://ropensci.org/blog/2018/06/08/unconf_recap_4/"&gt;recap 4&lt;/a&gt;.) In the spirit of exploration and experimentation at rOpenSci unconferences, these projects are not necessarily finished products or in scope for rOpenSci packages.&lt;/p&gt;
&lt;h3&gt;
&lt;code&gt;middlechild&lt;/code&gt;
&lt;/h3&gt;&lt;p&gt;&lt;img src="https://ropensci.org/img/blog-images/2018-06-06-unconf18_recap_2/middle_child_hex.png" alt="middlechild logo"&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Summary:&lt;/strong&gt; This package provides an R interface to the Man-in-the-middle (MITM) proxy and allows R users to intercept, modify, and introspect network traffic. The package provides functionality to download, install, configure and launch &lt;code&gt;mitmproxy&lt;/code&gt;. In addition to helping test API packages and identify dangerous calls, R users can also route their browser traffic through a specific port and capture all network traffic in R.&lt;/p&gt;</description></item><item><title>Exploring, experimenting, and building software and trust at rOpenSci’s unconf18</title><link>https://ropensci.org/blog/2018/06/05/unconf18/</link><pubDate>Tue, 05 Jun 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/06/05/unconf18/</guid><description>
&lt;p&gt;We held our &lt;a href="https://unconf18.ropensci.org/"&gt;5th annual unconference&lt;/a&gt; in Seattle, May 21-22, 2018 at Microsoft&amp;rsquo;s Reactor space. Researchers, students, postdocs and faculty, R software users and developers, and open data enthusiasts from academia, industry, government, and non-profits came together for two days to hack on projects they dreamed up and for an opportunity to meet and work together in person. We brought together 60 people from 11 countries in 5 continents - North and South America, Europe, Australia and Africa. Nearly one third of US states were represented!&lt;/p&gt;</description></item><item><title>Unconf18 projects 1: mchtoolbox, pkginspector, dataspice, rOpenSciEd, rOpenInterviews</title><link>https://ropensci.org/blog/2018/06/05/unconf_recap_1/</link><pubDate>Tue, 05 Jun 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/06/05/unconf_recap_1/</guid><description>
&lt;p&gt;After Stefanie&amp;rsquo;s recap of &lt;a href="https://ropensci.org/blog/2018/06/05/unconf18"&gt;unconf18&lt;/a&gt;, this week the blog will feature brief summaries of projects developed at the event: each day 4 to 5 projects will be highlighted. (Full set of project recaps: &lt;a href="https://ropensci.org/blog/2018/06/05/unconf_recap_1/"&gt;recap 1&lt;/a&gt;, &lt;a href="https://ropensci.org/blog/2018/06/06/unconf18_recap_2/"&gt;recap 2&lt;/a&gt;, &lt;a href="https://ropensci.org/blog/2018/06/07/unconf_recap_3/"&gt;recap 3&lt;/a&gt;, &lt;a href="https://ropensci.org/blog/2018/06/08/unconf_recap_4/"&gt;recap 4&lt;/a&gt;) In the following weeks, a handful of groups will share more thorough posts about their work.&lt;/p&gt;
&lt;p&gt;In the spirit of exploration and experimentation at rOpenSci unconferences, these projects are not necessarily finished products or in scope for rOpenSci packages.&lt;/p&gt;</description></item><item><title>vcr: record and replay HTTP requests</title><link>https://ropensci.org/blog/2018/05/25/vcr-http-request-cacahing/</link><pubDate>Fri, 25 May 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/05/25/vcr-http-request-cacahing/</guid><description>
&lt;p&gt;R package test suites that include HTTP requests are dependent on an internet connection being up, the internet connection speed, changing behavior of the remote server, as well as changing response formats/data from a remote server. We ideally want to test functionality of our package relative to some known data that isn&amp;rsquo;t intermittently unavailable or changing. Caveat is that we do want to make sure the package fails well, including fails well in response to server failures, but these responses can be cached.&lt;/p&gt;</description></item><item><title>taxize: seven years of taxonomy in R</title><link>https://ropensci.org/blog/2018/05/23/taxize-seven-years/</link><pubDate>Wed, 23 May 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/05/23/taxize-seven-years/</guid><description>
&lt;p&gt;&lt;a href="https://github.com/ropensci/taxize"&gt;taxize&lt;/a&gt; was seven years old this last Saturday!&lt;/p&gt;
&lt;h2&gt;
What is taxize?
&lt;/h2&gt;&lt;p&gt;&lt;code&gt;taxize&lt;/code&gt; is designed around making working with taxonomic names easier - abstracting away the details of what each of 20 or so taxonomic data sources require for a given use case.&lt;/p&gt;
&lt;p&gt;A samping of use cases covered in &lt;code&gt;taxize&lt;/code&gt; (all of these across many different data sources):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Taxonomic identifier from a taxonomic name and vice versa&lt;/li&gt;
&lt;li&gt;Taxonomic name from a vernacular (common) name and vice versa&lt;/li&gt;
&lt;li&gt;Taxonomic hierarchy/classification from identifier or name&lt;/li&gt;
&lt;li&gt;Taxonomic children of an identifier or name&lt;/li&gt;
&lt;li&gt;All taxa downstream to a certain rank from identifier or name&lt;/li&gt;
&lt;li&gt;Taxonomic name synonyms from identifier or name&lt;/li&gt;
&lt;li&gt;Lowest common taxon and rank for an identifier or name&lt;/li&gt;
&lt;li&gt;Resolve taxonomic names, i.e., fix spelling errors&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;
History
&lt;/h2&gt;&lt;p&gt;&lt;code&gt;taxize&lt;/code&gt; was one of our first packages. Our first commit was on &lt;a href="https://github.com/ropensci/taxize/commit/667004eac"&gt;2011-05-19&lt;/a&gt;, uneventfully adding an empty README:&lt;/p&gt;</description></item><item><title>drake's improved high-performance computing power</title><link>https://ropensci.org/blog/2018/05/18/drake-hpc/</link><pubDate>Fri, 18 May 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/05/18/drake-hpc/</guid><description>
&lt;p&gt;The &lt;a href="https://github.com/ropensci/drake"&gt;&lt;code&gt;drake&lt;/code&gt; R package&lt;/a&gt; is not only a reproducible research solution, but also a serious high-performance computing engine. The &lt;a href="https://docs.ropensci.org/drake/"&gt;package website&lt;/a&gt; introduces &lt;a href="https://github.com/ropensci/drake"&gt;&lt;code&gt;drake&lt;/code&gt;&lt;/a&gt;, and this technical note draws from the guides on high-performance computing and timing in the &lt;a href="https://github.com/ropenscilabs/drake-manual"&gt;&lt;code&gt;drake&lt;/code&gt; manual&lt;/a&gt;.&lt;/p&gt;
&lt;h3&gt;
You can help!
&lt;/h3&gt;&lt;p&gt;Some of these features are brand new, and others are newly refactored. The &lt;a href="https://github.com/ropensci/drake"&gt;GitHub version&lt;/a&gt; has all the advertised functionality, but it needs more testing and development before I can submit it to CRAN in good conscience. New issues such as &lt;a href="https://github.com/r-lib/processx/issues/113"&gt;r-lib/processx#113&lt;/a&gt; and &lt;a href="https://github.com/HenrikBengtsson/future/issues/226"&gt;HenrikBengtsson/future#226&lt;/a&gt; seem to affect &lt;a href="https://github.com/ropensci/drake"&gt;&lt;code&gt;drake&lt;/code&gt;&lt;/a&gt;, and more may emerge. If you use &lt;a href="https://github.com/ropensci/drake"&gt;&lt;code&gt;drake&lt;/code&gt;&lt;/a&gt; for your own work, please consider supporting the project by field-testing the claims below and posting feedback &lt;a href="https://github.com/ropensci/drake/issues/369"&gt;here&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>treeio: Phylogenetic data integration</title><link>https://ropensci.org/blog/2018/05/17/treeio/</link><pubDate>Thu, 17 May 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/05/17/treeio/</guid><description>
&lt;p&gt;Phylogenetic trees are commonly used to present evolutionary relationships of species. &lt;a href="http://evolution.genetics.washington.edu/phylip/newicktree.html"&gt;Newick&lt;/a&gt; is the &lt;em&gt;de facto&lt;/em&gt; format in phylogenetic for representing tree(s). &lt;a href="http://wiki.christophchamp.com/index.php?title=NEXUS_file_format"&gt;Nexus&lt;/a&gt; format incorporates Newick tree text with related information organized into separated units known as blocks. For the R community, we have &lt;a href="https://cran.r-project.org/package=ape"&gt;ape&lt;/a&gt; and &lt;a href="https://cran.r-project.org/package=phylobase"&gt;phylobase&lt;/a&gt; packages to import trees from Newick and Nexus formats. However, analysis results (tree + analysis findings) from widely used software packages in this field are not well supported. Some of them are extended from Newick and Nexus (&lt;em&gt;e.g.&lt;/em&gt; &lt;a href="https://revbayes.github.io/"&gt;RevBayes&lt;/a&gt; and &lt;a href="http://beast2.org/"&gt;BEAST&lt;/a&gt; outputs), while some of the others are just log files (&lt;em&gt;e.g.&lt;/em&gt; &lt;a href="https://academic.oup.com/bioinformatics/article/19/2/301/372781"&gt;r8s&lt;/a&gt; and &lt;a href="http://abacus.gene.ucl.ac.uk/software/paml.html"&gt;PAML&lt;/a&gt; outputs). Parsing these output files is important for interpreting analysis findings.&lt;/p&gt;</description></item><item><title>icon: web icons for rmarkdown</title><link>https://ropensci.org/blog/2018/05/15/icon/</link><pubDate>Tue, 15 May 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/05/15/icon/</guid><description>
&lt;h3&gt;
Icons in R
&lt;/h3&gt;&lt;div class="float-left"&gt;&lt;figure class="m-0"&gt;&lt;img src="YTJIhij.png"ZgotmplZ
ZgotmplZ
ZgotmplZ
ZgotmplZ
style=" object-fit: cover; object-position: center; height: 150px; width: 150px; margin-right: 15px"
/&gt;
&lt;p&gt;
The &lt;a href="https://github.com/ropenscilabs/icon"&gt;icon&lt;/a&gt; package provides a convenient interface for adding icons from popular web fonts to R Markdown documents. The project began at &lt;a href="https://ozunconf17.ropensci.org/"&gt;rOpenSci OzUnconf 2017&lt;/a&gt;, and was developed by &lt;a href="https://github.com/mitchelloharawild"&gt;Mitchell O&amp;rsquo;Hara-Wild&lt;/a&gt;, &lt;a href="https://github.com/earowang"&gt;Earo Wang&lt;/a&gt; and &lt;a href="https://github.com/timothyhyndman"&gt;Timothy Hyndman&lt;/a&gt;. The package currently supports icons from &lt;a href="https://fontawesome.com/"&gt;Font Awesome&lt;/a&gt;, &lt;a href="https://jpswalsh.github.io/academicons/"&gt;Academicons&lt;/a&gt;, and &lt;a href="https://ionicons.com/"&gt;ionicons&lt;/a&gt;.
&lt;/p&gt;
&lt;/figure&gt;
&lt;/div&gt;
&lt;div style="clear: both;"&gt;&lt;/div&gt;
&lt;p&gt;Icons can be added to your R Markdown documents using short prefixes which identify the font&amp;rsquo;s library.&lt;/p&gt;</description></item><item><title>The social weather of rOpenSci onboarding system</title><link>https://ropensci.org/blog/2018/05/10/onboarding-social-weather/</link><pubDate>Thu, 10 May 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/05/10/onboarding-social-weather/</guid><description>
&lt;p&gt;Our &lt;a href="https://github.com/ropensci/software-review/"&gt;onboarding process&lt;/a&gt;
ensures that packages contributed by the community undergo a
transparent, constructive, non adversarial and open review process.
Before even submitting my first R package to rOpenSci onboarding system
in December 2015, I spent a fair amount of time reading through previous
issue threads in order to assess whether onboarding was a friendly place
for me: a newbie, very motivated to learn more but a newbie nonetheless.
I soon got the feeling that yes, onboarding would help me make my
package better without ever making me feel inadequate.&lt;/p&gt;</description></item><item><title>Nomisr - Access Nomis UK Labour Market Data</title><link>https://ropensci.org/blog/2018/05/08/nomisr/</link><pubDate>Tue, 08 May 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/05/08/nomisr/</guid><description>
&lt;p&gt;I&amp;rsquo;m excited to announce a new package for accessing official statistics from the UK. &lt;a href="https://github.com/ropensci/nomisr"&gt;&lt;code&gt;nomisr&lt;/code&gt;&lt;/a&gt; is the R client for the &lt;a href="https://www.nomisweb.co.uk/"&gt;Nomis&lt;/a&gt; database. Nomis is run by Durham University on behalf of the UK&amp;rsquo;s Office for National Statistics (ONS), and contains over a thousand datasets, primarily on the UK labour market, census data, benefit spending and general economic activity. Registration is optional, although registration and the use of an API key allows for larger queries without the risk of being timed out or rate limited by the API.&lt;/p&gt;</description></item><item><title>How much work is onboarding?</title><link>https://ropensci.org/blog/2018/05/03/onboarding-is-work/</link><pubDate>Thu, 03 May 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/05/03/onboarding-is-work/</guid><description>
&lt;p&gt;Our &lt;a href="https://github.com/ropensci/software-review/"&gt;onboarding process&lt;/a&gt;, that
ensures that packages contributed by the community undergo a
transparent, constructive, non adversarial and open review process,
involves a lot of work from many actors: authors, reviewers and editors;
but &lt;em&gt;how much work&lt;/em&gt;? Managing the effort involved in the peer-review
process is a major part of ensuring its sustainability and quality. In
this post, we’ll take a look at the effort put in by participants in the
review process, and also learn something about exploring GitHub data
along the way.&lt;/p&gt;</description></item><item><title>Our package reviews in review: Introducing a 3-post series about software onboarding data</title><link>https://ropensci.org/blog/2018/04/26/a-satrday-ct-series/</link><pubDate>Thu, 26 Apr 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/04/26/a-satrday-ct-series/</guid><description>
&lt;p&gt;On March the 17th I had the honor to give a keynote talk about rOpenSci&amp;rsquo;s package onboarding system at the &lt;a href="https://capetown2018.satrdays.org/"&gt;satRday conference in Cape Town&lt;/a&gt;, entitled &amp;ldquo;Our package reviews in review: introducing and analyzing rOpenSci onboarding system&amp;rdquo;. You can &lt;a href="https://www.youtube.com/watch?v=lZ3deq52qCk"&gt;watch its recording&lt;/a&gt;, &lt;a href="https://www.masalmon.eu/satrday_keynote/slides"&gt;skim through the corresponding slides&lt;/a&gt; or&amp;hellip; read this series!&lt;/p&gt;
&lt;h2&gt;
What is rOpenSci onboarding?
&lt;/h2&gt;&lt;p&gt;rOpenSci&amp;rsquo;s &lt;a href="https://ropensci.org/packages/"&gt;suite of packages&lt;/a&gt; is partly contributed by staff members and partly contributed by community members, which means the suite stems from a great diversity of skills and experience of developers. How to ensure quality for the whole set? That&amp;rsquo;s where onboarding comes into play: packages contributed by the community undergo a transparent, constructive, non adversarial and open review process. For that process relying mostly on volunteer work, four editors manage the incoming flow and ensure progress of submissions; authors create, submit and improve their package; reviewers, two per submission, examine the software code and user experience. &lt;a href="https://www.numfocus.org/blog/how-ropensci-uses-code-review-to-promote-reproducible-science/"&gt;This blog post&lt;/a&gt; written by rOpenSci onboarding editors is a good introduction to rOpenSci onboarding.&lt;/p&gt;</description></item><item><title>Rectangling onboarding</title><link>https://ropensci.org/blog/2018/04/26/rectangling-onboarding/</link><pubDate>Thu, 26 Apr 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/04/26/rectangling-onboarding/</guid><description>
&lt;p&gt;Our &lt;a href="https://ropensci.org/blog/2017/09/11/software-review-update/"&gt;onboarding
reviews&lt;/a&gt;,
that ensure that packages contributed by the community undergo a
transparent, constructive, non adversarial and open review process, take
place in the issue tracker of a GitHub repository. Development of the
packages we onboard also takes place in the open, most often in GitHub
repositories.&lt;/p&gt;
&lt;p&gt;Therefore, when wanting to get data about our onboarding system for
giving a data-driven overview, my mission was to extract data from
GitHub and git repositories, and to put it into nice rectangles (as
defined &lt;a href="https://speakerdeck.com/jennybc/data-rectangling"&gt;by Jenny
Bryan&lt;/a&gt;) ready for
analysis. You might call that the first step of a “tidy git analysis”
using the term coined by &lt;a href="https://drsimonj.svbtle.com/embarking-on-a-tidy-git-analysis"&gt;Simon
Jackson&lt;/a&gt;.
So, how did I collect data?&lt;/p&gt;</description></item><item><title>Lessons Learned from rtika, a Digital Babel Fish</title><link>https://ropensci.org/blog/2018/04/25/rtika-introduction/</link><pubDate>Wed, 25 Apr 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/04/25/rtika-introduction/</guid><description>
&lt;p&gt;The Apache Tika parser is like the Babel fish in Douglas Adam&amp;rsquo;s book, &amp;ldquo;The Hitchhikers&amp;rsquo; Guide to the Galaxy&amp;rdquo; &lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt;. The Babel fish translates any natural language to any other. Although Tika does not yet translate natural language, it starts to tame the tower of babel of digital document formats. As the Babel fish allowed a person to understand Vogon poetry, Tika allows an analyst to extract text and objects from Microsoft Word.&lt;/p&gt;</description></item><item><title>Monkeying around with Code and Paying it Forward</title><link>https://ropensci.org/blog/2018/04/20/monkeydo/</link><pubDate>Fri, 20 Apr 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/04/20/monkeydo/</guid><description>
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-r" data-lang="r"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nf"&gt;library&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;tidyverse&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nf"&gt;library&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;monkeylearn&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;This is a story (mostly) about how I started contributing to the rOpenSci package &lt;a href="https://github.com/ropensci/monkeylearn"&gt;monkeylearn&lt;/a&gt;. I can&amp;rsquo;t promise any life flipturning upside down, but there will be a small discussion about git best practices which is almost as good 🤓. The tl;dr here is nothing novel but is something I wish I&amp;rsquo;d experienced firsthand sooner. That is, that tinkering with and improving on the code others have written is more rewarding for you and more valuable to others when you contribute it back to the original source.&lt;/p&gt;</description></item><item><title>The 2018 author and reviewer survey</title><link>https://ropensci.org/blog/2018/04/17/author-survey/</link><pubDate>Tue, 17 Apr 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/04/17/author-survey/</guid><description>
&lt;p&gt;rOpenSci&amp;rsquo;s package review system (aka
&lt;a href="https://github.com/ropensci/software-review/"&gt;onboarding&lt;/a&gt;) is one of our key
activities to &lt;a href="https://ropensci.org/blog/2017/09/01/nf-softwarereview/"&gt;improve quality and sustainability of scientific R
packages&lt;/a&gt;. The
editorial team are constantly working towards improving the experience
for both authors and reviewers. After our first year, we &lt;a href="https://ropensci.org/blog/2016/03/28/software-review/"&gt;surveyed
authors and
reviewers&lt;/a&gt; who
participated in our onboarding process to help us better understand
what&amp;rsquo;s working well and where there is room for improvement. At the end
of last year, we did so again, re-designing our survey so as to better
track participant opinions year-to-year. In this post we summarize the
45 responses that we received and what we&amp;rsquo;re doing to address your
feedback.&lt;/p&gt;</description></item><item><title>.rprofile: Noam Ross</title><link>https://ropensci.org/blog/2018/04/13/rprofile-noam-ross/</link><pubDate>Fri, 13 Apr 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/04/13/rprofile-noam-ross/</guid><description>
&lt;div class="float-left"&gt;&lt;figure class="m-0"&gt;&lt;img src="https://ropensci.org/img/blog-images/2018-04-13-rprofile-noam-ross/noam-ross.jpg"
alt="Noam Ross"ZgotmplZ
ZgotmplZ
style=" object-fit: cover; object-position: center; height: 250px; width: 250px; margin-right: 15px"
/&gt;
&lt;p&gt;
&lt;em&gt;Dr. Noam Ross [@noamross on Twitter] is a disease ecologist at &lt;a href="https://www.ecohealthalliance.org/"&gt;EcoHealth Alliance&lt;/a&gt; in NYC, as well as an editor for rOpenSci. Topics of discussion included Noam&amp;rsquo;s history with R and rOpenSci, working in a team-driven research environment, and inspirations for pushing research processes and rOpenSci projects in exciting new directions.&lt;/em&gt;
&lt;/p&gt;
&lt;/figure&gt;
&lt;/div&gt;
&lt;div style="clear: both;"&gt;&lt;/div&gt;
&lt;hr&gt;
&lt;p&gt;KO: What is your name, job title, and how long have you been using R?&lt;/p&gt;</description></item><item><title>Forcing Yourself to Make Your Life Easier</title><link>https://ropensci.org/blog/2018/04/12/ijtiff/</link><pubDate>Thu, 12 Apr 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/04/12/ijtiff/</guid><description>
&lt;h3&gt;
The general struggle
&lt;/h3&gt;&lt;p&gt;Something that will make life easier in the long-run can be the most difficult thing to do &lt;em&gt;today&lt;/em&gt;. For coders, prioritising the long term may involve an overhaul of current practice and the learning of a new skill. This can be painful for a number of reasons:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;We have to admit to ourselves that we’ve been doing things inefficiently (i.e. wasting time). This makes us feel stupid and fosters a sense of missed opportunity: we could’ve done something cool with the time we’d have saved (e.g. vacation).&lt;/li&gt;
&lt;li&gt;We’re fond of our existing methods, probably because we’re used to them and they’ve served us pretty well thus far.&lt;/li&gt;
&lt;li&gt;The learning we have to do may seem beneath us: “I’m an expert in R, I’ve even written my own package. Surely ‘Version Control for Beginners’ wasn’t intended for the likes of me.” This kind of thought permits us to dismiss good ideas.&lt;/li&gt;
&lt;li&gt;We’re tired. Overhauling workflows and learning new skills takes energy and concentration. Today, we’ll go through the motions just like we did yesterday. And hey, no one complained about the work we did yesterday.&lt;/li&gt;
&lt;li&gt;We feel like the task is actually beyond us. This is almost never true (so long as we’re good at asking for help).&lt;/li&gt;
&lt;li&gt;In the context of a work environment, when we’re concentrated on learning, our apparent output drops (often to zero) until the learning period ends. A bad manager/supervisor who doesn’t appreciate the worth of taking the time to learn how to do things better may not forgive this short-term drop in apparent output.&lt;/li&gt;
&lt;/ol&gt;
&lt;blockquote&gt;
&lt;p&gt;Something that will make life easier in the long-run can be the most difficult thing to do &lt;em&gt;today&lt;/em&gt;.&lt;/p&gt;</description></item><item><title>Where is the value in package peer review?</title><link>https://ropensci.org/blog/2018/04/06/peer-review-value/</link><pubDate>Fri, 06 Apr 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/04/06/peer-review-value/</guid><description>
&lt;p&gt;If you read my &lt;a href="https://milesmcbain.xyz/ropensci-onboarding1/"&gt;reflection #1 on rOpenSci Onboarding&lt;/a&gt;, then you know I see value in the Onboarding process. A LOT of value even. This post is about where that value lies.&lt;/p&gt;
&lt;p&gt;This question has important corollaries which I will explore here based on my experience as a reviewer of &lt;a href="https://docs.ropensci.org/bowerbird/index.html"&gt;&lt;code&gt;bowerbird&lt;/code&gt;&lt;/a&gt;:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;How is a package peer reviewer&amp;rsquo;s time best spent?&lt;/li&gt;
&lt;li&gt;When is the best time in a software package&amp;rsquo;s life cycle to undertake peer review?&lt;/li&gt;
&lt;/ol&gt;
&lt;h3&gt;
Doing a good job
&lt;/h3&gt;&lt;p&gt;As I&amp;rsquo;ve read the growing number of reflective posts by other Onboarding reviewers, I&amp;rsquo;m struck similarities in our experiences. &lt;a href="https://ropensci.org/blog/2017/08/22/first-package-review/"&gt;Mara Averick&lt;/a&gt;, &lt;a href="https://ropensci.org/blog/2017/09/08/first-review-experiences/"&gt;Verena Haunschmid&lt;/a&gt;, and &lt;a href="https://ropensci.org/blog/2018/03/13/ode-to-testing/"&gt;Charles Gray&lt;/a&gt; all place emphasis on reviewing from a &amp;ldquo;user&amp;rsquo;s&amp;rdquo; perspective. For Mara and Charles, this perspective was used to gain traction after initial nervousness about their ability to do a good job.&lt;/p&gt;</description></item><item><title>ὕδωρ + σκοπῶ = water + observe</title><link>https://ropensci.org/blog/2018/04/03/hydroscoper/</link><pubDate>Tue, 03 Apr 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/04/03/hydroscoper/</guid><description>
&lt;blockquote&gt;
&lt;p&gt;Hydrology is a concept to unify statistics, data analysis and numerical models in order to understand and analyze the endless circulation of water between the earth and its atmosphere.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;That&amp;rsquo;s a lot alike Data Science, isn&amp;rsquo;t it? Hydrologic Processes evolve in space and time, are extremely complex and we may never comprehend them. For this reason Hydrologists use models where their inputs and outputs are measurable variables: climatic and hydrologic data, land uses, vegetation coverage, soil type etc.&lt;/p&gt;</description></item><item><title>DoOR - The Database of Odorant Responses</title><link>https://ropensci.org/blog/2018/03/27/door/</link><pubDate>Tue, 27 Mar 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/03/27/door/</guid><description>
&lt;h3&gt;
Olfactory Coding
&lt;/h3&gt;&lt;p&gt;Detecting volatile chemicals and encoding these into neuronal activity is a vital task for all animals that is performed by their olfactory sensory systems. While these olfactory systems vary vastly between species regarding their numerical complexity, they are amazingly similar in their general structure. The periphery of olfactory systems consists of different classes of olfactory sensory neurons (OSN). In mammals, OSNs are located in the nose, in insects, OSNs are located on the antenna. OSN classes are tuned to defined but overlapping sets of odors. Thus a single odor usually elicits differential responses across an ensemble of OSNs. This &lt;em&gt;ensemble code&lt;/em&gt; is able to encode thousands of odors, even in comparably simple olfactory systems.&lt;/p&gt;</description></item><item><title>A rentrez paper, and how to use the NCBI's new API keys</title><link>https://ropensci.org/blog/2018/03/20/rentrez-paper/</link><pubDate>Tue, 20 Mar 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/03/20/rentrez-paper/</guid><description>
&lt;p&gt;I am happy to say that the latest issue of &lt;em&gt;The R Journal&lt;/em&gt; &lt;a href="https://journal.r-project.org/archive/2017/RJ-2017-058/index.html"&gt;includes a paper
describing rentrez&lt;/a&gt;,
the rOpenSci package for retrieving data from the National Center for Biotechnology Information
(NCBI).&lt;/p&gt;
&lt;p&gt;&lt;a href="https://www.ncbi.nlm.nih.gov/"&gt;The NCBI&lt;/a&gt; is one of the most important sources of biological data. The centre
provides access to information on 28 million scholarly articles through PubMed and 250
million DNA sequences through GenBank. More importantly, records in the &lt;a href="https://www.ncbi.nlm.nih.gov/guide/all/#databases"&gt;50 public
databases&lt;/a&gt; maintained by the NCBI are strongly cross-referenced. As a result, it is
possible to pinpoint searches using almost 2 million taxonomic names or a
&lt;a href="https://www.nlm.nih.gov/mesh/"&gt;controlled vocabulary with 270,000 terms&lt;/a&gt;.
&lt;code&gt;rentrez&lt;/code&gt; has been designed to make it easy to search for and download NCBI
records and download them from within an R session.&lt;/p&gt;</description></item><item><title>Thanking Your Reviewers: Gratitude through Semantic Metadata</title><link>https://ropensci.org/blog/2018/03/16/thanking-reviewers-in-metadata/</link><pubDate>Fri, 16 Mar 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/03/16/thanking-reviewers-in-metadata/</guid><description><i><a href="https://ropensci.org/es/blog/2018/03/16/thanking-reviewers-in-metadata/">Read it in: Español</a>.</i><i><a href="https://ropensci.org/pt/blog/2018/03/16/thanking-reviewers-in-metadata/">Read it in: Português</a>.</i>
&lt;p&gt;At rOpenSci, our &lt;a href="https://ropensci.org/blog/2017/09/01/nf-softwarereview/"&gt;R package peer review process&lt;/a&gt; relies on the the hard work of many volunteer reviewers. These community members donate their &lt;a href="https://ropensci.org/blog/2016/03/28/software-review/#review-takes-a-lot-of-time"&gt;time&lt;/a&gt; and expertise to improving the quality of rOpenSci packages and helping drive best practices into scientific software.&lt;/p&gt;
&lt;p&gt;Our &lt;em&gt;open&lt;/em&gt; review process, where reviews and reviewers are public, means that one benefit for reviewers is that they can get credit for their reviews. We want reviewers to see as much benefit as possible, and for their contributions to be recorded as part of the intellectual trail of academic work, so we have been working at making reviews visible and discoverable.&lt;/p&gt;</description></item><item><title>An Ode to Testing, my first review</title><link>https://ropensci.org/blog/2018/03/13/ode-to-testing/</link><pubDate>Tue, 13 Mar 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/03/13/ode-to-testing/</guid><description>
&lt;p&gt;To give you an idea of where I am in my &lt;code&gt;R&lt;/code&gt; developer germination, I&amp;rsquo;d just started reading about &lt;a href="http://r-pkgs.had.co.nz/tests.html"&gt;testing&lt;/a&gt; when I received an email from &lt;a href="https://ropensci.org/"&gt;@rOpenSci&lt;/a&gt; inviting me to review the &lt;a href="https://github.com/ropensci/weathercan"&gt;&lt;code&gt;weathercan&lt;/code&gt;&lt;/a&gt; package. Many of us in the &lt;code&gt;R&lt;/code&gt; community feel like &lt;a href="https://en.wikipedia.org/wiki/Impostor_syndrome"&gt;imposters&lt;/a&gt; when it comes to software development. In fact, as a statistician, it was a surprise to me when I was recently called a developer.&lt;/p&gt;
&lt;p&gt;In terms of formal computer science training, I took one subject in first year, with the appropriate &lt;a href="https://www.quickanddirtytips.com/education/grammar/abbreviations-acronyms-and-initialisms"&gt;initialism&lt;/a&gt; &lt;em&gt;OOF&lt;/em&gt;. Ostensibly, this was to school me in Object Oriented Fundamentals, but mostly educated me in just how much one person can pontificate about doubles and floats. I am almost always befuddled by regexes on the rare occasions I come across them.&lt;/p&gt;</description></item><item><title>Integrating data from weathercan</title><link>https://ropensci.org/blog/2018/03/06/weathercan/</link><pubDate>Tue, 06 Mar 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/03/06/weathercan/</guid><description>
&lt;p&gt;I love working with R and have been sharing the love with my friends and colleagues for almost seven years now. I&amp;rsquo;m one of those really annoying people whose response to most analysis-related questions is &amp;ldquo;You can do that in R! Five minutes, tops!&amp;rdquo; or &amp;ldquo;Three lines of code, I swear!&amp;rdquo; The problem was that I invariably spent an hour or more showing people how to get the data, load the data, clean the data, transform the data, and join the data, before we could even start the &amp;ldquo;five minute analysis&amp;rdquo;. With the advent of &lt;a href="https://www.tidyverse.org"&gt;&lt;code&gt;tidyverse&lt;/code&gt;&lt;/a&gt;, data manipulation has gotten much, much easier, but I still find that data manipulation is where most new users get stuck. This is one of the reasons why, when I designed &lt;a href="https://github.com/ropensci/weathercan"&gt;&lt;code&gt;weathercan&lt;/code&gt;&lt;/a&gt;, I tried as hard as possible to make it simple and straightforward.&lt;/p&gt;</description></item><item><title>rOpenSci Vancouver Community Meetup: Transforming science through open data and software</title><link>https://ropensci.org/blog/2018/02/23/ropensci-in-yvr/</link><pubDate>Fri, 23 Feb 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/02/23/ropensci-in-yvr/</guid><description>
&lt;p&gt;&lt;a href="https://ropensci.org/"&gt;rOpenSci&lt;/a&gt; is holding our annual &lt;a href="https://ropensci.org/about/#team"&gt;staff and leadership&lt;/a&gt; meeting in Vancouver, so we’re taking the opportunity to share what we do and, if you’re interested, how you can get involved. Join us for a series of 7 short talks and demos followed by informal networking over snacks &amp;amp; refreshments.&lt;/p&gt;
&lt;p&gt;rOpenSci is a non-profit initiative that promotes open and reproducible research using shared data and reusable software. We are creating technical infrastructure in the form of carefully vetted, staff- and community-contributed R software tools that lower barriers to working with scientific data sources on the web, and building a welcoming and diverse global community of R users and developers from a range of research domains.&lt;/p&gt;</description></item><item><title>webmockr: mock HTTP requests</title><link>https://ropensci.org/blog/2018/02/20/webmockr-intro/</link><pubDate>Tue, 20 Feb 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/02/20/webmockr-intro/</guid><description>
&lt;h2&gt;
webmockr
&lt;/h2&gt;&lt;p&gt;&lt;code&gt;webmockr&lt;/code&gt; is an R library for stubbing and setting expectations on HTTP requests.
It is a port of the Ruby gem &lt;a href="https://github.com/bblimke/webmock"&gt;webmock&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;code&gt;webmockr&lt;/code&gt; works by plugging in to another R package that does HTTP requests. It currently only works with &lt;a href="https://github.com/ropensci/crul"&gt;crul&lt;/a&gt; right now, but we plan to add support for &lt;a href="https://github.com/jeroen/curl"&gt;curl&lt;/a&gt; and &lt;a href="https://github.com/r-lib/httr"&gt;httr&lt;/a&gt; later.&lt;/p&gt;
&lt;p&gt;&lt;code&gt;webmockr&lt;/code&gt; has the following high level features:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Stubbing HTTP requests at low http client level&lt;/li&gt;
&lt;li&gt;Setting expectations on HTTP requests&lt;/li&gt;
&lt;li&gt;Matching requests based any combination of HTTP method (e.g., GET/POST/PUT), URI (i.e., URL), request headers and body&lt;/li&gt;
&lt;li&gt;Will soon integrate with &lt;a href="https://github.com/ropensci/vcr"&gt;vcr&lt;/a&gt; so that you can cache real HTTP responses - and easily integrate with &lt;code&gt;testthat&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;code&gt;webmockr&lt;/code&gt; has been on CRAN for a little while now, but I&amp;rsquo;ve recently made some improvements and am nearing another
CRAN release, which is also preparation for a first release of the related &lt;a href="https://github.com/ropensci/vcr"&gt;vcr&lt;/a&gt; package. The following is a
run down of major features and how to use the package, including a bit on testing at the end.&lt;/p&gt;</description></item><item><title>Introducing the 2018 rOpenSci Research Fellows!</title><link>https://ropensci.org/blog/2018/02/14/announcing-2018-ropensci-fellows/</link><pubDate>Wed, 14 Feb 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/02/14/announcing-2018-ropensci-fellows/</guid><description>
&lt;p&gt;rOpenSci’s mission is to enable and support a thriving community of researchers who embrace open and reproducible research practices as part of their work. Since our inception, one of the mechanisms through which we have supported the community is by developing high-quality open source tools that lower barriers to working with scientific data. Equally important to our mission is to build capacity and promote researchers who are engaged in such practices within their disciplinary communities. This fellowship program is a unique opportunity for us to enable such individuals to have a bigger voice in their communities.&lt;/p&gt;</description></item><item><title>Support for hOCR and Tesseract 4 in R</title><link>https://ropensci.org/blog/2018/02/14/tesseract-18/</link><pubDate>Wed, 14 Feb 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/02/14/tesseract-18/</guid><description>
&lt;p&gt;Earlier this month we released a new version of the &lt;a href="https://cran.r-project.org/package=tesseract"&gt;tesseract&lt;/a&gt; package to CRAN. This package provides R bindings to Google&amp;rsquo;s open source optical character recognition (OCR) engine &lt;a href="https://github.com/tesseract-ocr/tesseract"&gt;Tesseract&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Two major new features are support for HOCR and support for the upcoming Tesseract 4.&lt;/p&gt;
&lt;h2&gt;
hOCR output
&lt;/h2&gt;&lt;p&gt;Support for HOCR output was &lt;a href="https://github.com/ropensci/tesseract/issues/20"&gt;requested&lt;/a&gt; by one of our users on Github. The &lt;code&gt;ocr()&lt;/code&gt; function gains a parameter &lt;code&gt;HOCR&lt;/code&gt; which allows for returning results in hOCR format:&lt;/p&gt;</description></item><item><title>.rprofile: Julia Stewart Lowndes</title><link>https://ropensci.org/blog/2018/02/09/rprofile-julia-stewart-lowndes/</link><pubDate>Fri, 09 Feb 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/02/09/rprofile-julia-stewart-lowndes/</guid><description>
&lt;div class="float-left"&gt;&lt;figure class="m-0"&gt;&lt;img src="https://ropensci.org/img/blog-images/2018-02-09-julia-stewart-lowndes/lowndes_profile.jpg"
alt="Julia Stewart Lowndes"ZgotmplZ
ZgotmplZ
style=" object-fit: cover; object-position: center; height: 250px; width: 250px; margin-right: 15px"
/&gt;
&lt;p&gt;
&lt;em&gt;Dr. Julia Stewart Lowndes [@juliesquid on Twitter] is the Science Program Lead for the Ocean Health Index and works at the National Center for Ecological Analysis and Synthesis. She and Sean Kross discussed how data science, open science, and community can help reproducibility in research.&lt;/em&gt;
&lt;/p&gt;
&lt;/figure&gt;
&lt;/div&gt;
&lt;div style="clear: both;"&gt;&lt;/div&gt;
&lt;hr&gt;
&lt;p&gt;[This interview occurred at the 2017 rOpenSci unconference]&lt;/p&gt;
&lt;p&gt;SK: I’m &lt;a href="https://twitter.com/seankross"&gt;Sean Kross&lt;/a&gt;, I’m the CTO of the &lt;a href="https://jhudatascience.org/"&gt;Johns Hopkins Data Science Lab&lt;/a&gt;. Today I’m interviewing Julia Stewart Lowndes. Julia, what is your current preferred job title?&lt;/p&gt;</description></item><item><title>Apply to attend rOpenSci unconf 2018!</title><link>https://ropensci.org/blog/2018/02/08/unconf2018/</link><pubDate>Thu, 08 Feb 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/02/08/unconf2018/</guid><description>
&lt;p&gt;For a fifth year running, we are excited to announce the &lt;a href="https://unconf18.ropensci.org/"&gt;rOpenSci unconference&lt;/a&gt;, our annual event loosely modeled on &lt;a href="https://en.wikipedia.org/wiki/Foo_Camp"&gt;Foo Camp&lt;/a&gt;. rOpenSci unconferences have a &lt;a href="https://ropensci.org/blog/2014/05/14/ropenhack/"&gt;rich history&lt;/a&gt;. You can get a feel for them by reading collected stories about &lt;a href="https://ropensci.org/blog/2017/06/02/unconf2017/"&gt;people and projects from unconf17&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;We&amp;rsquo;re organizing unconf18 to bring together scientists, developers, and open data enthusiasts from academia, industry, government, and non-profits to get together for a couple of days to hack on various projects and generally enrich our community. The agenda is mostly decided during the unconference itself. &lt;a href="https://github.com/ropensci/unconf17/issues"&gt;Past projects&lt;/a&gt; have related to open data, data visualization, data publication and open science using R. This event is unlike many other unconferences in that it is primarily invite-only, with a few spots set aside for self-nominations from the community at large. That&amp;rsquo;s you!&lt;/p&gt;</description></item><item><title>The prequel to the drake R package</title><link>https://ropensci.org/blog/2018/02/06/drake/</link><pubDate>Tue, 06 Feb 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/02/06/drake/</guid><description>
&lt;p&gt;The &lt;a href="https://github.com/ropensci/drake"&gt;&lt;code&gt;drake&lt;/code&gt;&lt;/a&gt; R package is a &lt;a href="https://github.com/pditommaso/awesome-pipeline"&gt;pipeline&lt;/a&gt; toolkit. It manages data science workflows, &lt;a href="https://docs.ropensci.org/drake/#what-gets-done-stays-done-"&gt;saves time&lt;/a&gt;, and &lt;a href="https://docs.ropensci.org/drake/#reproducibility-with-confidence"&gt;adds more confidence to reproducibility&lt;/a&gt;. I hope it will impact the landscapes of reproducible research and high-performance computing, but I originally created it for different reasons. This post is the prequel to &lt;a href="https://github.com/ropensci/drake"&gt;&lt;code&gt;drake&lt;/code&gt;&lt;/a&gt;&amp;rsquo;s inception. There was struggle, and &lt;a href="https://github.com/ropensci/drake"&gt;&lt;code&gt;drake&lt;/code&gt;&lt;/a&gt; was the answer.&lt;/p&gt;
&lt;h3&gt;
Dissertation frustration
&lt;/h3&gt;&lt;figure class="center"&gt;&lt;a href="https://sites.google.com/site/sisyphusa/"&gt;&lt;img src="https://ropensci.org/img/blog-images/2018-02-06-drake/uphill.png"
alt="Sisyphus" width="300"&gt;&lt;/a&gt;&lt;figcaption&gt;
&lt;p&gt;&lt;a href="https://sites.google.com/site/sisyphusa/"&gt;&lt;em&gt;Sisyphus&lt;/em&gt;&lt;/a&gt;&lt;/p&gt;
&lt;/figcaption&gt;
&lt;/figure&gt;
&lt;p&gt;My dissertation project was intense. The final computational challenge was to analyze multiple genomics datasets using an &lt;a href="https://github.com/wlandau/fbseq"&gt;emerging method&lt;/a&gt; and its competitors. Even with &lt;a href="https://blog.revolutionanalytics.com/2015/06/computing-with-gpus-in-r.html"&gt;GPU computing&lt;/a&gt;, which shrank days of runtime down to hours, the full battery of &lt;a href="https://en.wikipedia.org/wiki/Markov_chain_Monte_Carlo"&gt;Markov chain Monte Carlo&lt;/a&gt; runs took several weeks from start to finish. I organized my &lt;a href="https://github.com/wlandau/fbseqStudies"&gt;workflow as an R package&lt;/a&gt;, and I worked in a loop:&lt;/p&gt;</description></item><item><title>Writing Packages to Support Research Communities - zoon &amp; greta</title><link>https://ropensci.org/commcalls/2018-01-30/</link><pubDate>Tue, 30 Jan 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/commcalls/2018-01-30/</guid><description/></item><item><title>Introducing Maëlle Salmon, rOpenSci’s new Research Software Engineer</title><link>https://ropensci.org/blog/2018/01/29/rse-ma%C3%ABlle-salmon/</link><pubDate>Mon, 29 Jan 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/01/29/rse-ma%C3%ABlle-salmon/</guid><description>
&lt;p&gt;We’re very pleased to be introducing someone who needs no introduction in the R community. Join us in welcoming Maëlle Salmon to rOpenSci as a Research Software Engineer (part time, working from Nancy, France). We’d like to formally introduce her here and share a bit about the kinds of things she’ll be working on.&lt;/p&gt;
&lt;p&gt;Maëlle did a B.Sc. in Biology with an emphasis on maths and quantitative work, two Masters degrees - one in Ecology and one in Public Health - and a Ph.D. in epidemiological statistics at the Ludwig-Maximilian University in Germany. Her thesis dealt with statistical algorithms for aberration detection in time series of counts of reported cases of infectious diseases. Most recently, Maëlle worked as a data manager and statistician for the &lt;a href="http://www.chaiproject.org/"&gt;CHAI project&lt;/a&gt;. Maëlle has contributed &lt;a href="https://github.com/ropensci/onboarding/issues?q=is%3Aissue+author%3Amaelle+is%3Aclosed+label%3Apackage"&gt;six packages&lt;/a&gt; to rOpenSci to date, and has written about two of them, &lt;a href="https://ropensci.org/blog/2017/02/21/ropenaq/"&gt;&lt;code&gt;ropenaq&lt;/code&gt;&lt;/a&gt; and &lt;a href="https://ropensci.org/blog/2017/08/29/rtimicropem/"&gt;&lt;code&gt;rtimicropem&lt;/code&gt;&lt;/a&gt; for our guest blog series about onboarded software.&lt;/p&gt;</description></item><item><title>nodbi: the NoSQL Database Connector</title><link>https://ropensci.org/blog/2018/01/25/nodbi/</link><pubDate>Thu, 25 Jan 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/01/25/nodbi/</guid><description>
&lt;h2&gt;
DBI
&lt;/h2&gt;&lt;p&gt;What is DBI? &lt;a href="https://cran.r-project.org/web/packages/DBI/"&gt;DBI&lt;/a&gt; is an R package. It defines an interface to relational database management systems (R/DBMS) that other R packages build upon to interact with a specific relational database, such as &lt;a href="https://sqlite.org/"&gt;SQLite&lt;/a&gt; or &lt;a href="https://www.postgresql.org/"&gt;PostgreSQL&lt;/a&gt;.&lt;/p&gt;
&lt;h2&gt;
NoSQL
&lt;/h2&gt;&lt;p&gt;&lt;a href="https://nosql-database.org/"&gt;NoSQL databases&lt;/a&gt; are a very broad class of database that can include document databases such as CouchDB and MongoDB, key-value stores such as Redis, and more. They are generally not row-column relational stores though, though can include that. NoSQL is often thought of now as &amp;ldquo;not only SQL&amp;rdquo;.&lt;/p&gt;</description></item><item><title>fulltext v1: text-mining scholarly works</title><link>https://ropensci.org/blog/2018/01/17/fulltext-v1/</link><pubDate>Wed, 17 Jan 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/01/17/fulltext-v1/</guid><description>
&lt;h2&gt;
The problem
&lt;/h2&gt;&lt;p&gt;Text-mining - the art of answering questions by extracting patterns, data, etc. out of the published literature - is not easy.&lt;/p&gt;
&lt;p&gt;It&amp;rsquo;s made incredibly difficult because of publishers. It is a fact that the vast majority of publicly funded research across the globe is published in paywall journals. That is, taxpayers pay twice for research: once for the grant to fund the work, then again to be able to read it. These paywalls mean that every potential person text-mining will have different access: some have access through their university, some may have access through their company, and others may only have access to whatever happens to be open access. On top of that, access for paywall journals often depends on your &lt;a href="https://en.wikipedia.org/wiki/IP_address"&gt;IP address&lt;/a&gt; - something not generally on top of mind for most people.&lt;/p&gt;</description></item><item><title>5 Things I Learned Making a Package to Work with Hydrometric Data in R</title><link>https://ropensci.org/blog/2018/01/16/tidyhydat/</link><pubDate>Tue, 16 Jan 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/01/16/tidyhydat/</guid><description>
&lt;p&gt;One of the best things about learning R is that no matter your skill level, there is always someone who can benefit from your experience. Topics in R ranging from complicated machine learning approaches to calculating a mean all find their relevant audiences. This is particularly true when writing R packages. With an ever evolving R package development landscape (R, GitHub, external data, CRAN, continuous integration, users), there is a strong possibility that you will be taken into regions of the R world that you never knew existed. More experienced developers may not get stuck in these regions and therefore not think to shine a light on them. It is the objective of this post to explore some of those regions in the R world that were &lt;a href="https://github.com/ropensci/software-review/issues/152"&gt;highlighted for me when the &lt;code&gt;tidyhydat&lt;/code&gt; package was reviewed by rOpenSci&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>.rprofile: Karthik Ram</title><link>https://ropensci.org/blog/2018/01/12/rprofile-karthik-ram/</link><pubDate>Fri, 12 Jan 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/01/12/rprofile-karthik-ram/</guid><description>
&lt;div class="float-left"&gt;&lt;figure class="m-0"&gt;&lt;img src="https://ropensci.org/img/blog-images/2018-01-12-rprofile-karthik-ram/karthik-ram.png"
alt="Karthik Ram"ZgotmplZ
ZgotmplZ
style=" object-fit: cover; object-position: center; height: 250px; width: 250px; margin-right: 15px"
/&gt;
&lt;p&gt;
&lt;em&gt;Karthik Ram is a Data Scientist at the Berkeley Institute for Data Science and Berkeley Institute for Global Change Biology. He is a co-founder of rOpenSci, a collective to support the development of R-based tools which facilitate open science and access to open data. In this interview, Karthik and I discuss the birth of rOpenSci, tools and life hacks for staying sane while managing the constant stress of work fires and the importance of saying no.&lt;/em&gt;
&lt;/p&gt;</description></item><item><title>Community Call - Writing Packages to Support Research Communities - zoon &amp; greta</title><link>https://ropensci.org/blog/2018/01/03/comm-call-v15/</link><pubDate>Wed, 03 Jan 2018 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2018/01/03/comm-call-v15/</guid><description>
&lt;p&gt;&lt;strong&gt;Join our &lt;a href="https://communitycalls.ropensci.org/"&gt;Community Call on Tuesday, January 30th&lt;/a&gt;&lt;/strong&gt; (January 31 for our Australian friends)&lt;/p&gt;
&lt;p&gt;Nick Golding, 2017 rOpenSci Fellow, will talk about two R packages he has developed recently. &lt;a href="https://github.com/zoonproject/zoon"&gt;zoon&lt;/a&gt; aims to promote open and reproducible research in ecological modeling by helping researchers share their code in a modular way and produce reproducible research artifacts. Nick has recently been trying to bootstrap a community around this idea and says this is a much harder problem.&lt;/p&gt;</description></item><item><title>.rprofile: Jenny Bryan</title><link>https://ropensci.org/blog/2017/12/08/rprofile-jenny-bryan/</link><pubDate>Fri, 08 Dec 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/12/08/rprofile-jenny-bryan/</guid><description>
&lt;div class="float-left"&gt;&lt;figure class="m-0"&gt;&lt;img src="https://ropensci.org/img/blog-images/2017-12-08-rprofile-jenny-bryan/jenny_bryan_lowres.jpg"
alt="Jenny Bryan"ZgotmplZ
ZgotmplZ
style=" object-fit: cover; object-position: center; height: 250px; width: 250px; margin-right: 15px"
/&gt;
&lt;p&gt;
&lt;em&gt;Jenny Bryan @JennyBryan is a Software Engineer at RStudio and is on leave from being an Associate Professor at the University of British Columbia. Jenny serves in leadership positions with rOpenSci and &lt;a href="https://forwards.github.io/"&gt;Forwards&lt;/a&gt; and as an Ordinary member of &lt;a href="https://www.r-project.org/foundation/"&gt;The R Foundation&lt;/a&gt;.&lt;/em&gt;
&lt;/p&gt;
&lt;/figure&gt;
&lt;/div&gt;
&lt;div style="clear: both;"&gt;&lt;/div&gt;
&lt;hr&gt;
&lt;p&gt;KO: What is your name, your title, and how many years have you worked in R?&lt;/p&gt;</description></item><item><title>Exploratory Data Analysis of Ancient Texts with rperseus</title><link>https://ropensci.org/blog/2017/12/05/rperseus/</link><pubDate>Tue, 05 Dec 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/12/05/rperseus/</guid><description>
&lt;h3&gt;
Introduction
&lt;/h3&gt;&lt;p&gt;When I was in grad school at Emory, I had a favorite desk in the library. The desk wasn’t particularly cozy or private, but what it lacked in comfort it made up for in real estate. My books and I needed room to operate. Students of the ancient world require many tools, and when jumping between commentaries, lexicons, and interlinears, additional clutter is additional “friction”, i.e., lapses in thought due to frustration. Technical solutions to this clutter exist, but the best ones are proprietary and expensive. Furthermore, they are somewhat inflexible, and you may have to shoehorn your thoughts into their framework. More friction.&lt;/p&gt;</description></item><item><title>Magick 1.6: clipping, geometries, fonts, fuzz, and a bit of history</title><link>https://ropensci.org/blog/2017/12/05/magick-16/</link><pubDate>Tue, 05 Dec 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/12/05/magick-16/</guid><description>
&lt;p&gt;This week &lt;a href="https://cran.r-project.org/web/packages/magick/vignettes/intro.html"&gt;magick&lt;/a&gt; 1.6 appeared on CRAN. This release is a big all-round maintenance update with lots of tweaks and improvements across the package.&lt;/p&gt;
&lt;p&gt;The &lt;a href="https://cran.r-project.org/web/packages/magick/NEWS"&gt;NEWS&lt;/a&gt; file gives an overview of changes in this version. In this post we highlight some changes.&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-r" data-lang="r"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nf"&gt;library&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;magick&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nf"&gt;stopifnot&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nf"&gt;packageVersion&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s"&gt;&amp;#39;magick&amp;#39;&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;&amp;gt;=&lt;/span&gt; &lt;span class="m"&gt;1.6&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;If you are new to magick, check out the &lt;a href="https://cran.r-project.org/web/packages/magick/vignettes/intro.html"&gt;vignette&lt;/a&gt; for a quick introduction.&lt;/p&gt;
&lt;h2&gt;
Perfect Graphics Rendering
&lt;/h2&gt;&lt;p&gt;I have fixed a few small rendering imperfections in the graphics device. The native magick graphics device &lt;code&gt;image_graph()&lt;/code&gt; now renders identical or better quality images as the R-base bitmap devices &lt;code&gt;png&lt;/code&gt;, &lt;code&gt;jpeg&lt;/code&gt;, etc.&lt;/p&gt;</description></item><item><title>The Value of Welcome, part 2: How to prepare 40 new community members for an unconference</title><link>https://ropensci.org/blog/2017/12/01/unconf-welcome/</link><pubDate>Fri, 01 Dec 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/12/01/unconf-welcome/</guid><description>
&lt;p&gt;I’ve raved about the value of &lt;a href="https://ropensci.org/blog/2017/07/18/value-of-welcome/"&gt;extending a personalized welcome&lt;/a&gt; to new community members and I recently shared &lt;a href="https://ropensci.org/blog/2017/11/17/unconf-sixtips"&gt;six tips for running a successful hackathon-flavoured unconference&lt;/a&gt;. Building on these, I’d like to share the specific approach and (free!) tools I used to help prepare new rOpenSci community members to be productive at our &lt;a href="https://unconf17.ropensci.org/"&gt;unconference&lt;/a&gt;. My approach was inspired directly by my &lt;a href="https://www.cscce.org/2016/12/05/introducing-the-2017-community-engagement-fellows/"&gt;AAAS Community Engagement Fellowship Program&lt;/a&gt; (AAAS-CEFP) training. Specifically, 1) one mentor said that the most successful conference they ever ran involved having one-to-one meetings with all participants prior to the event, and 2) prior to our in-person AAAS-CEFP training, we completed an intake questionnaire that forced us to consider things like “what do you hope to get out of this” and “what do you hope to contribute”.&lt;/p&gt;</description></item><item><title>Announcing a New rOpenSci Software Review Collaboration</title><link>https://ropensci.org/blog/2017/11/29/review-collaboration-mee/</link><pubDate>Wed, 29 Nov 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/11/29/review-collaboration-mee/</guid><description>
&lt;p&gt;rOpenSci is pleased to announce a new collaboration with the &lt;a href="http://besjournals.onlinelibrary.wiley.com/hub/journal/10.1111/(ISSN)2041-210X/"&gt;Methods in Ecology and Evolution (MEE)&lt;/a&gt;, a journal of the &lt;a href="https://www.britishecologicalsociety.org/"&gt;British Ecological Society&lt;/a&gt;, published by Wiley press &lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt;. Publications destined for MEE that include the development of a scientific R package will now have the option of a joint review process whereby the R package is reviewed by rOpenSci, followed by fast-tracked review of the manuscript by MEE. Authors opting for this process will be recognized via a mark on both web and print versions of their paper.&lt;/p&gt;</description></item><item><title>changes: easy Git-based version control from R</title><link>https://ropensci.org/blog/2017/11/28/ropensci-changes/</link><pubDate>Tue, 28 Nov 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/11/28/ropensci-changes/</guid><description>
&lt;p&gt;Are you new to version control and always running into trouble with Git?
Or are you a seasoned user, haunted by the traumas of learning Git and reliving them whilst trying to teach it to others?
Yeah, us too.&lt;/p&gt;
&lt;p&gt;&lt;img src="https://ropensci.org/img/blog-images/2017-11-28-ropensci-changes/monkeys.jpg" alt=""&gt;&lt;/p&gt;
&lt;p&gt;Git is a version control tool designed for software development, and it is extraordinarily powerful. It didn’t actually dawn on me quite how amazing Git is until I spent a weekend in Melbourne with a group of Git whizzes using Git to write a package targeted toward Git beginners. Whew, talk about total Git immersion! I was taking part in the 2017 &lt;a href="https://ozunconf17.ropensci.org/"&gt;rOpenSci ozunconf&lt;/a&gt;, in which forty-odd developers, scientists, researchers, nerds, teachers, starving students, cat ladies, and R users of all descriptions form teams to create new R packages fulfilling some new and useful function. Many of the groups used Git for their collaborative workflows all weekend.&lt;/p&gt;</description></item><item><title>ochRe - Australia themed colour palettes</title><link>https://ropensci.org/blog/2017/11/21/ochre/</link><pubDate>Tue, 21 Nov 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/11/21/ochre/</guid><description>
&lt;p&gt;The second rOpenSci &lt;a href="https://ozunconf17.ropensci.org/"&gt;OzUnConf&lt;/a&gt; was held in Melbourne Australia a few weeks ago. A diverse range of &lt;a href="https://ropensci.org/blog/2017/10/31/ozunconf2017/"&gt;scientists, developers and general good-eggs&lt;/a&gt; came together to make some R-magic happen and also learn a lot along the way. Before the conference began, a huge stack of projects were suggested on the unconf &lt;a href="https://github.com/ropensci/ozunconf17/issues"&gt;GitHub repo&lt;/a&gt;. For six data-visualisation enthusiasts, one issue in particular caught their eye, and the &lt;code&gt;ochRe&lt;/code&gt; package was born.&lt;/p&gt;
&lt;p&gt;&lt;img src="https://ropensci.org/img/blog-images/2017-11-21-ochRe/AusElevationExamplePalettes.png" alt=""&gt;&lt;/p&gt;
&lt;p&gt;The &lt;a href="https://github.com/ropenscilabs/ochRe"&gt;&lt;code&gt;ochRe&lt;/code&gt;&lt;/a&gt; package contains colour palettes influenced by the Australian landscape, iconic Australian artists and images. OchRe is originally the brain-child of &lt;a href="https://twitter.com/visnut"&gt;Di Cook&lt;/a&gt;, who was inspired by Karthik Ram&amp;rsquo;s &lt;a href="https://github.com/karthik/wesanderson"&gt;&lt;code&gt;wesanderson&lt;/code&gt;&lt;/a&gt; package.&lt;/p&gt;</description></item><item><title>Six tips for running a successful unconference</title><link>https://ropensci.org/blog/2017/11/17/unconf-sixtips/</link><pubDate>Fri, 17 Nov 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/11/17/unconf-sixtips/</guid><description>
&lt;figure class="center"&gt;&lt;img src="https://ropensci.org/img/blog-images/2017-11-17-unconf-sixtips/ropensci-unconf17-community-nistara-randawa.jpg"
alt="Attendees at the May 2017 rOpenSci unconference. Photo credit: Nistara Randhawa"&gt;&lt;figcaption&gt;
&lt;p&gt;Attendees at the May 2017 rOpenSci unconference. Photo credit: Nistara Randhawa&lt;/p&gt;
&lt;/figcaption&gt;
&lt;/figure&gt;
&lt;p&gt;In May 2017, I helped run a wildly successful “unconference” that had a huge positive impact on the community I serve. rOpenSci is a non-profit initiative enabling open and reproducible research by creating technical infrastructure in the form of staff- and community-contributed software tools in the R programming language that lower barriers to working with scientific data sources on the web, and creating social infrastructure through a welcoming and diverse community of software users and developers. Our 4th annual unconference brought together 70 people to hack on projects they dreamed up and to give them opportunities to meet and work together in person. One third of the participants had attended before, and two thirds were first-timers, selected from an open call for applications. We paid all costs up front for anyone who requested this in order to lower barriers to participation.&lt;/p&gt;</description></item><item><title>2017 rOpenSci ozunconf :: Reflections and the realtime Package</title><link>https://ropensci.org/blog/2017/11/14/realtime/</link><pubDate>Tue, 14 Nov 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/11/14/realtime/</guid><description>
&lt;p&gt;This year&amp;rsquo;s &lt;a href="https://ozunconf17.ropensci.org/"&gt;rOpenSci ozunconf&lt;/a&gt; was held in Melbourne, bringing together over 45 R enthusiasts from around the country and beyond. As is customary, ideas for projects were discussed in &lt;a href="https://github.com/ropensci/ozunconf17/issues"&gt;GitHub Issues&lt;/a&gt; (41 of them by the time the unconf rolled around!) and there was no shortage of enthusiasm, interesting concepts, and varied experience.&lt;/p&gt;
&lt;p&gt;I&amp;rsquo;ve been to a few unconfs now and I treasure the time I get to spend with new people, new ideas, new backgrounds, new approaches, and new insights. That&amp;rsquo;s not to take away from the time I get to spend with people I met at previous unconfs; I&amp;rsquo;ve gained great friendships and started collaborations on side projects with these wonderful people.&lt;/p&gt;</description></item><item><title>.rprofile: Mara Averick</title><link>https://ropensci.org/blog/2017/11/10/rprofile-mara-averick/</link><pubDate>Fri, 10 Nov 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/11/10/rprofile-mara-averick/</guid><description>
&lt;div class="float-left"&gt;&lt;figure class="m-0"&gt;&lt;img src="https://ropensci.org/img/blog-images/2017-11-10-rprofile-mara-averick/mara_averick.png"
alt="Mara Averick, Data Nerd At Large"ZgotmplZ
ZgotmplZ
style=" object-fit: cover; object-position: center; height: 250px; width: 250px; margin-right: 15px"
/&gt;
&lt;figcaption&gt;
Mara Averick, Data Nerd At Large
&lt;/figcaption&gt;
&lt;p&gt;
&lt;em&gt;Mara Averick is a non-profit data nerd, NBA stats junkie, and most recently, tidyverse developer advocate at RStudio. She is the voice behind two very popular Twitter accounts, &lt;a href="https://twitter.com/dataandme"&gt;@dataandme&lt;/a&gt; and &lt;a href="https://twitter.com/batpigandme"&gt;@batpigandme&lt;/a&gt;. Mara and I discussed sports analytics, how attending a cool conference can change the approach to your career, and how she uses Twitter as a mechanism for self-imposed forced learning.&lt;/em&gt;
&lt;/p&gt;</description></item><item><title>solrium 1.0: Working with Solr from R</title><link>https://ropensci.org/blog/2017/11/08/solrium-solr-r/</link><pubDate>Wed, 08 Nov 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/11/08/solrium-solr-r/</guid><description>
&lt;p&gt;Nearly 4 years ago I wrote on this blog about an R package &lt;a href="https://github.com/ropensci/solr"&gt;solr&lt;/a&gt; for working with the database &lt;a href="https://lucene.apache.org/solr//"&gt;Solr&lt;/a&gt;. Since then we&amp;rsquo;ve created a refresh of that package in the &lt;a href="https://github.com/ropensci/solrium"&gt;solrium&lt;/a&gt; package. Since &lt;code&gt;solrium&lt;/code&gt; first hit CRAN about two years ago, users have raised a number of issues that required breaking changes. Thus, this blog post is about a major version bump in &lt;code&gt;solrium&lt;/code&gt;.&lt;/p&gt;
&lt;h2&gt;
What is Solr?
&lt;/h2&gt;&lt;p&gt;Solr is a &amp;ldquo;search platform&amp;rdquo; - a NoSQL database - data is organized by so called documents that are xml/json/etc blobs of text. Documents are nested within either collections or cores (depending on the mode you start Solr in). Solr makes it easy to search for documents, with a huge variety of parameters, and a number of different data formats (json/xml/csv). Solr is similar to &lt;a href="https://www.elastic.co/products/elasticsearch"&gt;Elasticsearch&lt;/a&gt; (see our Elasticsearch client &lt;a href="https://github.com/ropensci/elastic"&gt;elastic&lt;/a&gt;) - and was around before it. Solr in my opinion is harder to setup than Elasticsearch, but I don&amp;rsquo;t claim to be an expert on either.&lt;/p&gt;</description></item><item><title>Using Magick with RMarkdown and Shiny</title><link>https://ropensci.org/blog/2017/11/07/magick-knitr/</link><pubDate>Tue, 07 Nov 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/11/07/magick-knitr/</guid><description>
&lt;p&gt;This week &lt;a href="https://cran.r-project.org/web/packages/magick/vignettes/intro.html"&gt;magick&lt;/a&gt; 1.5 appeared on CRAN. The latest update adds support for using images in knitr documents and shiny apps. In this post we show how this nicely ties together a reproducible image workflow in R, from source image or plot directly into your report or application.&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-r" data-lang="r"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nf"&gt;library&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;magick&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nf"&gt;stopifnot&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nf"&gt;packageVersion&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s"&gt;&amp;#39;magick&amp;#39;&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;&amp;gt;=&lt;/span&gt; &lt;span class="m"&gt;1.5&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Also the magick &lt;a href="https://cran.r-project.org/web/packages/magick/vignettes/intro.html"&gt;intro vignette&lt;/a&gt; has been updated in this version to cover the latest features available in the package.&lt;/p&gt;
&lt;h2&gt;
Magick in Knitr / RMarkdown Documents
&lt;/h2&gt;&lt;p&gt;Magick 1.5 is now fully compatible with knitr. To embed magick images in your rmarkdown report, simply use standard code chunk syntax in your &lt;code&gt;Rmd&lt;/code&gt; file. No special options or packages are required; the image automatically appears in your documents when printed!&lt;/p&gt;</description></item><item><title>Image Convolution in R using Magick</title><link>https://ropensci.org/blog/2017/11/02/image-convolve/</link><pubDate>Thu, 02 Nov 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/11/02/image-convolve/</guid><description>
&lt;p&gt;Release 1.4 of the &lt;a href="https://cran.r-project.org/web/packages/magick/vignettes/intro.html"&gt;magick package&lt;/a&gt; introduces
a new feature called &lt;a href="https://en.wikipedia.org/wiki/Kernel_(image_processing)#Convolution"&gt;image convolution&lt;/a&gt; that
was requested by Thomas L. Pedersen. In this post we explain what this is all about.&lt;/p&gt;
&lt;h2&gt;
Kernel Matrix
&lt;/h2&gt;&lt;p&gt;The new &lt;code&gt;image_convolve()&lt;/code&gt; function applies a &lt;a href="https://en.wikipedia.org/wiki/Kernel_(image_processing)"&gt;kernel&lt;/a&gt; over the image. Kernel convolution means that each pixel value is recalculated using the &lt;em&gt;weighted neighborhood sum&lt;/em&gt; defined in the kernel matrix. For example lets look at this simple kernel:&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-r" data-lang="r"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nf"&gt;library&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;magick&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="n"&gt;kern&lt;/span&gt; &lt;span class="o"&gt;&amp;lt;-&lt;/span&gt; &lt;span class="nf"&gt;matrix&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="m"&gt;0&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;ncol&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="m"&gt;3&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;nrow&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="m"&gt;3&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="n"&gt;kern[1&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="m"&gt;2&lt;/span&gt;&lt;span class="n"&gt;]&lt;/span&gt; &lt;span class="o"&gt;&amp;lt;-&lt;/span&gt; &lt;span class="m"&gt;0.25&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="n"&gt;kern[2&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nf"&gt;c&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="m"&gt;1&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="m"&gt;3&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="n"&gt;]&lt;/span&gt; &lt;span class="o"&gt;&amp;lt;-&lt;/span&gt; &lt;span class="m"&gt;0.25&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="n"&gt;kern[3&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="m"&gt;2&lt;/span&gt;&lt;span class="n"&gt;]&lt;/span&gt; &lt;span class="o"&gt;&amp;lt;-&lt;/span&gt; &lt;span class="m"&gt;0.25&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="n"&gt;kern&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;## [,1] [,2] [,3]&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;## [1,] 0.00 0.25 0.00&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;## [2,] 0.25 0.00 0.25&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;## [3,] 0.00 0.25 0.00&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;This kernel changes each pixel to the mean of its horizontal and vertical neighboring pixels, which results in a slight blurring effect in the right-hand image below:&lt;/p&gt;</description></item><item><title>Building Communities Together at ozunconf, 2017</title><link>https://ropensci.org/blog/2017/10/31/ozunconf2017/</link><pubDate>Tue, 31 Oct 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/10/31/ozunconf2017/</guid><description>
&lt;p&gt;Just last week we organised the 2nd rOpenSci &lt;a href="https://ozunconf17.ropensci.org"&gt;ozunconference&lt;/a&gt;, the sibling rOpenSci unconference, held in Australia. Last year it was &lt;a href="https://auunconf.ropensci.org"&gt;held in Brisbane&lt;/a&gt;, this time around, the ozunconf was hosted in Melbourne, from October 26-27, 2017.&lt;/p&gt;
&lt;p&gt;At the ozunconf, we brought together 45 R-software users and developers, scientists, and open data enthusiasts from academia, industry, government, and non-profits. Participants travelled from far and wide, with people coming from 6 cities around Australia, 2 cities in New Zealand, and one city in the USA. Before the ozunconf we discussed and dreamt up projects to work on for a few days, then met up and brought about a bakers dozen of them into reality.&lt;/p&gt;</description></item><item><title>Data from Public Bicycle Hire Systems</title><link>https://ropensci.org/blog/2017/10/17/bikedata/</link><pubDate>Tue, 17 Oct 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/10/17/bikedata/</guid><description>
&lt;p&gt;A new rOpenSci package provides access to data to which users may already have directly contributed, and for which contribution is fun, keeps you fit, and &lt;a href="https://www.bmj.com/content/357/bmj.j1456"&gt;helps make the world a better place&lt;/a&gt;. The data come from using public bicycle hire schemes, and the package is called &lt;a href="https://github.com/ropensci/bikedata"&gt;&lt;code&gt;bikedata&lt;/code&gt;&lt;/a&gt;. Public bicycle hire systems operate in many cities throughout the world, and most systems collect (generally anonymous) data, minimally consisting of the times and locations at which every single bicycle trip starts and ends. The &lt;a href="https://github.com/ropensci/bikedata"&gt;&lt;code&gt;bikedata&lt;/code&gt;&lt;/a&gt; package provides access to data from all cities which openly publish these data, currently including &lt;a href="https://tfl.gov.uk/modes/cycling/santander-cycles"&gt;London, U.K.&lt;/a&gt;, and in the U.S.A., &lt;a href="https://www.citibikenyc.com"&gt;New York&lt;/a&gt;, &lt;a href="https://bikeshare.metro.net"&gt;Los Angeles&lt;/a&gt;, &lt;a href="https://www.rideindego.com"&gt;Philadelphia&lt;/a&gt;, &lt;a href="https://www.divvybikes.com"&gt;Chicago&lt;/a&gt;, &lt;a href="https://www.thehubway.com"&gt;Boston&lt;/a&gt;, and &lt;a href="https://www.capitalbikeshare.com"&gt;Washington DC&lt;/a&gt;. The package will expand as more cities openly publish their data (with the newly enormously expanded San Francisco system &lt;a href="https://github.com/ropensci/bikedata/issues/2"&gt;next on the list&lt;/a&gt;).&lt;/p&gt;</description></item><item><title>.rprofile: David Smith</title><link>https://ropensci.org/blog/2017/10/13/rprofile-david-smith/</link><pubDate>Fri, 13 Oct 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/10/13/rprofile-david-smith/</guid><description>
&lt;div class="float-left"&gt;&lt;figure class="m-0"&gt;&lt;img src="https://ropensci.org/assets/blog-images/2017-10-13-rprofile_david_smith/david-smith.jpg"
alt="David Smith, R Community Lead at Microsoft"ZgotmplZ
ZgotmplZ
style=" object-fit: cover; object-position: center; height: 250px; width: 250px; margin-right: 15px"
/&gt;
&lt;p&gt;
&lt;em&gt;David Smith is a Blogger and Community Lead at Microsoft. I had the chance to interview David last May at rOpenSci unconf17. We spoke about his career, the process of working remote within a team, community development/outreach and his personal methods for discovering great content to share and write about.&lt;/em&gt;
&lt;/p&gt;
&lt;/figure&gt;
&lt;/div&gt;
&lt;div style="clear: both;"&gt;&lt;/div&gt;
&lt;hr&gt;
&lt;p&gt;KO: What is your name, job title, and how long have you been using R?&lt;/p&gt;</description></item><item><title>Changes to Internet Connectivity in R on Windows</title><link>https://ropensci.org/blog/2017/10/10/curl-30/</link><pubDate>Tue, 10 Oct 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/10/10/curl-30/</guid><description>
&lt;p&gt;This week we released version 3.0 of the &lt;a href="https://cran.r-project.org/web/packages/curl/vignettes/intro.html"&gt;curl&lt;/a&gt; R package to CRAN. You may have never used this package directly, but &lt;code&gt;curl&lt;/code&gt; provides the foundation for most HTTP infrastructure in R, including &lt;code&gt;httr&lt;/code&gt;, &lt;code&gt;rvest&lt;/code&gt;, and all packages that build on it. If R packages need to go online, chances are traffic is going via curl.&lt;/p&gt;
&lt;p&gt;This release introduces an important change for Windows users: we are switching from OpenSSL to Secure Channel on Windows 7 / 2008-R2 and up. Let me explain this in a bit more detail.&lt;/p&gt;</description></item><item><title>Governance, Engagement, and Resistance in the Open Science Movement: A Comparative Study</title><link>https://ropensci.org/blog/2017/10/06/sholler-plan/</link><pubDate>Fri, 06 Oct 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/10/06/sholler-plan/</guid><description>
&lt;p&gt;A growing community of scientists from a variety of disciplines is moving the norms of scientific research toward open practices. Supporters of open science hope to increase the quality and efficiency of research by enabling the widespread sharing of datasets, research software source code, publications, and other processes and products of research. The speed at which the open science community seems to be growing mirrors the rapid development of technological capabilities, including robust open source scientific software, new services for data sharing and publication, and novel data science techniques for working with massive datasets. Organizations like rOpenSci harness such capabilities and deploy various combinations of these research tools, or what I refer to here as open science infrastructures, to facilitate open science.&lt;/p&gt;</description></item><item><title>googleLanguageR - Analysing language through the Google Cloud Machine Learning APIs</title><link>https://ropensci.org/blog/2017/10/03/googlelanguager/</link><pubDate>Tue, 03 Oct 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/10/03/googlelanguager/</guid><description>
&lt;!-- open source image taken from: https://upload.wikimedia.org/wikipedia/commons/2/21/Bell_System_switchboard.jpg --&gt;
&lt;p&gt;&lt;figure class="center"&gt;&lt;a href="https://upload.wikimedia.org/wikipedia/commons/2/21/Bell_System_switchboard.jpg"&gt;&lt;img src="https://ropensci.org/assets/blog-images/2017-10-03-googlelanguager/switchboard.jpg"&gt;&lt;/a&gt;
&lt;/figure&gt;
&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;One of the greatest assets human beings possess is the power of speech and language, from which almost all our other accomplishments flow. To be able to analyse communication offers us a chance to gain a greater understanding of one another.&lt;/p&gt;
&lt;p&gt;To help you with this, &lt;a href="https://code.markedmondson.me/googleLanguageR/"&gt;&lt;code&gt;googleLanguageR&lt;/code&gt;&lt;/a&gt; is an R package that allows you to perform speech-to-text transcription, neural net translation and natural language processing via the &lt;a href="https://cloud.google.com/products/machine-learning/"&gt;Google Cloud machine learning services&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Help us build capacity of open software users and developers with Hacktoberfest</title><link>https://ropensci.org/blog/2017/10/02/hacktoberfest/</link><pubDate>Mon, 02 Oct 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/10/02/hacktoberfest/</guid><description>
&lt;p&gt;One of rOpenSci’s aims is to build capacity of software users and developers and foster a sense of pride in their work. What better way to do that than to encourage you to participate in &lt;a href="https://hacktoberfest.digitalocean.com/"&gt;Hacktoberfest&lt;/a&gt;, a month-long celebration of open source software!&lt;/p&gt;
&lt;p&gt;&lt;img src="https://ropensci.org/assets/blog-images/2017-10-02-hacktoberfest/hacktoberfest-2017.jpg" alt=""&gt;&lt;/p&gt;
&lt;h3&gt;
It doesn’t take much to get involved
&lt;/h3&gt;&lt;p&gt;Beginners to experts. Contributors and package maintainers welcome. You can get involved by applying the label &lt;code&gt;Hacktoberfest&lt;/code&gt; to issues in your rOpenSci repo (or any project) that are ready for contributors to work on. You can find already-labelled &lt;a href="https://github.com/search?utf8=%E2%9C%93&amp;amp;q=user%3Aropensci+user%3Aropenscilabs+label%3Ahacktoberfest+state%3Aopen+type%3Aissue&amp;amp;type="&gt;rOpenSci and ropenscilabs issues here&lt;/a&gt;. A contribution can be anything - fixing typos, improving documentation, writing tests, fixing bugs, or creating new features. Who better to improve a vignette than the person who’s using the package?!&lt;/p&gt;</description></item><item><title>rrricanes to Access Tropical Cyclone Data</title><link>https://ropensci.org/blog/2017/09/27/rrricanes/</link><pubDate>Wed, 27 Sep 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/09/27/rrricanes/</guid><description>
&lt;h3&gt;
What is rrricanes
&lt;/h3&gt;&lt;h4&gt;
Why Write rrricanes?
&lt;/h4&gt;&lt;p&gt;There is a tremendous amount of weather data available on the internet. Much of it is in raw format and not very easy to obtain. Hurricane data is no different. When one thinks of this data they may be inclined to think it is a bunch of map coordinates with some wind values and not much else. A deeper look will reveal structural and forecast data. An even deeper look will find millions of data points from hurricane reconnaissance, computer forecast models, ship and buoy observations, satellite and radar imagery, &amp;hellip;&lt;/p&gt;</description></item><item><title>Accessing patent data with the patentsview package</title><link>https://ropensci.org/blog/2017/09/19/patentsview/</link><pubDate>Tue, 19 Sep 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/09/19/patentsview/</guid><description>
&lt;h3&gt;
Why care about patents?
&lt;/h3&gt;&lt;p&gt;&lt;strong&gt;1. Patents play a critical role in incentivizing innovation, without
which we wouldn&amp;rsquo;t have much of the technology we rely on everyday&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;What does your iPhone, Google&amp;rsquo;s PageRank algorithm, and a butter
substitute called Smart Balance all have in common?&lt;/p&gt;
&lt;!-- These are open source images taken from: https://pixabay.com/ --&gt;
&lt;div class="gallery caption-position-bottom caption-effect-slide hover-effect-zoom hover-transition" itemscope itemtype="http://schema.org/ImageGallery"&gt;
&lt;div class="box" &gt;
&lt;figure itemprop="associatedMedia" itemscope itemtype="http://schema.org/ImageObject"&gt;
&lt;div class="img" style="background-image: url('/img/blog-images/2017-09-19-patentsview/iphone.png');"&gt;
&lt;img itemprop="thumbnail" src="https://ropensci.org/img/blog-images/2017-09-19-patentsview/iphone.png" alt="IPhone"/&gt;
&lt;/div&gt;
&lt;a href="https://ropensci.org/img/blog-images/2017-09-19-patentsview/iphone.png" itemprop="contentUrl" aria-disabled="true"&gt;&lt;/a&gt;
&lt;figcaption&gt;
&lt;p&gt;Iphone&lt;/p&gt;
&lt;/figcaption&gt;
&lt;/figure&gt;
&lt;/div&gt;
&lt;div class="box" &gt;
&lt;figure itemprop="associatedMedia" itemscope itemtype="http://schema.org/ImageObject"&gt;
&lt;div class="img" style="background-image: url('/img/blog-images/2017-09-19-patentsview/google.jpg');"&gt;
&lt;img itemprop="thumbnail" src="https://ropensci.org/img/blog-images/2017-09-19-patentsview/google.jpg" alt="Google homepage screenshot"/&gt;
&lt;/div&gt;
&lt;a href="https://ropensci.org/img/blog-images/2017-09-19-patentsview/google.jpg" itemprop="contentUrl" aria-disabled="true"&gt;&lt;/a&gt;
&lt;figcaption&gt;
&lt;p&gt;Google homepage screenshot&lt;/p&gt;</description></item><item><title>rOpenSci Software Review and Onboarding</title><link>https://ropensci.org/commcalls/2017-09-13/</link><pubDate>Wed, 13 Sep 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/commcalls/2017-09-13/</guid><description/></item><item><title>rOpenSci Software Review: Always Improving</title><link>https://ropensci.org/blog/2017/09/11/software-review-update/</link><pubDate>Mon, 11 Sep 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/09/11/software-review-update/</guid><description>
&lt;p&gt;The R package ecosystem now contains more than 10K packages, and several flagship packages belong under the rOpenSci suite. Some of these are: &lt;a href="https://github.com/ropensci/magick"&gt;magick&lt;/a&gt; for image manipulation, &lt;a href="https://github.com/ropensci/plotly"&gt;plotly&lt;/a&gt; for interactive plots, and &lt;a href="https://github.com/ropensci/git2r"&gt;git2r&lt;/a&gt; for interacting with &lt;code&gt;git&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;rOpenSci is a community of people making software to facilitate open and reproducible science/research. While the rOpenSci team continues to develop and maintain core infrastructure packages, an increasing number of packages in our suite are contributed by members of the extended R community.&lt;/p&gt;</description></item><item><title>Experiences as a first time rOpenSci package reviewer</title><link>https://ropensci.org/blog/2017/09/08/first-review-experiences/</link><pubDate>Fri, 08 Sep 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/09/08/first-review-experiences/</guid><description><i><a href="https://ropensci.org/es/blog/2017/09/08/first-review-experiences/">Read it in: Español</a>.</i><i><a href="https://ropensci.org/pt/blog/2017/09/08/first-review-experiences/">Read it in: Português</a>.</i>
&lt;p&gt;It all started January 26&lt;sup&gt;th&lt;/sup&gt; this year when I signed up to volunteer as
a reviewer for R packages submitted to rOpenSci. My main motivation for
wanting to volunteer was to learn something new and to
contribute to the R open source community. If you are wondering why the
people behind rOpenSci are doing this, you can read &lt;a href="https://www.numfocus.org/blog/how-ropensci-uses-code-review-to-promote-reproducible-science/"&gt;How rOpenSci uses Code Review to Promote Reproducible Science&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Three months later I was contacted by &lt;a href="https://twitter.com/masalmon"&gt;Maëlle Salmon&lt;/a&gt; asking whether I was interested in
reviewing the R package &lt;a href="https://github.com/ropensci/patentsview"&gt;&lt;code&gt;patentsview&lt;/code&gt;&lt;/a&gt; for rOpenSci. And yes, I
was! To be honest I was a little bit thrilled.&lt;/p&gt;</description></item><item><title>The writexl package: zero dependency xlsx writer for R</title><link>https://ropensci.org/blog/2017/09/08/writexl-release/</link><pubDate>Fri, 08 Sep 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/09/08/writexl-release/</guid><description>
&lt;p&gt;We have started working on a new rOpenSci package called &lt;a href="https://github.com/ropensci/writexl#readme"&gt;writexl&lt;/a&gt;. This package wraps the very powerful &lt;a href="https://libxlsxwriter.github.io/"&gt;libxlsxwriter&lt;/a&gt; library which allows for exporting data to Microsoft Excel format.&lt;/p&gt;
&lt;p&gt;The major benefit of writexl over other packages is that it is completely written in C and has absolutely zero dependencies. No Java, Perl or Rtools are required.&lt;/p&gt;
&lt;h2&gt;
Getting Started
&lt;/h2&gt;&lt;p&gt;The &lt;code&gt;write_xlsx&lt;/code&gt; function writes a data frame to an xlsx file. You can test that data roundtrips properly by reading it back using the readxl package. Columns containing dates and factors get automatically coerced to character strings.&lt;/p&gt;</description></item><item><title>Spelling 1.0: quick and effective spell checking in R</title><link>https://ropensci.org/blog/2017/09/07/spelling-release/</link><pubDate>Thu, 07 Sep 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/09/07/spelling-release/</guid><description>
&lt;p&gt;The new rOpenSci &lt;a href="https://cran.r-project.org/web/packages/spelling/index.html"&gt;spelling&lt;/a&gt; package provides utilities for spell checking common document formats including latex, markdown, manual pages, and DESCRIPTION files. It also includes tools especially for package authors to automate spell checking of R documentation and vignettes.&lt;/p&gt;
&lt;h2&gt;
Spell Checking Packages
&lt;/h2&gt;&lt;p&gt;The main purpose of this package is to quickly find spelling errors in R packages. The &lt;code&gt;spell_check_package()&lt;/code&gt; function extracts all text from your package manual pages and vignettes, compares it against a language (e.g. en_US or en_GB), and lists potential errors in a nice tidy format:&lt;/p&gt;</description></item><item><title>How rOpenSci uses Code Review to Promote Reproducible Science</title><link>https://ropensci.org/blog/2017/09/01/nf-softwarereview/</link><pubDate>Fri, 01 Sep 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/09/01/nf-softwarereview/</guid><description><i><a href="https://ropensci.org/es/blog/2017/09/01/nf-softwarereview-es/">Read it in: Español</a>.</i><i><a href="https://ropensci.org/pt/blog/2017/09/01/nf-softwarereview/">Read it in: Português</a>.</i>
&lt;p&gt;At rOpenSci, we create and curate software to help scientists with the data life cycle. These tools access, download, manage, and archive scientific data in open, reproducible ways. Early on, we realized this could only be a community effort. The variety of scientific data and workflows could only be tackled by drawing on contributions of scientists with field-specific expertise.&lt;/p&gt;
&lt;p&gt;With the community approach came challenges. &lt;strong&gt;How could we ensure the quality of code written by scientists without formal training in software development practices? How could we drive adoption of best practices among our contributors? How could we create a community that would support each other in this work?&lt;/strong&gt;&lt;/p&gt;</description></item><item><title>Community Call - rOpenSci Software Review and Onboarding</title><link>https://ropensci.org/blog/2017/08/31/comm-call-v14/</link><pubDate>Thu, 31 Aug 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/08/31/comm-call-v14/</guid><description>
&lt;p&gt;Are you thinking about submitting a package to rOpenSci&amp;rsquo;s open peer software review? Considering volunteering to review for the first time? Maybe you&amp;rsquo;re an experienced package author or reviewer and have ideas about how we can improve.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Join our &lt;a href="https://ropensci.org/commcalls/2017-09-13/"&gt;Community Call on Wednesday, September 13th&lt;/a&gt;&lt;/strong&gt;. We want to get your feedback and we&amp;rsquo;d love to answer your questions!&lt;/p&gt;
&lt;h3&gt;
Agenda
&lt;/h3&gt;&lt;ol&gt;
&lt;li&gt;Welcome (Stefanie Butland, rOpenSci Community Manager, 5 min)&lt;/li&gt;
&lt;li&gt;guest: Noam Ross, editor (15 min)
Noam will give an overview of the rOpenSci software review and onboarding, highlighting the role editors play and how decisions are made about policies and changes to the process.&lt;/li&gt;
&lt;li&gt;guest: Andee Kaplan, reviewer (15 min)
Andee will give her perspective as a package reviewer, sharing specifics about her workflow and her motivation for doing this.&lt;/li&gt;
&lt;li&gt;Q &amp;amp; A (25 min, moderated by Noam Ross)&lt;/li&gt;
&lt;/ol&gt;
&lt;h3&gt;
Speaker bios
&lt;/h3&gt;&lt;p&gt;&lt;strong&gt;Andee Kaplan&lt;/strong&gt; is a Postdoctoral Fellow at Duke University. She is a recent PhD graduate from the Iowa State University Department of Statistics, where she learned a lot about R and reproducibility by developing a class on data stewardship for Agronomists. Andee has reviewed multiple (two!) packages for rOpenSci, &lt;a href="https://github.com/ropensci/software-review/issues/107"&gt;&lt;code&gt;iheatmapr&lt;/code&gt;&lt;/a&gt; and &lt;a href="https://github.com/ropensci/software-review/issues/58"&gt;&lt;code&gt;getlandsat&lt;/code&gt;&lt;/a&gt;, and hopes to one day be on the receiving end of the review process.&lt;/p&gt;</description></item><item><title>rtimicropem: Using an R package as platform for harmonized cleaning of data from RTI MicroPEM air quality sensors</title><link>https://ropensci.org/blog/2017/08/29/rtimicropem/</link><pubDate>Tue, 29 Aug 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/08/29/rtimicropem/</guid><description>
&lt;p&gt;As you might remember from &lt;a href="https://ropensci.org/blog/2017/02/21/ropenaq"&gt;my blog post about &lt;code&gt;ropenaq&lt;/code&gt;&lt;/a&gt;, I work as a data manager and statistician for an &lt;a href="http://www.chaiproject.org/"&gt;epidemiology project called CHAI&lt;/a&gt; for Cardio-vascular health effects of air pollution in Telangana, India. One of our interests in CHAI is determining exposure, and sources of exposure, to PM2.5 which are very small particles in the air that have diverse adverse health effects. You can find more details about CHAI &lt;a href="https://www.ncbi.nlm.nih.gov/pubmed/28606699"&gt;in our recently published protocol paper&lt;/a&gt;. In this blog post that partly corresponds to the content of &lt;a href="https://sched.co/AxrS"&gt;my useR! 2017 lightning talk&lt;/a&gt;, I&amp;rsquo;ll present a package we wrote for dealing with the output of a scientific device, which might remind you of similar issues in your experimental work.&lt;/p&gt;</description></item><item><title>FedData - Getting assorted geospatial data into R</title><link>https://ropensci.org/blog/2017/08/24/feddata-release/</link><pubDate>Thu, 24 Aug 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/08/24/feddata-release/</guid><description>
&lt;p&gt;The package &lt;a href="https://github.com/ropensci/FedData"&gt;&lt;code&gt;FedData&lt;/code&gt;&lt;/a&gt; has gone through software review and is now part of &lt;a href="https://ropensci.org/"&gt;rOpenSci&lt;/a&gt;. &lt;code&gt;FedData&lt;/code&gt; includes functions to automate downloading geospatial data available from several federated data sources (mainly sources maintained by the US Federal government).&lt;/p&gt;
&lt;p&gt;Currently, the package enables extraction from six datasets:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The &lt;a href="https://ned.usgs.gov"&gt;National Elevation Dataset (NED)&lt;/a&gt; digital elevation models (1 and 1/3 arc-second; USGS)&lt;/li&gt;
&lt;li&gt;The &lt;a href="https://nhd.usgs.gov"&gt;National Hydrography Dataset (NHD)&lt;/a&gt; (USGS)&lt;/li&gt;
&lt;li&gt;The &lt;a href="https://websoilsurvey.sc.egov.usda.gov/"&gt;Soil Survey Geographic (SSURGO) database&lt;/a&gt; from the National Cooperative Soil Survey (NCSS), which is led by the Natural Resources Conservation Service (NRCS) under the USDA,
NA&lt;/li&gt;
&lt;li&gt;The &lt;a href="https://daymet.ornl.gov/"&gt;Daymet&lt;/a&gt; gridded estimates of daily weather parameters for North America, version 3, available from the Oak Ridge National Laboratory&amp;rsquo;s Distributed Active Archive Center (DAAC), and&lt;/li&gt;
&lt;li&gt;The &lt;a href="https://www.ncdc.noaa.gov/data-access/paleoclimatology-data/datasets/tree-ring"&gt;International Tree Ring Data Bank (ITRDB)&lt;/a&gt;, coordinated by National Climatic Data Center at NOAA.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;code&gt;FedData&lt;/code&gt; is designed with the large-scale geographic information system (GIS) use-case in mind: cases where the use of dynamic web-services is impractical due to the scale (spatial and/or temporal) of analysis. It functions primarily as a means of downloading tiled or otherwise spatially-defined datasets; additionally, it can preprocess those datasets by extracting data within an area of interest (AoI), defined spatially. It relies heavily on the &lt;a href="https://cran.r-project.org/package=sp"&gt;&lt;code&gt;sp&lt;/code&gt;&lt;/a&gt;, &lt;a href="https://cran.r-project.org/package=raster"&gt;&lt;code&gt;raster&lt;/code&gt;&lt;/a&gt;, and &lt;a href="https://cran.r-project.org/package=rgdal"&gt;&lt;code&gt;rgdal&lt;/code&gt;&lt;/a&gt; packages.&lt;/p&gt;</description></item><item><title>Onboarding visdat, a tool for preliminary visualisation of whole dataframes</title><link>https://ropensci.org/blog/2017/08/22/visdat/</link><pubDate>Tue, 22 Aug 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/08/22/visdat/</guid><description>
&lt;blockquote&gt;
&lt;p&gt;Take a look at the data&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;This is a phrase that comes up when you first get a dataset.&lt;/p&gt;
&lt;p&gt;It is also ambiguous. Does it mean to do some exploratory modelling? Or make some histograms, scatterplots, and boxplots? Is it both?&lt;/p&gt;
&lt;p&gt;Starting down either path, you often encounter the non-trivial growing pains of working with a new dataset. The mix ups of data types - height in cm coded as a factor, categories are numerics with decimals, strings are datetimes, and somehow datetime is one long number. And let&amp;rsquo;s not forget everyone&amp;rsquo;s favourite: missing data.&lt;/p&gt;</description></item><item><title>So you (don't) think you can review a package</title><link>https://ropensci.org/blog/2017/08/22/first-package-review/</link><pubDate>Tue, 22 Aug 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/08/22/first-package-review/</guid><description><i><a href="https://ropensci.org/es/blog/2017/08/22/first-package-review/">Read it in: Español</a>.</i>
&lt;p&gt;Contributing to an open-source community &lt;em&gt;without&lt;/em&gt; contributing code is an oft-vaunted idea that can seem nebulous. Luckily, putting vague ideas into action is one of the strengths of the &lt;a href="https://ropensci.org/community/"&gt;rOpenSci Community&lt;/a&gt;, and their package onboarding system offers a chance to do just that.&lt;/p&gt;
&lt;p&gt;This was my first time reviewing a package, and, as with so many things in life, I went into it worried that I&amp;rsquo;d somehow ruin the package-reviewing process— not just the package itself, but the actual onboarding infrastructure&amp;hellip;maybe even rOpenSci on the whole.&lt;/p&gt;</description></item><item><title>Tesseract and Magick: High Quality OCR in R</title><link>https://ropensci.org/blog/2017/08/17/tesseract-16/</link><pubDate>Thu, 17 Aug 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/08/17/tesseract-16/</guid><description>
&lt;p&gt;Last week we released an update of the tesseract package to CRAN. This package provides R bindings to Google&amp;rsquo;s OCR library &lt;a href="https://en.wikipedia.org/wiki/Tesseract_(software)"&gt;Tesseract&lt;/a&gt;.&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-r" data-lang="r"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nf"&gt;install.packages&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s"&gt;&amp;#34;tesseract&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;The new version ships with the latest libtesseract 3.05.01 on Windows and MacOS. Furthermore it includes enhancements for managing language data and using tesseract together with the magick package.&lt;/p&gt;
&lt;h2&gt;
Installing Language Data
&lt;/h2&gt;&lt;p&gt;The new version has several improvements for installing additional language data. On Windows and MacOS you use the &lt;code&gt;tesseract_download()&lt;/code&gt; function to install additional languages:&lt;/p&gt;</description></item><item><title>Magick 1.0: 🎩 ✨🐇 Advanced Graphics and Image Processing in R</title><link>https://ropensci.org/blog/2017/08/15/magick-10/</link><pubDate>Tue, 15 Aug 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/08/15/magick-10/</guid><description>
&lt;p&gt;Last week, version 1.0 of the &lt;a href="https://cran.r-project.org/web/packages/magick/index.html"&gt;magick&lt;/a&gt; package appeared on CRAN: an ambitious effort to modernize and simplify high quality image processing in R. This R package builds upon the &lt;a href="https://www.imagemagick.org/Magick++/STL.html"&gt;Magick++ STL&lt;/a&gt; which exposes a powerful C++ API to the famous ImageMagick library.&lt;/p&gt;
&lt;p&gt;&lt;img src="https://jeroen.github.io/images/magick.png" alt="RStudio Screenshot"&gt;&lt;/p&gt;
&lt;p&gt;The best place to start learning about magick is the &lt;a href="https://cran.r-project.org/web/packages/magick/vignettes/intro.html"&gt;vignette&lt;/a&gt; which gives a brief overview of the overwhelming amount of functionality in this package.&lt;/p&gt;
&lt;h3&gt;
Towards Release 1.0
&lt;/h3&gt;&lt;p&gt;Last year around this time rOpenSci &lt;a href="https://ropensci.org/blog/2016/08/23/z-magick-release"&gt;announced&lt;/a&gt; the first release of the magick package: a new powerful toolkit for image reading, writing, converting, editing, transformation, annotation, and animation in R. Since the initial release there have been several updates with additional functionality, and many useRs have started to discover the power of this package to take visualization in R to the next level.&lt;/p&gt;</description></item><item><title>Chat with the rOpenSci team at upcoming meetings</title><link>https://ropensci.org/blog/2017/08/11/ropensci-at-meetings/</link><pubDate>Fri, 11 Aug 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/08/11/ropensci-at-meetings/</guid><description>
&lt;p&gt;You can find members of the rOpenSci team at various meetings and workshops around the world. Come say &amp;lsquo;hi&amp;rsquo;, learn about how our &lt;a href="https://ropensci.org/packages/"&gt;packages&lt;/a&gt; can enable your research, or about our &lt;a href="https://github.com/ropensci/software-review"&gt;onboarding&lt;/a&gt; process for contributing new packages, discuss software &lt;a href="https://ropensci.org/blog/2016/05/25/software-sustanability-ropensci"&gt;sustainability&lt;/a&gt; or tell us how we can help you do open and reproducible research.&lt;/p&gt;</description></item><item><title>Unconf 2017: The Roads Not Taken</title><link>https://ropensci.org/blog/2017/08/08/unconfroadsnottaken/</link><pubDate>Tue, 08 Aug 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/08/08/unconfroadsnottaken/</guid><description>
&lt;p&gt;Since June, we have been highlighting the &lt;a href="https://ropensci.org/blog/2017/06/08/unconf_recap_4"&gt;many projects&lt;/a&gt; that emerged from this year&amp;rsquo;s &lt;a href="https://ropensci.org/blog/2017/06/02/unconf2017"&gt;rOpenSci Unconf&lt;/a&gt;. These projects start many weeks before unconf participants gather in-person. Each year, we ask participants to propose and discuss project ideas ahead of time in a &lt;a href="https://github.com/ropensci/unconf17/issues"&gt;GitHub repo&lt;/a&gt;. This serves to get creative juices flowing as well as help people get to know each other a bit through discussion.&lt;/p&gt;
&lt;p&gt;This year wasn&amp;rsquo;t just our biggest unconf ever, it was the biggest in terms of proposed ideas! We had more proposals than participants, so we had a great pool to draw from when we got down to work in L.A. Yet many good ideas were left on the cutting room floor. Here we highlight some of those ideas we didn&amp;rsquo;t quite get to. Many have lots of potential and we hope the R and rOpenSci communities take them up!&lt;/p&gt;</description></item><item><title>elastic - Elasticsearch for R</title><link>https://ropensci.org/blog/2017/08/02/elasticsearch-client/</link><pubDate>Wed, 02 Aug 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/08/02/elasticsearch-client/</guid><description>
&lt;p&gt;&lt;strong&gt;elastic&lt;/strong&gt; is an R client for &lt;a href="https://www.elastic.co/products/elasticsearch"&gt;Elasticsearch&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;code&gt;elastic&lt;/code&gt; has been around since 2013, with the first commit in &lt;a href="https://github.com/ropensci/elastic/commit/f7b04589b2cb711a21223bb4f20b34bc9330ef8d"&gt;November, 2013&lt;/a&gt;.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;sidebar - &amp;rsquo;elastic&amp;rsquo; was picked as a package named before the company now known as Elastic
changed their name to Elastic.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2&gt;
What is Elasticsearch?
&lt;/h2&gt;&lt;p&gt;If you aren&amp;rsquo;t familiar with Elasticsearch, it is a distributed, RESTful search and analytics engine.
It&amp;rsquo;s similar to &lt;a href="https://lucene.apache.org/solr//"&gt;Solr&lt;/a&gt;. It falls in the NoSQL bin of databases, holding data in JSON documents, instead
of rows and columns. Elasticsearch has a concept of &lt;strong&gt;index&lt;/strong&gt;, similar to a database in SQL-land.
You can hold many documents of similar type within a single index. There is powerful search
capabilities, including lots of different types of queries that can be done separately
or combined. And best of all it&amp;rsquo;s super fast.&lt;/p&gt;</description></item><item><title>emldown - From machine readable EML metadata to a pretty documentation website</title><link>https://ropensci.org/blog/2017/08/01/emldown/</link><pubDate>Tue, 01 Aug 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/08/01/emldown/</guid><description>
&lt;p&gt;How do you get the maximum value out of a dataset? Data is most valuable when it can easily be shared, understood, and used by others. This requires some form of metadata that describes the data. While metadata can take many forms, the most useful metadata is that which follows a standardized specification. The &lt;a href="https://knb.ecoinformatics.org/#external//emlparser/docs/index.html"&gt;Ecological Metadata Language (EML)&lt;/a&gt; is an example of such a specification originally developed for ecological datasets. EML describes what information should be included to describe the data, and what format that information should be represented in.&lt;/p&gt;</description></item><item><title>The rOpenSci Taxonomy Suite</title><link>https://ropensci.org/blog/2017/07/27/taxonomy-suite/</link><pubDate>Thu, 27 Jul 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/07/27/taxonomy-suite/</guid><description>
&lt;h2&gt;
What is Taxonomy?
&lt;/h2&gt;&lt;p&gt;Taxonomy in its most general sense is &lt;a href="https://en.wikipedia.org/wiki/Taxonomy_(general)"&gt;the practice and science of classification&lt;/a&gt;. It can refer to many things. You may have heard or used the word &lt;em&gt;taxonomy&lt;/em&gt; used to indicate any sort of classification of things, whether it be companies or widgets. Here, we&amp;rsquo;re talking about &lt;a href="https://en.wikipedia.org/wiki/Taxonomy_(biology)"&gt;biological taxonomy&lt;/a&gt;, the science of defining and naming groups of biological organisms.&lt;/p&gt;
&lt;p&gt;In case you aren&amp;rsquo;t familiar with the terminology, here&amp;rsquo;s a brief intro.&lt;/p&gt;</description></item><item><title>notary - Signing &amp; Verification of R Packages</title><link>https://ropensci.org/blog/2017/07/25/notary/</link><pubDate>Tue, 25 Jul 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/07/25/notary/</guid><description>
&lt;p&gt;Most of us who work in R just want to Get Stuff Done™. We want a minimum amount of friction between ourselves and the data we need to wrangle, analyze, and visualize. We&amp;rsquo;re focused on solving a problem or gaining insights into a new area of research. We rely on a rich, community-driven ecosystem of packages to help get our work done and likely make an unconscious assumption that there is a safety net out there, protecting us from harm.&lt;/p&gt;</description></item><item><title>The Value of #Welcome</title><link>https://ropensci.org/blog/2017/07/18/value-of-welcome/</link><pubDate>Tue, 18 Jul 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/07/18/value-of-welcome/</guid><description>
&lt;p&gt;In my training as a &lt;a href="https://www.cscce.org/2016/12/05/introducing-the-2017-community-engagement-fellows/"&gt;AAAS Community Engagement Fellow&lt;/a&gt;, I hear repeatedly about the value of extending a personal welcome to your community members. This seems intuitive, but recently I put this to the test. Let me tell you about my experience creating and maintaining a #welcome channel in a community Slack group.&lt;/p&gt;
&lt;figure class="center"&gt;&lt;a href="https://www.flickr.com/photos/90371939@N00/4344878104"&gt;&lt;img src="https://live.staticflickr.com/4047/4344878104_5b22de25b1_h.jpg"
alt="welcome" width="550"&gt;&lt;/a&gt;&lt;figcaption&gt;
&lt;p&gt;&lt;a href="https://www.flickr.com/photos/90371939@N00/4344878104"&gt;Welcome&lt;/a&gt; by &lt;a href="https://www.flickr.com/photos/90371939@N00/"&gt;Nathan&lt;/a&gt; under &lt;a href="https://creativecommons.org/licenses/by-sa/2.0/"&gt;CC BY-SA 2.0&lt;/a&gt;&lt;/p&gt;
&lt;/figcaption&gt;
&lt;/figure&gt;
&lt;p&gt;I listen in on and occasionally participate in a Slack group for &lt;a href="https://rladies.org/"&gt;R-Ladies&lt;/a&gt; community organizers (R-Ladies is a global organization with local meetup chapters around the world, for women who do/want to do programming in R). Their Slack is incredibly well-organized and has a #welcome channel where new joiners are invited to introduce themselves in a couple of sentences. The leaders regularly jump in to add a wave emoji and ask people to introduce themselves if they have not already.&lt;/p&gt;</description></item><item><title>skimr for useful and tidy summary statistics</title><link>https://ropensci.org/blog/2017/07/11/skimr/</link><pubDate>Tue, 11 Jul 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/07/11/skimr/</guid><description>
&lt;p&gt;Like every R user who uses summary statistics (so, everyone), our team has to rely on some combination of summary functions beyond &lt;code&gt;summary()&lt;/code&gt; and &lt;code&gt;str()&lt;/code&gt;. But we found them all lacking in some way because they can be generic, they don&amp;rsquo;t always provide easy-to-operate-on data structures, and they are not pipeable. What we wanted was a frictionless approach for quickly skimming useful and tidy summary statistics as part of a pipeline. And so at &lt;a href="https://unconf17.ropensci.org/"&gt;rOpenSci #unconf17&lt;/a&gt;, we developed &lt;a href="https://github.com/ropenscilabs/skimr#skimr"&gt;&lt;code&gt;skimr&lt;/code&gt;&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Announcing the rOpenSci Fellowships Program</title><link>https://ropensci.org/blog/2017/07/06/ropensci-fellowships/</link><pubDate>Thu, 06 Jul 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/07/06/ropensci-fellowships/</guid><description>
&lt;p&gt;rOpenSci&amp;rsquo;s mission is to promote a culture of open, transparent, and reproducible research across various research domains. Everything we do, from developing high-quality open-source software for data science and, &lt;a href="https://github.com/ropensci/software-review"&gt;software review&lt;/a&gt;, to building community through events like our &lt;a href="https://ropensci.org/commcalls/"&gt;community calls&lt;/a&gt; and &lt;a href="https://unconf17.ropensci.org/"&gt;annual unconference&lt;/a&gt; are all geared toward lowering barriers to reproducible, open science.&lt;/p&gt;
&lt;p&gt;The rOpenSci Fellowship presents a unique opportunity for researchers who are engaged in open source to have a bigger voice in their communities. These fellowships are designed to support individual researchers and collaborative efforts to help them do better science, build community around projects or best practices, or develop some tools as part of ongoing research that could impact one or more research domains. Two areas that are of particular interest to us are:&lt;/p&gt;</description></item><item><title>Launching webrockets at runconf17</title><link>https://ropensci.org/blog/2017/07/05/webrockets/</link><pubDate>Wed, 05 Jul 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/07/05/webrockets/</guid><description>
&lt;p&gt;We, &lt;a href="https://github.com/AliciaSchep/"&gt;Alicia Schep&lt;/a&gt; and &lt;a href="https://github.com/MilesMcBain"&gt;Miles
McBain&lt;/a&gt;, drove the &lt;code&gt;webrockets&lt;/code&gt; project
at &lt;a href="https://ropensci.org/blog/2017/06/02/unconf2017"&gt;#runconf17&lt;/a&gt;.
To make progress we solicited code, advice, and entertaining anecdotes
from a host of other attendees, whom we humbly thank for helping to make
our project possible.&lt;/p&gt;
&lt;p&gt;This post is divided into two sections: First up we&amp;rsquo;ll relate &lt;a href="#our-experiences"&gt;our
experiences&lt;/a&gt;, prompted by some questions we wrote for
one another. Second, we&amp;rsquo;ll put the &lt;a href="#cool-but-what-is-a-websocket"&gt;&lt;code&gt;webrockets&lt;/code&gt;
package&lt;/a&gt; into context and walk you
through a fun example where you can live plot streaming sensor data from
a mobile device.&lt;/p&gt;</description></item><item><title>Introducing our Postdoctoral Fellow, Dr. Dan Sholler</title><link>https://ropensci.org/blog/2017/06/30/postdoc_dan_sholler/</link><pubDate>Fri, 30 Jun 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/06/30/postdoc_dan_sholler/</guid><description>
&lt;p&gt;We are pleased to welcome our Postdoctoral Fellow, &lt;a href="https://danielsholler.wordpress.com/"&gt;Dr. Dan Sholler&lt;/a&gt;. Dan is an expert in qualitative research (yes, you read that correctly) and studies digital infrastructure creation, growth, and maintenance efforts. Through this research interest, he was drawn to the open science community and its ongoing development of tools and communities to support sustainable, reproducible, high-quality research. With rOpenSci, he intends to investigate &lt;em&gt;what drives scientists to engage with or resist open science tools and communities&lt;/em&gt;.&lt;/p&gt;</description></item><item><title>packagemetrics - Helping you choose a package since runconf17</title><link>https://ropensci.org/blog/2017/06/27/packagemetrics/</link><pubDate>Tue, 27 Jun 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/06/27/packagemetrics/</guid><description>
&lt;p&gt;Before everybody made their way to the unconf via &lt;a href="https://twitter.com/sckottie/status/867211430914736128"&gt;LAX&lt;/a&gt; and &lt;a href="https://twitter.com/sctyner/status/867505241234604033"&gt;Lyft&lt;/a&gt;, attendees &lt;a href="https://github.com/ropensci/unconf17/issues"&gt;discussed&lt;/a&gt; potential project ideas online. The &lt;strong&gt;packagemetrics&lt;/strong&gt; package was our answer to two related issues.&lt;/p&gt;
&lt;p&gt;The first &lt;a href="https://github.com/ropensci/unconf17/issues/69"&gt;proposal&lt;/a&gt; centered on creating and formatting tables in a reproducible workflow. After many different package suggestions started pouring in, we were left with a classic R user conundrum: &amp;ldquo;Which package do I choose?&amp;rdquo;&lt;/p&gt;
&lt;p&gt;With over 10,000 packages on CRAN - and thousands more on GitHub and Bioconductor - a useR needs a way to navigate this wealth of options. There are many existing tools to categorize and facilitate searching of R packages such as &lt;a href="https://cran.r-project.org/web/views/"&gt;CRAN TaskViews&lt;/a&gt;, &lt;a href="https://rseek.org/"&gt;RSeek&lt;/a&gt;, &lt;a href="https://www.rdocumentation.org/"&gt;Rdocumentation&lt;/a&gt;, &lt;a href="https://crantastic.org/"&gt;Crantastic!&lt;/a&gt;, &lt;a href="https://www.r-pkg.org/"&gt;METACRAN&lt;/a&gt; and &lt;a href="http://dirk.eddelbuettel.com/cranberries/"&gt;CRANberries&lt;/a&gt;. GitHub also provides lots of great metrics for individual packages developed there.&lt;/p&gt;</description></item><item><title>Hey! You there! You are welcome here</title><link>https://ropensci.org/blog/2017/06/23/community/</link><pubDate>Fri, 23 Jun 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/06/23/community/</guid><description>
&lt;p&gt;What&amp;rsquo;s that? You&amp;rsquo;ve heard of R? You use R? You develop in R? You know someone else who&amp;rsquo;s mentioned R? Oh, you&amp;rsquo;re breathing? Well, in that case, welcome! Come join the R community!&lt;/p&gt;
&lt;p&gt;We recently had a group discussion at &lt;a href="https://ropensci.org/"&gt;rOpenSci&lt;/a&gt;&amp;rsquo;s &lt;a href="https://twitter.com/search?q=%23runconf17&amp;amp;lang=en"&gt;#runconf17&lt;/a&gt; in Los Angeles, CA about the R community. I initially opened the &lt;a href="https://github.com/ropensci/unconf17/issues/63"&gt;issue on GitHub&lt;/a&gt;. After this issue was well-received (check out the emoji-love below!), we realized people were keen to talk about this and decided to have an optional and informal discussion in person.&lt;/p&gt;</description></item><item><title>All the fake data that's fit to print</title><link>https://ropensci.org/blog/2017/06/22/charlatan/</link><pubDate>Thu, 22 Jun 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/06/22/charlatan/</guid><description>
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;charlatan&lt;/strong&gt; makes fake data.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Excited to annonunce a new package called &lt;code&gt;charlatan&lt;/code&gt;. While perusing
packages from other programming languages, I saw a neat Python library
called &lt;code&gt;faker&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;&lt;code&gt;charlatan&lt;/code&gt; is inspired from and ports many things from Python&amp;rsquo;s
&lt;a href="https://github.com/joke2k/faker"&gt;https://github.com/joke2k/faker&lt;/a&gt; library. In turn, &lt;code&gt;faker&lt;/code&gt; was inspired from
&lt;a href="https://github.com/fzaninotto/Faker"&gt;PHP&amp;rsquo;s faker&lt;/a&gt;,
&lt;a href="https://search.cpan.org/~jasonk/Data-Faker-0.07/"&gt;Perl&amp;rsquo;s Faker&lt;/a&gt;, and
&lt;a href="https://rubygems.org/gems/faker"&gt;Ruby&amp;rsquo;s faker&lt;/a&gt;. It appears that the PHP
library was the original - nice work PHP.&lt;/p&gt;
&lt;h2&gt;
Use cases
&lt;/h2&gt;&lt;p&gt;What could you do with this package? Here&amp;rsquo;s some use cases:&lt;/p&gt;</description></item><item><title>Tackling the Research Compendium at runconf17</title><link>https://ropensci.org/blog/2017/06/20/checkers/</link><pubDate>Tue, 20 Jun 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/06/20/checkers/</guid><description>
&lt;p&gt;Two years ago at &lt;a href="https://twitter.com/hashtag/runconf15"&gt;#runconf15&lt;/a&gt;, there was a great discussion about best practices for organizing R-based analysis projects that yielded a &lt;a href="https://github.com/ropensci/rrrpkg"&gt;nice guidance document&lt;/a&gt; describing &lt;em&gt;research compendia&lt;/em&gt;. Compendia, as we described them, were minimal products of reproducible research, using parts of R package structure to organize the inputs, analyses, and outputs of research projects.&lt;/p&gt;
&lt;p&gt;Since then, we&amp;rsquo;ve seen more examples and models of research compendia emerge (the organization of such projects is &lt;a href="https://discuss.ropensci.org/t/resources-on-project-directory-organization/340"&gt;something of an obsession&lt;/a&gt; for some of the community). In parallel, there&amp;rsquo;s been much progress on a number of fronts with R &lt;em&gt;packages&lt;/em&gt;: rOpenSci&amp;rsquo;s &lt;a href="https://github.com/ropensci/software-review"&gt;package review process&lt;/a&gt; has expanded and we&amp;rsquo;ve worked out many kinks. Infrastructure for automated testing of package code has been developed and field tested. So at &lt;a href="unconf17.ropensci.org"&gt;#runconf17&lt;/a&gt;, we wanted to see how much of this progress in review, testing, and automation could apply to research compendia.&lt;/p&gt;</description></item><item><title>New rOpenSci Packages for Text Processing in R</title><link>https://ropensci.org/blog/2017/06/13/ropensci_text_tools/</link><pubDate>Tue, 13 Jun 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/06/13/ropensci_text_tools/</guid><description>
&lt;p&gt;Textual data and natural language processing are still a niche domain within the R ecosytstem. The &lt;a href="https://cran.r-project.org/view=NaturalLanguageProcessing"&gt;NLP task view&lt;/a&gt; gives an overview of existing work however a lot of basic infrastructure is still missing.
At the rOpenSci &lt;a href="https://ropensci.org/blog/2017/05/03/textworkshop17"&gt;text workshop&lt;/a&gt; in April we discussed many ideas for improving text processing in R which revealed several core areas that need improvement:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Reading: better tools for extracing text and metadata from documents in various formats (doc, rtf, pdf, etc).&lt;/li&gt;
&lt;li&gt;Encoding: many text packages work well for ascii text but rapidly break down when text contains Hungarian, Korean or emojis.&lt;/li&gt;
&lt;li&gt;Interchange: packages don&amp;rsquo;t work well together due to lack of data classes or conventions for textual data (see also &lt;a href="https://github.com/ropensci/tif"&gt;ropensci/tif&lt;/a&gt;)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Participants also had many good suggestions for C/C++ libraries that text researchers in R might benefit from. Over the past weeks I was able to look into these suggestions and work on a few packages for reading and analyzing text. Below is an update on new and improved rOpenSci tools for text processsing in R!&lt;/p&gt;</description></item><item><title>Unconf projects 5: mwparser, Gargle, arresteddev</title><link>https://ropensci.org/blog/2017/06/09/unconf_recap_5/</link><pubDate>Fri, 09 Jun 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/06/09/unconf_recap_5/</guid><description>
&lt;p&gt;And finally, we end our series of &lt;a href="https://ropensci.org/blog/2017/06/02/unconf2017"&gt;unconf&lt;/a&gt; project summaries (&lt;a href="https://ropensci.org/blog/2017/06/05/unconf_recap_1"&gt;day 1&lt;/a&gt;, &lt;a href="https://ropensci.org/blog/2017/06/06/unconf_recap_2"&gt;day 2&lt;/a&gt;, &lt;a href="https://ropensci.org/blog/2017/06/07/unconf_projects_3"&gt;day 3&lt;/a&gt;, &lt;a href="https://ropensci.org/blog/2017/06/08/unconf_recap_4"&gt;day 4&lt;/a&gt;).&lt;/p&gt;
&lt;h2&gt;
&lt;code&gt;mwparser&lt;/code&gt;
&lt;/h2&gt;&lt;p&gt;&lt;strong&gt;Summary:&lt;/strong&gt; Wikimarkup is the language used on Wikipedia and similar projects, and as such contains a lot of valuable data both for scientists studying collaborative systems and people studying things documented on or in Wikipedia. mwparser parses wikimarkup, allowing a user to filter down to specific types of tags such as links or templates, and then extract components of those tags.&lt;/p&gt;</description></item><item><title>Unconf projects 4: cityquant, notary, packagemetrics, pegax</title><link>https://ropensci.org/blog/2017/06/08/unconf_recap_4/</link><pubDate>Thu, 08 Jun 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/06/08/unconf_recap_4/</guid><description>
&lt;p&gt;Continuing our series of blog posts (&lt;a href="https://ropensci.org/blog/2017/06/05/unconf_recap_1"&gt;day 1&lt;/a&gt;, &lt;a href="https://ropensci.org/blog/2017/06/06/unconf_recap_2"&gt;day 2&lt;/a&gt;, &lt;a href="https://ropensci.org/blog/2017/06/07/unconf_projects_3"&gt;day 3&lt;/a&gt;) this week about &lt;a href="https://ropensci.org/blog/2017/06/02/unconf2017"&gt;unconf 17&lt;/a&gt;.&lt;/p&gt;
&lt;h2&gt;
&lt;code&gt;cityquant&lt;/code&gt;
&lt;/h2&gt;&lt;p&gt;&lt;strong&gt;Summary:&lt;/strong&gt; The goal with the &lt;code&gt;cityquant&lt;/code&gt; project was to build a digital dashboard for sustainable cities.&lt;/p&gt;
&lt;p&gt;&lt;img src="https://sustainsb.github.io/images/scores_flower-plot_sbcounty.png" alt="sustain"&gt;&lt;/p&gt;
&lt;p&gt;They also had a &amp;ldquo;spin-off&amp;rdquo; project called &lt;a href="https://github.com/maczokni/selfquant"&gt;selfquant&lt;/a&gt; to get data from a quantified self google sheets template to keep track of weekly performance in various categories.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Team:&lt;/strong&gt; &lt;a href="https://github.com/maczokni"&gt;Reka Solymosi&lt;/a&gt;, &lt;a href="https://github.com/bbest"&gt;Ben Best&lt;/a&gt;, &lt;a href="https://github.com/chursaner"&gt;Chelsea Ursaner&lt;/a&gt;, &lt;a href="https://github.com/timphan"&gt;Tim Phan&lt;/a&gt;, &lt;a href="https://github.com/jasdumas"&gt;Jasmine Dumas&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Github:&lt;/strong&gt; &lt;a href="https://github.com/ropenscilabs/cityquant"&gt;https://github.com/ropenscilabs/cityquant&lt;/a&gt;&lt;/p&gt;
&lt;p&gt; &lt;/p&gt;
&lt;h2&gt;
&lt;code&gt;notary&lt;/code&gt;
&lt;/h2&gt;&lt;p&gt;&lt;strong&gt;Summary:&lt;/strong&gt; &lt;code&gt;notary&lt;/code&gt; is actually two things:&lt;/p&gt;</description></item><item><title>Unconf projects 3: available, miner, rcheatsheet, ponyexpress</title><link>https://ropensci.org/blog/2017/06/07/unconf_projects_3/</link><pubDate>Wed, 07 Jun 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/06/07/unconf_projects_3/</guid><description>
&lt;p&gt;Continuing our series of blog posts (&lt;a href="https://ropensci.org/blog/2017/06/05/unconf_recap_1"&gt;day 1&lt;/a&gt;, &lt;a href="https://ropensci.org/blog/2017/06/06/unconf_recap_2"&gt;day 2&lt;/a&gt;) this week about &lt;a href="https://ropensci.org/blog/2017/06/02/unconf2017"&gt;unconf 17&lt;/a&gt;.&lt;/p&gt;
&lt;h2&gt;
&lt;code&gt;available&lt;/code&gt;
&lt;/h2&gt;&lt;p&gt;&lt;strong&gt;Summary:&lt;/strong&gt; Ever have trouble naming your software package? Find a great name and realize it&amp;rsquo;s already taken on CRAN, or further along in development on GitHub? The &lt;code&gt;available&lt;/code&gt; package makes it easy to check for valid, available names, and also checks various sources for any unintended meanings. The package can also suggest names based on the description and title of your package.&lt;/p&gt;</description></item><item><title>Unconf projects 2: checkers, gramr, data-packages, exploRingJSON</title><link>https://ropensci.org/blog/2017/06/06/unconf_recap_2/</link><pubDate>Tue, 06 Jun 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/06/06/unconf_recap_2/</guid><description>
&lt;p&gt;Following up on Stefanie&amp;rsquo;s recap of &lt;a href="https://ropensci.org/blog/2017/06/02/unconf2017"&gt;unconf 17&lt;/a&gt;, we are following up this entire week with summaries of projects developed at the event. We plan to highlight 4-5 projects each day, with detailed posts from a handful of teams to follow.&lt;/p&gt;
&lt;h2&gt;
&lt;code&gt;checkers&lt;/code&gt;
&lt;/h2&gt;&lt;p&gt;&lt;strong&gt;Summary:&lt;/strong&gt; &lt;code&gt;checkers&lt;/code&gt; is a framework for reviewing analysis projects. It provides automated checks for best practices, using extensions on the goodpractice package.&lt;/p&gt;
&lt;figure class="center"&gt;&lt;img src="https://ropensci.org/img/blog-images/2017-06-06-unconf_recap_2/checkers_version_control.png"
alt="caption" width="300"&gt;&lt;figcaption&gt;
&lt;p&gt;caption&lt;/p&gt;
&lt;/figcaption&gt;
&lt;/figure&gt;
&lt;p&gt;In addition, checkers includes a &lt;a href="https://docs.google.com/document/d/1OYcWJUk-MiM2C1TIHB1Rn6rXoF5fHwRX-7_C12Blx8g/edit#"&gt;descriptive guide for best practices&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Unconf projects 1: skimr, emldown, testrmd, webrockets</title><link>https://ropensci.org/blog/2017/06/05/unconf_recap_1/</link><pubDate>Mon, 05 Jun 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/06/05/unconf_recap_1/</guid><description>
&lt;p&gt;Following up on Stefanie&amp;rsquo;s recap of &lt;a href="https://ropensci.org/blog/2017/06/02/unconf2017"&gt;unconf 17&lt;/a&gt;, we are following up this entire week with summaries of projects developed at the event. We plan to highlight 4-5 projects each day, with detailed posts from a handful of teams to follow.&lt;/p&gt;
&lt;h2&gt;
&lt;code&gt;skimr&lt;/code&gt;
&lt;/h2&gt;&lt;p&gt;&lt;strong&gt;Summary:&lt;/strong&gt; &lt;code&gt;skimr&lt;/code&gt;, a package inspired by Hadley Wickham&amp;rsquo;s &lt;a href="https://github.com/hadley/precis"&gt;precis package&lt;/a&gt;, aims to provide summary statistics iteratively and interactively as part of a pipeline. The package provides easily skimmable summary statistics to help you better understand your data and see what is missing.&lt;/p&gt;</description></item><item><title>Bringing Together People and Projects at Unconf17</title><link>https://ropensci.org/blog/2017/06/02/unconf2017/</link><pubDate>Fri, 02 Jun 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/06/02/unconf2017/</guid><description>
&lt;p&gt;We held our &lt;a href="https://unconf17.ropensci.org/"&gt;4th annual unconference&lt;/a&gt; in Los Angeles, May 25-26, 2017. Scientists, R-software users and developers, and open data enthusiasts from academia, industry, government, and non-profits came together for two days to hack on projects they dreamed up and to give our online community an opportunity to connect in-person.&lt;/p&gt;
&lt;p&gt;The result? 70 people from 7 countries on 3 continents proposed 69 ideas leading to 21 projects in 2 days, and one awesome community just upped its game!&lt;/p&gt;</description></item><item><title>Easy linguistic mapping with lingtypology</title><link>https://ropensci.org/blog/2017/05/16/lingtypology/</link><pubDate>Tue, 16 May 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/05/16/lingtypology/</guid><description>
&lt;p&gt;As all other types of visualization, linguistic mapping has two main goals: data presentation and data analysis. The most common purpose for which linguistic maps are used, is simply pointing to the location of one or more languages of interest (presentation). A more sophisticated task is showing the distribution of particular linguistic features or their combination among languages of a certain area (presentation and analysis). There are three linguistic subdisciplines that use maps for visualization: linguistic typology, areal linguistics and dialectology. &lt;code&gt;lingtypology&lt;/code&gt; makes it easier to create all kinds of linguistic maps simplifying both: data presentation and data analysis.&lt;/p&gt;</description></item><item><title>Text Analysis R Developers' Workshop 2017</title><link>https://ropensci.org/blog/2017/05/03/textworkshop17/</link><pubDate>Wed, 03 May 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/05/03/textworkshop17/</guid><description>
&lt;p&gt;On 21-22 April, the London School of Economics hosted the &lt;a href="https://textworkshop17.ropensci.org"&gt;&lt;em&gt;Text Analysis Package Developers&amp;rsquo; Workshop&lt;/em&gt;&lt;/a&gt;, a two-day event held in London that brought together developers of R packages for working with text and text-related data. This included a wide range of applications, including string handling (&lt;a href="https://github.com/gagolews/stringi"&gt;&lt;code&gt;stringi&lt;/code&gt;&lt;/a&gt;) and tokenization (the rOpenSci-onboarded &lt;a href="https://github.com/ropensci/tokenizers"&gt;&lt;code&gt;tokenizers&lt;/code&gt;&lt;/a&gt;, &lt;a href="https://github.com/haven-jeon/KoNLP"&gt;&lt;code&gt;KoNLP&lt;/code&gt;&lt;/a&gt;), corpus and text processing (&lt;a href="https://github.com/kbenoit/readtext"&gt;&lt;code&gt;readtext&lt;/code&gt;&lt;/a&gt;, &lt;a href="http://tm.r-forge.r-project.org"&gt;&lt;code&gt;tm&lt;/code&gt;&lt;/a&gt;, &lt;a href="https://quanteda.io"&gt;&lt;code&gt;quanteda&lt;/code&gt;&lt;/a&gt;, and &lt;a href="https://github.com/trinker/qdap"&gt;&lt;code&gt;qdap&lt;/code&gt;&lt;/a&gt;), natural language processing (NLP) such as part of speech and dependency tagging (&lt;a href="https://github.com/statsmaths/cleanNLP"&gt;&lt;code&gt;cleanNLP&lt;/code&gt;&lt;/a&gt;, &lt;a href="https://github.com/kbenoit/spacyr"&gt;&lt;code&gt;spacyr&lt;/code&gt;&lt;/a&gt;), and the statistical analysis of textual data (&lt;a href="https://www.structuraltopicmodel.com"&gt;&lt;code&gt;stm&lt;/code&gt;&lt;/a&gt;, &lt;a href="https://github.com/dselivanov/text2vec"&gt;&lt;code&gt;text2vec&lt;/code&gt;&lt;/a&gt;, and &lt;a href="https://reaktanz.de/?c=hacking&amp;amp;s=koRpus"&gt;&lt;code&gt;koRpus&lt;/code&gt;&lt;/a&gt;) &amp;ndash; although this list is hardly complete. The main objective was to bring together experts working on various aspects of text processing and text analysis using R, to discuss common challenges and identify collaborative solutions.&lt;/p&gt;</description></item><item><title>Chat with the rOpenSci team at upcoming meetings</title><link>https://ropensci.org/blog/2017/05/01/ropensci-at-meetings/</link><pubDate>Mon, 01 May 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/05/01/ropensci-at-meetings/</guid><description>
&lt;p&gt;You can find members of the rOpenSci team at various meetings and workshops around the world. Come say &amp;lsquo;hi&amp;rsquo;, learn about how our &lt;a href="https://ropensci.org/packages/"&gt;packages&lt;/a&gt; can enable your research, or about our &lt;a href="https://github.com/ropensci/software-review"&gt;onboarding&lt;/a&gt; process for contributing new packages, discuss software &lt;a href="https://ropensci.org/blog/2016/05/25/software-sustanability-ropensci"&gt;sustainability&lt;/a&gt; or tell us how we can help you do open and reproducible research.&lt;/p&gt;</description></item><item><title>Welcome to our rOpenSci Interns</title><link>https://ropensci.org/blog/2017/04/27/ropensci-interns/</link><pubDate>Thu, 27 Apr 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/04/27/ropensci-interns/</guid><description>
&lt;p&gt;There&amp;rsquo;s a lot of work that goes in to making software: the code that does the thing itself, unit testing, examples, tutorials, documentation, and support. rOpenSci software is created and maintained both by our &lt;a href="https://ropensci.org/about/#staff"&gt;staff&lt;/a&gt; and by our (awesome) community. In keeping with our aim to build capacity of software users and developers, three interns from our academic home at &lt;a href="https://bids.berkeley.edu/research"&gt;UC Berkeley&lt;/a&gt; are now working with us as well. Our interns are mentored by &lt;a href="https://ropensci.org/about/#team"&gt;Carl Boettiger&lt;/a&gt;, &lt;a href="https://ropensci.org/about/#team"&gt;Scott Chamberlain&lt;/a&gt;, and &lt;a href="https://ropensci.org/about/#team"&gt;Karthik Ram&lt;/a&gt; and they will receive academic credit and/or pay for their work.&lt;/p&gt;</description></item><item><title>Random GeoJSON and WKT with randgeo</title><link>https://ropensci.org/blog/2017/04/20/randgeo/</link><pubDate>Thu, 20 Apr 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/04/20/randgeo/</guid><description>
&lt;p&gt;&lt;strong&gt;randgeo&lt;/strong&gt; generates random points and shapes in GeoJSON and WKT formats for
use in examples, teaching, or statistical applications.&lt;/p&gt;
&lt;p&gt;Points and shapes are generated in the long/lat coordinate system and with
appropriate spherical geometry; random points are distributed evenly across
the globe, and random shapes are sized according to a maximum great-circle
distance from the center of the shape.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;randgeo&lt;/strong&gt; was adapted from &lt;a href="https://github.com/tmcw/geojson-random"&gt;https://github.com/tmcw/geojson-random&lt;/a&gt; to have
a pure R implementation without any dependencies as well as appropriate
geometry. Data generated by &lt;strong&gt;randgeo&lt;/strong&gt; may be processed or displayed of with
packages such as &lt;a href="https://cran.r-project.org/package=sf"&gt;&lt;strong&gt;sf&lt;/strong&gt;&lt;/a&gt;,
&lt;a href="https://cran.r-project.org/package=wicket"&gt;&lt;strong&gt;wicket&lt;/strong&gt;&lt;/a&gt;,
&lt;a href="https://cran.r-project.org/package=geojson"&gt;&lt;strong&gt;geojson&lt;/strong&gt;&lt;/a&gt;,
&lt;a href="https://cran.r-project.org/package=wellknown"&gt;&lt;strong&gt;wellknown&lt;/strong&gt;&lt;/a&gt;,
&lt;a href="https://cran.r-project.org/package=geojsonio"&gt;&lt;strong&gt;geojsonio&lt;/strong&gt;&lt;/a&gt;, or
&lt;a href="https://cran.r-project.org/package=lawn"&gt;&lt;strong&gt;lawn&lt;/strong&gt;&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Release 'open' data from their PDF prisons using tabulizer</title><link>https://ropensci.org/blog/2017/04/18/tabulizer/</link><pubDate>Tue, 18 Apr 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/04/18/tabulizer/</guid><description>
&lt;p&gt;There is no problem in science quite as frustrating as &lt;em&gt;other peoples&amp;rsquo; data&lt;/em&gt;. Whether it&amp;rsquo;s malformed spreadsheets, disorganized documents, proprietary file formats, data without metadata, or any other data scenario created by someone else, &lt;a href="https://twitter.com/hashtag/otherpeoplesdata?src=hash"&gt;scientists have taken to Twitter to complain about it&lt;/a&gt;. As a political scientist who regularly encounters so-called &amp;ldquo;open data&amp;rdquo; in PDFs, this problem is particularly irritating. PDFs may have &amp;ldquo;portable&amp;rdquo; in their name, making them display consistently on various platforms, but that portability means any information contained in a PDF is irritatingly difficult to extract computationally.&lt;/p&gt;</description></item><item><title>Data validation with the assertr package</title><link>https://ropensci.org/blog/2017/04/11/assertr/</link><pubDate>Tue, 11 Apr 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/04/11/assertr/</guid><description>
&lt;p&gt;Version 2.0 of my data set validation package &lt;code&gt;assertr&lt;/code&gt; hit CRAN just this weekend. It has some pretty great improvements over version 1. For those new to the package, what follows is a short and new introduction. For those who are already using &lt;code&gt;assertr&lt;/code&gt;, the text below will point out the improvements.&lt;/p&gt;
&lt;p&gt;I can (and have) go on and on about the treachery of messy/bad datasets. Though its substantially less exciting than… pretty much everything else, I believe (proportional to the heartache and stress it causes) we don’t spend enough time talking about it or building solutions around it. No matter how new and fancy your ML algorithm is, it’s success is predicated upon a properly sanitized dataset. If you are using bad data, your approach will fail—either flagrantly (best case), or unnoticeably (considerably more probable and considerably more pernicious).&lt;/p&gt;</description></item><item><title>Everybody talks about the weather</title><link>https://ropensci.org/blog/2017/04/04/gsodr/</link><pubDate>Tue, 04 Apr 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/04/04/gsodr/</guid><description>
&lt;blockquote&gt;
&lt;p&gt;Everybody talks about the weather, but nobody does anything about it. - Charles Dudley Warner&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;As a scientist who models &lt;a href="https://github.com/adamhsparks/STRASA-Biotic-Stress-Maps"&gt;plant diseases&lt;/a&gt;, I use a lot of weather data. Often this data is not available for areas of interest. Previously, I worked with the &lt;a href="https://www.irri.org/"&gt;International Rice Research Institute (IRRI)&lt;/a&gt; and often the countries I was working with did not have weather data available or I was working on a large area covering several countries and needed a single source of data to work from. Other scientists who work with crop biophysical models to model crop yields also have similar weather data needs and may experience similar issues with data availability.&lt;/p&gt;</description></item><item><title>camsRad, satellite-based time series of solar irradiation</title><link>https://ropensci.org/blog/2017/03/21/camsrad/</link><pubDate>Tue, 21 Mar 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/03/21/camsrad/</guid><description>
&lt;p&gt;&lt;a href="https://github.com/ropenscilabs/camsRad"&gt;&lt;code&gt;camsRad&lt;/code&gt;&lt;/a&gt; is a lightweight R client for the &lt;a href="http://www.soda-pro.com/web-services/radiation/cams-radiation-service"&gt;CAMS Radiation Service&lt;/a&gt;, that provides satellite-based time series of solar irradiation for the actual weather conditions as well as for clear-sky conditions. Satellite-based solar irradiation data have been around roughly as long our modern era satellites. But the price tag has been very high, in the range of several thousand euros per site. This has damped research and development of downstream applications. With CAMS Radiation Service coming online in 2016, this changed as the services are provided under the (not yet fully implemented) European Union stand point that data and services produced with public funding shall be provided on free and open grounds. The service is part of &lt;a href="https://www.copernicus.eu"&gt;Copernicus&lt;/a&gt;, a European Union programme aimed at developing information services based on satellite earth observation and in situ data. All Copernicus information services are free and openly accessible.&lt;/p&gt;</description></item><item><title>Release mongolite 1.0</title><link>https://ropensci.org/blog/2017/03/10/mongolite/</link><pubDate>Fri, 10 Mar 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/03/10/mongolite/</guid><description>
&lt;p&gt;After 2.5 years of development, version 1.0 of the &lt;a href="https://cran.r-project.org/web/packages/mongolite/index.html"&gt;mongolite&lt;/a&gt; package has been released to CRAN. The package is now stable, well documented, and will soon be submitted for peer review to be onboarded in the rOpenSci suite.&lt;/p&gt;
&lt;h2&gt;
MongoDB in R and mongolite
&lt;/h2&gt;&lt;p&gt;I started working on mongolite in September 2014, and it was first announced at the rOpenSci unconf 2015. At this time, there were already two Mongo clients on CRAN: &lt;a href="https://cran.r-project.org/web/packages/rmongodb/index.html"&gt;rmongodb&lt;/a&gt; (no longer works) and &lt;a href="https://cran.r-project.org/web/packages/RMongo/index.html"&gt;RMongo&lt;/a&gt; (depends on Java). However I found both of them pretty clunky, and the MongoDB folks had just released 1.0 of their new C driver, so I decided to write a new client from scratch.&lt;/p&gt;</description></item><item><title>Discover hydrological data using the hddtools R package</title><link>https://ropensci.org/blog/2017/03/07/hddtools/</link><pubDate>Tue, 07 Mar 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/03/07/hddtools/</guid><description>
&lt;p&gt;I&amp;rsquo;ve worked for over 12 years in hydrology and natural hazard modelling and one of the things that still fascinates me is the variety of factors that come into play in trying to predict phenomena such as river floods. From local observations of meteorological and hydrological variables and their spatio-temporal patterns to the type and condition of soils and vegetation/land use as well as the geometry and state of river channels and engineering structures affecting the flow.&lt;/p&gt;</description></item><item><title>How to Ask Questions so they get Answered! Possibly by Yourself!</title><link>https://ropensci.org/commcalls/2017-03-07/</link><pubDate>Tue, 07 Mar 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/commcalls/2017-03-07/</guid><description/></item><item><title>ccafs - client for CCAFS General Circulation Models data</title><link>https://ropensci.org/blog/2017/03/01/ccafs-release/</link><pubDate>Wed, 01 Mar 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/03/01/ccafs-release/</guid><description>
&lt;p&gt;I&amp;rsquo;ve recently released the new package &lt;a href="https://github.com/ropensci/ccafs"&gt;ccafs&lt;/a&gt;, which provides access
to data from Climate Change, Agriculture and Food Security
(CCAFS; &lt;a href="http://ccafs-climate.org/"&gt;http://ccafs-climate.org/&lt;/a&gt;) General Circulation Models (GCM) data.
GCM&amp;rsquo;s are a particular type of climate model, used for weather forecasting,
and climate change forecasting - read more at
&lt;a href="https://en.wikipedia.org/wiki/General_circulation_model"&gt;https://en.wikipedia.org/wiki/General_circulation_model&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;code&gt;ccafs&lt;/code&gt; falls in the data client camp - its focus is on getting users
data - many &lt;a href="https://ropensci.org/packages/#data_access"&gt;rOpenSci packages&lt;/a&gt;
fall into this area. These kinds of packages are important so that
scientists don&amp;rsquo;t have to recreate the wheel themselves every time, but
instead use one client that everyone else uses.&lt;/p&gt;</description></item><item><title>ropenaq, a breath of fresh air/R</title><link>https://ropensci.org/blog/2017/02/21/ropenaq/</link><pubDate>Tue, 21 Feb 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/02/21/ropenaq/</guid><description>
&lt;p&gt;Do you fancy open data, R, and breathing? Then you might be interested in &lt;code&gt;ropenaq&lt;/code&gt; which provides access to open air quality data via OpenAQ! Also note that in French, R and air are homophones, therefore we French speakers can make puns like the one in the title. Please re-read it with a French accent and don&amp;rsquo;t judge me.&lt;/p&gt;
&lt;p&gt;In this post I&amp;rsquo;ll motivate the existence of the package, then show you the basics of its use, and finally show off with some pretty figures. You can skip any part but if I were you I wouldn&amp;rsquo;t!&lt;/p&gt;</description></item><item><title>Community Call v13 - How to ask questions so they get answered! Possibly by yourself!</title><link>https://ropensci.org/blog/2017/02/17/comm-call-v13/</link><pubDate>Fri, 17 Feb 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/02/17/comm-call-v13/</guid><description>
&lt;p&gt;Our &lt;a href="https://ropensci.org/commcalls/2017-03-07/"&gt;Community Call on Tuesday, March 7th, 8-9 AM PST&lt;/a&gt;, will cover &amp;ldquo;How to ask questions so they get answered! Possibly by yourself!&amp;rdquo;. Asking questions about programming is a skill you can develop - we&amp;rsquo;re not just born with it. The speakers will cover some of the background and skills you&amp;rsquo;ll need to increase your chances of having your questions answered by your peers or by a busy expert.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;a href="https://ropensci.org/commcalls/2017-03-07/"&gt;Join the Call&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;</description></item><item><title>From a million nested `ifelse`s to the plater package</title><link>https://ropensci.org/blog/2017/02/06/plater-blog-post/</link><pubDate>Mon, 06 Feb 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/02/06/plater-blog-post/</guid><description>
&lt;p&gt;As a lab scientist, I do almost all of my experiments in &lt;a href="https://en.wikipedia.org/wiki/Microtiter_plate"&gt;microtiter plates&lt;/a&gt;. These tools are an efficient means of organizing many parallel experimental conditions. It&amp;rsquo;s not always easy, however, to translate between the physical plate and a useful data structure for analysis. My first attempts to solve this problem&amp;ndash;nesting one &lt;code&gt;ifelse&lt;/code&gt; call inside of the next to describe which well was which&amp;ndash;were very unsatisfying. Over time, my attempts at solving the problem grew more sophisticated, and eventually, the &lt;code&gt;plater&lt;/code&gt; package was born. Here I will tell the story of how with the help of &lt;a href="http://r-pkgs.had.co.nz/"&gt;R Packages&lt;/a&gt; and the amazing reviewers (&lt;a href="https://www.juliagustavsen.com/"&gt;Julia Gustavsen&lt;/a&gt; and &lt;a href="https://deanattali.com/"&gt;Dean Attali&lt;/a&gt;) and &lt;a href="https://scottchamberlain.info/"&gt;editors&lt;/a&gt; at rOpenSci, I ended up with a package that makes it easy to work with plate-based data.&lt;/p&gt;</description></item><item><title>Apply to attend rOpenSci unconf 2017!</title><link>https://ropensci.org/blog/2017/02/02/unconf2017/</link><pubDate>Thu, 02 Feb 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/02/02/unconf2017/</guid><description>
&lt;p&gt;For a fourth year running, we are excited to announce the &lt;a href="https://unconf17.ropensci.org/"&gt;rOpenSci unconference&lt;/a&gt;, our annual event loosely modeled on &lt;a href="https://en.wikipedia.org/wiki/Foo_Camp"&gt;Foo Camp&lt;/a&gt;. We&amp;rsquo;re organizing &lt;a href="https://twitter.com/search?f=tweets&amp;amp;q=%23runconf17"&gt;#runconf17&lt;/a&gt; to bring together scientists, developers, and open data enthusiasts from academia, industry, government, and non-profits to get together for a couple of days to hack on various projects and generally enrich our community. The agenda is mostly decided during the unconference itself. &lt;a href="https://github.com/ropensci/unconf16"&gt;Past projects&lt;/a&gt; have related to open data, data visualization, data publication and open science using R. This event is unlike many other unconferences in that it is primarily invite-only, with a few spots set aside for self-nominations from the community at large. That&amp;rsquo;s you!&lt;/p&gt;</description></item><item><title>Extracting and Enriching Ocean Biogeographic Information System (OBIS) Data with R</title><link>https://ropensci.org/blog/2017/01/25/obis/</link><pubDate>Wed, 25 Jan 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/01/25/obis/</guid><description>
&lt;p&gt;Programmatic access to biodiversity data is revolutionising large-scale, reproducible biodiversity research. In the marine realm, the largest global database of species occurrence records is the Ocean Biogeographic Information System, &lt;a href="http://www.iobis.org/"&gt;OBIS&lt;/a&gt;. As of January 2017, OBIS contains 47.78 million occurrences of 117,345 species, all openly available and accessible via the &lt;a href="http://www.iobis.org/manual/api/"&gt;OBIS API&lt;/a&gt;. The number of questions to address using these kinds of resources is as large as the number of investigators, but certain operations commonly crop up in many workflows. In my group, &lt;a href="https://shefmeme.org/"&gt;shefmeme.org&lt;/a&gt;, these typically involve checking the taxonomy of a list of species, extracting occurrence records for each species, mapping these and matching them to various environmental and geographic data layers, all using R. I recently wrote up these common operations in a &lt;a href="http://www.iobis.org/2016/11/22/sorbycollection/"&gt;detailed tutorial for OBIS&lt;/a&gt;, with &lt;a href="https://github.com/iobis/training/tree/master/sorbycollection"&gt;associated code and data on GitHub&lt;/a&gt;. This tutorial made extensive use of &lt;a href="https://ropensci.org/"&gt;rOpenSci&lt;/a&gt; packages and expertise, and so I’m delighted to have the opportunity to present an edited version here. (Please note that the code chunks included here are a subset of our original code, and are for illustration - if you want to run these examples we suggest visiting the original post.)&lt;/p&gt;</description></item><item><title>Using xml schema and xslt in R</title><link>https://ropensci.org/blog/2017/01/10/xslt-release/</link><pubDate>Tue, 10 Jan 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/01/10/xslt-release/</guid><description>
&lt;p&gt;This week an update for &lt;a href="https://cran.r-project.org/web/packages/xml2/index.html"&gt;xml2&lt;/a&gt; and a new &lt;a href="https://cran.r-project.org/web/packages/xslt/index.html"&gt;xslt&lt;/a&gt; package have appeared on CRAN. A full announcement for xml2 version 1.1 will appear on the &lt;a href="https://blog.rstudio.org/"&gt;rstudio blog&lt;/a&gt;. This post explains xml &lt;em&gt;validation&lt;/em&gt; (via xsd schema) and xml &lt;em&gt;transformation&lt;/em&gt; (via xslt stylesheets) which have been added in this release.&lt;/p&gt;
&lt;p&gt;XML schemas and stylesheets are not exactly new; both &lt;a href="https://www.w3.org/TR/xslt11/"&gt;xslt 1.1&lt;/a&gt; (2001) and &lt;a href="https://www.w3.org/TR/xmlschema-1/"&gt;xsd 1.0&lt;/a&gt; (2004) have been available in browsers for over a decade. Revised specifications for xsd/xslt are still developed, but not widely implemented due to declined popularity of xml itself. Our R implementation builds on &lt;a href="http://xmlsoft.org/libxslt/"&gt;libxslt&lt;/a&gt; which supports XSLT 1.0 features plus most of the EXSLT set of processor-portable extensions functions.&lt;/p&gt;</description></item><item><title>A guide to sustainability models for research software projects</title><link>https://ropensci.org/blog/2017/01/09/sustaining-research-projects/</link><pubDate>Mon, 09 Jan 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/01/09/sustaining-research-projects/</guid><description>
&lt;p&gt;A research project often starts with a bright idea and an initial commitment of volunteer time, or perhaps,
a fixed term grant. But what happens after that initial activity? How can the project continue to
sustain itself? (We define sustainability as the capacity to endure. Software is sustainable if it
will continue to be available in the future, on new platforms, and meeting new needs.
[This is from slide 23 of http://www.slideshare.net/danielskatz/scientific-software-challenges-and-community-responses,
though it may have been taken from somewhere else earlier - if you know where, let me know.])&lt;/p&gt;</description></item><item><title>Package evolution - changing stuff in your package</title><link>https://ropensci.org/blog/2017/01/05/package-evolution/</link><pubDate>Thu, 05 Jan 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/01/05/package-evolution/</guid><description>
&lt;p&gt;Making packages is a great way to organize R code, whether it’s a set of scripts for personal use, a set of functions for internal company use or a lab group, or to distribute your new cool framework &lt;code&gt;foobar&lt;/code&gt; to the masses. There&amp;rsquo;s a number of guides to writing packages, including &lt;a href="http://r-pkgs.had.co.nz/"&gt;http://r-pkgs.had.co.nz/&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;As you develop packages there&amp;rsquo;s a number of issues that don&amp;rsquo;t often get much air time. I&amp;rsquo;ll cover some of them here.&lt;/p&gt;</description></item><item><title>Update jsonlite 1.2</title><link>https://ropensci.org/blog/2017/01/04/jsonlite-12/</link><pubDate>Wed, 04 Jan 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/01/04/jsonlite-12/</guid><description>
&lt;p&gt;A new version of &lt;a href="https://cran.r-project.org/web/packages/jsonlite/index.html"&gt;jsonlite&lt;/a&gt; package to CRAN. This is a maintenance release with enhancements and bug fixes. A summary of changes in v1.2 from the &lt;a href="https://cran.r-project.org/web/packages/jsonlite/NEWS"&gt;NEWS&lt;/a&gt; file:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Add &lt;code&gt;read_json&lt;/code&gt; and &lt;code&gt;write_json&lt;/code&gt; convenience wrappers, &lt;a href="https://github.com/jeroen/jsonlite/issues/161"&gt;#161&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Update &lt;code&gt;modp_numtoa&lt;/code&gt; from upstream, fixes a rounding issue in &lt;a href="https://github.com/jeroen/jsonlite/issues/148"&gt;#148&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Ensure &lt;code&gt;asJSON.POSIXt&lt;/code&gt; does not use sci notation for negative values, &lt;a href="https://github.com/jeroen/jsonlite/issues/155"&gt;#155&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Tweak &lt;code&gt;num_to_char&lt;/code&gt; to properly print large negative numbers&lt;/li&gt;
&lt;li&gt;Performance optimization for simplyfing data frames (see below)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Use the &lt;em&gt;Github compare&lt;/em&gt; page to see the full diff on &lt;a href="https://github.com/cran/jsonlite/compare/1.1...1.2"&gt;metacran&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Our Community Manager Selected for AAAS Community Engagement Fellowship Program</title><link>https://ropensci.org/blog/2017/01/03/aaas-cefp/</link><pubDate>Tue, 03 Jan 2017 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2017/01/03/aaas-cefp/</guid><description>
&lt;p&gt;Next week I&amp;rsquo;ll be in Washington DC to meet my peers in research community management as part of the inaugural class of the AAAS &lt;a href="https://www.cscce.org/cefp/"&gt;Community Engagement Fellowship Program&lt;/a&gt;!&lt;/p&gt;
&lt;p&gt;The program, funded by the &lt;a href="https://sloan.org/"&gt;Alfred P. Sloan Foundation&lt;/a&gt;, has a mission to improve community building and collaboration in scientific organizations and research collaborations by providing a year of training and support to a cohort of scientific community managers. The Fellowship will begin in January 2017 when we 17 Fellows gather for a week-long training course with leaders in the field at AAAS headquarters. Over the next year we&amp;rsquo;ll attend monthly webinars, report on our challenges and successes, and attend mid-year and end-of-year meetings.&lt;/p&gt;</description></item><item><title>finch - parse Darwin Core files</title><link>https://ropensci.org/blog/2016/12/23/finch-release/</link><pubDate>Fri, 23 Dec 2016 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2016/12/23/finch-release/</guid><description>
&lt;p&gt;&lt;code&gt;finch&lt;/code&gt; has just been released to CRAN (binaries should be up soon).&lt;/p&gt;
&lt;p&gt;&lt;code&gt;finch&lt;/code&gt; is a package to parse Darwin Core files. &lt;a href="http://rs.tdwg.org/dwc/"&gt;Darwin Core&lt;/a&gt; (&lt;code&gt;DwC&lt;/code&gt;) is:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;a body of standards. It includes a glossary of terms (in other contexts these might be called properties, elements, fields, columns, attributes, or concepts) intended to facilitate the sharing of information about biological diversity by providing reference definitions, examples, and commentaries. The Darwin Core is primarily based on taxa, their occurrence in nature as documented by observations, specimens, samples, and related information. &amp;hellip; The Simple Darwin Core [SIMPLEDWC] is a specification for one particular way to use the terms - to share data about taxa and their occurrences in a simply structured way - and is probably what is meant if someone suggests to &amp;ldquo;format your data according to the Darwin Core&amp;rdquo;.&lt;/p&gt;</description></item><item><title>Highlights and Resources from Community Call v12: How do I create a code of conduct for my event/lab/codebase?</title><link>https://ropensci.org/blog/2016/12/21/commcallv12-review-coc/</link><pubDate>Wed, 21 Dec 2016 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2016/12/21/commcallv12-review-coc/</guid><description>
&lt;p&gt;Our &lt;a href="https://ropensci.org/blog/2016/10/31/comm-call-v12"&gt;Community Call&lt;/a&gt; on December 15th covered a big topic in tech communities: &amp;ldquo;How do I create a code of conduct for my event/lab/codebase?&amp;rdquo;. Here, we cover some of the key themes and considerations that arose from the discussion and point to curated resources and examples to follow when developing a code of conduct (CoC) for your community.&lt;/p&gt;
&lt;p&gt;Three guest speakers shared different perspectives. Dr Pauline Barmby talked about the process and lessons learned as &lt;a href="https://www.datacarpentry.org/"&gt;Data Carpentry&lt;/a&gt; and &lt;a href="https://software-carpentry.org/"&gt;Software Carpentry&lt;/a&gt; recently updated their CoC; Ms Safia Abdalla talked about &amp;ldquo;Codes of conduct for open source: the stuff no one tells you&amp;rdquo;; and Dr Titus Brown talked about his lab CoC. You can &lt;a href="#speaker-bios"&gt;read their bios&lt;/a&gt; below and watch the &lt;a href="https://vimeo.com/196503807"&gt;video&lt;/a&gt; of the call. Speakers did not use other presentation materials.&lt;/p&gt;</description></item><item><title>How do I Create a Code of Conduct for my Event/Lab/Codebase?</title><link>https://ropensci.org/commcalls/2016-12-15/</link><pubDate>Thu, 15 Dec 2016 00:00:00 +0000</pubDate><guid>https://ropensci.org/commcalls/2016-12-15/</guid><description/></item><item><title>Announcing our first fellowship awarded to Dr. Nick Golding</title><link>https://ropensci.org/blog/2016/12/12/ropensci-fellowship-zoon/</link><pubDate>Mon, 12 Dec 2016 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2016/12/12/ropensci-fellowship-zoon/</guid><description>
&lt;p&gt;rOpenSci&amp;rsquo;s overarching mission is to promote a culture of transparent, open, and reproducible research across various scientific communities. All of our activities are geared towards lowering barriers to participation, and building a community of practitioners around the world. In addition to developing and maintaining a large suite of open source tools for data science, we actively support the research community with expert review on research software development, community calls, and hosting annual unconferences around the world.&lt;/p&gt;</description></item><item><title>Announcing pdftools 1.0</title><link>https://ropensci.org/blog/2016/12/09/pdftools-10/</link><pubDate>Fri, 09 Dec 2016 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2016/12/09/pdftools-10/</guid><description>
&lt;p&gt;This week we released version &lt;code&gt;1.0&lt;/code&gt; of the ropensci &lt;a href="https://cran.r-project.org/web/packages/pdftools/index.html"&gt;pdftools&lt;/a&gt; package to CRAN. Pdftools provides utilities for extracting text, fonts, attachments and other data from PDF files. It also supports rendering of PDF files into bitmap images.&lt;/p&gt;
&lt;p&gt;This release has a few internal enhancements and fixes an annoying bug for landscape PDF pages. The version bump to &lt;code&gt;1.0&lt;/code&gt; signifies that the package has undergone sufficient testing and the API is stable.&lt;/p&gt;</description></item><item><title>Tesseract Update: Options and Languages</title><link>https://ropensci.org/blog/2016/12/08/tesseract-13/</link><pubDate>Thu, 08 Dec 2016 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2016/12/08/tesseract-13/</guid><description>
&lt;p&gt;A few weeks ago we &lt;a href="https://ropensci.org/blog/2016/11/16/tesseract"&gt;announced&lt;/a&gt; the first release of the &lt;a href="https://cran.r-project.org/web/packages/tesseract/index.html"&gt;tesseract&lt;/a&gt; package: a high quality OCR engine in R. We have now released an update with extra features.&lt;/p&gt;
&lt;h2&gt;
Installing Training Data
&lt;/h2&gt;&lt;p&gt;As explained in the &lt;a href="https://ropensci.org/blog/2016/11/16/tesseract"&gt;first post&lt;/a&gt;, the tesseract system is powered by language specific training data. By default only English training data is installed. &lt;a href="https://cran.r-project.org/web/packages/tesseract/index.html"&gt;Version 1.3&lt;/a&gt; adds utilities to make it easier to install additional training data.&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-r" data-lang="r"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;# Download French training data&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nf"&gt;tesseract_download&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s"&gt;&amp;#34;fra&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Note that this function is not needed on Linux. Here you should install training data via your system package manager instead. For example on Debian/Ubuntu:&lt;/p&gt;</description></item><item><title>High Performance CommonMark and Github Markdown Rendering in R</title><link>https://ropensci.org/blog/2016/12/02/commonmark/</link><pubDate>Fri, 02 Dec 2016 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2016/12/02/commonmark/</guid><description>
&lt;p&gt;This week the folks at Github have open sourced their &lt;a href="https://github.com/github/cmark"&gt;fork&lt;/a&gt; of libcmark (based on the extensive &lt;a href="https://github.com/jgm/cmark/pull/123"&gt;PR by Mathieu Duponchelle&lt;/a&gt;), which they use to render markdown text within documents, issues, comments and anything else on the Github website. The new release of the &lt;a href="https://cran.r-project.org/web/packages/commonmark/index.html"&gt;commonmark&lt;/a&gt; R package incorporates this library so that we can take advantage of Github quality markdown rendering in R.&lt;/p&gt;
&lt;p&gt;The most exciting change is that the library has gained an extension mechanism to provide optional rendering features which are missing from the commonmark spec. Most notably, Github has added extentions for rendering GFM style tables and autolinks, both very useful features for R users.&lt;/p&gt;</description></item><item><title>The rOpenSci geospatial suite</title><link>https://ropensci.org/blog/2016/11/22/geospatial-suite/</link><pubDate>Tue, 22 Nov 2016 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2016/11/22/geospatial-suite/</guid><description>
&lt;p&gt;Geospatial data - data embedded in a spatial context - is used across disciplines, whether it be history, biology, business, tech, public health, etc. Along with community contributors, we&amp;rsquo;re working on a suite of tools to make working with spatial data in R as easy as possible.&lt;/p&gt;
&lt;p&gt;If you&amp;rsquo;re not familiar with geospatial tools, it&amp;rsquo;s helpful to see what people do with them in the real world.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Example 1&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;One of our geospatial packages, &lt;a href="https://github.com/ropensci/geonames"&gt;geonames&lt;/a&gt;, is used for geocoding, the practice of either sorting out place names from geographic data, or vice versa. &lt;code&gt;geonames&lt;/code&gt; interfaces with the open database of the same name: &lt;a href="https://www.geonames.org/"&gt;https://www.geonames.org/&lt;/a&gt;. A recent paper in PlosONE highlights a common use case. Harsch &amp;amp; HilleRisLambers&lt;sup id="fnref:1"&gt;&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref"&gt;1&lt;/a&gt;&lt;/sup&gt; asked how plant species distributions have shifted due to climate warming. They used the &lt;code&gt;GNsrtm3()&lt;/code&gt; function in &lt;code&gt;geonames&lt;/code&gt;, which uses &lt;a href="https://www.geonames.org/export/web-services.html#srtm3"&gt;Shuttle Radar Topography Mission&lt;/a&gt; elevation data, to fill in missing or incorrect elevation values in their dataset.&lt;/p&gt;</description></item><item><title>fauxpas - HTTP conditions package</title><link>https://ropensci.org/blog/2016/11/18/fauxpas-release/</link><pubDate>Fri, 18 Nov 2016 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2016/11/18/fauxpas-release/</guid><description>
&lt;p&gt;HTTP, or &lt;a href="https://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol"&gt;Hypertext Transfer Protocol&lt;/a&gt; is a protocol by which most
of us interact with the web. When we do requests to a website in a browser
on desktop or mobile, or get some data from a server in R, all of that is
using HTTP.&lt;/p&gt;
&lt;p&gt;HTTP has a rich suite of &lt;a href="https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html"&gt;status codes&lt;/a&gt; describing different HTTP
conditions, ranging from &lt;code&gt;Success&lt;/code&gt; to various client errors, to server errors.
R has a few HTTP client libraries - &lt;a href="https://cran.rstudio.com/web/packages/crul"&gt;crul&lt;/a&gt;, &lt;a href="https://cran.rstudio.com/web/packages/curl"&gt;curl&lt;/a&gt;, &lt;a href="https://cran.rstudio.com/web/packages/httr"&gt;httr&lt;/a&gt;,
and &lt;a href="https://cran.rstudio.com/web/packages/RCurl"&gt;RCurl&lt;/a&gt; - each of which is slightly different. I thought it would
be nice if there was a single way to do HTTP exception handling across these
libraries.&lt;/p&gt;</description></item><item><title>The new Tesseract package: High Quality OCR in R</title><link>https://ropensci.org/blog/2016/11/16/tesseract/</link><pubDate>Wed, 16 Nov 2016 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2016/11/16/tesseract/</guid><description>
&lt;p&gt;Optical character recognition (OCR) is the process of extracting written or typed text from images such as photos and scanned documents into machine-encoded text. The new rOpenSci package &lt;a href="https://cran.r-project.org/web/packages/tesseract/index.html"&gt;tesseract&lt;/a&gt; brings one of the best open-source OCR engines to R. This enables researchers or journalists, for example, to search and analyze vast numbers of documents that are only available in printed form.&lt;/p&gt;
&lt;p&gt;People looking to extract text and metadata from pdf files in R should try our &lt;a href="https://cran.r-project.org/web/packages/pdftools/index.html"&gt;pdftools&lt;/a&gt; package.&lt;/p&gt;</description></item><item><title>Chat with the rOpenSci team at upcoming meetings</title><link>https://ropensci.org/blog/2016/11/09/ropensci-at-meetings/</link><pubDate>Wed, 09 Nov 2016 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2016/11/09/ropensci-at-meetings/</guid><description>
&lt;p&gt;You can find members of the rOpenSci team at various meetings and workshops around the world. Come say &amp;lsquo;hi&amp;rsquo;, learn about how our &lt;a href="https://ropensci.org/packages/"&gt;packages&lt;/a&gt; can enable your research, or about our &lt;a href="https://github.com/ropensci/software-review"&gt;onboarding&lt;/a&gt; process for contributing new packages, discuss software &lt;a href="https://ropensci.org/blog/2016/05/25/software-sustanability-ropensci"&gt;sustainability&lt;/a&gt; or tell us how we can help you do open and reproducible research.&lt;/p&gt;</description></item><item><title>crul - an HTTP client</title><link>https://ropensci.org/blog/2016/11/09/crul-release/</link><pubDate>Wed, 09 Nov 2016 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2016/11/09/crul-release/</guid><description>
&lt;p&gt;A new package &lt;a href="https://cran.rstudio.com/web/packages/crul"&gt;crul&lt;/a&gt; is
on CRAN. &lt;code&gt;crul&lt;/code&gt; is another HTTP client for R, but is relatively simplified
compared to &lt;a href="https://github.com/hadley/httr"&gt;httr&lt;/a&gt;, and is being built
to link closely with &lt;a href="https://github.com/ropenscilabs/webmockr"&gt;webmockr&lt;/a&gt; and &lt;a href="https://github.com/ropenscilabs/vcr"&gt;vcr&lt;/a&gt;. &lt;code&gt;webmockr&lt;/code&gt; and
&lt;code&gt;vcr&lt;/code&gt; are packages ported from Ruby&amp;rsquo;s &lt;a href="https://github.com/bblimke/webmock"&gt;webmock&lt;/a&gt;
and &lt;a href="https://github.com/vcr/vcr"&gt;vcr&lt;/a&gt;, respectively.
They both make mocking HTTP requests really easy.&lt;/p&gt;
&lt;p&gt;A major use case for mocking HTTP requests is for unit tests. Nearly all the
packages I work on personally make HTTP
requests in their test suites, so I wanted to make it really easy to
mock HTTP requests. You don&amp;rsquo;t have to use mocking in test suites of course.&lt;/p&gt;</description></item><item><title>Parse NOAA Integrated Surface Data Files</title><link>https://ropensci.org/blog/2016/11/03/isdparser-release/</link><pubDate>Thu, 03 Nov 2016 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2016/11/03/isdparser-release/</guid><description>
&lt;p&gt;A new package &lt;a href="https://cran.rstudio.com/web/packages/isdparser"&gt;isdparser&lt;/a&gt; is
on CRAN. &lt;code&gt;isdparser&lt;/code&gt; was in part liberated from &lt;a href="https://github.com/ropensci/rnoaa"&gt;rnoaa&lt;/a&gt;,
then improved. We&amp;rsquo;ll use &lt;code&gt;isdparser&lt;/code&gt; in &lt;code&gt;rnoaa&lt;/code&gt; soon.&lt;/p&gt;
&lt;p&gt;&lt;code&gt;isdparser&lt;/code&gt; does not download files for you from NOAA&amp;rsquo;s ftp servers. The
package focuses on parsing the files, which are variable length ASCII strings
stored line by line, where each line has some mandatory data, and any amount
of optional data.&lt;/p&gt;
&lt;p&gt;The data is great, and includes for example, wind speed and direction, temperature,
cloud data, sea level pressure, and more. Includes data from approximately 35,000
stations worldwide, though best coverage is in North America/Europe/Australia.
Data go all the way back to 1901, and are updated daily.&lt;/p&gt;</description></item><item><title>Community Call v12 - How do I create a code of conduct for my event/lab/codebase?</title><link>https://ropensci.org/blog/2016/10/31/comm-call-v12/</link><pubDate>Mon, 31 Oct 2016 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2016/10/31/comm-call-v12/</guid><description>
&lt;p&gt;In order to facilitate a transformation towards open and reproducible research, rOpenSci is building and improving not only the technical infrastructure, but the social infrastructure as well. To support this, occasionally a Community Call will focus on a topic that reflects the values of rOpenSci. The first of these, on Thursday, December 15th, 8-9 AM PST, will be on &amp;ldquo;How do I create a code of conduct for my event/lab/codebase?&amp;rdquo;.&lt;/p&gt;</description></item><item><title>Encryption and Digital Signatures in R using GPG</title><link>https://ropensci.org/blog/2016/10/19/gpg-release/</link><pubDate>Wed, 19 Oct 2016 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2016/10/19/gpg-release/</guid><description>
&lt;p&gt;A new package &lt;a href="https://cran.r-project.org/web/packages/gpg/index.html"&gt;gpg&lt;/a&gt; has appeared on CRAN. From the package description:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;Bindings to GnuPG for working with OpenGPG (RFC4880) cryptographic methods. Includes utilities for public key encryption, creating and verifying digital signatures, and managing your local keyring. Note that some functionality depends on the version of GnuPG that is installed on the system. In particular GnuPG 2 mandates the use of &amp;lsquo;gpg-agent&amp;rsquo; for entering passphrases, which only works if R runs in a terminal session.&lt;/em&gt;&lt;/p&gt;</description></item><item><title>Greetings from Your Community Manager!</title><link>https://ropensci.org/blog/2016/10/12/your-community-manager/</link><pubDate>Wed, 12 Oct 2016 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2016/10/12/your-community-manager/</guid><description>
&lt;p&gt;I feel both proud and privileged to join rOpenSci as your Community Manager. I’ve been a compulsive community builder since the early 2000’s, but it has rarely been part of my job description. Now it seems like all roads have led to this. After a couple of fine days of indoctrination at the &lt;a href="https://bids.berkeley.edu/"&gt;UC Berkeley&lt;/a&gt; home of rOpenSci, I’m settled into work in beautiful Kamloops, British Columbia, Canada.&lt;/p&gt;
&lt;p&gt;So much of my perspective of rOpenSci comes from being a newcomer. I was impressed with the funding from three major grants (you must be doing a few things right!), &lt;a href="https://twitter.com/rOpenSci"&gt;@ropensci&lt;/a&gt; having nearly 11,000 followers on Twitter, the awesome &lt;a href="https://ropensci.org/about/#staff"&gt;staff, leadership team and advisory board&lt;/a&gt;, growing from one full time person to four (with two more positions to open up), and having an enthusiastic &lt;a href="https://ropensci.org/community/"&gt;community&lt;/a&gt; that is known for helping each other out and getting things done.&lt;/p&gt;</description></item><item><title>Get air quality data for the United Kingdom using the rdefra package</title><link>https://ropensci.org/blog/2016/10/06/rdefra-release-033/</link><pubDate>Thu, 06 Oct 2016 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2016/10/06/rdefra-release-033/</guid><description>
&lt;p&gt;Whether you are an environmental scientist, a pollution expert or just concerned about the air you breathe when cycling in the United Kingdom, the ropensci &lt;a href="https://cran.r-project.org/package=rdefra"&gt;rdefra&lt;/a&gt; package can help find the information you need. This package gives you access to the UK-AIR database, hosted by the Department for Environment, Food &amp;amp; Rural Affairs in the United Kingdom, directly from R. The database comprises hundreds of air quality monitoring sites and each provides time series of concentration for different pollutants such as ozone, carbon dioxide and nitrogen oxides amongst others. It allows you to efficiently download, plot and compare data for multiple years/stations so that you can easily carry out spatio-temporal analysis or simply plan an healthier route for you bike ride. The package is fully documented and the &lt;a href="https://github.com/ropenscilabs/rdefra"&gt;vignette&lt;/a&gt; contains examples for a number of applications, such as how to generate the interactive map of the monitoring stations (see screenshot below).&lt;/p&gt;</description></item><item><title>New package graphql: A GraphQL Query Parser</title><link>https://ropensci.org/blog/2016/10/05/graphql-release-10/</link><pubDate>Wed, 05 Oct 2016 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2016/10/05/graphql-release-10/</guid><description>
&lt;p&gt;The new ropensci &lt;a href="https://cran.r-project.org/web/packages/graphql/"&gt;graphql&lt;/a&gt; package is now on CRAN. It implements R bindings to the &lt;a href="https://github.com/graphql/libgraphqlparser"&gt;libgraphqlparser C++ library&lt;/a&gt; to parse GraphQL syntax and export the syntax tree in JSON format:&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-r" data-lang="r"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nf"&gt;graphql2json&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s"&gt;&amp;#34;{ field(complex: { a: { b: [ $var ] } }) }&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;A syntax parser is perhaps not super useful to most end-users, but can be used to validate graphql queries or implement a GraphQL API in R. We hope to add more related functionality later on.&lt;/p&gt;</description></item><item><title>Hunspell 2.0: High-Performance Stemmer, Tokenizer, and Spell Checker for R</title><link>https://ropensci.org/blog/2016/09/12/hunspell-release-20/</link><pubDate>Mon, 12 Sep 2016 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2016/09/12/hunspell-release-20/</guid><description>
&lt;p&gt;A new version of the ropensci &lt;a href="https://cran.r-project.org/package=hunspell"&gt;hunspell&lt;/a&gt; package has been released to CRAN. Hunspell is the spell checker library used by LibreOffice, OpenOffice, Mozilla Firefox, Google Chrome, Mac OS-X, InDesign, Opera, RStudio and many others. It provides a system for tokenizing, stemming and spelling in almost any language or alphabet. The R package exposes both the high-level spell-checker as well as low-level stemmers and tokenizers which analyze or extract individual words from various formats (text, html, xml, latex).&lt;/p&gt;</description></item><item><title>New in Magick 0.3</title><link>https://ropensci.org/blog/2016/09/08/magick-release-03/</link><pubDate>Thu, 08 Sep 2016 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2016/09/08/magick-release-03/</guid><description>
&lt;p&gt;A new version of the ropensci &lt;a href="https://cran.r-project.org/package=magick"&gt;magick&lt;/a&gt; package has been released to CRAN. Magick is a package for Advanced Image-Processing in R. It wraps the ImageMagick STL which is perhaps the most comprehensive open-source image processing library available today. Our &lt;a href="https://ropensci.org/blog/2016/08/23/z-magick-release"&gt;original announcement&lt;/a&gt; has more details.&lt;/p&gt;
&lt;h2&gt;
New features
&lt;/h2&gt;&lt;p&gt;This new version now includes a beautiful &lt;a href="https://cloud.r-project.org/web/packages/magick/vignettes/intro.html"&gt;vignette&lt;/a&gt; which gives an overview of the main functionality to get you started! It lists the various formats, transformations, effects, operations and much more.&lt;/p&gt;</description></item><item><title>Postdoctoral Scholar – Sustainable Software and Reproducible Research</title><link>https://ropensci.org/blog/2016/09/07/postdoc-position/</link><pubDate>Wed, 07 Sep 2016 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2016/09/07/postdoc-position/</guid><description>
&lt;p&gt;The rOpenSci project based at the University of California, Berkeley seeks to hire a postdoctoral scholar to work on the research activities funded by the grant titled “Fostering the next generation of sustainable software and reproducible research practices in the scientific community”. The project develops open source software to promote reproducible research practices in the scientific community. The postdoctoral scholar will focus on a research topic aligned with their own interests in order to better understand and improve scientific software practices. Possible topics include but are not limited to:&lt;/p&gt;</description></item><item><title>Advanced Graphics and Image Processing in R with magick</title><link>https://ropensci.org/commcalls/2016-08-24/</link><pubDate>Wed, 24 Aug 2016 00:00:00 +0000</pubDate><guid>https://ropensci.org/commcalls/2016-08-24/</guid><description/></item><item><title>Advanced Image-Processing in R with Magick, Part I</title><link>https://ropensci.org/blog/2016/08/23/z-magick-release/</link><pubDate>Tue, 23 Aug 2016 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2016/08/23/z-magick-release/</guid><description>
&lt;p&gt;The new &lt;a href="https://cran.r-project.org/web/packages/magick/index.html"&gt;magick&lt;/a&gt; package is an ambitious effort to modernize and simplify high-quality image processing in R. It wraps the &lt;a href="https://www.imagemagick.org/Magick++/STL.html"&gt;ImageMagick STL&lt;/a&gt; which is perhaps the most comprehensive open-source image processing library available today.&lt;/p&gt;
&lt;p&gt;The ImageMagick library has an overwhelming amount of functionality. The current version of Magick exposes a decent chunk of it, but being a first release, documentation is still sparse. This post briefly introduces the most important concepts to get started. There will also be an &lt;a href="https://ropensci.org/commcalls/2016-08-24/"&gt;rOpenSci community call&lt;/a&gt; on Wednesday in which we demonstrate basic functionality.&lt;/p&gt;</description></item><item><title>New package tokenizers joins rOpenSci</title><link>https://ropensci.org/blog/2016/08/23/tokenizers-joins-ropensci/</link><pubDate>Tue, 23 Aug 2016 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2016/08/23/tokenizers-joins-ropensci/</guid><description>
&lt;p&gt;The R package ecosystem for natural language processing has been flourishing in recent days. R packages for text analysis have usually been based on the classes provided by the &lt;a href="https://cran.r-project.org/package=NLP/"&gt;NLP&lt;/a&gt; or &lt;a href="https://cran.r-project.org/package=tm/"&gt;tm&lt;/a&gt; packages. Many of them depend on Java. But recently there have been a number of new packages for text analysis in R, most notably &lt;a href="https://github.com/dselivanov/text2vec"&gt;text2vec&lt;/a&gt;, &lt;a href="https://github.com/kbenoit/quanteda"&gt;quanteda&lt;/a&gt;, and &lt;a href="https://github.com/juliasilge/tidytext"&gt;tidytext&lt;/a&gt;. These packages are built on top of &lt;a href="http://www.rcpp.org/"&gt;Rcpp&lt;/a&gt; instead of &lt;a href="https://cran.r-project.org/package=rJava/"&gt;rJava&lt;/a&gt;, which makes them much more reliable and portable. And instead of the classes based on NLP, which I have never thought to be particularly idiomatic for R, they use standard R data structures. The text2vec and quanteda packages both rely on the sparse matrices provided by the rock solid &lt;a href="https://cran.r-project.org/package=Matrix/"&gt;Matrix&lt;/a&gt; package. The tidytext package is idiosyncratic (in the best possible way!) for doing all of its work in data frames rather than matrices, but a data frame is about as standard as you can get. For a long time when I would recommend R to people, I had to add the caveat that they should use Python if they were primarily interested in text analysis. But now I no longer feel the need to hedge.&lt;/p&gt;</description></item><item><title>rotl paper published</title><link>https://ropensci.org/blog/2016/07/26/rotl-paper-published/</link><pubDate>Tue, 26 Jul 2016 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2016/07/26/rotl-paper-published/</guid><description>
&lt;p&gt;We are excited to announce a paper describing &lt;code&gt;rotl&lt;/code&gt;, our package for the
&lt;a href="http://www.opentreeoflife.org/"&gt;Open Tree of Life&lt;/a&gt; data, has been
&lt;a href="https://doi.org/10.1111/2041-210X.12593"&gt;published&lt;/a&gt;. The full
citation is:&lt;/p&gt;
&lt;p&gt;Michonneau, F., Brown, J. W. and Winter, D. J. (2016), rotl: an R
package to interact with the Open Tree of Life data. &lt;em&gt;Methods Ecol
Evol.&lt;/em&gt; doi: &lt;a href="https://doi.org/10.1111/2041-210X.12593"&gt;https://doi.org/10.1111/2041-210X.12593&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;The paper, which is freely available, describes the package and the data
it wraps in detail. Rather than rehash the information here, we will use
this post to briefly introduce the goals of the package and thank some
of the people that helped it come to be.&lt;/p&gt;</description></item><item><title>Testing packages with R Travis for OS-X</title><link>https://ropensci.org/blog/2016/07/12/travis-osx/</link><pubDate>Tue, 12 Jul 2016 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2016/07/12/travis-osx/</guid><description>
&lt;p&gt;Travis is a continuous integration service which allows for running automated testing code everytime you push to GitHub. Hadley&amp;rsquo;s &lt;a href="http://r-pkgs.had.co.nz/check.html"&gt;book&lt;/a&gt; about R packages explains how and why R package authors should take advantage of this in their development process.&lt;/p&gt;
&lt;h2&gt;
The build matrix
&lt;/h2&gt;&lt;p&gt;Travis is now providing support for &lt;a href="https://docs.travis-ci.com/user/multi-os/"&gt;multiple operating systems&lt;/a&gt;, including Ubuntu 14.04 (Trusty) and various flavors of Mac OS-X. Jim Hester has done a great job of &lt;a href="https://github.com/travis-ci/travis-build/commits/master/lib/travis/build/script/r.rb"&gt;tweaking&lt;/a&gt; the travis &lt;a href="https://github.com/travis-ci/travis-build/blob/master/lib/travis/build/script/r.rb"&gt;R-language build script&lt;/a&gt; to automate building and checking of R packages on the various platforms.&lt;/p&gt;</description></item><item><title>Australia Unconference</title><link>https://ropensci.org/blog/2016/06/16/au-unconf/</link><pubDate>Thu, 16 Jun 2016 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2016/06/16/au-unconf/</guid><description>
&lt;p&gt;On April 21st and 22nd of 2016, we had 40 members of the R community gather in Brisbane, Australia, with the goal of reproducing the rOpensci Unconference events that have been running with great success in San Francisco since 2014. Like every event organisers ever, we went through the usual crisis: Where will it be? Will anyone actually show up? Is the problem space over venue, date, attendees, catering, sponsors convex? It it even possible to organise an event by only uttering TRUE statements?&lt;/p&gt;</description></item><item><title>Software sustainability research with rOpenSci</title><link>https://ropensci.org/blog/2016/05/25/software-sustanability-ropensci/</link><pubDate>Wed, 25 May 2016 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2016/05/25/software-sustanability-ropensci/</guid><description>
&lt;p&gt;I’m happy to announce that I’ve started a project with &lt;a href="https://ropensci.org"&gt;rOpenSci&lt;/a&gt;
under &lt;a href="https://ropensci.org/blog/2015/11/19/helmsley-trust-funding/"&gt;their recent award from the Helmsley Foundation&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;My work with rOpenSci will focus on sustainability of the project itself. Sustainability can be defined as having the
resources to do the necessary work to continue and grow rOpenSci. This is one of the most difficult challenges for
rOpenSci and for many other research software projects.&lt;/p&gt;
&lt;p&gt;rOpenSci has a very broad and very ambitious goal, as stated on their web site, &amp;ldquo;Transforming science through open data.&amp;rdquo;
In practice, the work being done by rOpenSci is &amp;ldquo;creating packages that allow access to data repositories through the
R statistical programming environment&amp;rdquo; with tools that “not only facilitate drawing data into an environment where it
can readily be manipulated, but also one in which those analyses and methods can be easily shared, replicated, and
extended by other researchers.”
An interesting question is how much rOpenSci will choose to move beyond R to meet its goal, which I would encourage as
much as possible. I actually might rephrase the goal as &amp;ldquo;Transforming science through open data and open software&amp;rdquo;
better matching what is now happening in the project while not calling out R, since I would prefer to try to affect
the non-R science community as well.&lt;/p&gt;</description></item><item><title>Python String Methods in R, pystr</title><link>https://ropensci.org/commcalls/2016-05-11/</link><pubDate>Wed, 11 May 2016 00:00:00 +0000</pubDate><guid>https://ropensci.org/commcalls/2016-05-11/</guid><description/></item><item><title>Onboarding at rOpenSci: A Year in Reviews</title><link>https://ropensci.org/blog/2016/03/28/software-review/</link><pubDate>Mon, 28 Mar 2016 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2016/03/28/software-review/</guid><description>
&lt;p&gt;Code review, in which peers manually inspect the source code of software
written by others, is widely recognized as one of the best tools for finding
bugs in software. Code review is relatively uncommon in &lt;em&gt;scientific&lt;/em&gt; software
development, though. Scientists, despite being familiar with the process of
peer review, often have little exposure to code review due to lack of training and
historically little incentive to share the source code from their research. So
scientific code, from one-off scripts to reusable R packages, is rarely subject
to review. Most R packages are subject only to the automated checks required by
CRAN, which primarily ensure that packages can be installed on multiple systems.
As such, The burden is on software users to discern well-written and efficient
packages from poorly written ones.&lt;/p&gt;</description></item><item><title>rOpenSci geospatial libraries</title><link>https://ropensci.org/blog/2016/03/17/ropensci-geospatial-stack/</link><pubDate>Thu, 17 Mar 2016 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2016/03/17/ropensci-geospatial-stack/</guid><description>
&lt;p&gt;Geospatial data input/output, manipulation, and vizualization are tasks that are common to many disciplines. Thus, we&amp;rsquo;re keenly interested in making great tools in this space. We have an increasing set of spatial tools, each of which we&amp;rsquo;ll cover sparingly. See the &lt;strong&gt;cran&lt;/strong&gt; and &lt;strong&gt;github&lt;/strong&gt; badges for more information.&lt;/p&gt;
&lt;p&gt;We are not trying to replace the current R geospatial libraries - rather, we&amp;rsquo;re trying to fill in gaps and create smaller tools to make it easy to plug in just the tools you need to your workflow.&lt;/p&gt;</description></item><item><title>We're hiring a community manager!</title><link>https://ropensci.org/blog/2016/03/10/community-manager-position/</link><pubDate>Thu, 10 Mar 2016 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2016/03/10/community-manager-position/</guid><description>
&lt;p&gt;The rOpenSci team is growing, thanks in part to our &lt;a href="https://ropensci.org/blog/2015/11/19/helmsley-trust-funding/"&gt;recent funding&lt;/a&gt;. We recently &lt;a href="https://ropensci.org/blog/2016/03/01/pdftools-and-jeroen"&gt;welcomed&lt;/a&gt; Jeroen Ooms on the software development side and today we&amp;rsquo;re thrilled to announce a position for community manager.&lt;/p&gt;
&lt;p&gt;Our mission is to expand access to scientific data and promote a culture of reproducible research and sustainable research software. We aim to cultivate a vibrant and open community through activities such as our &lt;a href="https://communitycalls.ropensci.org/"&gt;community calls&lt;/a&gt;, &lt;a href="https://discuss.ropensci.org/"&gt;discussion forums&lt;/a&gt;, &lt;a href="https://github.com/ropensci/software-review"&gt;package review&lt;/a&gt;, and &lt;a href="https://unconf16.ropensci.org/"&gt;annual unconferences&lt;/a&gt;. We are ready for a dedicated community manager to come on board to broaden the understanding and reach of rOpenSci to the researcher community.&lt;/p&gt;</description></item><item><title>Australian rOpenSci Unconference</title><link>https://ropensci.org/blog/2016/03/09/au-unconf-down-under/</link><pubDate>Wed, 09 Mar 2016 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2016/03/09/au-unconf-down-under/</guid><description>
&lt;p&gt;The rOpenSci Unconference is coming to Australia and we are excited!!&lt;/p&gt;
&lt;p&gt;The event will take place in sunny Brisbane, on April 21-22 2016 hosted at the Microsoft Innovation Centre. You can find more information about the event and how to register at &lt;a href="https://auunconf.ropensci.org/"&gt;https://auunconf.ropensci.org/&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;I was completely and unceremoniously thrown into the deep end when I first started learning R. Contrary to what I initially thought possible, I am now irreversibly converted to the ideology of open source. Create tools to make other people&amp;rsquo;s lives easier? Make methods easily reproducible? Get your hands on state-of-the-art methodology, hot off the presses? Yes please! Can I have some more?&lt;/p&gt;</description></item><item><title>Google Sheets in R</title><link>https://ropensci.org/commcalls/2016-03-02/</link><pubDate>Wed, 02 Mar 2016 00:00:00 +0000</pubDate><guid>https://ropensci.org/commcalls/2016-03-02/</guid><description/></item><item><title>Introducing pdftools - A fast and portable PDF extractor</title><link>https://ropensci.org/blog/2016/03/01/pdftools-and-jeroen/</link><pubDate>Tue, 01 Mar 2016 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2016/03/01/pdftools-and-jeroen/</guid><description>
&lt;p&gt;Scientific articles are typically locked away in PDF format, a format designed primarily for printing but not so great for searching or indexing. The new &lt;a href="https://cran.r-project.org/package=pdftools"&gt;pdftools&lt;/a&gt; package allows for extracting text and metadata from pdf files in R. From the extracted plain-text one could find articles discussing a particular drug or species name, without having to rely on publishers providing metadata, or pay-walled search engines.&lt;/p&gt;
&lt;p&gt;The pdftools slightly overlaps with the &lt;a href="https://cran.r-project.org/web/packages/Rpoppler/index.html"&gt;Rpoppler&lt;/a&gt; package by Kurt Hornik. The main motivation behind developing pdftools was that Rpoppler depends on glib, which does not work well on Mac and Windows. The pdftools package uses the poppler c++ interface together with Rcpp, which results in a lighter and more portable implementation.&lt;/p&gt;</description></item><item><title>Help us prioritize what to build in 2016</title><link>https://ropensci.org/blog/2016/01/07/survey/</link><pubDate>Thu, 07 Jan 2016 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2016/01/07/survey/</guid><description>
&lt;p&gt;We&amp;rsquo;ve got a big year ahead of us as we work towards expanding our team and organizing various events and activities. We remain committed to supporting and expanding the landscape of open source tools that are available to researchers. While much of our focus has been around making it easier to access various data repositories, we are keen on improving other parts of the research pipeline, including data munging, documentation and sharing. To help us prioritize our development activities and better understand the needs of researchers, we would really appreciate 5-12 minutes of your time to complete a survey:&lt;/p&gt;</description></item><item><title>Designing dat 1.0</title><link>https://ropensci.org/commcalls/2015-12-02/</link><pubDate>Wed, 02 Dec 2015 00:00:00 +0000</pubDate><guid>https://ropensci.org/commcalls/2015-12-02/</guid><description/></item><item><title>rOpenSci Announces $2.9M Award from the Helmsley Charitable Trust</title><link>https://ropensci.org/blog/2015/11/19/helmsley-trust-funding/</link><pubDate>Thu, 19 Nov 2015 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2015/11/19/helmsley-trust-funding/</guid><description>
&lt;p&gt;rOpenSci, whose mission is to develop and maintain sustainable software
tools that allow researchers to access, visualize, document, and publish
open data on the Web, is pleased to announce that it has been awarded a
grant of nearly $2.9 million over three years from &lt;a href="https://helmsleytrust.org/"&gt;The Leona M. and
Harry B. Helmsley Charitable Trust&lt;/a&gt;. The
grant, which was awarded through the Trust’s &lt;a href="https://helmsleytrust.org/programs/health-biomedical-research-infrastructure"&gt;Biomedical Research
Infrastructure Program&lt;/a&gt;, will be used to expand rOpenSci’s mission of developing tools and community around open data and reproducible research practices.&lt;/p&gt;</description></item><item><title>Failing Fast and Early, assertr</title><link>https://ropensci.org/commcalls/2015-10-07/</link><pubDate>Wed, 07 Oct 2015 00:00:00 +0000</pubDate><guid>https://ropensci.org/commcalls/2015-10-07/</guid><description/></item><item><title>Rentrez 1_0 released</title><link>https://ropensci.org/blog/2015/09/24/rentrez-1_0-release/</link><pubDate>Thu, 24 Sep 2015 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2015/09/24/rentrez-1_0-release/</guid><description>
&lt;p&gt;A new version of &lt;code&gt;rentrez&lt;/code&gt;, our package for the NCBI&amp;rsquo;s EUtils API, is making
it&amp;rsquo;s way around the CRAN mirrors. This release represents a substantial
improvement to &lt;code&gt;rentrez&lt;/code&gt;, including a &lt;a href="https://cran.r-project.org/web/packages/rentrez/vignettes/rentrez_tutorial.html"&gt;new vignette&lt;/a&gt;
that documents the whole package.&lt;/p&gt;
&lt;p&gt;This posts describes some of the new things in &lt;code&gt;rentrez&lt;/code&gt;, and gives us a chance
to thank some of the people that have contributed to this package&amp;rsquo;s development.&lt;/p&gt;
&lt;h2&gt;
Thanks
&lt;/h2&gt;&lt;p&gt;Thanks to everyone who has filed and issue or written us an email about &lt;code&gt;rentrez&lt;/code&gt;,
your contributions have been an important part of the package&amp;rsquo;s development. In particular, we welcome
&lt;a href="http://ewrebio.me"&gt;Han Guangchun&lt;/a&gt; as a new contributor to &lt;code&gt;rentrez&lt;/code&gt; and thank
&lt;a href="http://docking.org/~momeara/"&gt;Matthew O&amp;rsquo;Meara&lt;/a&gt; for posting
an issue that brought the &lt;code&gt;by_id&lt;/code&gt; mode for &lt;code&gt;entrez_link&lt;/code&gt; (discussed below) to our
attention.&lt;/p&gt;</description></item><item><title>Tools for R package development, metacran</title><link>https://ropensci.org/commcalls/2015-08-19/</link><pubDate>Wed, 19 Aug 2015 00:00:00 +0000</pubDate><guid>https://ropensci.org/commcalls/2015-08-19/</guid><description/></item><item><title>A drat repository for rOpenSci</title><link>https://ropensci.org/blog/2015/08/04/a-drat-repository-for-ropensci/</link><pubDate>Tue, 04 Aug 2015 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2015/08/04/a-drat-repository-for-ropensci/</guid><description>
&lt;p&gt;We&amp;rsquo;re happy to announce the launch of a CRAN-style repository for rOpenSci at &lt;a href="http://packages.ropensci.org"&gt;http://packages.ropensci.org&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;This repository contains the latest nightly builds from the master branch of all rOpenSci packages currently on GitHub. This allows users to install development versions of our software without specialized functions such as &lt;code&gt;install_github()&lt;/code&gt;, allows
dependencies not hosted on CRAN to still be resolved automatically, and permits the use of &lt;code&gt;update.packages()&lt;/code&gt;.&lt;/p&gt;
&lt;h2&gt;
Using the repository
&lt;/h2&gt;&lt;p&gt;To use, simply add
&lt;code&gt;packages.ropensci.org&lt;/code&gt; to your existing list of R repos, such as:&lt;/p&gt;</description></item><item><title>broom, An R Package to Convert Statistical Models into Tidy Data Frames</title><link>https://ropensci.org/commcalls/2015-07-08/</link><pubDate>Wed, 08 Jul 2015 00:00:00 +0000</pubDate><guid>https://ropensci.org/commcalls/2015-07-08/</guid><description/></item><item><title>The challenge of combining 176 otherpeoplesdata to create the Biomass And Allometry Database</title><link>https://ropensci.org/blog/2015/06/03/baad/</link><pubDate>Wed, 03 Jun 2015 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2015/06/03/baad/</guid><description>
&lt;p&gt;Despite the hype around &amp;ldquo;big data&amp;rdquo;, a more immediate problem facing many scientific analyses is that large-scale databases must be assembled from a collection of small independent and heterogeneous fragments &amp;ndash; the outputs of many and isolated scientific studies conducted around the globe.&lt;/p&gt;
&lt;p&gt;Collecting and compiling these fragments is challenging at both political and technical levels. The political challenge is to manage the carrots and sticks needed to promote sharing of data within the scientific community. The politics of data sharing have been the primary focus for debate over the last 5 years, but now that many journals and funding agencies are requiring data to be archived at the time of publication, the availability of these data fragments is increasing. But little progress has been made on the technical challenge: &lt;strong&gt;how can you combine a collection of independent fragments, each with its own peculiarities, into a single quality database?&lt;/strong&gt;&lt;/p&gt;</description></item><item><title>Getting NCBI Data into your R Sessions, rentrez; rocker, Docker for R</title><link>https://ropensci.org/commcalls/2015-05-27/</link><pubDate>Wed, 27 May 2015 00:00:00 +0000</pubDate><guid>https://ropensci.org/commcalls/2015-05-27/</guid><description/></item><item><title>Database interfaces</title><link>https://ropensci.org/blog/2015/05/20/database-interfaces/</link><pubDate>Wed, 20 May 2015 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2015/05/20/database-interfaces/</guid><description>
&lt;p&gt;There are many different databases. The most familiar are row-column SQL databases like MySQL, SQLite, or PostgreSQL. Another type of database is the key-value store, which as a concept is very simple: you save a value specified by a key, and you can retrieve a value by its key. One more type is the document database, which instead of storing rows and columns, stores blobs of text or even binary files. The key-value and document types fall under the NoSQL umbrella. As there are mature R clients for many SQL databases, and &lt;a href="https://github.com/hadley/dplyr"&gt;dplyr&lt;/a&gt; is a great generic interface to SQL backends (see &lt;a href="https://cran.rstudio.com/web/packages/dplyr/"&gt;&lt;code&gt;dplyr&lt;/code&gt; vignettes&lt;/a&gt; for an intro), we won&amp;rsquo;t delve into SQL clients here.&lt;/p&gt;</description></item><item><title>Getting Your Data into R</title><link>https://ropensci.org/commcalls/2015-04-15/</link><pubDate>Wed, 15 Apr 2015 00:00:00 +0000</pubDate><guid>https://ropensci.org/commcalls/2015-04-15/</guid><description/></item><item><title>Introducing a Wishlist for Scientific R Packages</title><link>https://ropensci.org/blog/2015/03/10/introducing-wishlist/</link><pubDate>Tue, 10 Mar 2015 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2015/03/10/introducing-wishlist/</guid><description>
&lt;p&gt;There are two things that make R such a wonderful programming environment - the vast number of packages to access, process and interpret
data, and the enthusiastic individuals and subcommunities (of which rOpenSci is a great example). One, of course, flows from the other:
R programmers write R packages to provide language users with more features, which makes everyone&amp;rsquo;s jobs easier and (hopefully!)
attracts more users and more contributions.&lt;/p&gt;
&lt;p&gt;But what if you have an idea, or a need, but not the time or confidence to write a package for it? I can&amp;rsquo;t speak for this blog&amp;rsquo;s
readers, but I&amp;rsquo;ve been writing R for about two years and it took a good long while before I felt comfortable contributing upstream
to CRAN. Or, what if you do have the time, and do have the confidence, but want to spend that time well, on things that you know
other people will find useful, and don&amp;rsquo;t know what that is?&lt;/p&gt;</description></item><item><title>htmlwidgets, Binding JS Libraries Made Easy</title><link>https://ropensci.org/commcalls/2015-03-05/</link><pubDate>Thu, 05 Mar 2015 00:00:00 +0000</pubDate><guid>https://ropensci.org/commcalls/2015-03-05/</guid><description/></item><item><title>Reproducibility Hackathon</title><link>https://ropensci.org/commcalls/reproducibility-hackathon/</link><pubDate>Wed, 14 Jan 2015 00:00:00 +0000</pubDate><guid>https://ropensci.org/commcalls/reproducibility-hackathon/</guid><description/></item><item><title>Curling - exploring web request options</title><link>https://ropensci.org/blog/2014/12/18/curl-options/</link><pubDate>Thu, 18 Dec 2014 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2014/12/18/curl-options/</guid><description>
&lt;p&gt;rOpenSci specializes in creating R libraries for accessing data resources on the web from R. Most times you request data from the web in R with our packages, you should have no problem. However, you evenutally will run into problems. In addition, there are advanced things you can do modifying requests to web resources that fall in the &lt;em&gt;advanced stuff&lt;/em&gt; category.&lt;/p&gt;
&lt;p&gt;Underlying almost all of our packages are requests to web resources served over the &lt;code&gt;http&lt;/code&gt; protocol via &lt;a href="https://curl.haxx.se/"&gt;curl&lt;/a&gt;. &lt;code&gt;curl&lt;/code&gt; &lt;em&gt;is a command line tool and library for transferring data with URL syntax, supporting (lots of protocols)&lt;/em&gt; . &lt;code&gt;curl&lt;/code&gt; has many options that you may not know about.&lt;/p&gt;</description></item><item><title>Community calls</title><link>https://ropensci.org/blog/2014/12/15/community-calls/</link><pubDate>Mon, 15 Dec 2014 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2014/12/15/community-calls/</guid><description>
&lt;p&gt;Key to the success of rOpenSci is our community and we want to hear more regularly from our members, and foster new interactions among the group. In addition, community calls are a way for us to give important updates, and get feedback on them.&lt;/p&gt;
&lt;p&gt;We tentatively plan on doing community calls once per month. The format of rOpenSci community calls could be of various types. We could have community members show off software they&amp;rsquo;ve been working on, or users demo use cases. Instead, we could focus more on conversations. For this first call, we&amp;rsquo;ll be doing a combination of demonstration and discussion. We would like to experiment with the call format over the next few months before we decide on one or more approaches that work best.&lt;/p&gt;</description></item><item><title>Growth of open data in biology</title><link>https://ropensci.org/blog/2014/11/10/open-data-growth/</link><pubDate>Mon, 10 Nov 2014 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2014/11/10/open-data-growth/</guid><description>
&lt;h2&gt;
Why open data growth
&lt;/h2&gt;&lt;p&gt;At rOpenSci we try to make it easier for people to use open data and contribute open data to the community. The question often arises: How much open data do we have? Another angle on this topic is: How much is open data growing?&lt;/p&gt;
&lt;p&gt;We provide access to dozens of data respositories through our various packages. We asked many of them to share numbers on the amount of data they have, and if possible, growth of their data holdings through time. Many of our partners came through with some data. Note that the below is biased towards those data sources we were able to get data from, and those that we were able to get growth through time data. In addition, note that much of the data we use below was from fall of 2013 (last year) - so the below is based on somewhat old data, but surely the trends are likely still the same now.&lt;/p&gt;</description></item><item><title>Introducing Rocker: Docker for R</title><link>https://ropensci.org/blog/2014/10/23/introducing-rocker/</link><pubDate>Thu, 23 Oct 2014 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2014/10/23/introducing-rocker/</guid><description>
&lt;blockquote&gt;
&lt;p&gt;You only know two things about Docker. First, it uses Linux
containers. Second, the Internet won&amp;rsquo;t shut up about it.&lt;/p&gt;
&lt;p&gt;&amp;ndash; attributed to Solomon Hykes, Docker CEO&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h3&gt;
So what is Docker?
&lt;/h3&gt;&lt;p&gt;&lt;a href="https://www.docker.com"&gt;Docker&lt;/a&gt; is a relatively new &lt;a href="https://github.com/docker/docker/tree/master/LICENSE"&gt;open
source&lt;/a&gt; application
and service, which is seeing interest across a number of areas. It
uses recent Linux kernel features (containers, namespaces) to shield
processes. While its use (superficially) resembles that of virtual
machines, it is &lt;em&gt;much more lightweight&lt;/em&gt; as it operates at the level of a
single process (rather than an emulation of an entire OS layer). This also
allows it to start almost instantly, require very little resources and
hence permits an order of magnitude more deployments per host than a
virtual machine.&lt;/p&gt;</description></item><item><title>New fiscal sponsorship agreement with NumFocus foundation</title><link>https://ropensci.org/blog/2014/10/01/numfocus-partnership/</link><pubDate>Wed, 01 Oct 2014 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2014/10/01/numfocus-partnership/</guid><description>
&lt;p&gt;I’m very pleased to announce that rOpenSci has signed a comprehensive &lt;a href="https://en.wikipedia.org/wiki/Fiscal_sponsorship"&gt;fiscal sponsorship agreement&lt;/a&gt; with the &lt;a href="https://numfocus.org/"&gt;NumFocus foundation&lt;/a&gt;, a 501(c)3 nonprofit that supports R&amp;amp;D for open source scientific software projects. We are delighted to be in the company of esteemed projects such as &lt;a href="https://ipython.org/"&gt;IPython&lt;/a&gt; and &lt;a href="https://julialang.org/"&gt;Julia&lt;/a&gt; that share our goal of promoting reproducible research practices across many scientific communities and developing a rich ecosystem of tools for open scientific computing.&lt;/p&gt;
&lt;p&gt;All of our activities, from hackathons and the &lt;a href="https://ropensci.org/blog/2014/08/11/ambassadors-program/"&gt;ambassador program&lt;/a&gt; to salaries for our full-time personnel, are 100% grant supported at this time. While we will continue to pursue all possible federal and private funding to support future efforts, our continued success necessitates a diverse funding model. Given the current funding climate additional donations from individuals, institutions, and corporations are critical to help us remain sustainable and give us the ability to scale.&lt;/p&gt;</description></item><item><title>NCEAS Codefest Follow-up</title><link>https://ropensci.org/blog/2014/09/23/nceas-codefest-follow-up/</link><pubDate>Tue, 23 Sep 2014 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2014/09/23/nceas-codefest-follow-up/</guid><description>
&lt;p&gt;The week after labor day, we had the pleasure of attending the &lt;a href="https://nceas.github.io/open-science-codefest/"&gt;NCEAS open science codefest&lt;/a&gt; event in Santa Barbara. It was great to meet folks like the new arrivals at the expanding &lt;a href="https://mozillascience.org"&gt;Mozilla Science Lab&lt;/a&gt;, &lt;a href="https://twitter.com/billdoesphysics"&gt;Bill Mills&lt;/a&gt; and &lt;a href="https://twitter.com/abbycabs"&gt;Abby Cabunoc&lt;/a&gt; (Bill even already has a great &lt;a href="https://mozillascience.org/worries-critical-mass/"&gt;post up about the codefest&lt;/a&gt;), and see old friends from NCEAS and DataONE, among many more. This 2.5 day event ran smoothly thanks to the leadership of &lt;a href="https://www.nceas.ucsb.edu/~jones/"&gt;Matt Jones&lt;/a&gt;. The event was run in &lt;a href="https://en.wikipedia.org/wiki/Unconference"&gt;unconference style&lt;/a&gt;. Each idea was then posted up on a giant post it on the wall and people had 30 minutes to wander the room choosing projects. The approach allowed for a consensus based filtering of ideas. We had the opportunity to suggest some ideas, and a chance to help out with others. Here&amp;rsquo;s an overview of the projects the rOpenSci team worked on and what we accomplished at the open science codefest.&lt;/p&gt;</description></item><item><title>rOpenSci at NESCent Open Tree of Life Hackathon</title><link>https://ropensci.org/blog/2014/08/15/open-tree-of-life-hackathon/</link><pubDate>Fri, 15 Aug 2014 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2014/08/15/open-tree-of-life-hackathon/</guid><description>
&lt;p&gt;The &lt;a href="http://opentreeoflife.org"&gt;Open Tree of Life project&lt;/a&gt; aims to synthesize our combined knowledge of how organisms relate to each other, and make the results available to anyone who wants to use them. At present, the project contains data from more than 4,000 published phylogenies, which combine with other data sources to make &lt;a href="https://tree.opentreeoflife.org/"&gt;a tree that covers 2.5 million species&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;In September, the Open Tree of Life team are holding a hackathon to develop tools that use the project&amp;rsquo;s web services to extract, annotate and add data. We are excited to say that &lt;a href="https://francoismichonneau.net/"&gt;Francois Michonneau&lt;/a&gt; and &lt;a href="https://cartwrig.ht/people/#david-j-winter"&gt;I&lt;/a&gt; will be attending the hackathon, where they plan to work with &lt;a href="https://github.com/josephwb/"&gt;Joseph W. Brown&lt;/a&gt; on an R package that allows users to interact with the Open Tree data.&lt;/p&gt;</description></item><item><title>Announcing our ambassadors program</title><link>https://ropensci.org/blog/2014/08/11/ambassadors-program/</link><pubDate>Mon, 11 Aug 2014 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2014/08/11/ambassadors-program/</guid><description>
&lt;p&gt;In the last 12 months we traveled all over the world delivering talks and hands on workshops at various conferences and universities. This was a great opportunity for us to raise awareness for the project and get more of you involved as contributors and collaborators. As we scale the project to the next level, we need your help in spreading the message.&lt;/p&gt;
&lt;p&gt;Today we would like to officially announce the rOpenSci Ambassadors program. To facilitate more discussion about rOpenSci tools and projects, we like to support our community members in running small workshops (perhaps a lunch time event), talks (lightning or longer talk at the next conference you attend), hands on tutorials (for your grad department, seminar), or similar event.&lt;/p&gt;</description></item><item><title>Community conversations and a new package for full text</title><link>https://ropensci.org/blog/2014/08/08/text-commmunity/</link><pubDate>Fri, 08 Aug 2014 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2014/08/08/text-commmunity/</guid><description>
&lt;p&gt;&lt;strong&gt;UPDATE:&lt;/strong&gt; Use the new discussion forum at &lt;a href="https://discuss.ropensci.org/"&gt;https://discuss.ropensci.org/&lt;/a&gt;&lt;/p&gt;
&lt;h2&gt;
Community
&lt;/h2&gt;&lt;p&gt;Community is at the heart of rOpenSci. We couldn&amp;rsquo;t have accomplished most of our work without help from various &lt;a href="https://ropensci.org/community/#community"&gt;contributors and users&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Most of our discussions with the broader community over the past year have been through twitter or one-on-one conversations. However, we would like to foster more open ended and deeper discussions with our community. To this end, we are resurrecting our &lt;a href="https://groups.google.com/forum/#!forum/ropensci-discuss"&gt;public Google group list&lt;/a&gt;. We encourage you to sign up and post ideas for packages, solicit feedback on new ideas, and most importantly find other collaborators who share your domain interests. We also plan to use the list to solicit feedback on some of the bigger rOpenSci projects early on in the development phase allowing our community to shape future direction and also collaborate where appropriate.&lt;/p&gt;</description></item><item><title>NCEAS Codefest</title><link>https://ropensci.org/blog/2014/08/06/nceas-codefest/</link><pubDate>Wed, 06 Aug 2014 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2014/08/06/nceas-codefest/</guid><description>
&lt;p&gt;We&amp;rsquo;re delighted to be sponsoring the upcoming Open Science Codefest in Santa Barbara, California, alongside &lt;a href="https://renci.org/"&gt;RENCI&lt;/a&gt;, &lt;a href="https://www.nceas.ucsb.edu/"&gt;NCEAS&lt;/a&gt;, &lt;a href="https://www.nsf.gov/"&gt;NSF&lt;/a&gt;, &lt;a href="https://www.dataone.org/"&gt;DataONE&lt;/a&gt;, and &lt;a href="https://mozillascience.org/"&gt;Mozilla Science Lab&lt;/a&gt;. The Open Science Codefest&amp;rsquo;s goal is to gather researchers from across ecology, biodiversity science, and other earth and environmental sciences with programmer types to collaborate on coding projects. The ideas for the event so far include not just coding projects with the end result being software, but conversations on particular topics that may or my not lead to code being written.&lt;/p&gt;</description></item><item><title>Changes in rnoaa v0.2.0</title><link>https://ropensci.org/blog/2014/07/21/rnoaa_v02/</link><pubDate>Mon, 21 Jul 2014 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2014/07/21/rnoaa_v02/</guid><description>
&lt;p&gt;We just released &lt;code&gt;v0.2&lt;/code&gt; of &lt;code&gt;rnoaa&lt;/code&gt;. For details on the update, see the &lt;a href="https://github.com/ropensci/rnoaa/releases/tag/v0.2.0"&gt;release notes&lt;/a&gt;. What follows are some notes on the more important changes.&lt;/p&gt;
&lt;h2&gt;
Updating to v0.2
&lt;/h2&gt;&lt;p&gt;Install &lt;code&gt;rnoaa&lt;/code&gt; from CRAN&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-r" data-lang="r"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nf"&gt;install.packages&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s"&gt;&amp;#34;rnoaa&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;or Github&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-r" data-lang="r"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="n"&gt;devtools&lt;/span&gt;&lt;span class="o"&gt;::&lt;/span&gt;&lt;span class="nf"&gt;install_github&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s"&gt;&amp;#34;ropensci/rnoaa&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Then load &lt;code&gt;rnoaa&lt;/code&gt;&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-r" data-lang="r"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nf"&gt;library&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s"&gt;&amp;#34;rnoaa&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;h2&gt;
UI changes
&lt;/h2&gt;&lt;p&gt;We changed almost all function names to have a more intuitive programmatic user interface (or &lt;em&gt;UI&lt;/em&gt;).&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;We changed all &lt;code&gt;noaa*()&lt;/code&gt; functions to &lt;code&gt;ncdc*()&lt;/code&gt; - these work only with NOAA National Climatic Data Center (NCDC) data, so the &lt;code&gt;ncdc&lt;/code&gt; name makes sense.&lt;/li&gt;
&lt;li&gt;&lt;code&gt;noaa_seaice()&lt;/code&gt; changed to &lt;code&gt;seaice()&lt;/code&gt;, which works with NOAA sea ice data.&lt;/li&gt;
&lt;li&gt;&lt;code&gt;noaa_swdi()&lt;/code&gt; changed to &lt;code&gt;swdi()&lt;/code&gt;, which works with data from the Severe Weather Data Inventory.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;
Two new data sources
&lt;/h2&gt;&lt;h3&gt;
ERDDAP
&lt;/h3&gt;&lt;p&gt;We added new functions to interact with &lt;a href="https://coastwatch.pfeg.noaa.gov/erddap/index.html"&gt;NOAA ERDDAP data&lt;/a&gt;: &lt;code&gt;erddap_info()&lt;/code&gt;, &lt;code&gt;erddap_data()&lt;/code&gt;, and &lt;code&gt;erddap_search()&lt;/code&gt;. As a quick example, let&amp;rsquo;s search for data, get a dataset identifier, then get information on that dataset, then get the data.&lt;/p&gt;</description></item><item><title>rOpenSci awarded $300k from the Sloan Foundation</title><link>https://ropensci.org/blog/2014/06/10/new-sloan-award/</link><pubDate>Tue, 10 Jun 2014 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2014/06/10/new-sloan-award/</guid><description>
&lt;p&gt;We&amp;rsquo;re delighted to announce that we have received additional funding from the &lt;a href="https://www.sloan.org/"&gt;Sloan Foundation&lt;/a&gt; to &lt;a href="https://ropensci.org/blog/2013/06/12/sloan/"&gt;continue&lt;/a&gt; and expand our efforts from the past year.&lt;/p&gt;
&lt;p&gt;We&amp;rsquo;re grateful for the overwhelming support from the community, especially through engagement at various events we organized and attended this past year. Over the next year we plan to: &lt;strong&gt;advance not only the technical infrastructure for accessing, managing, and synthesizing large and heterogeneous data, but also the social infrastructure of research to facilitate collaboration and exchange of data, methods, and ideas so they can be easily reproduced and extended&lt;/strong&gt;. Over the next several months you can expect to see various tools that allow for seamless data interoperability, a comprehensive spatial and mapping toolkit, and a new suite of tools to support reproducibility.&lt;/p&gt;</description></item><item><title>Reproducible research is still a challenge</title><link>https://ropensci.org/blog/2014/06/09/reproducibility/</link><pubDate>Mon, 09 Jun 2014 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2014/06/09/reproducibility/</guid><description>
&lt;p&gt;Science is reportedly in the middle of a &lt;a href="https://theconversation.com/science-is-in-a-reproducibility-crisis-how-do-we-resolve-it-16998"&gt;reproducibility crisis&lt;/a&gt;. Reproducibility seems laudable and is frequently called for (e.g., &lt;a href="https://www.nature.com/nature/focus/reproducibility/"&gt;nature&lt;/a&gt; and &lt;a href="https://www.sciencemag.org/content/334/6060/1226"&gt;science&lt;/a&gt;). In general the argument is that research that can be independently reproduced is more reliable than research that cannot be independently reproduced. It is also worth noting that reproducing research is not solely a checking process, and it can provide useful jumping-off points for future research questions. It is difficult to find a counter-argument to these claims, but arguing that reproducibility is laudable in general glosses over the fact that for each research group it is a significant amount of work to make their research (easily) reproducible for independent scientists. While much of the attention has focused on &lt;a href="https://www.nature.com/nature/journal/v483/n7391/full/483531a.html"&gt;entirely repeating laboratory experiments&lt;/a&gt;, there are many simpler forms of reproducibility including, for example, the ability to recompute analyses on known sets of data.&lt;/p&gt;</description></item><item><title>taxize v0.3.0 update - a new data source, taxonomy in writing, and uBio examples</title><link>https://ropensci.org/blog/2014/05/20/taxize_v03/</link><pubDate>Tue, 20 May 2014 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2014/05/20/taxize_v03/</guid><description>
&lt;p&gt;We just released &lt;code&gt;v0.3&lt;/code&gt; of &lt;code&gt;taxize&lt;/code&gt;. For details on the update, see the &lt;a href="https://github.com/ropensci/taxize/releases/tag/v0.3.0"&gt;release notes&lt;/a&gt;.&lt;/p&gt;
&lt;h2&gt;
Some new features
&lt;/h2&gt;&lt;ul&gt;
&lt;li&gt;New function &lt;code&gt;iplant_resolve()&lt;/code&gt; to do name resolution using the iPlant name resolution service. Note, this is different from &lt;a href="http://taxosaurus.org/"&gt;http://taxosaurus.org/&lt;/a&gt; that is wrapped in the &lt;code&gt;tnrs()&lt;/code&gt; function.&lt;/li&gt;
&lt;li&gt;New function &lt;code&gt;ipni_search()&lt;/code&gt; to search for names in the International Plant Names Index (IPNI). See below for more.&lt;/li&gt;
&lt;li&gt;New function &lt;code&gt;resolve()&lt;/code&gt; that unifies name resolution services from iPlant&amp;rsquo;s name resolution service (via &lt;code&gt;iplant_resolve()&lt;/code&gt;), Taxosaurus&amp;rsquo; TNRS (via &lt;code&gt;tnrs()&lt;/code&gt;), and GNR&amp;rsquo;s name resolution service (via &lt;code&gt;gnr_resolve()&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;All &lt;code&gt;get_&lt;/code&gt; functions now returning a new &lt;em&gt;uri&lt;/em&gt; attribute that is a link to the taxon on the web. If NA is given back (e.g. nothing found), the uri attribute is blank. You can go directly to the uri in your default browser by doing, for example: &lt;code&gt;browseURL(attr(result, &amp;quot;uri&amp;quot;))&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;
Updating to v0.3
&lt;/h2&gt;&lt;p&gt;Since &lt;code&gt;taxize&lt;/code&gt; is not updated to &lt;code&gt;v0.3&lt;/code&gt; on CRAN yet at the time of writing this, install &lt;code&gt;taxize&lt;/code&gt; from GitHub:&lt;/p&gt;</description></item><item><title>rOpenHack report</title><link>https://ropensci.org/blog/2014/05/14/ropenhack/</link><pubDate>Wed, 14 May 2014 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2014/05/14/ropenhack/</guid><description>
&lt;p&gt;The rOpenSci project is a poster child for the fluid collaboration that has become increasingly common these days thanks to platforms like Twitter and GitHub. It has been really inspring to see open discussions take shape as rough ideas, which rapidly turn into prototype research software, all of which are now happening in the order of few days to weeks rather than months to years. The origins of this project itself lead back to a series of serendipitous conversations that occurred over Twitter three years ago. Today we are a rapidly growing community of scientists, students, software developers, and information researchers.&lt;/p&gt;</description></item><item><title>Overlaying species occurrence data with climate data</title><link>https://ropensci.org/blog/2014/04/22/rwbclimate-sp/</link><pubDate>Tue, 22 Apr 2014 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2014/04/22/rwbclimate-sp/</guid><description>
&lt;p&gt;One of the goals of the rOpenSci is to facilitate interoperability between different data sources around web with our tools. We can achieve this by providing functionality within our packages that converts data coming down via web APIs in one format (often a provider specific schema) into a standard format. The new version of &lt;a href="https://github.com/ropensci/rwbclimate"&gt;rWBclimate&lt;/a&gt; that we just posted to &lt;a href="https://cran.r-project.org/web/packages/rWBclimate/index.html"&gt;CRAN&lt;/a&gt; does just that. In an &lt;a href="https://www.ropensci.org/blog/2013/07/29/rWBclimate-rgbif/"&gt;earlier post&lt;/a&gt; I wrote about how users could combine data from both &lt;a href="https://github.com/ropensci/rgbif"&gt;rgbif&lt;/a&gt; and &lt;code&gt;rWBclimate&lt;/code&gt;. Back then I just thought it was pretty cool that you could overlay the points on a nice climate map. Now we&amp;rsquo;ve come a long way, with the development of an easier to use and more comprehensive package for accessing species occurrence data, &lt;a href="https://github.com/ropensci/spocc"&gt;spocc&lt;/a&gt;, and added conversion functions to create spatial objects out of both climate data maps, and species occurrence data. The result is that you can grab data from both sources, and then extract climate information about your species occurrence data.&lt;/p&gt;</description></item><item><title>Make your ggplots shareable, collaborative, and with D3</title><link>https://ropensci.org/blog/2014/04/17/plotly/</link><pubDate>Thu, 17 Apr 2014 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2014/04/17/plotly/</guid><description>
&lt;p&gt;&lt;em&gt;Editor&amp;rsquo;s note: This is a guest post by Matt Sundquist from &lt;a href="https://plot.ly/"&gt;Plot.ly&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://github.com/ropensci/plotly"&gt;Ggplotly&lt;/a&gt; and &lt;a href="https://plot.ly/r/"&gt;Plotly&amp;rsquo;s R API&lt;/a&gt; let you make ggplot2 plots, add &lt;code&gt;py$ggplotly()&lt;/code&gt;, and make your plots interactive, online, and drawn with D3. Let&amp;rsquo;s make some.&lt;/p&gt;
&lt;h2&gt;
1. Getting Started and Examples
&lt;/h2&gt;&lt;p&gt;Here is Fisher&amp;rsquo;s iris data.&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-r" data-lang="r"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nf"&gt;library&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s"&gt;&amp;#34;ggplot2&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="n"&gt;ggiris&lt;/span&gt; &lt;span class="o"&gt;&amp;lt;-&lt;/span&gt; &lt;span class="nf"&gt;qplot&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;Petal.Width&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;Sepal.Length&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;data&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;iris&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;color&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;Species&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nf"&gt;print&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;ggiris&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;&lt;img src="https://ropensci.org/assets/blog-images/2014-04-17-plotly/unnamed-chunk-2.png" alt=""&gt;&lt;/p&gt;
&lt;p&gt;Let&amp;rsquo;s make it in Plotly. Install:&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-r" data-lang="r"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nf"&gt;install.packages&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s"&gt;&amp;#34;devtools&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nf"&gt;library&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s"&gt;&amp;#34;devtools&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nf"&gt;install_github&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s"&gt;&amp;#34;plotly&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s"&gt;&amp;#34;ropensci&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Load.&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-r" data-lang="r"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nf"&gt;library&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s"&gt;&amp;#34;plotly&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;pre tabindex="0"&gt;&lt;code&gt;## Loading required package: RCurl
## Loading required package: bitops
## Loading required package: RJSONIO
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;Sign up &lt;a href="https://plot.ly"&gt;online&lt;/a&gt;, use our public keys below, or sign up like this:&lt;/p&gt;</description></item><item><title>Topic modeling in R</title><link>https://ropensci.org/blog/2014/04/16/topic-modeling-in-r/</link><pubDate>Wed, 16 Apr 2014 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2014/04/16/topic-modeling-in-r/</guid><description>
&lt;p&gt;&lt;em&gt;Editor&amp;rsquo;s note: This is the first in a series of posts from rOpenSci&amp;rsquo;s &lt;a href="https://ropensci.org/blog/2014/05/14/ropenhack//"&gt;recent hackathon&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;I recently had the pleasure of participating in &lt;a href="https://github.com/ropensci/hackathon/"&gt;rOpenSci&amp;rsquo;s hackathon&lt;/a&gt;. To be honest, I was quite nervous to work among such notables, but I immediately felt welcome thanks to a warm and personable group. &lt;a href="http://alyssafrazee.com/"&gt;Alyssa Frazee&lt;/a&gt; has a &lt;a href="https://simplystatistics.org/2014/04/10/the-ropensci-hackathon-ropenhack/"&gt;great post summarizing the event&lt;/a&gt;, so check that out if you haven&amp;rsquo;t already. Once again, many thanks to rOpenSci for making it possible!&lt;/p&gt;</description></item><item><title>The ins and outs of interacting with web APIs</title><link>https://ropensci.org/blog/2014/04/14/webapis/</link><pubDate>Mon, 14 Apr 2014 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2014/04/14/webapis/</guid><description>
&lt;p&gt;We&amp;rsquo;ve received a number of questions from our users about dealing with the finer details of data sources on the web. Whether you&amp;rsquo;re reading data from local storage such as a csv file, a &lt;code&gt;.Rdata&lt;/code&gt; store, or possibly a proprietary file format, you&amp;rsquo;ve most likely run into some issues in the past. Common problems include passing incorrect paths, files being too big for memory, or requiring several packages to read files in incompatible formats. Reading data from the web entails a whole other set of challenges. Although there are many ways to obtain data from the web, this post primarily deals with retrieving data from Application Programming Interfaces also known as APIs.&lt;/p&gt;</description></item><item><title>Accessing iNaturalist data</title><link>https://ropensci.org/blog/2014/03/26/rinat/</link><pubDate>Wed, 26 Mar 2014 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2014/03/26/rinat/</guid><description>
&lt;p&gt;The &lt;a href="https://www.inaturalist.org/"&gt;iNaturalist&lt;/a&gt; project is a really cool way to both engage people in citizen science and collect species occurrence data. The premise is pretty simple, users download an app for their smartphone, and then can easily geo reference any specimen they see, uploading it to the iNaturalist website. It let&amp;rsquo;s users turn casual observations into meaningful crowdsourced species occurrence data. They also provide a nice robust API to access almost all of their data. We&amp;rsquo;ve developed a package &lt;a href="https://github.com/ropensci/rinat"&gt;&lt;code&gt;rinat&lt;/code&gt;&lt;/a&gt; that can easily access all of that data in R. Our package &lt;a href="https://github.com/ropensci/spocc"&gt;&lt;code&gt;spocc&lt;/code&gt;&lt;/a&gt; uses iNaturalist data as one of it&amp;rsquo;s sources, &lt;code&gt;rinat&lt;/code&gt; provides an interface for all the features available in the API.&lt;/p&gt;</description></item><item><title>Species occurrence data</title><link>https://ropensci.org/blog/2014/03/17/spocc/</link><pubDate>Mon, 17 Mar 2014 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2014/03/17/spocc/</guid><description>
&lt;div class="alert alert-info" role="alert"&gt;
UPDATE: mapping functions are in a separate package now (&lt;a href="https://cran.rstudio.com/web/packages/mapr"&gt;mapr&lt;/a&gt;). Examples that do mapping below have been updated.
&lt;/div&gt;
&lt;p&gt;The rOpenSci projects aims to provide programmatic access to scientific data repositories on the web. A vast majority of the packages in our current suite retrieve some form of biodiversity or taxonomic data. Since several of these datasets have been georeferenced, it provides numerous opportunities for visualizing species distributions, building species distribution maps, and for using it analyses such as species distribution models. In an effort to streamline access to these data, we have developed a package called Spocc, which provides a unified API to all the biodiversity sources that we provide. The obvious advantage is that a user can interact with a common API and not worry about the nuances in syntax that differ between packages. As more data sources come online, users can access even more data without significant changes to their code. However, it is important to note that spocc will never replicate the full functionality that exists within specific packages. Therefore users with a strong interest in one of the specific data sources listed below would benefit from familiarising themselves with the inner working of the appropriate packages.&lt;/p&gt;</description></item><item><title>rnoaa - Access to NOAA National Climatic Data Center data</title><link>https://ropensci.org/blog/2014/03/13/rnoaa/</link><pubDate>Thu, 13 Mar 2014 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2014/03/13/rnoaa/</guid><description>
&lt;p&gt;We recently pushed the first version of &lt;code&gt;rnoaa&lt;/code&gt; to CRAN - version 0.1. NOAA has a lot of data, some of which is provided via the &lt;a href="https://www.ncdc.noaa.gov//"&gt;National Climatic Data Center&lt;/a&gt;, or NCDC. NOAA has provided access to NCDC climate data via a RESTful API - which is great because people like us can create clients for different programming languages to access their data programatically. If you are so inclined to write a bit of R code, this means you can get to NCDC data in the R environment where your workflow is reproducible, and you can connect data acquisition to a suite of tools for data manipulation (e.g., &lt;code&gt;plyr&lt;/code&gt;), visualization (e.g., &lt;code&gt;ggplot2&lt;/code&gt;), and statistics (e.g., &lt;code&gt;lme4&lt;/code&gt;, etc.).&lt;/p&gt;</description></item><item><title>dvn - Sharing Reproducible Research from R</title><link>https://ropensci.org/blog/2014/02/20/dvn-dataverse-network/</link><pubDate>Thu, 20 Feb 2014 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2014/02/20/dvn-dataverse-network/</guid><description>
&lt;p&gt;Reproducible research involves the careful, annotated preservation of data, analysis code, and associated files, such that statistical procedures, output, and published results can be directly and fully replicated. As the push for reproducible research has grown, the R community has responded with an increasingly large set of tools for engaging in reproducible research practices (see, for example, the &lt;a href="https://cran.r-project.org/web/views/ReproducibleResearch.html"&gt;ReproducibleResearch Task View&lt;/a&gt; on CRAN). Most of these tools focus on improving one&amp;rsquo;s own workflow through closer integration of data analysis and report generation. But reproducible research also requires the persistent - and perhaps indefinite - storage of research files so that they can be used to recreate or modify future analyses and reports.&lt;/p&gt;</description></item><item><title>New features in the most recent taxize update, v0.2</title><link>https://ropensci.org/blog/2014/02/19/taxize-update/</link><pubDate>Wed, 19 Feb 2014 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2014/02/19/taxize-update/</guid><description>
&lt;p&gt;We just released a new version of &lt;code&gt;taxize&lt;/code&gt; - version 0.2.0. This release contains a number of new features, and bug fixes. Here is a run down of some of the changes:&lt;/p&gt;
&lt;h2&gt;
First, install and load taxize
&lt;/h2&gt;&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-r" data-lang="r"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nf"&gt;install.packages&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s"&gt;&amp;#34;rgbif&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-r" data-lang="r"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nf"&gt;library&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;taxize&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;h2&gt;
New things
&lt;/h2&gt;&lt;h3&gt;
New functions: class2tree
&lt;/h3&gt;&lt;p&gt;Sometimes you just want to have a visual of the taxonomic relationships among taxa. If you don&amp;rsquo;t know how to build a molecular phylogeny, don&amp;rsquo;t have time, or there just isn&amp;rsquo;t molecular data, you can sorta build one using taxonomy. Building on our &lt;code&gt;classification&lt;/code&gt; function, you can get a bunch of taxonomic hierarchies from the &lt;code&gt;classification&lt;/code&gt; function, then pass them to the new function &lt;code&gt;class2tree&lt;/code&gt;. Like so:&lt;/p&gt;</description></item><item><title>AntWeb - programmatic interface to ant biodiversity data</title><link>https://ropensci.org/blog/2014/02/18/antweb/</link><pubDate>Tue, 18 Feb 2014 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2014/02/18/antweb/</guid><description>
&lt;!-- &lt;div class="alert alert-info" role="alert"&gt;
This post was updated on August 20, 2014, with &lt;code&gt;AntWeb&lt;/code&gt; version &lt;code&gt;0.7.2.99&lt;/code&gt;. Please install an updated version to make sure the code works.
&lt;/div&gt; --&gt;
&lt;blockquote&gt;
&lt;p&gt;This post was updated on August 20, 2014, with &lt;code&gt;AntWeb&lt;/code&gt; version &lt;code&gt;0.7.2.99&lt;/code&gt;. Please install an updated version to make sure the code works.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;&lt;img src="https://ropensci.org/assets/blog-images/2014-02-18-antweb/casent0003205_h_1_high.jpg" alt=""&gt;&lt;/p&gt;
&lt;p&gt;Data on more than &lt;code&gt;10,000&lt;/code&gt; species of ants recorded worldwide are available through from &lt;a href="https://www.calacademy.org/"&gt;California Academy of Sciences&lt;/a&gt;&amp;rsquo; &lt;a href="https://www.antweb.org/"&gt;AntWeb&lt;/a&gt;, a repository that boasts a wealth of natural history data, digital images, and specimen records on ant species from a large community of museum curators.&lt;/p&gt;</description></item><item><title>Changed and new things in the new version of rgbif, v0.5</title><link>https://ropensci.org/blog/2014/02/17/rgbif-update/</link><pubDate>Mon, 17 Feb 2014 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2014/02/17/rgbif-update/</guid><description>
&lt;p&gt;&lt;code&gt;rgbif&lt;/code&gt; is an R package to search and retrieve data from the Global Biodiverity Information Facilty (GBIF). &lt;code&gt;rgbif&lt;/code&gt; wraps R code around the [GBIF API][gbifapi] to allow you to talk to GBIF from R.&lt;/p&gt;
&lt;p&gt;We just pushed a new verion of &lt;code&gt;rgbif&lt;/code&gt; to cran - v0.5.0. Source and binary files are now available on CRAN.&lt;/p&gt;
&lt;p&gt;There are a few new functions: &lt;code&gt;count_facet&lt;/code&gt;, &lt;code&gt;elevation&lt;/code&gt;, and &lt;code&gt;installations&lt;/code&gt;. These are described, with examples, below.&lt;/p&gt;</description></item><item><title>Caching Encyclopedia of Life API calls</title><link>https://ropensci.org/blog/2014/02/12/caching-with-api/</link><pubDate>Wed, 12 Feb 2014 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2014/02/12/caching-with-api/</guid><description>
&lt;p&gt;In &lt;a href="https://ropensci.org/blog/2014/02/03/caching-offline/"&gt;a recent blog post&lt;/a&gt; we discussed caching calls to the web offline, on your own computer. Just like you can cache data on your own computer, a data provider can do the same thing. Most of the data providers we work with do not provide caching. However, at least one does: &lt;a href="https://eol.org/"&gt;EOL&lt;/a&gt;, or Encyclopedia of Life. EOL allows you to set the amount of time (in seconds) that the call is cached, within which time you can make the same call and get the data back faster. We have a number of functions to interface with EOL in our &lt;code&gt;taxize&lt;/code&gt; package.&lt;/p&gt;</description></item><item><title>rOpenSci developer meeting in March</title><link>https://ropensci.org/blog/2014/02/10/ropensci-hackathon/</link><pubDate>Mon, 10 Feb 2014 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2014/02/10/ropensci-hackathon/</guid><description>
&lt;p&gt;Our team has been cranking out a large number of tools over the past several months. As regular readers are aware, our software packages provide programmatic access to a diverse and extensive trove of scientific data. More recently we’ve expanded our efforts to build more general purpose and cross-domain tools. These include tools for reading, writing, integrating and publishing data, a unit testing platform for data, and a mapping engine that can visualize various kinds of spatial data. Many of our projects are inspired by ad hoc discussions with other scientists and software developers both online (often on &lt;a href="https://twitter.com/ropensci"&gt;Twitter&lt;/a&gt; and &lt;a href="https://github.com/ropensci"&gt;GitHub&lt;/a&gt;) and offline. Several of these folks are now &lt;a href="https://ropensci.org/community/"&gt;regular contributors&lt;/a&gt; to the project. To foster more such collaborations and drive new software innovations, we are excited to announce our first developer meeting next month at GitHub’s headquarters in San Francisco. This meeting is made possible by support from the Alfred P. Sloan foundation and GitHub.&lt;/p&gt;</description></item><item><title>Caching API calls offline</title><link>https://ropensci.org/blog/2014/02/03/caching-offline/</link><pubDate>Mon, 03 Feb 2014 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2014/02/03/caching-offline/</guid><description>
&lt;p&gt;I&amp;rsquo;ve recently heard the idea of &amp;ldquo;offline first&amp;rdquo; via especially &lt;a href="http://hood.ie/"&gt;Hood.ie&lt;/a&gt;. We of course don&amp;rsquo;t do web development, but primarily build R interfaces to data on the web. Internet availablility is increasinghly ubiqutous, but there still are times and places where you don&amp;rsquo;t have internet, but need to get work done.&lt;/p&gt;
&lt;p&gt;In the R packages we write there are generally two steps to every workflow:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Make a call to the web to request data and collect data&lt;/li&gt;
&lt;li&gt;Rearrange the result as some sort of R object (e.g., an R &lt;code&gt;data.frame&lt;/code&gt;), then visualize, analyze, etc.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;The first process is not possible if you don&amp;rsquo;t have an internet connection - making the second step fail as a result.&lt;/p&gt;</description></item><item><title>Introducing the ecoengine package</title><link>https://ropensci.org/blog/2014/01/30/ecoengine/</link><pubDate>Thu, 30 Jan 2014 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2014/01/30/ecoengine/</guid><description>
&lt;p&gt;Natural history museums have long been valuable repositories of data on species diversity. These data have been critical for fostering and shaping the development of fields such as biogeography and systematics. The importance of these data repositories is becoming increasingly important, especially in the context of climate change, where a strong understanding of how species responded to past climate is key to understanding their responses in the future. Leading the way in opening up such valuable data is a new effort by the &lt;a href="https://globalchange.berkeley.edu/ecoinformatics-engine"&gt; Berkeley Initiative in Global Change Biology&lt;/a&gt; called the &lt;a href="https://ecoengine.berkeley.edu/"&gt;Ecoengine&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>solr - an R interface to Solr</title><link>https://ropensci.org/blog/2014/01/27/solr/</link><pubDate>Mon, 27 Jan 2014 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2014/01/27/solr/</guid><description>
&lt;p&gt;A number of the APIs we interact with (e.g., PLOS full text API, and USGS&amp;rsquo;s BISON API in &lt;a href="https://cran.r-project.org/web/packages/rplos/index.html"&gt;rplos&lt;/a&gt; and &lt;a href="https://cran.r-project.org/web/packages/rbison/index.html"&gt;rbison&lt;/a&gt;, respectively) expose &lt;a href="https://lucene.apache.org/solr/"&gt;Solr&lt;/a&gt; endpoints. &lt;a href="https://lucene.apache.org/solr/"&gt;Solr&lt;/a&gt; is an Apache hosted project - it is a powerful search server. Given that at least two, and possibly more in the future, of the data providers we interact with provide Solr endpoints, it made sense to create an R package to make robust functions to interact with Solr that work across any Solr endpoint. This is then useful to us, and hopefully others.&lt;/p&gt;</description></item><item><title>Highlighting text in text mining</title><link>https://ropensci.org/blog/2013/12/02/rplos-highlights/</link><pubDate>Mon, 02 Dec 2013 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2013/12/02/rplos-highlights/</guid><description>
&lt;p&gt;&lt;code&gt;rplos&lt;/code&gt; is an R package to facilitate easy search and full-text retrieval from all Public Library of Science (PLOS) articles, and we have a little feature which aren&amp;rsquo;t sure if is useful or not. I don&amp;rsquo;t actually do any text-mining for my research, so perhaps text-mining folks can give some feedback.&lt;/p&gt;
&lt;p&gt;You can quickly get a lot of results back using &lt;code&gt;rplos&lt;/code&gt;, so perhaps it is useful to quickly browse what you got. What better tool than a browser to browse? Enter &lt;code&gt;highplos&lt;/code&gt; and &lt;code&gt;highbrow&lt;/code&gt;. &lt;code&gt;highplos&lt;/code&gt; uses the &lt;a href="https://lucene.apache.org/solr/"&gt;Solr&lt;/a&gt; capabilities of the PLOS search API, and lets you get back a string with the term you searched for highlighted (by default with &lt;code&gt;&amp;lt;em&amp;gt;&lt;/code&gt; tag for italics).&lt;/p&gt;</description></item><item><title>Open Science with R</title><link>https://ropensci.org/blog/2013/12/02/open-science-with-r/</link><pubDate>Mon, 02 Dec 2013 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2013/12/02/open-science-with-r/</guid><description>
&lt;p&gt;&lt;strong&gt;Upcoming Book on Open Science with R&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;We&amp;rsquo;re pleased to announce that the rOpenSci core team has just signed a contract with &lt;a href="https://www.crcpress.com/go/the-r-series/"&gt;CRC Press/Taylor and Francis R series&lt;/a&gt; to publish a new book on practical ways to implement open science into your own research using R. Given all the talk about the importance of open science, the discussion often lacks practical suggestions on how one might actually incorporate these practices into their day to day research workflow.&lt;/p&gt;</description></item><item><title>rgbif changes in v0.4</title><link>https://ropensci.org/blog/2013/11/21/rgbif-changes/</link><pubDate>Thu, 21 Nov 2013 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2013/11/21/rgbif-changes/</guid><description>
&lt;p&gt;The Global Biodiversity Information Facility (GBIF) is a warehouse of species occurrence data - collecting data from a lot of different sources. Our package &lt;code&gt;rgbif&lt;/code&gt; allows you to interact with GBIF from R. We interact with GBIF via their Application Programming Interface, or API. Our last version on CRAN (v0.3) interacted with the older version of their API - this version interacts with the new version of their API. However, we also retained functions that interact with the old API.&lt;/p&gt;</description></item><item><title>taxize changes</title><link>https://ropensci.org/blog/2013/11/19/taxize-changes/</link><pubDate>Tue, 19 Nov 2013 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2013/11/19/taxize-changes/</guid><description>
&lt;p&gt;We are building a taxonomic toolbelt for R called taxize - which gives you programmatic access to many sources of taxonomic data on the web. We just pushed a new version to &lt;a href="https://cran.r-project.org/web/packages/taxize/index.html"&gt;CRAN (v0.1.5)&lt;/a&gt; with a lot of changes (see &lt;a href="https://github.com/ropensci/taxize#notes-on-the-itis-api"&gt;here&lt;/a&gt; for a rundown). Here are a few highlights of the changes.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Note: the windows binary may not be available yet&amp;hellip;&lt;/em&gt;&lt;/p&gt;
&lt;hr&gt;
&lt;h2&gt;
Install and load taxize
&lt;/h2&gt;&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-r" data-lang="r"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nf"&gt;install.packages&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s"&gt;&amp;#34;taxize&amp;#34;&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nf"&gt;library&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;taxize&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;hr&gt;
&lt;h2&gt;
Taxonomic identifiers
&lt;/h2&gt;&lt;p&gt;Each taxonomic service has their own unique ID for a taxon. We had a way to get ITIS and NCBI identifiers before - we now have functions for Tropicos, EOL, and the Catalogue of Life.&lt;/p&gt;</description></item><item><title>Species occurrence data to CartoDB</title><link>https://ropensci.org/blog/2013/11/04/data-to-cartodb/</link><pubDate>Mon, 04 Nov 2013 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2013/11/04/data-to-cartodb/</guid><description>
&lt;p&gt;We have previously written about creating interactive maps on the web from R, with the interactive maps on Github. See &lt;a href="https://ropensci.org/blog/2013/10/23/style-geojson-polygon/"&gt;here&lt;/a&gt;, &lt;a href="https://ropensci.org/blog/2013/07/17/style-geojson/"&gt;here&lt;/a&gt;, &lt;a href="https://ropensci.org/blog/2013/07/04/rbison-geoson/"&gt;here&lt;/a&gt;, and &lt;a href="https://recology.info/2013/06/geojson/"&gt;here&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;A different approach is to use &lt;a href="https://cartodb.com/"&gt;CartoDB&lt;/a&gt;, &lt;a href="https://cartodb.com/pricing/"&gt;a freemium service&lt;/a&gt; with sql interface to your data tables that provides a map to visualize data in those tables. They released an R interace to their sql API &lt;a href="https://github.com/Vizzuality/cartodb-r"&gt;on Github here&lt;/a&gt; - which we can use to make an interactive map from R.&lt;/p&gt;
&lt;p&gt;We&amp;rsquo;ll first get some data from GBIF, ~500 occurrences of &lt;em&gt;Puma concolor&lt;/em&gt; in the US, then push that data to a CartoDB table. There are a couple more non-programmatic steps in this workflow than with pushing geojson file to Github as outlined in the previous linked above (i.e., going to the CartoDB site and making a visualization, and making it public).&lt;/p&gt;</description></item><item><title>Interactive maps with polygons using R, Geojson, and Github</title><link>https://ropensci.org/blog/2013/10/23/style-geojson-polygon/</link><pubDate>Wed, 23 Oct 2013 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2013/10/23/style-geojson-polygon/</guid><description>
&lt;p&gt;Previously on this blog we have discussed making geojson maps and uploading to Github for interactive visualization &lt;a href="https://ropensci.org/blog/2013/07/04/rbison-geoson/"&gt;with USGS BISON data&lt;/a&gt;, and &lt;a href="https://ropensci.org/blog/2013/07/17/style-geojson/"&gt;with GBIF data&lt;/a&gt;, and on &lt;a href="https://sckott.github.io/2013/06/geojson/"&gt;my own personal blog&lt;/a&gt;. This is done using a file format called &lt;a href="https://en.wikipedia.org/wiki/GeoJSON"&gt;&lt;em&gt;geojson&lt;/em&gt;&lt;/a&gt;, a file format based on JSON (JavaScript Object Notation) in which you can specify geographic data along with any other metadata.&lt;/p&gt;
&lt;p&gt;In two the previous posts about &lt;em&gt;geojson&lt;/em&gt;, I described how you could get data from the USGS BISON API using our &lt;a href="https://github.com/ropensci/rbison"&gt;rbison package&lt;/a&gt;, and from the GBIF API using the &lt;a href="https://github.com/ropensci/rgbif"&gt;rgbif package&lt;/a&gt;, then make a &lt;em&gt;geojson&lt;/em&gt; file, and send to Github. In both examples, the data were points. What about polygons? This is a relatively common use case in which an area is defined on a map instead of points - and polygons are supported in geojson. How do we do this with the R to geojson to Github workflow?&lt;/p&gt;</description></item><item><title>OA week - A simple use case for programmatic access to PLOS full text</title><link>https://ropensci.org/blog/2013/10/22/oaweek-rplos/</link><pubDate>Tue, 22 Oct 2013 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2013/10/22/oaweek-rplos/</guid><description>
&lt;p&gt;Open access week is here! We love open access, and think it&amp;rsquo;s extremely important to publish in open access journals. One of the many benefits of open access literature is that we likely can use the text of articles in OA journals for many things, including text-mining.&lt;/p&gt;
&lt;p&gt;What&amp;rsquo;s even more awesome is some OA publishers provide API (application programming interface) access to their full text articles. Public Library of Science (PLOS) is one of these. We have had an R package for a while now that makes it convenient to search PLOS full text programatically. You can search on specific parts of articles (e.g., just in titles, or just in results sections), and you can return specific parts of articles (e.g., just abstracts). There are additional options for more fine-grained control over searches like facetting.&lt;/p&gt;</description></item><item><title>Altmetrics workshop recap</title><link>https://ropensci.org/blog/2013/10/15/altmetrics-conf/</link><pubDate>Tue, 15 Oct 2013 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2013/10/15/altmetrics-conf/</guid><description>
&lt;p&gt;I attended the recent &lt;a href="https://www.lagotto.io/workshop_2013//"&gt;ALM Workshop 2013&lt;/a&gt; and &lt;a href="https://almdatachallenge.eventbrite.com/"&gt;data challenge&lt;/a&gt; hosted by Public Library of Science (PLOS) in San Francisco. The workshop covered various issues having to do with altmetrics, or article-level metrics (ALM). The same workshop last year definitely had a feeling of &lt;strong&gt;we don&amp;rsquo;t know x, y, and z&lt;/strong&gt;, while the workshop this year felt like we know a lot more. There were many great talks - you can see the list of speakers &lt;a href="http://www.lagotto.io/workshop_2013/-preliminary-program/"&gt;here&lt;/a&gt;. I was there representing rOpenSci as altmetrics is one of the types of data for which we make R libraries (&lt;a href="https://github.com/ropensci/raltmetric"&gt;rAltmetric&lt;/a&gt; for Altmetric.com data, and &lt;a href="https://github.com/ropensci/alm"&gt;alm&lt;/a&gt; for the PLOS altmetrics data).&lt;/p&gt;</description></item><item><title>Guide to using rOpenSci packages during the US Gov't shutdown</title><link>https://ropensci.org/blog/2013/10/08/shutdown/</link><pubDate>Tue, 08 Oct 2013 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2013/10/08/shutdown/</guid><description>
&lt;p&gt;With the US government shut down, many of the federal government provided data APIs are down. We write R packages to interact with many of these APIs. We have been tweeting about what APIs that are down related to R pacakges we make, but we thought we would write up a proper blog post on the issue.&lt;/p&gt;
&lt;p&gt;NCBI services are still up! NCBI is within NIH, which is within the Department of Health and Human Services. Here is the message on the NCBI page:&lt;/p&gt;</description></item><item><title>A new tutorials setup</title><link>https://ropensci.org/blog/2013/10/03/tutorials/</link><pubDate>Thu, 03 Oct 2013 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2013/10/03/tutorials/</guid><description>
&lt;p&gt;To help you use rOpenSci packages we put tutorials up on our site at &lt;a href="https://ropensci.org/tutorials"&gt;/tutorials&lt;/a&gt;. Up to now, we created them with combination of raw html + converting code blocks to html and inserting them, etc. &amp;ndash; it was a slow process to update them when changes happened in our packages.&lt;/p&gt;
&lt;p&gt;So we thought of a better plan&amp;hellip;&lt;/p&gt;
&lt;p&gt;Recently CRAN started accepting R package vignettes (basically, tutorials built in to packages) in R Markdown format. This is great because executable Markdown with code plus text is easy to do with the help of &lt;a href="https://yihui.name/knitr/"&gt;knitr&lt;/a&gt;. And since our website is created using Jekyll, we can take our package vignettes with only text and code as a .Rmd file, convert to a .md file with text + code + the output of that code, insert some yaml metadata at the top, and have Jekyll automagically generate html pages. This may sound complicated, but once we have the vignette in a package, it&amp;rsquo;s just a few lines of code away from generating the html page for this site.&lt;/p&gt;</description></item><item><title>Web Technologies and Services taskview is up on CRAN</title><link>https://ropensci.org/blog/2013/10/03/uptaskview/</link><pubDate>Thu, 03 Oct 2013 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2013/10/03/uptaskview/</guid><description>
&lt;p&gt;Just a quick note that the Task View we have been working on with others &lt;strong&gt;Web Technologies and Services&lt;/strong&gt; is up on CRAN now. Find it here &lt;a href="https://cran.r-project.org/web/views/WebTechnologies.html"&gt;https://cran.r-project.org/web/views/WebTechnologies.html&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;This is the first version - there are definitely changes to come. Changes are being suggested as I write this on Twitter&amp;hellip;&lt;/p&gt;
&lt;p&gt;The draft version of the task view is on Github &lt;a href="https://github.com/ropensci/webservices"&gt;here&lt;/a&gt; if you want to &lt;a href="https://github.com/ropensci/webservices/issues"&gt;file an issue&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;We use many packages to do stuff with the web like XML, RCurl, httr, RJSONIO, etc., and we create many packages that grab data from the web. So it made a lot of sense to work on this task view. We hope it is a good resource for everyone.&lt;/p&gt;</description></item><item><title>A task view for interacting with the web from R</title><link>https://ropensci.org/blog/2013/09/11/taskview/</link><pubDate>Wed, 11 Sep 2013 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2013/09/11/taskview/</guid><description>
&lt;p&gt;There is an increasing set of R packages for interacting with the web from R, whether it be the low level tools to interact with the web via http (see &lt;a href="https://cran.r-project.org/web/packages/RCurl/index.html"&gt;RCurl&lt;/a&gt; and &lt;a href="https://cran.r-project.org/web/packages/httr/index.html"&gt;httr&lt;/a&gt;), parsing data from the web (like &lt;a href="https://cran.r-project.org/web/packages/RJSONIO/index.html"&gt;RJSONIO&lt;/a&gt; and &lt;a href="https://cran.r-project.org/web/packages/XML/index.html"&gt;XML&lt;/a&gt;), or wrappers to web APIs that provide data (like &lt;a href="https://cran.r-project.org/web/packages/twitteR/index.html"&gt;twitteR&lt;/a&gt;).&lt;/p&gt;
&lt;p&gt;Most of you probably know about &lt;a href="https://cran.r-project.org/web/views/"&gt;CRAN Task Views&lt;/a&gt; that aggregate information about R packages and functions on a particular subject area into a simple web page. There isn&amp;rsquo;t one for interacting with the web, so we have started drafting one on Github, and it is below.&lt;/p&gt;</description></item><item><title>Use cases as an interface to tool discovery</title><link>https://ropensci.org/blog/2013/09/10/usecases/</link><pubDate>Tue, 10 Sep 2013 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2013/09/10/usecases/</guid><description>
&lt;p&gt;Good discovery tools for sotware are important as they can facilitate the pace of software development, bugs are found and squashed and new features added more quickly, and users find software they need faster. We have a page on our website for &lt;a href="https://ropensci.org/packages/"&gt;our packages&lt;/a&gt; that provides an overview of the packages we have, with descriptions and links.&lt;/p&gt;
&lt;p&gt;Two other ways to discover things include&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;A gallery of examples, or use cases, in which the entry point is something someone would want to do. This is opposed to a list of software packages in which the entry point is a description of what the package does. Examples include the &lt;a href="https://gallery.rcpp.org/"&gt;Rcpp gallery&lt;/a&gt;, &lt;a href="http://www.sr.bham.ac.uk/~ajrs/R/r-gallery.html"&gt;R graph gallery&lt;/a&gt;, and &lt;a href="https://nbviewer.ipython.org/"&gt;the iPython Notebook Viewer gallery&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Images: Scrolling through images is a fast way to select an item of interest.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;We just rolled out a new page for user stories, or use cases, organized in an gallery of thumbnail images with a brief description, which goes to another page with a brief script and output. &lt;a href="https://ropensci.org/usecases/"&gt;Check it out&lt;/a&gt;. On this page we are gathering brief examples of tasks scientists can carry out in R. So far these include:&lt;/p&gt;</description></item><item><title>Working with climate data from the web in R</title><link>https://ropensci.org/blog/2013/08/18/sciordata/</link><pubDate>Sun, 18 Aug 2013 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2013/08/18/sciordata/</guid><description>
&lt;p&gt;I recently attended &lt;a href="https://scioclimate.wikispaces.com"&gt;ScienceOnline Climate&lt;/a&gt;, a conference in Washington, D.C. at AAAS. You may have heard of the &lt;a href="https://twitter.com/#sciox"&gt;ScienceOnline annual meeting in North Carolina&lt;/a&gt; - this was one of their topical meetings focused on Climate Change. I moderated a session on &lt;a href="https://scioclimate.wikispaces.com/3W.+Working+With+Science+Data+From+Around+The+Web"&gt;working with data from the web in R&lt;/a&gt;, focusing on climate data. Search Twitter for #scioClimate for tweets from the conference, and #sciordata for tweets from the session I ran. The following is an abbreviated demo of what I did in the workshop showing some of what you can do with climate data in R using our packages.&lt;/p&gt;</description></item><item><title>NOAA climate sparklines</title><link>https://ropensci.org/blog/2013/08/05/noaa-sparklines/</link><pubDate>Mon, 05 Aug 2013 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2013/08/05/noaa-sparklines/</guid><description>
&lt;p&gt;We have started a new R package interacting with NOAA climate data called &lt;strong&gt;rnoaa&lt;/strong&gt;. You can find our package in development &lt;a href="https://github.com/ropensci/rnoaa"&gt;here&lt;/a&gt; and documentation for NOAA web services &lt;a href="https://www.ncdc.noaa.gov/cdo-web/webservices"&gt;here&lt;/a&gt;. It is still early days for this package, but we wanted to demo what you can do with the package.&lt;/p&gt;
&lt;p&gt;In this example, we search for stations that collect climate data, then get the data for those stations, pull out only the precipitation data, then get latitude/longitude coordinates for each station, and plot data on a map.&lt;/p&gt;</description></item><item><title>Consuming article-level metrics</title><link>https://ropensci.org/blog/2013/08/01/altmetrics/</link><pubDate>Thu, 01 Aug 2013 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2013/08/01/altmetrics/</guid><description>
&lt;p&gt;We recently had a paper come out in &lt;a href="https://www.niso.org/niso-io/isq/2013/06/information-standards-quarterly-summer-2013"&gt;a special issue&lt;/a&gt; on &lt;em&gt;article-level metrics&lt;/em&gt; in the journal Information Standards Quarterly. Our paper basically compared article-level metrics provided by different aggregators. The other papers covered various article-level metrics topics from folks at PLOS, Mendeley, and more. &lt;a href="https://www.niso.org/niso-io/isq/2013/06/information-standards-quarterly-summer-2013/chamberlain"&gt;Get our paper&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;To get data from the &lt;em&gt;article-level metrics&lt;/em&gt; providers we used one R package we created to get DOIs for PLOS articles (&lt;a href="https://github.com/ropensci/rplos"&gt;rplos&lt;/a&gt;) and three R packages we created to get metrics: &lt;a href="https://github.com/ropensci/alm"&gt;alm&lt;/a&gt;, &lt;a href="https://github.com/ropensci/rimpactstory"&gt;rImpactStory&lt;/a&gt;, and &lt;a href="https://github.com/ropensci/rAltmetric"&gt;rAltmetric&lt;/a&gt;. Here, we will show how we produced visualizations in the paper. The code here is basically that used in the paper - but modified to make it useable by you hopefully.&lt;/p&gt;</description></item><item><title>Overlaying climate data with species occurrence data</title><link>https://ropensci.org/blog/2013/07/29/rwbclimate-rgbif/</link><pubDate>Mon, 29 Jul 2013 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2013/07/29/rwbclimate-rgbif/</guid><description>
&lt;p&gt;One of our primary goals at ROpenSci is to wrap as many science API&amp;rsquo;s as possible. While each package can be used as a standalone interface, there&amp;rsquo;s lots of ways our packages can overlap and complement each other. Sure &lt;a href="https://www.youtube.com/watch?v=7yeA7a0uS3A"&gt;He-Man&lt;/a&gt; usually rode &lt;a href="https://en.wikipedia.org/wiki/Battle_Cat"&gt;Battle Cat&lt;/a&gt;, but there&amp;rsquo;s no reason he couldn&amp;rsquo;t ride a my little pony sometimes too. That&amp;rsquo;s the case with our packages for &lt;a href="https://www.gbif.org/"&gt;GBIF&lt;/a&gt; and the &lt;a href="https://data.worldbank.org/developers/climate-data-api"&gt;worldbank climate data api&lt;/a&gt;. Both packages will give you lots and lots of data, but a shared feature of both is the ability to plot spatial information. The &lt;a href="https://github.com/ropensci/rWBclimate"&gt;rWBclimate&lt;/a&gt; package provides a robust mapping ability on top of access to climate data. At it&amp;rsquo;s most bare bones, it can be used as alternative to the built in mapping facilities included in &lt;a href="https://github.com/ropensci/rgbif/"&gt;rgbif&lt;/a&gt;. Building on the example in the &lt;a href="https://ropensci.org/tutorials/rgbif_tutorial.html#occurrencelist"&gt;rgbif tutorial&lt;/a&gt; we&amp;rsquo;ll plot data for two species in the US and Mexico, the dark eyed junco (&lt;em&gt;Junco hyemalis&lt;/em&gt;) and the wood duck (&lt;em&gt;Aix sponsa&lt;/em&gt;). Here&amp;rsquo;s how you can use the kml interface from rWBclimate to download a map of the US and Mexico and overlay it with data from rgbif.&lt;/p&gt;</description></item><item><title>rOpenSci at ESA 2013</title><link>https://ropensci.org/blog/2013/07/29/esa-2013/</link><pubDate>Mon, 29 Jul 2013 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2013/07/29/esa-2013/</guid><description>
&lt;p&gt;It&amp;rsquo;s the last week in July and this means that ecologists across North America (and elsewhere) are busy returning from the field and preparing their presentations and posters in anticipation of the annual Ecological Society of America meeting. The entire &lt;a href="https://ropensci.org/about/#devteam"&gt;rOpenSci dev team&lt;/a&gt; will be in attendance &lt;a href="https://www.esa.org/minneapolis/"&gt;this year&lt;/a&gt; and we have several workshops, talks, and events planned out. The topics range from half-day workshops on open data, data visualization, reproducible research, to an entire symposium on open science.&lt;/p&gt;</description></item><item><title>Making maps of climate change</title><link>https://ropensci.org/blog/2013/07/19/rwbclimate-maps/</link><pubDate>Fri, 19 Jul 2013 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2013/07/19/rwbclimate-maps/</guid><description>
&lt;p&gt;A recent video on the &lt;a href="https://video.pbs.org/program/idea-channel/"&gt;PBS Ideas Channel&lt;/a&gt; posited that the discovery of &lt;a href="http://www.youtube.com/watch?v=1M1BPz0nY3s"&gt;climate change is humanities greatest scientific achievement&lt;/a&gt;. It took synthesizing generations of data from thousands of scientists, hundreds of thousands (if not more) of hours of computer time to run models at institutions all over the world. But how can the individual researcher get their hands of some this data? Right now the &lt;a href="https://www.worldbank.org"&gt;World Bank&lt;/a&gt; provides access to global circulation model (GCM) output from between 1900 and 2100 in 20 year intervals via their &lt;a href="https://data.worldbank.org/developers/climate-data-api"&gt;climate data api&lt;/a&gt;. Using our new package &lt;a href="https://github.com/ropensci/rWBclimate"&gt;rWBclimate&lt;/a&gt; you can access model output from 15 different GCM&amp;rsquo;s, ensemble data from all GCM&amp;rsquo;s aggregated, and historical climate data. This data is available at two different spatial scales, individual countries or watershed basins. On top of access to all this data, the API provides a way to download &lt;a href="https://developers.google.com/kml/documentation/"&gt;KML&lt;/a&gt; definitions for each corresponding spatial element (country or basin). This means with our package it&amp;rsquo;s easy to download climate data and create maps of any of the thousands of datapoints you have access to via the API.&lt;/p&gt;</description></item><item><title>Style GeoJSON</title><link>https://ropensci.org/blog/2013/07/17/style-geojson/</link><pubDate>Wed, 17 Jul 2013 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2013/07/17/style-geojson/</guid><description>
&lt;p&gt;&lt;a href="https://ropensci.org/blog/2013/07/04/rbison-geoson/"&gt;Previously on this blog&lt;/a&gt; and on &lt;a href="https://sckott.github.io/2013/06/geojson/"&gt;my own personal blog&lt;/a&gt;, I have discussed how easy it is to create interactive maps on Github using a combination of R, git and Github. This is done using a file format called &lt;a href="https://en.wikipedia.org/wiki/GeoJSON"&gt;&lt;em&gt;geojson&lt;/em&gt;&lt;/a&gt;, a file format based on JSON (JavaScript Object Notation) in which you can specify geographic data along with any other metadata.&lt;/p&gt;
&lt;p&gt;In my &lt;a href="https://ropensci.org/blog/2013/07/04/rbison-geoson/"&gt;previous post on this blog&lt;/a&gt; about &lt;em&gt;geojson&lt;/em&gt;, I described how you could get data from the USGS BISON API using our &lt;a href="https://github.com/ropensci/rbison"&gt;rbison package&lt;/a&gt;, then make a &lt;em&gt;geojson&lt;/em&gt; file, then push to Github. Here, I describe briefly how you can style your map. This time, we&amp;rsquo;ll get data from &lt;a href="https://www.gbif.org/"&gt;GBIF&lt;/a&gt; using the &lt;a href="https://github.com/ropensci/rgbif"&gt;rgbif package&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>From occurrence data to interactive maps on the web</title><link>https://ropensci.org/blog/2013/07/04/rbison-geoson/</link><pubDate>Thu, 04 Jul 2013 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2013/07/04/rbison-geoson/</guid><description>
&lt;p&gt;We have a number of packages for getting species occurrence data: &lt;a href="https://github.com/ropensci/rgbif"&gt;rgbif&lt;/a&gt; and &lt;a href="https://github.com/ropensci/rbison"&gt;rbison&lt;/a&gt;. The power of R is that you can pull down this occurrence data, manipulate the data, do some analyses, and visualize the data - all in one open source framework.&lt;/p&gt;
&lt;p&gt;However, when dealing with occurrence data on maps, it is often useful to be able to interact with the visualization. &lt;a href="https://github.com/"&gt;Github&lt;/a&gt;, a code hosting and collaboration site, now renders a particular type of map file format as an interactive map. This file format is called &lt;code&gt;.geojson&lt;/code&gt;. Here is an example of an interactive map hosted on Github, embedded here:&lt;/p&gt;</description></item><item><title>Revisiting our USGS app</title><link>https://ropensci.org/blog/2013/06/19/usgs-app/</link><pubDate>Wed, 19 Jun 2013 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2013/06/19/usgs-app/</guid><description>
&lt;p&gt;R has a reputation of not playing nice on the web. At rOpenSci, we write R pacakages to bring data from around the web into R on your local machine - so we mostly don&amp;rsquo;t do any dev for the web. However, the United States Geological Survey (USGS) recenty held an app competition - it was a good opportunity to play with R on the web. We won best overall app as described in &lt;a href="https://ropensci.org/blog/2013/04/22/usgs_app/"&gt;an earlier post on this blog&lt;/a&gt;. Check out our app &lt;strong&gt;TaxaViewer&lt;/strong&gt; at &lt;a href="https://ropensci.shinyapps.io/taxaviewer/"&gt;https://ropensci.shinyapps.io/taxaviewer/&lt;/a&gt;. Last week we presented the app to the USGS - a video of the presentation will be coming soon. A screenshot:&lt;/p&gt;</description></item><item><title>What we hope to accomplish with the new funding</title><link>https://ropensci.org/blog/2013/06/14/goals-for-year/</link><pubDate>Fri, 14 Jun 2013 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2013/06/14/goals-for-year/</guid><description>
&lt;p&gt;At rOpenSci&amp;rsquo;s virtual HQ we&amp;rsquo;re busy planning out several exciting projects for the coming year thanks to the generous &lt;a href="https://ropensci.org/blog/2013/06/12/sloan/"&gt;180k grant from Sloan&lt;/a&gt;. In the interest of maintaining transparency with our community here are additional details of what we hope to accomplish and how we&amp;rsquo;ll measure our successes. We have also posted a full copy of our proposal over at &lt;a href="https://figshare.com/articles/rOpenSci_Open_Tools_to_Facilitate_Data_Driven_Science_in_Ecology_and_Evolution/719786"&gt;figshare&lt;/a&gt;.&lt;/p&gt;
&lt;h2&gt;
Objectives for the year
&lt;/h2&gt;&lt;p&gt;a) Focus on identifying shortcomings, strengthening our core products, and working to link existing tools through interoperable data structures and visualization routines. To facilitate this process, we will convene two hackathons, one with the core development team and advisors and a second with a wider group of rOpenSci collaborators.&lt;/p&gt;</description></item><item><title>rOpenSci awarded 180K from The Sloan Foundation</title><link>https://ropensci.org/blog/2013/06/12/sloan/</link><pubDate>Wed, 12 Jun 2013 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2013/06/12/sloan/</guid><description>
&lt;p&gt;Today we are pleased to announce that rOpenSci has been awarded a generous 180K grant from the &lt;a href="https://www.sloan.org/"&gt;Alfred P. Sloan foundation&lt;/a&gt;. This funding will allow us to develop a whole new suite of tools and provide scientists with general purpose toolkits to access various kinds of scientific data. We will also be traveling a whole bunch this year and running workshops at several conferences and universities. If you&amp;rsquo;d like us to speak to your research group, please &lt;a href="https://ropensci.org/contact/"&gt;get in touch&lt;/a&gt;. We&amp;rsquo;ll be at several events over the coming months including &lt;a href="https://www.nceas.ucsb.edu/news/nceas-leads-hands-primer-ecoinformatics-ecological-society-americas-2013-conference"&gt;The Ecological Society of America annual meeting&lt;/a&gt;, &lt;a href="https://okcon.org/"&gt;The Open knowledge conference&lt;/a&gt;, Science Online Climate, &lt;a href="https://www.agu.org/Plan-for-a-Meeting/AGUMeetings/"&gt;American Geophysical Union&lt;/a&gt; and several others. Stay tuned for announcements on &lt;a href="https://twitter.com/ropensci"&gt;Twitter&lt;/a&gt;, our &lt;a href="https://ropensci.org/blog/"&gt;blog&lt;/a&gt; (&lt;a href="https://ropensci.org/feed.xml"&gt;rss&lt;/a&gt;) and new mailing list.&lt;/p&gt;</description></item><item><title>BISON USGS species occurrence data</title><link>https://ropensci.org/blog/2013/05/27/rbison/</link><pubDate>Mon, 27 May 2013 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2013/05/27/rbison/</guid><description>
&lt;p&gt;The USGS recently released a way to search for and get species occurrence records for the USA. The service is called &lt;a href="https://bison.usgs.gov//"&gt;BISON&lt;/a&gt; (Biodiversity Information Serving Our Nation). The service has &lt;a href="https://bison.usgs.gov//"&gt;a web interface&lt;/a&gt; for human interaction in a browser, and &lt;a href="https://bison.usgs.gov//services.html"&gt;two APIs&lt;/a&gt; (application programming interface) to allow machines to interact with their database. One of the APIs allows you to search and retrieve data, and the other gives back maps as either a heatmap or a species occurrence map. The latter is more appropriate for working in a browser, so I&amp;rsquo;ll leave that to the web app folks.&lt;/p&gt;</description></item><item><title>rOpenSci updates on packages and the website</title><link>https://ropensci.org/blog/2013/05/20/updates/</link><pubDate>Mon, 20 May 2013 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2013/05/20/updates/</guid><description>
&lt;h2&gt;
We&amp;rsquo;ve been busy
&lt;/h2&gt;&lt;p&gt;We have been busy hacking away at code and our website. Here is an update on what we&amp;rsquo;ve been up to.&lt;/p&gt;
&lt;h2&gt;
Packages
&lt;/h2&gt;&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;rplos/alm&lt;/strong&gt; PLoS provides two different API services: &lt;a href="https://api.plos.org/solr/examples/"&gt;the Search API&lt;/a&gt; and &lt;a href="https://github.com/articlemetrics/alm/wiki"&gt;ALM API&lt;/a&gt;. As their names suggest, the search API lets you search and get text from their papers and associated metadata. The ALM API allows you to get &lt;a href="https://altmetrics.org/manifesto/"&gt;article level metrics&lt;/a&gt; data on PLoS papers. Up until a few weeks ago, both APIs were accessible via functions inside the &lt;a href="https://github.com/ropensci/rplos"&gt;rplos package&lt;/a&gt;, but they really served two different purposes. Thus, we decided to make two packages: &lt;a href="https://github.com/ropensci/rplos"&gt;rplos&lt;/a&gt;, which wraps just the Search API, and &lt;a href="https://github.com/ropensci/alm"&gt;alm&lt;/a&gt;, which wraps just the ALM API. It especially made sense to break off the ALM API into its own package as other publishers can use the ALM API for delivering their own article level metrics given that the PLoS ALM code is open source. Thus, down the road, you should be able to get altmetrics from XYZ publisher using the alm package just by changing the base URL (a.k.a. the API endpoint).&lt;/p&gt;</description></item><item><title>Facilitating Open Science with Python</title><link>https://ropensci.org/blog/2013/05/16/pyopensci/</link><pubDate>Thu, 16 May 2013 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2013/05/16/pyopensci/</guid><description>
&lt;p&gt;&lt;em&gt;A guest blog post by Steve Moss&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;img src="https://ropensci.org/assets/blog-images/steve_moss.png" alt="Steve Moss"&gt;&lt;/p&gt;
&lt;h1&gt;
Why Python? A little background!
&lt;/h1&gt;&lt;p&gt;I started using &lt;a href="https://www.python.org/"&gt;Python&lt;/a&gt; in the summer of 2010. I had applied for the Master of Research postgraduate degree in Computational Biology at the &lt;a href="https://www.york.ac.uk/"&gt;University of York&lt;/a&gt;. They teach the programming portion of their course using Python. I thought it might be useful to learn it, before starting, to give me a bit of a head start.&lt;/p&gt;</description></item><item><title>Introducing the BEFData package</title><link>https://ropensci.org/blog/2013/05/10/introducing-befdata/</link><pubDate>Fri, 10 May 2013 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2013/05/10/introducing-befdata/</guid><description>
&lt;p&gt;&lt;em&gt;This is a guest post by Class-Thido Pfaff&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;We here present the &lt;a href="https://github.com/befdata/rbefdata"&gt;BEFdata R package&lt;/a&gt; as part of the rOpenSci project. It is an API package that combines the strengths of the BEFdata portal in handling small, complex datasets with the powerful statics package R. The portal itself is free software as well and can be found &lt;a href="https://github.com/befdata/befdata"&gt;here&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;The BEFdata platforms support interdisciplinary data sharing and harmonisation of distributed research projects collaborating with each other. They upload, validate and store data from a formatted Excel workbook. Metadata can be downloaded in Ecological Metadata Language (EML) format. BEFdata allows the harmonization of naming conventions by generating category lists from the primary data, which can be reviewed and managed via the Excel workbook or directly on the platform. BEFdata provides a secure environment during on-going analysis; project members can only access primary data from other researchers after the acceptance of a data request
The combination allows for efficient storage, description and access of research data. The package leverages the access to datasets as well as to workflows in form of R scripts stored on the portal for provenance tracking of computed results.&lt;/p&gt;</description></item><item><title>USGS App Contest</title><link>https://ropensci.org/blog/2013/04/22/usgs_app/</link><pubDate>Mon, 22 Apr 2013 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2013/04/22/usgs_app/</guid><description>
&lt;p&gt;Many US federal agencies are now running app competitions to highlight their web services (see &lt;a href="https://challenge.gov/"&gt;here&lt;/a&gt;), and hopefully get people to build cool stuff using government data (see &lt;a href="https://www.data.gov/"&gt;Data.gov&lt;/a&gt; for more). See &lt;a href="https://github.com/GSA/slash-developer-pages#readme"&gt;here&lt;/a&gt; for a nice list of the US government&amp;rsquo;s web services.&lt;/p&gt;
&lt;p&gt;One of these agencies was the United States Geological Survey (USGS). They opened up an app competition and [we won best overall app! Check out our app called &lt;strong&gt;TaxaViewer&lt;/strong&gt; here: &lt;a href="http://glimmer.rstudio.com/ropensci/usgs_app/"&gt;http://glimmer.rstudio.com/ropensci/usgs_app/&lt;/a&gt;. We were directed to use one or more of their web services, including mashing up with other web services. Of the USGS web services, we only used ITIS, but included 4 web services from other providers.&lt;/p&gt;</description></item><item><title>Use case - how to get species occurrence data from GBIF for a genus</title><link>https://ropensci.org/blog/2013/04/12/rgbif-genus/</link><pubDate>Fri, 12 Apr 2013 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2013/04/12/rgbif-genus/</guid><description>
&lt;p&gt;Real use cases from people using our software are awesome. They are important for many reasons: 1) They make the code more useable because we may change code to make the interace and output easier to understand; 2) They may highlight bugs in our code; and 3) They show us what functions users care the most about (if we can assume number of questions equates to use).&lt;/p&gt;
&lt;p&gt;If someone has a question, others are likely to have the same, or a similar question. Thus, we are sharing use cases on our blog.&lt;/p&gt;</description></item><item><title>Scholarly metadata in R</title><link>https://ropensci.org/blog/2013/03/15/r-metadata/</link><pubDate>Fri, 15 Mar 2013 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2013/03/15/r-metadata/</guid><description>
&lt;p&gt;Scholarly metadata - the meta-information surrounding articles - can be super useful. Although metadata does not contain the full content of articles, it contains a lot of useful information, including title, authors, abstract, URL to the article, etc.&lt;/p&gt;
&lt;p&gt;One of the largest sources of metadata is provided via the Open Archives Initiative Protocol for Metadata Harvesting or &lt;a href="https://www.openarchives.org/OAI/openarchivesprotocol.html"&gt;OAI-PMH&lt;/a&gt;. Many publishers, provide their metadata through their own endpoint, and implement the standard OAI-PMH methods: &lt;a href="https://www.openarchives.org/OAI/openarchivesprotocol.html#GetRecord"&gt;GetRecord&lt;/a&gt;, &lt;a href="https://www.openarchives.org/OAI/openarchivesprotocol.html#Identify"&gt;Identify&lt;/a&gt;, &lt;a href="https://www.openarchives.org/OAI/openarchivesprotocol.html#ListIdentifiers"&gt;ListIdentifiers&lt;/a&gt;, &lt;a href="https://www.openarchives.org/OAI/openarchivesprotocol.html#ListMetadataFormats"&gt;ListMetadataFormats&lt;/a&gt;, &lt;a href="https://www.openarchives.org/OAI/openarchivesprotocol.html#ListRecords"&gt;ListRecords&lt;/a&gt;, and &lt;a href="https://www.openarchives.org/OAI/openarchivesprotocol.html#ListSets"&gt;ListSets&lt;/a&gt;. Many providers use OAI-PMH, including &lt;a href="https://oai.datacite.org/"&gt;DataCite&lt;/a&gt;, &lt;a href="http://wiki.datadryad.org/Data_Access#OAI-PMH"&gt;Dryad&lt;/a&gt;, and &lt;a href="https://www.ncbi.nlm.nih.gov/pmc/tools/oai//"&gt;PubMed&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>The 2013 rOpenSci challenge</title><link>https://ropensci.org/blog/2013/03/14/ropensci-challenge/</link><pubDate>Thu, 14 Mar 2013 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2013/03/14/ropensci-challenge/</guid><description>
&lt;p&gt;At rOpenSci we&amp;rsquo;re very passionate about engaging with our community and getting more people on board with open science and open data. There are many challenges to be overcome before this practice becomes mainstream. Even when researchers see the value in engaging more openly, the learning curve associated with various aspects of the workflow can seem daunting. To identify some of these challenges and barriers, we launched an open science challenge at the start of the year. If any researchers were interesting is using the suite of tools we&amp;rsquo;ve built so far, we offered to help them through the technical challenges they might encounter. We&amp;rsquo;re excited to report that we&amp;rsquo;ll be working closely with &lt;a href="https://www.simonqueenborough.com/"&gt;Simon Queenborough&lt;/a&gt; and &lt;a href="http://lab.brembs.net/author/julien//"&gt;Julien Colomb&lt;/a&gt; on this effort. Below are brief summaries of their work. Stay tuned for updates.&lt;/p&gt;</description></item><item><title>Visualizing rOpenSci collaboration</title><link>https://ropensci.org/blog/2013/03/08/ropensci-collaboration/</link><pubDate>Fri, 08 Mar 2013 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2013/03/08/ropensci-collaboration/</guid><description>
&lt;p&gt;We have been writing code for R packages for a couple years, so it is time to take a look back at the data. What data you ask? The commits data from GitHub ~ data that records who did what and when.&lt;/p&gt;
&lt;p&gt;Using the &lt;a href="https://developer.github.com/v3/repos/commits/"&gt;Github commits API&lt;/a&gt; we can gather data on who commited code to a Github repository, and when they did it. Then we can visualize this hitorical record.&lt;/p&gt;</description></item><item><title>is.invasive()</title><link>https://ropensci.org/blog/2012/11/26/is-invasive/</link><pubDate>Mon, 26 Nov 2012 00:00:00 +0000</pubDate><guid>https://ropensci.org/blog/2012/11/26/is-invasive/</guid><description>
&lt;p&gt;The following was a guest post from &lt;a href="http://www.bartomeus.cat/es/ignasi/"&gt;Ignasi Bartomeus&lt;/a&gt;, originally &lt;a href="https://ibartomeus.wordpress.com/2012/11/26/is-invasive/"&gt;posted&lt;/a&gt; on &lt;a href="https://ibartomeus.wordpress.com/"&gt;his blog&lt;/a&gt; on 26 Nov, 2012. Check out a related blog post &lt;a href="https://sckott.github.com/2012/12/is-invasive/"&gt;here&lt;/a&gt;. Note the functionality discussed in this post is now in our &lt;a href="https://github.com/ropensci/taxize_"&gt;taxize&lt;/a&gt; package under the function &lt;a href="https://github.com/ropensci/taxize_/blob/master/R/gisd_isinvasive.R"&gt;&lt;code&gt;gisd_isinvasive&lt;/code&gt;&lt;/a&gt;. We hacked out a quick &lt;a href="https://www.rstudio.com/shiny/"&gt;Shiny&lt;/a&gt; app so you can play around with the below function in taxize on the web to get invasive status and plot it on a phylogeny. Check it out &lt;a href="http://glimmer.rstudio.com/ropensci/taxize_invasive/"&gt;here&lt;/a&gt;.&lt;/p&gt;
&lt;hr&gt;
&lt;h2&gt;
Ignasi Bartomeus
&lt;/h2&gt;&lt;p&gt;&lt;img src="https://ropensci.org/assets/blog-images/ignasi_bartomeus.png" alt="ignasi"&gt;&lt;/p&gt;</description></item><item><title/><link>https://ropensci.org/404/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://ropensci.org/404/</guid><description>
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-r" data-lang="r"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="n"&gt;page&lt;/span&gt;&lt;span class="o"&gt;$&lt;/span&gt;&lt;span class="nf"&gt;browse&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="c1"&gt;#&amp;gt; Error: object &amp;#39;page&amp;#39; not found&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;</description></item><item><title>AAAS-Community Engagement Fellows Program</title><link>https://ropensci.org/events/2019-01-12-stef-aaas/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://ropensci.org/events/2019-01-12-stef-aaas/</guid><description>
&lt;p&gt;Our Community Manager, Stefanie Butland, will be participating as a mentor for the 2019 cohort of &lt;a href="https://www.cscce.org/cefp/"&gt;AAAS-Community Engagement Fellows&lt;/a&gt;. Are you in DC and have questions about rOpenSci? Let&amp;rsquo;s find time to chat. Contact stefanie [at] ropensci.org&lt;/p&gt;</description></item><item><title>AGU Fall Meeting</title><link>https://ropensci.org/events/2018-12-11-karthik-agu/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://ropensci.org/events/2018-12-11-karthik-agu/</guid><description>
&lt;p&gt;Are you attending &lt;a href="https://fallmeeting.agu.org/2018/"&gt;AGU18&lt;/a&gt;? Have questions about rOpenSci? Our Project Lead and co-founder Karthik Ram will be there and happy to chat.&lt;/p&gt;</description></item><item><title>AGU Fall Meeting</title><link>https://ropensci.org/events/2019-12-09-agu2019/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://ropensci.org/events/2019-12-09-agu2019/</guid><description>
&lt;p&gt;&lt;a href="https://ropensci.org/authors/karthik-ram"&gt;&lt;strong&gt;Karthik Ram&lt;/strong&gt;&lt;/a&gt;, rOpenSci Project Lead and Co-founder, will participate in a town hall Tue Dec 10, &amp;ldquo;&lt;a href="https://agu.confex.com/agu/fm19/meetingapp.cgi/Session/82043"&gt;Data FAIR: Citations lead to Credit – Cite your data and software accurately!&lt;/a&gt;&amp;rdquo;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://ropensci.org/authors/carl-boettiger/"&gt;&lt;strong&gt;Carl Boettiger&lt;/strong&gt;&lt;/a&gt;, rOpenSci Leadership team member and co-founder, is speaking at &lt;a href="https://www.agu.org/Fall-Meeting"&gt;AGU19&lt;/a&gt; on Wed Dec 11 &amp;ldquo;&lt;a href="https://agu.confex.com/agu/fm19/meetingapp.cgi/Paper/541411"&gt;Theoretical Limits to Forecasting in Ecological Systems (And What to Do About It)&lt;/a&gt;&amp;rdquo;.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://ropensci.org/authors/leah-wasser"&gt;&lt;strong&gt;Leah Wasser&lt;/strong&gt;&lt;/a&gt;, &lt;a href="https://www.pyopensci.org/"&gt;pyOpenSci&lt;/a&gt; Leadership team member and Director of the Earth Analytics Education Initiative at U Colorado, will be at a pyOpenSci town hall &amp;ldquo;&lt;a href="https://www.agu.org/Fall-Meeting/Events/Data-TH33F"&gt;Data FAIR: pyOpenSci: Building a Community Around Open Source Python Software for Science&lt;/a&gt;&amp;rdquo; on Wed Dec 11 and giving a talk on Tues Dec 10 &amp;ldquo;&lt;a href="https://agu.confex.com/agu/fm19/meetingapp.cgi/Paper/541546"&gt;pyOpenSci Promoting Open Source Python Software To Support Open Reproducible Science&lt;/a&gt;&amp;rdquo;. pyOpenSci is being modeled after rOpenSci, but for python!&lt;/p&gt;</description></item><item><title>Bristol R User Group</title><link>https://ropensci.org/events/2019-08-20-bristolr/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://ropensci.org/events/2019-08-20-bristolr/</guid><description>
&lt;p&gt;Rich FitzJohn, rOpenSci Leadership team member will talk about &amp;ldquo;Reproducible research and “productionising” research code&amp;rdquo;. Other speakers include Nic Crane and Deirdre Toher.&lt;/p&gt;
&lt;p&gt;See the &lt;a href="https://www.meetup.com/Bristol-R-User-Group/events/262283223/"&gt;BristolR meetup page&lt;/a&gt; for details and to RSVP.&lt;/p&gt;</description></item><item><title>Code of Conduct (English version)</title><link>https://ropensci.org/code-of-conduct/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://ropensci.org/code-of-conduct/</guid><description><i><a href="https://ropensci.org/es/c%C3%B3digo-de-conducta/">Read it in: Español</a>.</i><i><a href="https://ropensci.org/pt/c%C3%B3digo-de-conduta/">Read it in: Português</a>.</i>
&lt;p&gt;&lt;em&gt;El código de conducta también está disponible en &lt;a href="https://ropensci.org/es/c%C3%B3digo-de-conducta/"&gt;español&lt;/a&gt;.&lt;/em&gt;
&lt;em&gt;O código de conduta também está disponível em &lt;a href="https://ropensci.org/pt/c%C3%B3digo-de-conduta"&gt;Português&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;rOpenSci&amp;rsquo;s community is our best asset and we believe that our diversity is our strength. We are building a welcoming and diverse global community of software users and developers from a range of research domains. It&amp;rsquo;s so important to us, it&amp;rsquo;s in &lt;a href="https://ropensci.org/about/"&gt;our mission statement&lt;/a&gt;. Whether you’re a regular contributor or a newcomer, we care about making this a safe place for you and we’ve got your back.&lt;/p&gt;</description></item><item><title>Computing Infrastructure</title><link>https://ropensci.org/packages/scalereprod/index.json</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://ropensci.org/packages/scalereprod/index.json</guid><description><i><a href="https://ropensci.org/es/packages/scalereprod/index.json">Read it in: Español</a>.</i></description></item><item><title>Course: Tools for Southern Ocean Spatial Analysis and Modeling</title><link>https://ropensci.org/events/2019-09-02-scar-course/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://ropensci.org/events/2019-09-02-scar-course/</guid><description>
&lt;p&gt;The &lt;a href="https://www.scar.org/"&gt;Scientific Committee on Antarctic Research&lt;/a&gt; is partnering with rOpenSci and the &lt;a href="http://www.biodiversity.aq"&gt;Antarctic Biodiversity Portal&lt;/a&gt; in organizing a short course on tools for Southern Ocean spatial analysis and modeling using R. &lt;a href="https://github.com/SCAR/EGABIcourse19"&gt;Details&lt;/a&gt;. Apply by Friday, June 15, 2019.&lt;/p&gt;</description></item><item><title>Data Access</title><link>https://ropensci.org/packages/data-access/index.json</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://ropensci.org/packages/data-access/index.json</guid><description><i><a href="https://ropensci.org/es/packages/data-access/index.json">Read it in: Español</a>.</i></description></item><item><title>Data Extraction</title><link>https://ropensci.org/packages/data-extraction/index.json</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://ropensci.org/packages/data-extraction/index.json</guid><description><i><a href="https://ropensci.org/es/packages/data-extraction/index.json">Read it in: Español</a>.</i></description></item><item><title>Data Publication</title><link>https://ropensci.org/packages/data-publication/index.json</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://ropensci.org/packages/data-publication/index.json</guid><description><i><a href="https://ropensci.org/es/packages/data-publication/index.json">Read it in: Español</a>.</i></description></item><item><title>Data Visualization</title><link>https://ropensci.org/packages/data-visualization/index.json</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://ropensci.org/packages/data-visualization/index.json</guid><description><i><a href="https://ropensci.org/es/packages/data-visualization/index.json">Read it in: Español</a>.</i></description></item><item><title>Databases</title><link>https://ropensci.org/packages/databases/index.json</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://ropensci.org/packages/databases/index.json</guid><description><i><a href="https://ropensci.org/es/packages/databases/index.json">Read it in: Español</a>.</i></description></item><item><title>Electronic Resources &amp; Libraries conference</title><link>https://ropensci.org/events/2019-03-05-karthik-erl/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://ropensci.org/events/2019-03-05-karthik-erl/</guid><description>
&lt;p&gt;Karthik Ram will speak at the 14th annual &lt;a href="https://erl19.sched.com/event/I8Q6/s36-building-towards-a-future-where-reproducible-and-open-data-science-is-the-norm"&gt;Electronic Resources &amp;amp; Libraries conference&lt;/a&gt;.&lt;/p&gt;
&lt;h3&gt;
Building Towards a Future Where Reproducible and Open Data Science is the Norm
&lt;/h3&gt;&lt;p&gt;&lt;em&gt;The Open Science movement promotes the sharing of all artifacts of scientific research, including data, code, and methods. This movement has become popular among researchers worldwide, as evidenced by the thriving ecosystem of tools and the numerous training initiatives that have sprung up at various institutions.&lt;/em&gt;&lt;/p&gt;</description></item><item><title>Geospatial</title><link>https://ropensci.org/packages/geospatial/index.json</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://ropensci.org/packages/geospatial/index.json</guid><description><i><a href="https://ropensci.org/es/packages/geospatial/index.json">Read it in: Español</a>.</i></description></item><item><title>How to Cite rOpenSci?</title><link>https://ropensci.org/how-to-cite-ropensci/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://ropensci.org/how-to-cite-ropensci/</guid><description><i><a href="https://ropensci.org/es/how-to-cite-ropensci/">Read it in: Español</a>.</i>
&lt;p&gt;Thank you for citing rOpenSci! &amp;#x1f64f;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;To cite the &lt;strong&gt;rOpenSci project&lt;/strong&gt;: Boettiger, C., Chamberlain, S., Hart, E., &amp;amp; Ram, K. (2015). Building Software, Building Community: Lessons from the rOpenSci Project. Journal of Open Research Software, 3(1), e8. &lt;a href="https://doi.org/10.5334/jors.bu"&gt;doi:10.5334/jors.bu&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;To cite &lt;strong&gt;rOpenSci Software Peer Review&lt;/strong&gt;: Ram, K., Boettiger, C., Chamberlain, S., Ross, N., Salmon, M., &amp;amp; Butland, S. (2018) A Community of Practice Around Peer-review for Long-term Research Software Sustainability. Computing in Science &amp;amp; Engineering, vol. 21, no. 2, pp. 59-65, 1 March-April 2019 &lt;a href="https://doi.org/10.1109/MCSE.2018.2882753"&gt;doi:10.1109/MCSE.2018.2882753&lt;/a&gt;&lt;/p&gt;</description></item><item><title>HTTP tools</title><link>https://ropensci.org/packages/http-tools/index.json</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://ropensci.org/packages/http-tools/index.json</guid><description><i><a href="https://ropensci.org/es/packages/http-tools/index.json">Read it in: Español</a>.</i></description></item><item><title>Image &amp; Audio Processing</title><link>https://ropensci.org/packages/image-processing/index.json</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://ropensci.org/packages/image-processing/index.json</guid><description><i><a href="https://ropensci.org/es/packages/image-processing/index.json">Read it in: Español</a>.</i></description></item><item><title>LatinR 2019</title><link>https://ropensci.org/events/2019-09-25-latinr2019/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://ropensci.org/events/2019-09-25-latinr2019/</guid><description>
&lt;p&gt;See the &lt;a href="https://latin-r.com/"&gt;LatinR conference page&lt;/a&gt; for details.&lt;/p&gt;</description></item><item><title>Literature</title><link>https://ropensci.org/packages/literature/index.json</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://ropensci.org/packages/literature/index.json</guid><description><i><a href="https://ropensci.org/es/packages/literature/index.json">Read it in: Español</a>.</i></description></item><item><title>Noam Ross at PyData</title><link>https://ropensci.org/events/2019-11-05-noam-pydata/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://ropensci.org/events/2019-11-05-noam-pydata/</guid><description>
&lt;p&gt;Noam Ross, rOpenSci Software Peer Review Editor and Leadership Team member, is talking about &lt;a href="https://pydata.org/nyc2019/schedule/presentation/73/building-software-and-communities-with-peer-review/"&gt;Building Software and Communities With Peer Review&lt;/a&gt; at PyData.&lt;/p&gt;
&lt;h3&gt;
Description
&lt;/h3&gt;&lt;p&gt;Software peer review can improve software quality, accelerate the adoption of best practices and community standards, and build communities of practice. I will present lessons from over four years of software peer review at rOpenSci, and new initiatives such as pyOpenSci that are expanding software peer review into new fields and languages.&lt;/p&gt;</description></item><item><title>Open Science Through rOpenSci</title><link>https://ropensci.org/events/2019-07-08-mel-rladiesmelb/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://ropensci.org/events/2019-07-08-mel-rladiesmelb/</guid><description>
&lt;p&gt;Registration: &lt;a href="https://www.meetup.com/rladies-melbourne/events/262566179/"&gt;https://www.meetup.com/rladies-melbourne/events/262566179/&lt;/a&gt;&lt;/p&gt;</description></item><item><title>R-Ladies Seattle</title><link>https://ropensci.org/events/2019-05-22-rladies-seattle/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://ropensci.org/events/2019-05-22-rladies-seattle/</guid><description>
&lt;p&gt;Our Community Manager, &lt;a href="https://ropensci.org/authors/stefanie-butland/"&gt;Stefanie Butland&lt;/a&gt;, is speaking at an R-Ladies Seattle meetup on the theme of Learning R and Building Community. Other speakers are Malisa Smith, Bioinformatician at University of Washington, and Pamela Moriarty, Data Scientist at zulily.&lt;/p&gt;
&lt;p&gt;See the &lt;a href="https://www.meetup.com/rladies-seattle/events/261245337/"&gt;R-Ladies Seattle meetup site&lt;/a&gt; for details.&lt;/p&gt;</description></item><item><title>rOpenSci Packages</title><link>https://ropensci.org/packages/all/index.json</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://ropensci.org/packages/all/index.json</guid><description><i><a href="https://ropensci.org/es/packages/all/index.json">Read it in: Español</a>.</i></description></item><item><title>rOpenSci website privacy policy</title><link>https://ropensci.org/privacy/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://ropensci.org/privacy/</guid><description>
&lt;p&gt;This Privacy Policy is applicable to our website.
By using our website, you agree to the terms of this Privacy Policy.&lt;/p&gt;
&lt;h2&gt;
What information do we obtain?
&lt;/h2&gt;&lt;p&gt;We collect information about visitors’ devices and browsers, such as browser version and type, IP address, website referred from and country of visitor.&lt;/p&gt;
&lt;h2&gt;
What do we do with this information?
&lt;/h2&gt;&lt;p&gt;We use this information to improve our sites and services.
This information may also be used for statistical purposes.
However, we may share de-identified aggregate or summary information regarding visitors publicly or with volunteers, partners or third parties, including but not limited to funding entities.
We may use publicly available data of the external online services in programmatic analysis and evaluation.&lt;/p&gt;</description></item><item><title>RSEConUK 2019</title><link>https://ropensci.org/events/2019-09-17-rseconuk/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://ropensci.org/events/2019-09-17-rseconuk/</guid><description>
&lt;p&gt;rOpenSci &lt;a href="https://ropensci.org/software-review/"&gt;Software Peer Review&lt;/a&gt; Editor Anna Krystalli will be presenting &lt;a href="https://github.com/ropenscilabs/pkgreviewr"&gt;pkgreviewr&lt;/a&gt;, an R package that helps automate some of the steps and guide reviewers through the rOpenSci review process. In her poster she’ll present an overview of the rOpenSci review process and the use of pkgreviewr to support it. She’ll also tell the story of how the package came to be and how such contributions can lead to deeper involvement with the community.&lt;/p&gt;</description></item><item><title>Security</title><link>https://ropensci.org/packages/security/index.json</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://ropensci.org/packages/security/index.json</guid><description><i><a href="https://ropensci.org/es/packages/security/index.json">Read it in: Español</a>.</i></description></item><item><title>Statistics</title><link>https://ropensci.org/packages/stat/index.json</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://ropensci.org/packages/stat/index.json</guid><description><i><a href="https://ropensci.org/es/packages/stat/index.json">Read it in: Español</a>.</i></description></item><item><title>Taxonomy</title><link>https://ropensci.org/packages/taxonomy/index.json</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://ropensci.org/packages/taxonomy/index.json</guid><description><i><a href="https://ropensci.org/es/packages/taxonomy/index.json">Read it in: Español</a>.</i></description></item><item><title>Tutorials</title><link>https://ropensci.org/tutorials/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://ropensci.org/tutorials/</guid><description><i><a href="https://ropensci.org/es/tutorials/">Read it in: Español</a>.</i>
&lt;p&gt;We no longer maintain tutorials on our website.
We provide an &lt;a href="https://ropensci.org/blog/2019/06/07/ropensci-docs/"&gt;infrastructure&lt;/a&gt; building the &lt;a href="https://docs.ropensci.org/"&gt;pkgdown websites&lt;/a&gt; of &lt;a href="https://ropensci.org/packages"&gt;all the packages&lt;/a&gt; in our suite.&lt;/p&gt;</description></item><item><title>useR!2019</title><link>https://ropensci.org/events/2019-07-10-user2019/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://ropensci.org/events/2019-07-10-user2019/</guid><description>
&lt;p&gt;Three members of the rOpenSci team - Scott Chamberlain, Jenny Bryan, and Rich FitzJohn - as well as many community members will give talks at &lt;a href="http://www.user2019.fr/"&gt;useR!2019&lt;/a&gt;. Many other package authors, maintainers, reviewers and unconf participants will be there too. Don&amp;rsquo;t hesitate to ask them about rOpenSci &lt;a href="https://ropensci.org/packages/"&gt;packages&lt;/a&gt;, &lt;a href="https://ropensci.org/software-review/"&gt;software peer review&lt;/a&gt;, &lt;a href="https://ropensci.org/community/"&gt;community&lt;/a&gt;, or just say hello if you&amp;rsquo;re looking for a friendly face.&lt;/p&gt;
&lt;p&gt;We&amp;rsquo;ve listed their talks for you in a &lt;a href="https://ropensci.org/blog/2019/07/08/user2019/"&gt;blog post&lt;/a&gt;. Search the &lt;a href="https://connect.rstudioservices.com/content/331/user2019-schedule.html"&gt;schedule&lt;/a&gt; for details.&lt;/p&gt;</description></item></channel></rss>