[prev in list] [next in list] [prev in thread] [next in thread]
List: fedora-docs-list
Subject: Re: Translation needs clarity on how to get updates published and the process.
From: Pete Travis <me () petetravis ! com>
Date: 2016-08-15 15:21:22
Message-ID: CAPDshLtRfDoH7-70=p4h3CjUpJ=Sro8DXT2oAe1VVQJ-YFM2Rw () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On Aug 15, 2016 5:46 AM, "Petr Kovar" <pkovar@redhat.com> wrote:
>
> On Fri, 12 Aug 2016 13:18:15 -0400
> Zach Oglesby <zach@oglesby.co> wrote:
>
> > On Thu, Aug 11, 2016, at 09:34 AM, Brian Exelbierd wrote:
> > > This email is to drive some discussion around $subject. It
> > > follows from
> > > a blog soon to be posted on the Fedora Community blog
> > > (https://communityblog.fedoraproject.org). The text below is copied
> > > from that blog:
> > >
> > > Translation needs clarity on how to get updates published and the
> > > process.
> > >
> > > This seemed like a communication problem between the two projects that
> > > needed to be resolved with better docs on the process and hand-off
> > > procedures. Because the tooling proposal will hopefully include
> > > continuous deployment, this may become a lot easier in the future.
> > >
> > > Please reply here for discussion.
> > >
> > > regards,
> > >
> > > bex
> >
> > One of the goals of the new system is to handle publishing
> > automatically, this will include translations that are ready to be
> > published. 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 will
> > definitively work, but I can explain my the idea I have worked out in my
> > head and hope that it will help as we move forward.
> >
> > Step 1: Commits are made to a release branch of a document
> > Step 2: The CI/CD system will run and create PO files push them to
> > zanata
>
> Not sure if we can make Zanata talk to a CI/CD system. The usual workflow
> is that you sync between Zanata and your git repo, meaning POTs/POs
> must be stored in that (or another) git repo. Anyway, Zanata people would
> know more.
>
> Cheers,
> pk
> --
Zanata has an API, and there are cli tools for uploading POTs. A CI
platform should be able to run the same cli commands I can; Zanata pulling
would be nice, but it it feasible to automatically update Zanata projects
without it.
-- Pete
[Attachment #5 (text/html)]
<p dir="ltr"></p>
<p dir="ltr">On Aug 15, 2016 5:46 AM, "Petr Kovar" <<a \
href="mailto:pkovar@redhat.com">pkovar@redhat.com</a>> wrote:<br> ><br>
> On Fri, 12 Aug 2016 13:18:15 -0400<br>
> Zach Oglesby <<a href="mailto:zach@oglesby.co">zach@oglesby.co</a>> \
wrote:<br> ><br>
> > On Thu, Aug 11, 2016, at 09:34 AM, Brian Exelbierd wrote:<br>
> > > This email is to drive some discussion around $subject. It<br>
> > > follows from<br>
> > > a blog soon to be posted on the Fedora Community blog<br>
> > > (<a href="https://communityblog.fedoraproject.org">https://communityblog.fedoraproject.org</a>). \
The text below is copied<br> > > > from that blog:<br>
> > ><br>
> > > Translation needs clarity on how to get updates published and the<br>
> > > process.<br>
> > ><br>
> > > This seemed like a communication problem between the two projects \
that<br> > > > needed to be resolved with better docs on the process and \
hand-off<br> > > > procedures. Because the tooling proposal will hopefully \
include<br> > > > continuous deployment, this may become a lot easier in the \
future.<br> > > ><br>
> > > Please reply here for discussion.<br>
> > ><br>
> > > regards,<br>
> > ><br>
> > > bex<br>
> ><br>
> > One of the goals of the new system is to handle publishing<br>
> > automatically, this will include translations that are ready to be<br>
> > published. Unfortunately, we do not have the final plan worked out yet,<br>
> > and I don't have a clear way to tell the translation team how it \
will<br> > > definitively work, but I can explain my the idea I have worked out \
in my<br> > > head and hope that it will help as we move forward.<br>
> ><br>
> > Step 1: Commits are made to a release branch of a document<br>
> > Step 2: The CI/CD system will run and create PO files push them to<br>
> > zanata<br>
><br>
> Not sure if we can make Zanata talk to a CI/CD system. The usual workflow<br>
> is that you sync between Zanata and your git repo, meaning POTs/POs<br>
> must be stored in that (or another) git repo. Anyway, Zanata people would<br>
> know more.<br>
><br>
> Cheers,<br>
> pk<br>
> --</p>
<p dir="ltr">Zanata has an API, and there are cli tools for uploading POTs. A CI \
platform should be able to run the same cli commands I can; Zanata pulling would be \
nice, but it it feasible to automatically update Zanata projects without it.</p> <p \
dir="ltr">-- Pete<br> </p>
[Attachment #6 (text/plain)]
--
docs mailing list
docs@lists.fedoraproject.org
To unsubscribe:
https://lists.fedoraproject.org/admin/lists/docs@lists.fedoraproject.org
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic