Re: [DISCUSS] i18n maintanability policy

2025-06-03 Thread Shahar Epstein
Thanks Brent! I've tried to polish the PR as best as I could (probably over-engineered by now :D) - I added relevant instructions for release managers. I'd be happy if final (re-)reviews could be made by tomorrow so I could start the voting thread. Shahar On Tue, Jun 3, 2025 at 9:30 PM Brent Bo

Re: [DISCUSS] i18n maintanability policy

2025-06-03 Thread Brent Bovenzi
Thanks for starting this Shahar! It's been great to see how excited the community is about i18n. I love how many PRs from first time contributors have come in. But yes, we should agree on standards before 3.1.0 is released. I agree with everything so far. A few notes - We will continue to add esli

Re: [DISCUSS] i18n maintanability policy

2025-06-01 Thread Amogh Desai
Thanks for starting the thread Shahar! Well put up and far better than email discussions! Thanks & Regards, Amogh Desai On Sun, Jun 1, 2025 at 7:59 PM Jens Scheffler wrote: > Hi all, > > thanks @shahar for posting the discussion and the document. First hand > also added a few comments but in

Re: [DISCUSS] i18n maintanability policy

2025-06-01 Thread Jens Scheffler
Hi all, thanks @shahar for posting the discussion and the document. First hand also added a few comments but in general 99% agreeing to the definitions written there. After the text discussion is settled in a couple of days I'd propose to make it a README in the translations folder (airflow

Re: [DISCUSS] i18n maintanability policy

2025-06-01 Thread Buğra Öztürk
It is a good idea to bring procedures to maintain and keep the consistency across all translations. I am not 100% sure if it needs an AIP but we should have this well documented in the repository documentation as well, after the Wiki. Guidelines for policies and procedures after all of them agreed

Re: [DISCUSS] i18n maintanability policy

2025-06-01 Thread Jarek Potiuk
Yep. Absolutely introducing translation mechanisms and even a way to verify if translations are complete ( is a good starting point - but yes, just a starting point. Describing and agreeing the process of maintaining it is absolutely necessary, so good you started it - not sure if it needs an AIP

Re: [DISCUSS] i18n maintanability policy

2025-06-01 Thread Aritra Basu
Thanks for this, left a comment. Overall in agreement with it! -- Regards, Aritra Basu On Sun, 1 Jun 2025, 1:39 pm Wei Lee, wrote: > 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, 202

Re: [DISCUSS] i18n maintanability policy

2025-06-01 Thread Wei Lee
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 wrote: > > Hello community! > > It's great to see that people from all over the world make Airflow > multilingual

[DISCUSS] i18n maintanability policy

2025-06-01 Thread Shahar Epstein
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 m