L10N Move To Zanata

Move To Zanata Schedule Plan

2014-07-22	Software String Freeze
2014-08-19	L10N QA Test Day
2014-08-26	Software Translation Deadline

Task List

1. Copy the repo over to zanata
2. Inform all language team coordinators and translators
3. Testing
4. Implement notification feature
5. Move complete

Concerns

Infra at lists

• Tx moved to proprietary. Our main concern we build fedora with FLOSS/FOSS by using FOSS tools. Move to alternate is supported.
• Two alternates raised: zanata (there are supporters) & Translatewiki (no particular supporter)
• Need developers agreement

trans at lists

• How to migrate existing teams, members and coordinators smoother
• How to separate existing language teams which are independent from FLP
• How zanata deal with translators' credits
• Instance (existing zanata instance or fedora infra to create new?)
• Integration with FAS, ML, Badges and wiki
• Integration with FAS: sign Fedora Project Contributor Agreement
• How hard would be the migration
• Email notification
• F21 schedule
• Pseudo-tree view of projects, whereas in Zanata, we end up with just a

list of projects, where it becomes difficult to find a particular project.

• Explicitly include in the schedule the concept of a parallel run. That is, a small slice of time when the

Zanata instance will mirror everything that Transifex has.

• Communication channel for Move