Skip to content

Move Pilot and flesh out Feedback #6

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 4 commits into
base: main
Choose a base branch
from
Open

Move Pilot and flesh out Feedback #6

wants to merge 4 commits into from

Conversation

steffilazerte
Copy link
Collaborator

Hi @yabellini I've moved the pilot description to it's own chapter and summarized the feedback from the hackthons (also adding some of the things I forgot from the feedback to the hackathon chapter itself). I also standardized some of the text (i.e. always using '-' in mini-hackathon, and translathons going before hackathons, etc.). Finally I tried to remove some of the overlap between the preface, the introduction and the pilot.

what they enjoyed and suggestions for improvement.

### Translathons
...
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
...
As part of the translation efforts, we organized a mini-hackathon focused on reviewing existing Portuguese translations and introducing participants to the review workflow. The event was divided into two main parts: a walkthrough of the translation review process and hands-on sessions where participants practiced doing reviews.
Participants expressed that they enjoyed the opportunity to contribute and valued the chance to learn more about using GitHub. Many highlighted that learning the review process helped them contribute to this project and gave them skills and ideas they plan to apply in other open-source and localization projects. There was a suggestion to support other R-related translation projects.
Most participants also mentioned that organizing this event in collaboration with the LatinR Conference was especially meaningful. It created a space to collaborate with others across the region and contribute to something that brings value to the broader Latin American community.
One key suggestion that emerged was the importance of documenting shared agreements—especially on how to translate technical terms consistently. Having a reference guide or glossary would support current and future contributors in maintaining coherence across translations.
The enthusiasm sparked during the hackathon continued after the event, with several participants actively engaging in translation and review work in Slack and GitHub. Their commitment and motivation reflect the impact of creating inclusive, hands-on spaces for collaboration and learning.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants