The most interesting candidate is Damned Lies from Gnome:
https://wiki.gnome.org/DamnedLies
It requires changes to the SVN backend (or a custom one) to deal with our directory structure.
Or we could switch to a flat directory structure.
Well, I always said that DamnedLies is much better than anything eles (Pootle/Transifex/Weblate/etc), but I think we need to keep normal SVN access available as we have lots of file in KDE that are just few strings, and the whole process of downloading translating uploading for each one will be a huge headache :)
I never questioned the direct access to SVN, which is a central requirement and it is not prevented by the usage of that website.
The idea is to mostly use the website as we use the current one (view of the status, statistics) with the availibility of a reservation system which teams may use or not, and regardless from the way files are pushed.
What about a reservation system within lokalize, a coordinator would be able to update a reservation status on each file from the Project View then commit the reservations to SVN.
It would host a flat file that would be stored on SVN, and the site would just display these meta-information (we could add new columns if needed).
That seems like a cheap way to offer a new integrated system, and if teams choose another way to handle reservations they could still be displayed within lokalize, using that flat file as an input.
SVN already support reserving (‘locking’) files:
http://svnbook.red-bean.com/en/1.7/svn.advanced.locking.html
Couldn’t we just use that feature, instead of storing a flat file?
Maybe, or maybe not. A web interface with reservation will be needed anyway, and if a web translation system won't provide it, we will still need this.