>If a user can push the updated translation files directly to GIT, then no problem with daily updates.
>Instead if the user has to submit a patch and then one of the developers
have to push it, then daily updates are not the best IMO.
Most translators don't know about GIT, and if I may voice my opinion nor should they have to. Sites like Transifex exist for good reason. Translators can work on multiple projects within the one site and one login. While I'm not a fan of Canonical (although I used be be a big fan of Ubuntu) I do like Launchpad but I much prefer sites like Transifex. People who have been on sites such as this look for new projects, they have their resources (glossaries etc.) and this can make translation quick and relatively painless (as long as the source pot files are consistent with terminology and conventions). Users don't submit patches they translate the original pot file, which btw remains intact, and a po file is created. Everytime an updated pot file is uploaded the site lets the user know how many strings/words and what % of the file requires translating. Everytime the translator translates a string the po file is updated. All that is then required is reviewing the translation and that is done within each language team leaving the developer to continue developing.
That brings me to the 2nd part of my reply. Sites like transifex have 99% of the details already there, translators don't have to wade through alot of information, developers don't have to write up alot of information, it is already 99% there. All the developer really needs to do is load the pot files in the order they require them to be translated, and start off the different translation teams (language teams). Once a team has a team leader the team leader can control the team members leaving the developer with simply uploading the pot files and downloading the translated po files in a timely manner (once a week /month or so) and merging them into the source packages as they would do anyway.
Cheers.