![]() " with the URL to more about it, would not look too invasive. maybe a polite hint on 10n, like " seven more days to. My comment to all in advance:"where were you all, when I needed you".Īs regards the question about helping localizers keep deadlines. Note: with this hint I am probably risking a barrage of Why-dont-you, Havent-you-read and I-told-you-so comments. If this is not doable, then whoever has an en-US tree on hand, drop me a note. This can be done with one single compare, run once and for all languages. Hint 1: provide the en-US tree in l10n/releases, to serve as a source and template for a given channel. I asked for it already several times already: I really have no need for those extra 1394.56MB, the en-US tree, extracted from up-to-date product repositories, is all I would need. The size of my local Aurora repository is 1.4GB, out of which I need just 5.44MB in size. One more point: there's absolutely no need for localizers to have complete product repositories on hand. Anyhow, I have a strange feeling, that is one, two or even three repositories too many. Vito: with three channels (central, aurora, beta), each involving two product repositories, mozilla and comm, and one l10n repository, it is pretty hard to keep your ducks lined up properly - they get out of of line every six weeks anyhow. What suggestions would you give to remind communities about upcoming deadlines without giving the impression of being driven by deadlines? Jeff: Many communities struggle with remembering deadlines, causing their localized releases to fall behind with each release. Note, that there's differences between different language teams, from a lonely wolf to a well-oiled localization machine, involving several Mozillians (see my blog on localizing SuMo) so it is not one-shoe-fits-them-all. So what one needs is endurance first of all and any help to sustain it. I wonder if anybody, starting on this journey knows, what it takes (as of end of June, the aurora SL repository contains close to 70.000 words). That applies above all to the language teams among the 25% that are not yet fully there. Vito: what helps most, is attention and a positive feed-back. ![]() Do you feel that there is anything we can do to help re-inspire a " go-get-em drive" in localizers? Jeff: others, I'm sure, have shared this aspect of your experience. I am sure there's been a lot of soul searching and fighting over possible fall-outs involved in the decision.This is just one more negative side effect that was to be expected. Fore me it resulted in kind of a tunnel-vision response, with the dashboard record for Firefox, Fennec, Thunderbird and Calendar (times Aurora, Beta and Central) on the one side and the ticking deadlines bomb on the other side.Īs regards your second question: I think the major reason for " watch-for-deadlines routine" is the time squeeze. Instead of " watch-for-deadlines routine" one could talk about " riding on the release bus", were it not for the switch to tighter release cycles. I wish the remaining quarter all the best on their way to the " watch-for-deadlines routine". Note that 77 out of 106 languages represented in l10n repository can boast with an official 13.0.1 Firefox version. It just has to be understood as a sign of persistence. The evolution from " Go-get-em drive" to " watch-for-deadlines routine" is thus (of course) a natural result of contributing to the project over a longer period of time. With Fennec it is a similar story, with somewhat changed border conditions: after a year of active involvement we have nightly builds, but as yet no official release.Īs you see, I am not limiting the context just to Firefox, as was your initial intention. With Thunderbird it took us a whole year, if not more, to get fully involved in the release process. Firefox in Slovenian language has been around since ages, but it is a different story with Thunderbird and Fennec. ![]() ![]() Vito: what I meant by " Go-get-em drive" was getting into the release process in the first place. Jeff: you wrote that " from initial go-get-em drive it has turned into watch-for-deadlines routine." Do you attribute the evolution of a " go-get-em drive" to a " watch-for-deadlines routine" to being a natural result of contributing to the project over a long period of time? Or to any of the current l10n policies, communications, or procedures? Jeff then sent me a barrage of questions, which I am copying below, with my answers to them. The survey asked for additional comments and I raised my hand. ![]() Some time ago Jeff Beatty asked localizers to fill out a survey about motivations/reasons for doing localization of Firefox.The results of the survey can be read in Jeff's blog Why we localize Firefox. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |