When I read that all our requirements were met with Weblate I got the
feeling that it was the perfect solution ...
> Workflow proposal:
... but when I read your proposed workflow a few doubts arose.
> - When a new file needs to be translated, I need to create a new
> 'component' on Weblate, linked to the .po file, and it will be available
> to all translators.
Do we need to manual notify and create a "component" whenever a new file
is available for translation in our repo? Because if Weblate can't do
that automatically then this doesn't really "pull automatically from our
main Git repo". Well, somehow, but that's suboptimal...
And then, how are those "components" displayed to the user? Are their
organized automatically according to the structure of our file system?
Do you have screenshots of how to whole structure of the Git repo is
displayed to the user?
> - when a .po file has been reviewed, download it from the web interface
As a core developer with commit bit, do I really have to go through the
web interface to download the latest translations? If so, then this
doesn't match the requirement stated as "so that core developers only
have to fetch reviewed translations from there".
> - Weblate could pull automatically the tails repo without any safety
> problems for us.
So I have to manually activate a component, but then it's pulled
automatically?
