As we’ve said before, 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 multilingual publishing are crucial work for rOpenSci’s mission.When discussing this project at conferences and elsewhere, we start an important conversation with people less

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.

Dear rOpenSci friends, it’s time for our monthly news roundup! You can read this post on our blog. Now let’s dive into the activity at and around rOpenSci! 🔗rOpenSci HQ 🔗Help us maintain {pkgcheck}! You might know of our {pkgcheck} system used for our automated package checks, and for your own stand-alone and GitHub-action usage on any package. We are seeking co-maintainers for the {pkgcheck} package which powers this system.

To be part of the rOpenSci Champions program has been an experience of professional growth and an opportunity to contribute to the rOpenSci community . I learned about R package development while working on a tool to facilitate access to census data from Argentina.

A few years ago, the R community started using ORCID (“Open Researcher and Contributor ID”) to persistently and uniquely identify individual authors of packages in DESCRIPTION.The idea is the following: you enter authors’ ORCID as a specially named comment in their person() object.For instance I can be represented by:person("Maëlle", "Salmon", , "maelle@ropensci.org", role = c("cre", "aut"), comment = c(ORCID = "0000-0002-2815-0399"))

🔗Why did I create eDNAjoint? Environmental DNA (eDNA) - the genetic material left by organisms in their environment - is increasingly used as an efficient and cost-effective method in surveys of species distribution and abundance. This emerging data type presents new opportunities and new challenges, particularly around interpretation and fear of false positive detections.

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

Dear rOpenSci friends, it’s time for our monthly news roundup! You can read this post on our blog. Now let’s dive into the activity at and around rOpenSci! 🔗rOpenSci HQ 🔗rOpenSci Champions Program 2025 In Spanish: Apply before April 30th! 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!

🔗How it started 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 Dominion Land Survey system, introduced in the late 19th century to organize the European settlement and colonization of

The NumFOCUS Diversity & Inclusion in Scientific Computing (“DISC”) Unconf took place as a hybrid event in São Paulo, Brazil, from March 14 to 16, 2025.Our community manager, Yanina Bellini Saibene, and rOpenSci Champions, Andrea Gomez Vargas and Liz Hare, participated.In this short post we report on our experience at and around the unconference.

rOpenSci’s activities and spaces are supported by a Code of Conductthat 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