Put all translations in bzr (or possibly other vcs)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
Low
|
Unassigned |
Bug Description
Pootle can now drive the translation in Git. This got me thinking that this is actually a brilliant idea. Iinitially, translations should be automatically committed to a bzr branch. This would allow upstream to checkout that branch as well as people wishing offline work to check out and then push back their changes. Ideally, this should be able to drive into any VCS, allowing upstream to say "my pots are in this SVN|CVS|GIT repo, check translation back into there" thus the backend should either be abstracted or use bzr-svn, etc.. Implementation issues include when to checkin (probably when they move to the next page), what username to checkin under (their own or an LP generic one) and making checkin async (allowing users to move on).
This is something we've discussed a while ago in Alicante during one of our Translations sprints, however, it involves a lot of different issues (like security, transparency, etc.). There are some related specs in blueprints. launchpad. net/rosetta/ , but we haven't specced out all the ideas we had for resolving this.
Also, no timeframe for this yet.