Hi, Jason, I think this is a great step forward for improving translation consistency in Airflow, and Iβm personally excited to see Agent Skills being introduced to the repository for the first time π
I have a similar concern to what Jens mentioned. For Korean, we still have some open discussions within the translation team. There are cases where directly translating certain Airflow terms into Korean sounds very unnatural, so we sometimes use transliterations instead. On the other hand, some terms are translated more literally. However, we have not yet fully aligned on the WHY behind those decisions, and opinions may differ depending on the user perspective. Unlike the German case, we do not yet have clearly established terminology principles documented. Because of that, I am not entirely confident about what criteria we should use when reviewing PRs for the Korean skill definition. It might be helpful if we could define a recommended structure or guidance for how each locale-specific skill should document: * Terminology decision * Rationale (WHY) * Preferred patterns (e.g., transliteration vs. literal translation) * Cases that are intentionally flexible I think having a shared guidance framework across locales would make reviews more consistent and reduce ambiguity. Curious to hear othersβ thoughts. Best, Yeonguk 2026λ 2μ 17μΌ (ν) PM 12:25, Zhe-You Liu <[email protected]>λμ΄ μμ±: > Hi Jens, > > Great point! I agree that each locale should track the reasons for its > terminology choices. I will cross-post this to the German sub-issue and > mention this convention in the meta issue. Thanks! > > Best, > Jason > > On Tue, Feb 17, 2026 at 5:34β―AM Jens Scheffler <[email protected]> > wrote: > > > Hi! > > > > Good initiative to make it common. Please consider that for the German > > we created a > > airflow-core/src/airflow/ui/public/i18n/locales/de/README.md that > > describes _WHY_ we have selected which specific terms in the local > > translation. So encouraging that other translations maybe follow same > > approach. If need to be re-formatted for agent based processing this > > would be finde but I'd otherwise request to consider the existing > > definitions. > > > > Not sure if it is beneficial if it is renamed "de.md" instead of > > README.md though. > > > > Jens > > > > On 16.02.26 15:57, Shahar Epstein wrote: > > > Great initiative Jason! > > > > > > > > > Shahar > > > > > > On Mon, Feb 16, 2026, 15:58 Zhe-You(Jason) Liu <[email protected]> > > wrote: > > > > > >> Hi everyone, > > >> > > >> I would like to invite new contributors looking for a "Good First > Issue" > > >> (everyone else is welcome too!) to help define the **Translation Agent > > >> Skills for Airflow Terminology** [1]. > > >> > > >> We are looking to define **21 Translation Agent skills** in total. > This > > >> includes **1 global-level skill** and **20 locale-specific skills**. > > >> > > >> The goal is to implement a generic, up-to-date, and low-maintenance > > >> solution using Open-standardized Agent Skills [2]. This will help the > > >> Airflow community maintain translations more efficiently, ensuring > > better > > >> consistency across locales and reducing hallucinations in AI-assisted > > >> workflows. > > >> > > >> The skills will be organized as follows: > > >> ``` > > >> .github/skills/airflow-translations > > >> βββ locales > > >> β βββ ar.md > > >> β # ... all current locales, each with locale-specific skills > > >> β βββ zh-TW.md > > >> βββ SKILL.md # Global-level Airflow terminology guidelines > > >> ``` > > >> > > >> - **`SKILL.md`**: Contains only global-level Airflow terminology > > >> guidelines. > > >> - **`locales/{locale-name}.md`**: Documents guidelines specific to > that > > >> language, based on the existing locale files found in > > >> `airflow-core/src/airflow/ui/public/i18n/locales/{locale-name}/`. > > >> - **Inheritance**: All `locales/{locale-name}.md` files will depend on > > the > > >> global-level `SKILL.md` first. > > >> > > >> This is a significant milestone: these will be the **first Agent > Skills > > >> defined in the Airflow repository**. I am looking forward to seeing > how > > we > > >> can leverage these skills to make our AI-assisted tools more accurate > > and > > >> consistent for our contribution processes. > > >> > > >> **How to contribute:** > > >> If you are interested, please **comment on the specific sub-issue you > > want > > >> to work on** (rather than the meta issue), and I will assign it to > you. > > >> > > >> Thank you in advance for your contribution! > > >> > > >> [1] https://github.com/apache/airflow/issues/61984 > > >> [2] https://agentskills.io/home > > >> > > >> Best regards, > > >> Jason > > >> > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > >
