Thanks Shahar! Just left a few comments. If we’re to make it part of an AIP, a standalone one would probably be better IMO.
Best, Wei > On Jun 1, 2025, at 3:09 PM, Shahar Epstein <sha...@apache.org> wrote: > > Hello community! > > It's great to see that people from all over the world make Airflow > multilingual, thus accessible for even more people. > However, as Jarek mentioned in Slack [1], and as Jens prepares a PR that > adds plenty of new terms [2] - > I think that we need to make a short pause and discuss a > maintainability policy. > Jarek has already created a pre-commit [3] for automatically checking that > translations are completed, which is great - > but except for automation, I think that we need to agree as a community on > more broader terms, such as: responsibilities of language CODEOWNERS, > translation workflows, and quality standards. Specifically, within the > quality standards - we could list the "special terms" that should(n't) be > translated/transliterated [4]. > When writing this mail I thought that I could keep it short to include it > here - but then it got too long :) > Here's a link to a Google Docs I drafted - feel free to comment and suggest > changes: > https://docs.google.com/document/d/1Db2i12A0ZMfRAdEvoz4RQ0dLf0OBAcEpSIU-Cw6W3u4/edit?usp=sharing > > I'd like to ask to put it to a vote either as an independent AIP, or as an > extension of AIP-38 - so the policy will be clear and outlined for future > generations. > If there's a consensus for my request, I'll migrate the contents to the > Wiki. > > > Sincerely, > Shahar Epstein > > > *References* > [1] https://apache-airflow.slack.com/archives/C0809U4S1Q9/p1748730841507939 > [2] https://github.com/apache/airflow/pull/51243 > [3] https://github.com/apache/airflow/pull/51269 > [4] https://lists.apache.org/thread/bvsvoo4nln22wqkncxogpgtlpcd1fffj --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org For additional commands, e-mail: dev-h...@airflow.apache.org
