Hi!
You should ask to Noriko Mizumoto, she surely knows better about Zanata details.
Cheers,
Sylvia
On Mon, 2016-08-15 at 12:46 +0200, Petr Kovar wrote:
On Fri, 12 Aug 2016 13:18:15 -0400Zach Oglesby <zach@xxxxxxxxxx> wrote:On Thu, Aug 11, 2016, at 09:34 AM, Brian Exelbierd wrote:This email is to drive some discussion around $subject. Itfollows froma blog soon to be posted on the Fedora Community blog(https://communityblog.fedoraproject.org). The text below is copiedfrom that blog:Translation needs clarity on how to get updates published and theprocess.This seemed like a communication problem between the two projects thatneeded to be resolved with better docs on the process and hand-offprocedures. Because the tooling proposal will hopefully includecontinuous deployment, this may become a lot easier in the future.Please reply here for discussion.regards,bexOne of the goals of the new system is to handle publishingautomatically, this will include translations that are ready to bepublished. Unfortunately, we do not have the final plan worked out yet,and I don't have a clear way to tell the translation team how it willdefinitively work, but I can explain my the idea I have worked out in myhead and hope that it will help as we move forward.Step 1: Commits are made to a release branch of a documentStep 2: The CI/CD system will run and create PO files push them tozanataNot sure if we can make Zanata talk to a CI/CD system. The usual workflowis that you sync between Zanata and your git repo, meaning POTs/POsmust be stored in that (or another) git repo. Anyway, Zanata people wouldknow more.Cheers,pk--docs mailing listTo unsubscribe:https://lists.fedoraproject.org/admin/lists/docs@xxxxxxxxxxxxxxxxxxxxxxx
-- docs mailing list docs@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://lists.fedoraproject.org/admin/lists/docs@xxxxxxxxxxxxxxxxxxxxxxx
