Am 2019-04-28 10:01, schrieb Andreas Jaeger:
On 27/04/2019 03.56, Frank Kloeker wrote:
[...]
The biggest problem at the moment are pot files. Weblate expects this
in
the source repo which we haven't. But Weblate has it's own local
repos.
It's not clear at the moment how we design the
On 27/04/2019 03.56, Frank Kloeker wrote:
> [...]
> The biggest problem at the moment are pot files. Weblate expects this in
> the source repo which we haven't. But Weblate has it's own local repos.
> It's not clear at the moment how we design the workflow. Zuul can also
> push changes on rst
On 27/04/2019 03.56, Frank Kloeker wrote:
> [...]
> The biggest problem at the moment are pot files. Weblate expects this in
> the source repo which we haven't. But Weblate has it's own local repos.
> It's not clear at the moment how we design the workflow. Zuul can also
> push changes on rst
Am 2019-04-26 18:31, schrieb cor...@inaugust.com:
Frank Kloeker writes:
Just as a follow up: I've wrote down all required steps and ideas for
a migration to Weblate on [1].
Thanks for that! Will this be a topic at the PTG?
Not yet. I've just created our team Etherpad [1] and I think it
Frank Kloeker writes:
> Just as a follow up: I've wrote down all required steps and ideas for
> a migration to Weblate on [1].
Thanks for that! Will this be a topic at the PTG?
> There are some issues adressed but thats not unsolvable (i.e. invent
> openstackid as a OpenId provider).
We may
Am 2019-04-19 18:57, schrieb Frank Kloeker:
Am 2019-04-08 09:13, schrieb Ian Wienand:
On Tue, Apr 02, 2019 at 12:28:31PM +0200, Frank Kloeker wrote:
The OpenStack I18n team was aware about the fact, that we will run
into an
unsupported platform in the near future and started an investigation
Am 2019-04-08 09:13, schrieb Ian Wienand:
On Tue, Apr 02, 2019 at 12:28:31PM +0200, Frank Kloeker wrote:
The OpenStack I18n team was aware about the fact, that we will run
into an
unsupported platform in the near future and started an investigation
about
the renew of translation platform on
On Tue, Apr 02, 2019 at 12:28:31PM +0200, Frank Kloeker wrote:
> The OpenStack I18n team was aware about the fact, that we will run into an
> unsupported platform in the near future and started an investigation about
> the renew of translation platform on [1].
> [1]
>
Am 2019-03-25 23:14, schrieb Ian Wienand:
On Fri, Mar 15, 2019 at 11:01:44AM +0100, Andreas Jaeger wrote:
Anybody remembers or can reach out to Zanata folks for help on
fixing this for good, please?
From internal communication with people previously involved with
Zanata, it seems the team has
On Fri, Mar 15, 2019 at 11:01:44AM +0100, Andreas Jaeger wrote:
> Anybody remembers or can reach out to Zanata folks for help on
> fixing this for good, please?
From internal communication with people previously involved with
Zanata, it seems the team has disabanded and there is no current
Hello Carlos,
I am not sure which team you are working currently, but heard that you are
working in a tooling team a few months ago - would u help to resolve this?
I can’t forget your name - we met on Tokyo Summit in 2015, and many
OpenStack team members appreciate your lots of effort on Zanata +
All translation jobs are failing since zanata-cli fails, looking at the
error it looks like Java11 is too new for zanata-cli.
I tested the most recent zanata-cli package 4.6.2 (from last year), and
it failed as well.
Logs:
12 matches
Mail list logo
