shahar1 commented on code in PR #51292:
URL: https://github.com/apache/airflow/pull/51292#discussion_r2124422561


##########
airflow-core/src/airflow/ui/src/i18n/README.md:
##########
@@ -17,8 +17,188 @@
  under the License.
  -->
 
-Checking completeness of i18n files:
-------------------------------------
+# i18n Policy
+
+## 1. Purpose & scope
+
+This document outlines the policy for internationalization (i18n) in Apache 
Airflow, detailing the lifecycle of translations within the project.
+This policy aims to avoid inconsistencies, maintenance issues, unclear 
ownership, and to ensure translation quality.
+The scope of this policy is applied to:
+
+- Each supported language included in the 
`airflow-core/src/airflow/ui/src/i18n/locales` directory of the Apache Airflow 
project, or any suggested new translation.
+- Individuals responsible for maintaining these translations by any of the 
roles defined below.
+- Contributors who apply changes in the default language (English) that may 
affect translations.
+
+
+## 2. Definitions
+
+**i18n** - Internationalization, the process of designing a software 
application so that it can be adapted to various languages and regions without 
engineering changes.
+
+**Supported translation** - A translation that has been officially accepted 
into the project, located in `airflow-core/src/airflow/ui/src/i18n/locales`.
+
+**Default language** - The language used by default, and as a fallback to all 
other languages (English).
+
+**Translation owner** - A designated individual responsible for the 
maintenance and quality for a supported translation.
+
+**Code owner** - An Apache Airflow committer designated in the 
`.github/CODEOWNERS` file for a supported translation.

Review Comment:
   Probably, but not necessarily - I made this distinction to allow 
non-committers to participate :)



-- 
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]

Reply via email to