On Tue, Jun 14, 2011 at 11:54:43AM -0400, David Nalley wrote: > On Tue, Jun 14, 2011 at 11:38 AM, Toshio Kuratomi <a.badger@xxxxxxxxx> wrote: > > On Tue, Jun 14, 2011 at 12:44:54PM +0200, Kévin Raymond wrote: > >> On Tue, Jun 14, 2011 at 12:33 PM, Dimitris Glezos <glezos@xxxxxxxxxxx> wrote: > >> > On Tue, Jun 14, 2011 at 12:21 AM, Ruediger Landmann > >> > <r.landmann@xxxxxxxxxx> wrote: > >> >> Zanata[1] is a web-based translation interface that I would like to test > >> >> on Fedora infrastructure over the next six months. You can see a running > >> >> instance at https://translate.jboss.org > >> >> > >> >> I have filed an RFR[2] and would appreciate your feedback -- or better > >> >> still, your support! I feel confident that I will be able to get a > >> >> Zanata instance up and running, and that I will be able to recruit the > >> >> necessary project maintainers and translators necessary to test the > >> >> software. > >> > > >> > *sigh* > >> > > >> > Are there any specific concerns the Fedora translation community has > >> > raised about the existing, proven infrastructure which weren't > >> > addressed? Why do we need to test a new software? > >> > > >> > -d > >> > > >> > > >> > > >> > -- > >> > Dimitris Glezos > >> > > >> > >> I don't think so, this has not been discussed in the trans mailing list. > >> > > Since we've been paring down unused services in infrastructure recently, I'm > > inclined to wait for a need to arise/the translation community to ask for > > a new service before deploying something new. While theoretically someone > > in infrastructure could step forward to sponsor a zanata testing instance > > onto publictest boxes, it doesn't seem like a good use of time unless it > > addresses some need within Fedora.... > > > > -Toshio > > > I am inclined to agree with Toshio. > While there's obviously some bumps we ran into in the transition to > using tx.net's infrastructure this past release, I am almost certain > we'd run into issues transitioning to another platform, so I'd really > want to see compelling reasons why tx.net doesn't work. > In addition, getting a new platform up and going takes a lot of time. > For instance, Insight has taken more than a year, and at least the > base package was already in Fedora. Insight is probably not a good example case -- it was hobbled by a number of roadbumps. A very dedicated and highly skilled team could do much better![1] Nevertheless I agree in general with David and Toshio. Is this RFR related to some larger roadmap for Fedora translation that's been proposed and reviewed by the Fedora translation community list? * * * [1] Which, as I understand it, is one of the reasons that we're currently using tx.net. There were very few people with skill and interest who stepped up to maintain internal translation services in Fedora, despite a clear ongoing need and requests for help. My recollection is most of those who did are either now working to make tx.net serve our needs, or are part of this conversation. -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ The open source story continues to grow: http://opensource.com _______________________________________________ infrastructure mailing list infrastructure@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/infrastructure
