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’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.

According to a recent report from The Linux Foundation, language access is one of the environmental barriers to equity in open source. The report states that

The predominant language of open source is English—in code, content, and community interactions—and English proficiency is a metric by which performance and personality can be judged¹.

This might remind some readers of the famous quote from Modern Family, where a character called Gloria exclaims:

Do you even know how smart I am in Spanish?

By publishing multilingual resources, we can lower these barriers by increasing access to knowledge and democratizing access to quality resources, thereby increasing the potential for individuals to contribute to software and open science projects.

Language representation

The Spanish-speaking R community has been very active and growing in recent years, and has undertaken various translation activities for technical materials such as books, cheatsheets, guides, and datasets.

In 2017, several Latin American R-Ladies began translating the R-Ladies’ Code of Conduct and their Rules and Guidelines into Spanish.

In 2018, the R community in Latin America collectively translated the R for Data Science book into Spanish. This included the translation of all the data sets used in the book, which were compiled in the datos package, making it an excellent tool for teaching.

The community continued with the translation of Teaching Tech Together and contributed to the translations into Spanish of the Posit Cheatsheets, The Carpentries’ and The Programming Historian lessons.

Driven by this active and growing Spanish-speaking community, rOpenSci successfully piloted our first Spanish-language peer review, where the submission itself, as well as all reviews and editorial responses, were in Spanish.

All of this work and previous experience created the right conditions for us to start our multilingual publishing in Spanish! Spanish is the second most-spoken native language in the world and is one of the most geographically widespread languages, being an official language in many countries².

Technical materials, technical solutions

rOpenSci provides community support, standards, and infrastructure for scientists and research software engineers working in R to develop, maintain, and publish high-quality open-source scientific software. In addition, we develop and maintain high-quality documentation and resources to support these activities.

Multilingual publishing of documentation and resources involves two aspects:

• The internationalization refers to the technological solution allowing the software to adapt to different regions without requiring engineering changes to the source code. It is what enables us to localize our content³.

• The localization is the process of taking a piece of content in its original form and converting it into something more accessible and suitable for another region, country, or audience³. This includes language, date formats, currency, measurement units, and support for different character sets.

In addition, technical translations of living documents have two well-defined stages that involve different resources:

1. achieving a first version of the translated material, and

2. keeping the material updated and synchronized between the supported languages.

There are many solutions for internationalizing and localizing content and software. Translation is typically the most time-consuming component of these efforts³.

Based on our previous experiences and using the characteristics of our community, this project aims to complete Stage 1 by creating initial Spanish translations of rOpenSci materials, and testing a technical workflow for performing translations.

Our approach will test and develop a workflow using the automatic translator DeepL API to generate an initial translated version of the documents, which will be later reviewed by professional bilingual developers using GitHub as a platform.

The advantage of this workflow is that it reduces the time it takes to produce a quality translation. Reviewers will focus on linguistic tasks such as the use of inclusive language, the localization of examples, and the correct translation of phrases, metaphors, or analogies. They will also look for reference material in the language of the translation. In addition, if the workflow proves feasible and useful, it could be incorporated into the pipeline to keep the texts in different languages synchronized, contributing to solve challenges we may encounter in Stage 2.

Besides systematizing the experiences, other products of the project will be:

• a general guide of rules to follow when translating technical documents,
• a specific guide for the Spanish language,
• a list of technical terms which will be translated into Spanish and a list of those that will not be,
• an R package with our workflow for translating technical documents.

Building community

Multilingual publishing will help democratize access to quality resources for learning and teaching the necessary digital skills to become contributors to open source projects and to have a workflow for performing computationally reproducible open science.

At rOpenSci, we understand review as a way of building community. Developing the material for our review process in Spanish will allow rOpenSci to continue building the community in Spanish-speaking regions (such as Latin America), to increase the number of contributors, and to get feedback on how our tools and processes can be improved to better serve these community members.

In addition to learning how to be a developer, maintainer, reviewer, or editor, people can also contribute through translation. This type of contribution is often a good first step and is recognized as valuable by the community.

We also expect that the project’s documentation and tooling will be useful for extending this effort to other languages and for other communities and projects with translation efforts.

Sources