<div dir="ltr"><div>I have no comment on Liberty translation priority atm.</div><div><br></div><div>I think a couple of different topics are discussed at the same here.<br></div><div><br></div><div>* CLI translation priority</div><div>* Server side project translation priority</div><div>* (potential) usage of server side project translations in Horizon</div><div><br></div><div>We need to have more contact with project teams in the next cycle</div><div>more deeply to decide translation priorties before starting translations.</div><div>In the past releases, i18n team tended to start discussions after starting</div><div>translations and it is too late for the game in most cases.</div><div><br></div><div>Regarding client projects, I know openstackclient is our future and</div><div>the keystone team encourage to use openstackclient for Keystone v3 API.</div><div>However, regarding other projects like nova or neutron,<br></div><div>the progress of openstackclient integration is not well enojgh</div><div>and a new feature is implemented in each client.</div><div>Thus we need to consider the priority in the next cycle.</div><div><br></div><div>For other topics, I will comment on them later if necessary.</div><div><br></div><div>Akihiro</div><div><div class="gmail_extra"><br><div class="gmail_quote">2015-09-18 22:33 GMT+09:00 Ying Chun Guo <span dir="ltr"><<a href="mailto:guoyingc@cn.ibm.com" target="_blank">guoyingc@cn.ibm.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><font size="2" face="sans-serif">very important information.</font>
<br><font size="2" face="sans-serif">I don't think translators would like
to translate already <br>
deprecated or in the future deprecated clients.</font>
<br><font size="2" face="sans-serif">I might not be able to include openstack
client in the Liberty translation plan.</font>
<br><font size="2" face="sans-serif">But I would put it high priority after
Liberty translation.</font>
<br><font size="2" face="sans-serif">And next release, I will add openstack
client to in the translation plan.</font>
<br><span class="">
<br><font size="2" face="sans-serif">Best regards<br>
Ying Chun Guo (Daisy)<br>
</font>
<br>
<br></span><span class=""><tt><font size="2">Andreas Jaeger <<a href="mailto:aj@suse.com" target="_blank">aj@suse.com</a>> wrote on 09/18/2015
04:51:32 PM:<br>
<br>
> From: Andreas Jaeger <<a href="mailto:aj@suse.com" target="_blank">aj@suse.com</a>></font></tt>
<br></span><tt><font size="2">> To: Ying Chun Guo/China/IBM@IBMCN</font></tt>
<br><tt><font size="2">> Cc: "<a href="mailto:openstack-i18n@lists.openstack.org" target="_blank">openstack-i18n@lists.openstack.org</a>"
<<a href="mailto:openstack-i18n@lists.openstack.org" target="_blank">openstack-i18n@lists.openstack.org</a>></font></tt>
<br><tt><font size="2">> Date: 09/18/2015 04:52 PM</font></tt>
<br><tt><font size="2">> Subject: Re: [Openstack-i18n] translating python
clients</font></tt>
<br><div><div class="h5"><tt><font size="2">> <br>
> On 09/18/2015 10:35 AM, Ying Chun Guo wrote:<br>
> > Andreas,<br>
> ><br>
> > Forgive me if I ask funny question.<br>
> <br>
> There are no funny questions, please ask!<br>
> <br>
> > I see there is python-openstackclient in Zanata server.<br>
> > What is it for ?<br>
> <br>
> python-openstackclient is the "unnifed OpenStack client"
that will <br>
> replace the per-project clients like python-keystoneclient (command
<br>
> keystone).<br>
> <br>
> See </font></tt><a href="http://docs.openstack.org/developer/python-openstackclient/" target="_blank"><tt><font size="2">http://docs.openstack.org/developer/python-openstackclient/</font></tt></a><tt><font size="2"><br>
> <br>
> > What is the relationship between python-openstackclient and other
python<br>
> > clients ( e.g python-keystoneclient,<br>
> > python-heatclient, and python-novaclient) ?<br>
> <br>
> The goal of python-openstackclient is to replace these. keystoneclient
<br>
> is already deprecated in favor of openstackclient.<br>
> <br>
> So, priority wise: openstackclient has higher priority than the others.
<br>
> The question for me is whether we want to translate these already
<br>
> deprecated or in the future deprecated clients at all.<br>
> <br>
> Btw. I also think that the python-openstackclient has a higher priority
<br>
> than nova - but lower than horizon. Both horizon and the client address
<br>
> the end user while nova addresses the adminstrator,<br>
> <br>
> Andreas<br>
> <br>
> > Best regards<br>
> > Ying Chun Guo (Daisy)<br>
> ><br>
> ><br>
> > Andreas Jaeger <<a href="mailto:aj@suse.com" target="_blank">aj@suse.com</a>> wrote on 09/18/2015 01:45:37
AM:<br>
> ><br>
> > > From: Andreas Jaeger <<a href="mailto:aj@suse.com" target="_blank">aj@suse.com</a>><br>
> > > To: "<a href="mailto:openstack-i18n@lists.openstack.org" target="_blank">openstack-i18n@lists.openstack.org</a>"<br>
> > <<a href="mailto:openstack-i18n@lists.openstack.org" target="_blank">openstack-i18n@lists.openstack.org</a>><br>
> > > Date: 09/18/2015 01:47 AM<br>
> > > Subject: [Openstack-i18n] translating python clients<br>
> > ><br>
> > > We now have setup python-keystoneclient for translation
and there're<br>
> > > requests for python-heatclient and python-novaclient<br>
> > > (</font></tt><a href="https://review.openstack.org/224832heat" target="_blank"><tt><font size="2">https://review.openstack.org/224832heat</font></tt></a><tt><font size="2">
and<br>
> > > </font></tt><a href="https://review.openstack.org/224222nova" target="_blank"><tt><font size="2">https://review.openstack.org/224222nova</font></tt></a><tt><font size="2">)<br>
> > ><br>
> > > Does it really make sense to translate these? Especially
with the<br>
> > > openstack client getting translated already?<br>
> > ><br>
> > > My proposal would be to concentrate on the openstack
client and tell the<br>
> > > teams to not mark the clients for translation.<br>
> > ><br>
> > > What do you think?<br>
> > ><br>
> > > Please see also<br>
> > ><br>
> > </font></tt><a href="http://lists.openstack.org/pipermail/openstack-dev/2015-September/" target="_blank"><tt><font size="2">http://lists.openstack.org/pipermail/openstack-dev/2015-September/</font></tt></a></div></div><tt><font size="2"><div><div class="h5"><br>
> 073698.html<br>
> > ><br>
> > > Andreas<br>
> > > --<br>
> > > Andreas Jaeger aj@{<a href="http://suse.com" target="_blank">suse.com</a>,<a href="http://opensuse.org" target="_blank">opensuse.org</a>} Twitter/Identica:
jaegerandi<br>
> > > SUSE LINUX GmbH, Maxfeldstr. 5, 90409
Nürnberg, Germany<br>
> > > GF: Felix Imendörffer, Jane Smithard,
Graham Norton,<br>
> > > HRB 21284 (AG Nürnberg)<br></div></div>
> > > GPG fingerprint = 93A3 365E CE47
B889 DF7F FED1 389A 563CC272 A126<span class=""><br>
> > ><br>
> > ><br>
> > > _______________________________________________<br>
> > > Openstack-i18n mailing list<br>
> > > <a href="mailto:Openstack-i18n@lists.openstack.org" target="_blank">Openstack-i18n@lists.openstack.org</a><br>
> > > </span></font></tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n" target="_blank"><tt><font size="2">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n</font></tt></a><div class="HOEnZb"><div class="h5"><tt><font size="2"><br>
> <br>
> <br>
> -- <br>
> Andreas Jaeger aj@{<a href="http://suse.com" target="_blank">suse.com</a>,<a href="http://opensuse.org" target="_blank">opensuse.org</a>} Twitter/Identica:
jaegerandi<br>
> SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany<br>
> GF: Felix Imendörffer, Jane Smithard, Graham Norton,<br>
> HRB 21284 (AG Nürnberg)<br>
> GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1
389A 563C C272 A126<br>
> <br>
</font></tt></div></div><br>_______________________________________________<br>
Openstack-i18n mailing list<br>
<a href="mailto:Openstack-i18n@lists.openstack.org">Openstack-i18n@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n</a><br>
<br></blockquote></div><br></div></div></div>