# A draft for *The Turing way* translation governance

> The translation initiative aims to make "The Turing Way" accessible to a global audience, reflecting the project's commitment to inclusivity and diversity. Translations should maintain the integrity of the original content while being culturally and contextually relevant.

## The translation team structure:
1. translators and proofreaders for each language
2. language leads for each language:
4. translation leads team: Batool, Andrea, Melissa

[name=Batool] Toby mentioned how people can go into their roles? it needs to be captured in the governance document.
[name=Andrea] Yes, this was a little bit ad hoc, people who were working were nominated to be leaders when the overall TTW governance started, but we should have a different mechanism and a rotating one, where each one has the opportunity to serve as co-lead for an amount of time (3-6 months).

## Contribution Types/Paths

- Translator
- Proofreader
- Manager
- Infrastructure
- Documentation
- Promoting the localisation in event

## Tasks for each team:
1. Translators and proofreaders:
* Translate and review,
* Add words to the glossary,
* File issues and questions about translation decisions.
* Feedback on the documentation, what is working and what is not, what could be done better.
2. Language leads:
* Final review for each translation,
* Maintenance of the glossaries,
* Onboarding of new translators (based on the documentation),
* Checking the integrity and progress of each language.
* Feedback on the documentation, what is working and what is not, what could be done better.
* Lead and document the translation rules/guidelines for each language. Decide who is a translator or a reviewer for each language. **Replying to comments in Crowdin**
3. Lead team:
* Onboarding of new language teams.
* Updating the documentation.
* Maintenance of the repository and the crowdin account.
* Communication with the core ttw team and the tech team about deployment.
* Lead the coworking translation calls but also *this could be done by the leads for each language in the future*

:::info
Everybody should be able to review and participate in the TTW chapter, give feedback and their opinion about the workflows.
:::

## Meetings
### Co-working Calls & Onboarding Calls
- **Frequency**: Once every month
- **Chair**: Selected from leads
- **Membership**: Open to anyone interested in localisation
- **Objectives**:
- A facilitator assists with onboarding in the breakout room.
- Question: can anybody that went through an onboarding process onboard other people, regardless of their role?
- It is an 'Ask Me Anything' call for any questions.
- The main room is dedicated to working on milestones for the localisation work.
- Tasks are prepared in advance (in Crowdin Kanban) to support new members.
- Who prepares them? Language leads?
### Community Meeting
- **Frequency**: This is integrated into the TTW Collaboration Café.
- **Chair**: Selected from leads
- [name= Melissa] Maybe open this role for translators too? Or have them in a facilitator role to feel more empowered.
- **Membership**: Open to anyone interested in localisation.
- **Objectives**: A forum to discuss deliverables/outputs (e.g. toolkits, glossary, blog post, ...etc), consult the community, and seek feedback.
### Localisaton Lead Team Meeting
- **Frequency**: Bi-monthly
- **Membership**: Exclusive to localisation leads.
- **Objectives**: To review milestones and decisions related to localisation.
### Language Leads Meeting
- **Frequency**: Every four months
- **Membership**: Language leads plus localisation leads.
- **Objectives**: To evaluate the work of each language, discuss potential plans, questions, or support needs.
### Language Localisation Sprints
- **Frequency**: This is organised by each language lead.
- **Chair**: Language lead.
- **Membership**: All language contributors.
- **Objectives**: Language leads, with support from localisation leads, organise localisation sprints. These can occur during a Book Dash or independently.
- [name= Toby] It help with motivation
- [name= Melissa] May require support from Alex/Anne and the Book Dash organizing committee
- [name = Melissa] Consider the timezones.

### Decision making:
+ If any big changes in the infrastructure of the whole workflow have to be made, they can be documented and the rest of the team should have reasonable time to see the proposal and approve it. What "big" change means, and what "reasonable" time means are up to each one--based on common sense, no need to wait forever for a tiny change--, but tagging the relevant team members to prompt a revision/an opinion can be a good practice to have quick feedback and make decisions quicker.
+ Not everybody in the team lead should have to participate to decide on something, maybe only one +1 is enough. If the first person reviewing does not agree or the change needs more discussion, they can call a third member to give an opinion and discuss the change. 3/4 people should be enough to make a decision.
+ Team lead meetings every 1-2 months in the same slot of the translation co-working call.
+ [name=Melissa] How do we communicate decisions and that the floor is open for any suggestions? Slack + calls?
+ Consider that the project might scale up and these decision-making instances might need to change

## Recognition

> [name= Batool] This section requires significantly more attention and detail. It seems the needs of contributors to the translation project may differ from what is typically acknowledged in a README, as many of them may not be familiar with GitHub.

Contributors will be acknowledged in The Turing Way README, and they are invited to add their contributions to the Turing Way contribution record

Besides GitHub:
- Authorship on Zenodo
- Authorship on the published translated version
- Names added to TTW book website (translation chapter)
- Badges in Linkedin.
- Ask Alycia!
- Badging services may be paid depending on the # of users
- Acknowledge all kinds of contributions, including first and small ones
-