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 -0400
> Zach Oglesby <zach(a)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
--
docs mailing list
docs(a)lists.fedoraproject.org
To unsubscribe:
>
https://lists.fedoraproject.org/admin/lists/docs@lists.fedoraproject.
org