| Page Properties | ||||||||
|---|---|---|---|---|---|---|---|---|
|
...
This retro is for S96:
Thursday, Septmber September 12th | Wednesday, September 25th |
...
Translation release check-in
Malayalam updates
Hannah is aware!
Get BETA ready for an guided tour (hiding the unfinished bits as an in progress demo)
Any way to highlight the flow of strings?
not necessarily worth the time
compare english and Malayalam and add placeholder in Crowdin to make it searchable
Translation Retro
Maintaining existing languages
Future languages minimum requirements / SOP for how to integrate them
List of all materials that need to be translated when adding a new language
What are our responsibilities for adding a new language?
As we keep adding new features, how do we keep up with translated versions of those features? Do we define a periodical frequency of such updation?
Standard of translation? (Especially for languages further and further from English)
Anto Sgarlatta - can we organize translation files better as devs?
How do we maintain a realistic correlation between effort and timelines?
Can AI translation help us maintaining release schedules? (It’s getting better and better, specially for western languages). Crowdin has an integrated AI module (in beta though)
Start doing | Stop doing | Keep doing | Shout outs |
|---|---|---|---|
|
Action items:
- Review previous retro’s action itemsDefine flows needing translating for demo Divya Chayanam
- Flag the files in the flows with a placeholder in linkedin Denis Dovganyuk
Rollover action items from last time
- Devs + Denis Dovganyuk + David Trapp to review a good labeling system for existing Jira bugs at pointing tomorrow - After sprint?