Planning

Transformation to git

1. Converting the script to git implies changes to the current workflow, which are changes we look forward to.
2. GNOME translators should now move to the workflow that they keep the local repositories of a GNOME release in a dedicated space on their computer. Now, we consider, as committers, to set aside the ~2GB space for the GNOME repositories.
3. This should a directory which has those repositories, and it would be as easy as pointing our script to the relevant directory that was retrieved with, let’s say “jhbuild”.
4. “git clone” is CPU-intensive for both the client and server; it should be possible to ‘git clone’ anonymously and put the tarballs on some server; then it’s simply downloading files. It is very easy to convert from anonymous repositories.
5. out script should not add files or make temporary changes to the repositories. We point links to the repositories, and when committing, we make changes and apply them.
6. our script depends on the XML output from damned-lies. we may request for changes to make our work easier (such as, define the location of translation files in repository)
7. Committing to a branch implies committing to ‘master’.
8. We need a way to package PO files as ‘work packages’, that a translator can take, work on, and then send back. We then use the script
   to merge in the translation package.
9. We need a way to embed the content of the LINKS/ subdirectory in the translation file. Currently, top solution is to avoid using LINKS/; figure out the link/location from the filename of the PO file. As long as the PO file is not renamed, it should be able to be pushed
10. Add checks to the PO files, as in msgfmt -c.
11. Find a way to check if the XML file has been updated. Use a version date?
12. Use Last-Translator field for —author when committing.