shahar1 commented on PR #55604: URL: https://github.com/apache/airflow/pull/55604#issuecomment-3288554215
> > > I tried an experiment here - added my commit where I AI-generated all trasnslations following exisitng ones and maybe we can do it in the way that translators will just review and approve (or update) the translations for their language so that in the "freeze" period we can do a joined effort in a single PR. > > > > > > Does it mean that we need to wait for every language reviewer to approve the translations before merging? How should we handle situations where one or more reviewers take a long time to respond? > > That's a good question - we have not done it before so this is a kind of experiment (and it is mostly based on the fact that **likely** the translation done by AI now when we have almost complete set of translations, will be generally very good. > > It is for PL for example. Fully automatically generated and it's **perfect**. > I tried an experiment here - added my commit where I AI-generated all trasnslations following exisitng ones and maybe we can do it in the way that translators will just review and approve (or update) the translations for their language so that in the "freeze" period we can do a joined effort in a single PR. > > cc: @shahar1 -> WDYT ? I'm up for trying it - like @jason810496 mentioned, we now depend on 16 translation owners for their approval and the more languages are added, the more time consuming the approval will take. Also, the AI did a good job overall - few misses, but I think that over time we could figure out a better prompt to avoid them :) In general, if the feature is "nice to have", there aren't too many additions, and the untranslated terms won't **significantly** affect the UX - I'm ok with approving the exemptions at the cost of few "misses" in some translations (I've just created a PR for updating the policy with some guidelines about that). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
