On 07/02/2014 07:07 PM, Ying Chun Guo wrote: > Hello, Elizabeth > > I could try to be infrastructure meeting. > When is the next infrastructure meeting? > > Now we cannot create new projects in Transifex. > See: https://bugs.launchpad.net/openstack-i18n/+bug/608725/comments/6
O noes! > It's a big issue for us. > Transifex supporting team is helping, but the response time is not that > quick. > > We do need to have another candidate to take place Transifex. > > I notice the key issue with Zanata is the JBoss version and license. > How about we use a Redhat donated enterprise version ? Ok. So - we don't want enterprise licenses for infra things. HOWEVER If it's a temporary thing, and I mean one with a commitment, like a real commitment (I might want Brian Stevens to chime in) to get the non-enterprise stuff working sensibly - then I could be convinced. I've included Mark McLoughlin here, because he knows everything ... Mark? > > Anita Kuno <ante...@anteaya.info> wrote on 2014/07/03 00:37:54: > >> Anita Kuno <ante...@anteaya.info> >> 2014/07/03 00:37 >> >> To >> >> openstack-infra@lists.openstack.org, >> >> cc >> >> Subject >> >> Re: [OpenStack-Infra] Current options for getting Zanata going >> >> On 07/02/2014 12:25 PM, Elizabeth K. Joseph wrote: >>> On Wed, Jul 2, 2014 at 8:04 AM, Anita Kuno <ante...@anteaya.info> > wrote: >>>> I'd like to look at this in terms of the end goal, translations. That > is >>>> the end goal, yes? >>>> >>>> Is one tool any better than the other (zanta and pootle are the two >>>> options, yes?) at doing translating? Is the end product substantially >>>> better using one tool than the other? >>> >>> Right, Zanata and Pootle are the two leading options. The translations >>> team seemed to prefer Zanata so we said we'd work to get a demo going >>> for them so they could try it themselves, just like we have for >>> Pootle. >>> >>> On our end maintainability is the major consideration, since we don't >>> want to deploy a solution that will be disruptive to translators >>> (during upgrades, etc) or insecure. >>> >> Can we get an item on next week's infra agenda and have some of the >> folks doing the translation work attend and offer their opinion? >> >> It seems we might be at a point of weighing costs of setup and >> maintenance time versus advantages of use. >> >> Thanks, >> Anita. >> >> _______________________________________________ >> OpenStack-Infra mailing list >> OpenStack-Infra@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra >> >> >> >> _______________________________________________ >> OpenStack-Infra mailing list >> OpenStack-Infra@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra _______________________________________________ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
