Re: Revisiting the translation freeze policies
aca <[email protected]>
| Newsgroups | gmane.linux.redhat.internationalization |
|---|---|
| Message-ID | <CAFtk_G57QpO1Rc8tQEoZ96iG3wBcByiva8KyfQcCgPWTVv3FCQ@mail.gmail.com> |
Hi, I would like to help with the translation but it is unfortunate that Filipino Language was not available. I hope I can be of service to other Fedora initiative other than Translation. Regards, Alvin On Tue, Oct 10, 2017 at 4:14 PM, Noriko Mizumoto <[email protected]> wrote: > Hi Randy, > Sorry, I was bit of behind and gave improper comment previously. Now I > think I caught up where we are. Let me do it again. Please see inline. > > > On Tue, Sep 26, 2017 at 5:18 AM, Randy Barlow < > [email protected]> wrote: > >> Greetings! >> >> During Friday's FESCo meeting[0] we were asked to approve a change to >> the release schedule to accommodate translation string freeze deadlines >> that somehow got left out of the new "no-alphas" schedule. >> >> Several participants pointed out that Fedora has not enforced the >> "string freeze" in many years, despite it being on the schedule until >> now. Thus, we would like to revisit the string freeze policy to >> determine if it is still valuable, and if so, how can/should it be >> enforced? >> >> We'd like to explore a couple of questions: >> >> * What exact things are frozen? Things like comps make sense to follow >> Fedora freezes, but do things like anaconda? or system-config-printer? >> > > > I've read through those, and it seems to me still valid and important for > Translation team. > https://fedoraproject.org/wiki/L10N_Freezes#string_freeze > https://fedoraproject.org/wiki/Software_String_Freeze_Policy > > For anaconda or s-c-printer, 'string freeze policy' should work. Most > likely we've been giving +2. If any particular concern on the developers > side, please share. > > > >> >> * Can we automate some way of enforcing or at least detecting when >> something changes a string in the freeze? >> > > > At last G11N FAD, i18n team raised their hand to explore some possibility > of developing a tool for detection (String Breakage monitoring by Jens and > Akira). Could you kindly check with i18n team as well? Or Pravin can > connect? > > G11N FAD Tokyo Summary: https://docs.google.com/document/d/17LU- > PmtuirbGd7wfxUuKTz7X6fsv82PVPgZaDELi4js/edit#heading=h.3gzh0ubdx8oy > > noriko > > > >> >> This ticket tracks the issue: >> >> https://pagure.io/fesco/issue/1777 >> >> >> [0] >> https://meetbot.fedoraproject.org/teams/fesco/fesco.2017-09-22-16.00.html >> _______________________________________________ >> trans mailing list -- [email protected] >> To unsubscribe send an email to [email protected] >> > > > _______________________________________________ > trans mailing list -- [email protected] > To unsubscribe send an email to [email protected] > > _______________________________________________ trans mailing list -- [email protected] To unsubscribe send an email to [email protected]