###### tags: `turing-way`

:::info
This is the [Master Doc](https://hackmd.io/Xx6lgXf-SiGssa-qoEEJiw) for all notes and docs!
Batool has made minor changes to this document and created a new doc [here](https://hackmd.io/asXt25PKQFOEfS5w2HDanw)
:::
# A very early draft for *The Turing way* translation governance

## The translation team structure:
1. translators and proofreaders for each language
2. language leads for each language: ==who?== preliminary: Anıl (tr), Joel/Kozo (jp), Batool (ara), Andrea/Melissa (pt-br), Alejandro/Camila (es), fr
4. translation leads team: Camila, Batool, Andrea

## 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.
:::

## The lead team:

+ Makes technical decisions about access to the accounts, to protect the repos/files and the whole process until the deployment.

:::info
We should document the ==current configuration== of the repos and the crowdin, we know it's not definitive but the preliminary ones:
+ Crowdin members status: not manager, everyone is a proofreader and everyone has access to the glossary. **Language team leads should take care of the glossary, though.**
+ Frequency of upstream pull: everytime there is a commit in the original ttw (pull bot setup by Batool, we already discussed it's better to be on top because TTW changes so fast)
+ What goes back to the translation repository: only approved translations. ==**if a team wants their translations to start showing on the repo they have to start translating-reviewing-approving**==
+ Is the crowdin translation workflow fixed? pre-translation + crowdsourcing + proofreading. If it's fixed, any further changes would have to go through a discussion* (see Decision making) with the rest of the lead team, we don't want some translation work to be lost.
+ ==**can we do a backup of everything in case we delete things in crowdin?** [name=Andrea] I am worried that waiting for approval means that the translation work is not commited and therefore can be lost [name=Batool] Translation in Crowdin shouldn't be lost, it should ideally be always saved in the Translation memory but I'd encourage Teams to do lots of Translation for more than 3 files without starting to proofread==
+ Acknowledgements: ==ask if the all contributors bot works== could we add some sub-categories for translation: proofread, translate?'
:::

### Decision making:
+ If any big changes in the infrastructure of the whole workflow have to be made, they can be documented ==in this pad (??)==, 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=Batool] Can we have 3 translation co-working calls and 1 translation leads call? I'm afraid that translation co-working calls is always busy with volunteers and it hard to multitask in it (discuss other issues) - maybe (to be organised) we can propose a schedule with who leading the discussion/Zoom link + calendar invite? [name=Andrea] i like that -do we have dates?
+ Do we want to split roles inside our roles?
+ [name=Batool] Maybe it'll be needed at some point, possible rules[name=Andrea] I joined our lists:
+ Updating the Translation Chapters with all changes in the infrastructure, languages, workflow to keep the Translation chapter up to date
+ Reviewing PRs and Merging new Translation with the help of the Translation Team
+ Leading/taking notes specific co-working calls
+ Replying to comments in Crowdin [name=Andrea] maybe this is language-specific? Team 2
+ Onboarding/offboarding new members and 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 anyone*