<html><body>
<p><font size="2" face="sans-serif">I think it could be an alternative solution.</font><br>
<font size="2" face="sans-serif">Of course, we will continue to work for a test environment in openstack infra but it might take time.</font><br>
<br>
<font size="2" face="sans-serif">@Akihiro, what's your opinion ?</font><br>
<br>
<font size="2" face="sans-serif">Best regards<br>
Ying Chun Guo (Daisy)<br>
</font><br>
<br>
<tt><font size="2">Douglas Fish <drfish@us.ibm.com> wrote on 2015/03/19 07:22:23:<br>
<br>
> From: Douglas Fish <drfish@us.ibm.com></font></tt><br>
<tt><font size="2">> To: Akihiro Motoki <amotoki@gmail.com></font></tt><br>
<tt><font size="2">> Cc: "openstack-i18n@lists.openstack.org" <Openstack-i18n@lists.openstack.org></font></tt><br>
<tt><font size="2">> Date: 2015/03/19 07:26</font></tt><br>
<tt><font size="2">> Subject: Re: [Openstack-i18n] Horizon translation check site for Kilo</font></tt><br>
<tt><font size="2">> <br>
> I've been thinking about Akihiro's request and it seems to me one of the<br>
> key challenges is finding the infrastructure to support this testing.<br>
> Maybe we should avoid the need for infrastructure entirely.<br>
> <br>
> I wonder if it would be more straightforward to enable the translators to<br>
> update a local, devstack based version of Horizon by running a script to<br>
> copy in-progress translations to their local Horizon. Akihiro has shared<br>
> some of the tooling he has used to manage this. I'm thinking of turning<br>
> this into a script that could be used after setting up Horizon to<br>
> automatically download, compile, and configure an updated translation.<br>
> <br>
> Would this be a useful approach for the translation community?<br>
> <br>
> Doug Fish<br>
> <br>
> Akihiro Motoki <amotoki@gmail.com> wrote on 03/04/2015 09:57:29 AM:<br>
> <br>
> > From: Akihiro Motoki <amotoki@gmail.com><br>
> > To: "openstack-i18n@lists.openstack.org"<br>
> <Openstack-i18n@lists.openstack.org><br>
> > Date: 03/04/2015 09:58 AM<br>
> > Subject: Re: [Openstack-i18n] Horizon translation check site for Kilo<br>
> ><br>
> > Thanks Andreas. It sounds useful and interesting topic.<br>
> > Regarding infra-cloud, I think it is enough that some limited set offolks<br>
> from<br>
> > i18n and docs team. Not all translators and doc writes need to access<br>
> > such infra.<br>
> > Of course we can continue to discuss with the infra team.<br>
> ><br>
> > Perhaps we need to break down plans and action items<br>
> > so that anyone interested in the work can join.<br>
> > The important thing is that we cannot assume the situation changes<br>
> > release by release as personnel, so we need more steady way *as a team*.<br>
> ><br>
> > I sent the previous mail to mention that I cannot have enough time for<br>
> > I18N work in Kilo and collect more involevement from other folks :-)<br>
> > I know not a small portion of folks involved work on translations<br>
> > as your private time effort (including me). Thus we need to work as a<br>
> team.<br>
> ><br>
> > Akihiro<br>
> ><br>
> ><br>
> > 2015-03-05 0:38 GMT+09:00 Andreas Jaeger <aj@suse.com>:<br>
> > > On 03/04/2015 04:30 PM, Akihiro Motoki wrote:<br>
> > >> Hi,<br>
> > >><br>
> > >> Kilo-3 is approaching and it is the time to start translations for<br>
> Kilo.<br>
> > >> I would like to know the status of the community effort on preparing<br>
> > >> the Horizon translation check site.<br>
> > >><br>
> > >> In the past releases, I18N team has the horizon translation check site<br>
> > >> but it was completely provided by my resource and time.<br>
> > >> For Kilo cycle, I am sure I can provide such site at all because I am<br>
> > >> spending very busy days on my main work.<br>
> > >><br>
> > >> The same situation continues for three release cycles<br>
> > >> and I think it is time we should have such site as the team.<br>
> > >> We should not depend on someone's personal effort as OpenStack<br>
> community.<br>
> > >><br>
> > >> I may be able to provide the site for Kilo release if I have time<br>
> > but not sure.<br>
> > >> I would like to raise this topic.<br>
> > >> If nobody other than me raises a hand, it is no longer a team<br>
> > >> and it means we fail as a community.<br>
> > >> I can help the work but don't have enough time to lead it.<br>
> > >><br>
> > >> I hope we have a progress on it.<br>
> > ><br>
> > > I raised the issue on the infra meeting yesterday - see topic<br>
> Infra-cloud:<br>
> > ><br>
> > > <a href="http://eavesdrop.openstack.org/meetings/infra/2015/infra">http://eavesdrop.openstack.org/meetings/infra/2015/infra</a>.<br>
> > 2015-03-03-19.01.html<br>
> > ><br>
> > > I suggest you continue discussion with the infra folks involved with<br>
> the<br>
> > > infra-cloud as well,<br>
> > ><br>
> > > Andreas<br>
> > > --<br>
> > > Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi<br>
> > > SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany<br>
> > > GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu,<br>
> > > Graham Norton, HRB 21284 (AG Nürnberg)<br>
> > > GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272<br>
> A126<br>
> > ><br>
> ><br>
> ><br>
> ><br>
> > --<br>
> > Akihiro Motoki <amotoki@gmail.com><br>
> ><br>
> > _______________________________________________<br>
> > Openstack-i18n mailing list<br>
> > Openstack-i18n@lists.openstack.org<br>
> > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n</a><br>
> ><br>
> <br>
> <br>
> _______________________________________________<br>
> Openstack-i18n mailing list<br>
> Openstack-i18n@lists.openstack.org<br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n</a><br>
> <br>
</font></tt></body></html>