The script is being updated, and I think at this stage it is useful for those that are willing to look at the Python code.

Having said that, you can use the script now to create clones for, let’s say, gnome-2-26 with a single command. Then, you can run with ‘–update-vcs’ which will go through the local repositories and do ‘git pull –rebase’ for you. It takes 8 and a half minutes on my system to go through the 93 modules, if no changes are there.

Regarding branches: We use full clones. When commiting, we check through the release that was specified if a module is at ‘master’ (we then commit to ‘master’ only), or if a branch is specified, we commit to both branch + ‘master’. This shall be added soon to the script.

Dimitris, regarding Transifex, I believe that it is of the interest of GNOME to have several options for the committing of translations.

Technically, you would need a new GNOME git account and a facility that would allow language team coordinators to delegate the committing of translations through Transifex. That is, a language team coordinator would enable the committing of translations through this additional avenue.

My primary view of this script is to have permanent local repositories of a whole GNOME release (about 2GB), and the script would allow to bring under a single directory all PO files. Having the same interface to submit translations through Transifex would be another big plus.

I think it’d be very interesting to see the tool interoperate with Transifex too. Ideally it should use Tx’s commit mechnism, which would reduce the code quite a bit, and allow submission to any VCS backend.