I understand your point Elad, but introducing translation is a good way to get 
new contributors involved in the project, so maybe we could find a way to 
include the translation, and then if they don’t keep it up we remove the 
translation at the next touch-point — so in this case introduce for 3.1, but if 
it’s not kept up to date for 3.2 remove it again?

(In this case it sounds like we might have a person to step up)

-ash

> On 29 Aug 2025, at 15:44, Eloi Codina <[email protected]> wrote:
> 
> Hi Elad,
> 
> I agree with you that new contributors should not be translation owners
> since it's difficult to know how committed they will be in the future to
> maintain the locale.
> 
> In case you mentioned that for the Catalan PR, I would like to present
> myself.
> 
> I've been using and maintaining Airflow in my company for the last 3 years.
> This would be my 3rd (I think) PR, and have also contributed by opening
> some issues and discussions.
> 
> I will attend the Summit and Seattle to give a presentation. I have also
> been in Toronto and San Francisco (where I also presented).
> 
> I would like to contribute more to the project (give back, I'd say), and
> translations are an area where I feel confident I can contribute
> positively.
> 
> Thanks,
> 
> Eloi
> 
> On Fri, 29 Aug 2025 at 16:27, Elad Kalif <[email protected]> wrote:
> 
>> I am -1 for accepting translations from contributors who are not yet
>> recognized/trusted by our community
>> 
>> Our policy says:
>> 
>> Translation owner - Designated contributor responsible for maintaining a
>>> supported locale.
>> 
>> 
>> Possibly we should raise discussion to clarify it further. From my point of
>> view it should be a trusted member of the community.
>> I have no objections to any languages out there - I even suggested Klingon
>> https://en.wikipedia.org/wiki/Klingon_language ;)
>> If someone speaks it and wishes to maintain it - that is good enough for
>> me.
>> My issue is with trust around the maintenance part. I expect the
>> translation owner to be proactive. To constantly keep the translation
>> updated so we won't have to keep pinning him or worse, be forced to remove
>> the translation after it has been adopted by users. That level of trust can
>> not be with a first time contributor or someone who is not very active in
>> the project.
>> 
>> On Fri, Aug 29, 2025 at 2:33 PM Wei Lee <[email protected]> wrote:
>> 
>>>> a) we want some popularity criteria
>>> 
>>> -1 from me, as long as someone is willing to maintain it actively and
>> meet
>>> 
>> https://github.com/apache/airflow/blob/main/airflow-core/src/airflow/ui/public/i18n/README.md
>> ,
>>> I think we should be good with accepting any language.
>>> 
>>>> b) someone can propose some concrete criteria that will have reasoning
>>> and we agree to
>>> 
>>> -0 to this, not a fan of adding any criteria, but open to the flexibility
>>> in case there might be some unexpected exceptions.
>>> 
>>> Best,
>>> Wei
>>> 
>>>> On Aug 29, 2025, at 6:59 PM, Eloi Codina <[email protected]> wrote:
>>>> 
>>>> Hi Pierre,
>>>> 
>>>> I don't think "not being an official EU language" should really matter
>>> (how
>>>> would this apply to languages spoken outside the EU?). In fact, it has
>>> 10M
>>>> speakers, more than other "EU official languages" (e.g. Finnish or
>>>> Swedish). Other reasons are:
>>>> 
>>>> 1. It is a language, not "just a regional language" or a "dialect".
>>>> Otherwise, it wouldn't have a ISO 391-1 code.
>>>> 2. It is official in 3 autonomous regions of Spain alongside Spanish,
>>>> according to the Spanish Constitution (wouldn't that make it official
>>>> enough?).
>>>> 3. It is the only official language in the country of Andorra.
>>>> 4. Most of the world-wide software is translated into Catalan. Android,
>>>> Windows, iOS, Google services, ...
>>>> 5. Catalan translators are often very engaged. For example, Softcatalà
>>> is a
>>>> very active association which offers translators tools to help with
>>>> translation of software.
>>>> 
>>>> Moreover, I'd like to add that the i18n policy allows for regional
>>> variants
>>>> of languages.
>>>> 
>>>> I believe open-source software should welcome as many languages as its
>>>> users (the community) speak. I opened this PR not to be political, but
>> to
>>>> add a language some of Airflow's users use, myself included. I am
>>> committed
>>>> to maintaining the translation up to date.
>>>> 
>>>> That said, the final decision is up to the community.
>>>> 
>>>> Thanks,
>>>> 
>>>> Eloi Codina
>>>> 
>>>> 
>>>> On Fri, Aug 29, 2025 at 12:35 PM Pierre Jeambrun <
>> [email protected]>
>>>> wrote:
>>>> 
>>>>>> Does it mean Pierre, that you want to propose and discuss a new rule
>>> that
>>>>> we should add? What would be that proposed rule in this case (we need
>> to
>>>>> have a concrete rule proposal that we can objectively apply to other
>>>>> potential languages). Until then I think we should follow the rules we
>>>>> agreed so far.
>>>>> 
>>>>> 
>>>>> I just wanted to mention that it might open doors for future regional
>>>>> languages to be added. I'm unsettled on this one and this is why I
>>> wanted
>>>>> to discuss it first before coming up with a concrete proposal.
>>>>> 
>>>>> On one hand I really do not see any harm in adding as many locals as
>> we
>>>>> want, as long as we have people maintaining them (which is the current
>>>>> policy). On the other hand, it's very rare to see any commercial
>> product
>>>>> supporting similar translations at least from my experience. (Chinese,
>>>>> Indian, European dialects). Without criteria of popularity / being
>>> official
>>>>> I believe there might be a gap in the policy and I think we can
>>>>> easily imagine potential abuses of the current policy.
>>>>> 
>>>>> What do you think?
>>>>> 
>>>>> On Fri, Aug 29, 2025 at 12:14 PM Jarek Potiuk <[email protected]>
>> wrote:
>>>>> 
>>>>>> And yes. Generally ASF is neutral. No politics. Apache Software
>>>>> Foundation
>>>>>> generally does not play politics. We have "users". That's all.
>> Anywhere
>>>>> in
>>>>>> the world. Doing whatever they want to do with their software. We do
>>> not
>>>>>> judge. We do not get involved in any political discussions (unless we
>>> are
>>>>>> forced by law).
>>>>>> 
>>>>>> On Fri, Aug 29, 2025 at 12:10 PM Jarek Potiuk <[email protected]>
>>> wrote:
>>>>>> 
>>>>>>> I don't think we have criteria of "popularity" or "official" status
>>>>>>> language. The only criteria we have is about committed people who
>> are
>>>>>>> willing to maintain it. We have some really good rules on when
>>> language
>>>>>> is
>>>>>>> supported - prepared by Shahar - and ones we agreed to.
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>> 
>>> 
>> https://github.com/apache/airflow/blob/main/airflow-core/src/airflow/ui/public/i18n/README.md#5-requirements
>>>>>>> 
>>>>>>> I don't think we have rules for "being official" or "being popular".
>>>>>>> 
>>>>>>> One of the reasons we introduced and agreed to the rules is ... to
>>>>>>> actually follow them when new language is proposed. And so that we
>> do
>>>>> not
>>>>>>> invent "new" reasons why we should accept/reject a language on the
>>> fly.
>>>>>>> Currently (at least) - if Catalan passes the original criteria we
>> have
>>>>>> and
>>>>>>> will be supported - we agreed to accept it. If not, we will drop it
>>>>> (and
>>>>>>> that's also described in the rules).
>>>>>>> 
>>>>>>> But of course if we would like to introduce new criteria for
>> languages
>>>>> -
>>>>>>> we could do it. We could even do it based on the Catalan example and
>>>>>>> propose new rules.
>>>>>>> 
>>>>>>> But it should not be "let's not approve Catalan" but "let's propose
>> a
>>>>> new
>>>>>>> rule based on what we see with Catalan".
>>>>>>> 
>>>>>>> Does it mean Pierre, that you want to propose and discuss a new rule
>>>>> that
>>>>>>> we should add? What would be that proposed rule in this case (we
>> need
>>>>> to
>>>>>>> have a concrete rule proposal that we can objectively apply to other
>>>>>>> potential languages). Until then I think we should follow the rules
>> we
>>>>>>> agreed so far.
>>>>>>> 
>>>>>>> J.
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> If we would like to introduce criteria like whether language is f
>>>>>>> 
>>>>>>> On Fri, Aug 29, 2025 at 11:48 AM Pierre Jeambrun <
>>>>> [email protected]>
>>>>>>> wrote:
>>>>>>> 
>>>>>>>> Hello guys,
>>>>>>>> 
>>>>>>>> I don't want to be rude, or start any political discussion, but I
>>>>> don't
>>>>>>>> see
>>>>>>>> Catalan listed as one of the 24 official EU languages. My question
>> is
>>>>>>>> whether or not we should allow such translations, if we do, we
>> might
>>>>>>>> expect
>>>>>>>> other similar additions which might lead to a lot of translations
>> to
>>>>>>>> maintain (Basque, Galician, etc...). 24 translations just for
>> Europe
>>>>> is
>>>>>> a
>>>>>>>> lot, and I'm not sure we should take responsibility to support
>> more.
>>>>>> Also
>>>>>>>> it sets boundaries on what can or cannot be added as a translation.
>>>>> (if
>>>>>> we
>>>>>>>> stretch this just to make a point, are local non official dialect
>>>>>> eligible
>>>>>>>> too?)
>>>>>>>> 
>>>>>>>> I don't have a strong opinion though I just wanted to mention it.
>>>>>>>> 
>>>>>>>> On Thu, Aug 28, 2025 at 6:32 PM Eloi Codina <[email protected]>
>>>>>> wrote:
>>>>>>>> 
>>>>>>>>> Hi Shahar,
>>>>>>>>> 
>>>>>>>>> My email client gave me an error and the message has been
>>>>> duplicated.
>>>>>>>> There
>>>>>>>>> are some other comments in
>>>>>>>>> https://lists.apache.org/thread/tcy6fwkgr21rdp7ln0wrn1g0qv2hgwvo
>>>>>>>>> 
>>>>>>>>> I thought the translation owner had to be a committer, but
>>>>> re-reading
>>>>>>>> the
>>>>>>>>> policy I see that's not the case. I have previously contributed to
>>>>> the
>>>>>>>>> project and I can volunteer to be the translation owner for this
>>>>>> locale.
>>>>>>>>> 
>>>>>>>>> That said, Bugra offered to be the sponsor in Github to reduce
>> Jens'
>>>>>>>>> workload. Either way, I look forward to the vote!
>>>>>>>>> 
>>>>>>>>> Thanks.
>>>>>>>>> 
>>>>>>>>> On Thu, Aug 28, 2025 at 5:17 PM Shahar Epstein <[email protected]
>>> 
>>>>>>>> wrote:
>>>>>>>>> 
>>>>>>>>>> Thank you very much for your contribution!
>>>>>>>>>> To merge this PR, we'll need that either you or your friend (or
>>>>>> both!)
>>>>>>>>> will
>>>>>>>>>> volunteer as a translation owner. Responsibilities are detailed
>> in
>>>>>> the
>>>>>>>>>> policy, the main parts are to ensure that the translation is
>>>>>>>> continuously
>>>>>>>>>> maintained, review related PRs, and complete translation coverage
>>>>>>>> before
>>>>>>>>>> new releases (FYI - the release of the i18n feature is coming
>> very
>>>>>>>> soon,
>>>>>>>>> by
>>>>>>>>>> the start of September - please read my last thread).
>>>>>>>>>> If the above is ok with you, Jens should open a vote/lazy
>>>>> concensus
>>>>>>>> for
>>>>>>>>>> nominating you as a translation owner.
>>>>>>>>>> After the vote is completed and the PR is over 90% coverage, we
>>>>>> could
>>>>>>>>> merge
>>>>>>>>>> this PR :)
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> Shahar
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> On Thu, Aug 28, 2025, 10:07 Eloi Codina <[email protected]>
>>>>>> wrote:
>>>>>>>>>> 
>>>>>>>>>>> Hello,
>>>>>>>>>>> 
>>>>>>>>>>> I have opened a PR (
>>>>> https://github.com/apache/airflow/pull/55013)
>>>>>>>>> which
>>>>>>>>>>> adds Catalan to Airflow.
>>>>>>>>>>> 
>>>>>>>>>>> Jens has offered to be our sponsor (thanks!).
>>>>>>>>>>> 
>>>>>>>>>>> Since I am not a committer, I could be an engaged translator. I
>>>>>> have
>>>>>>>>> also
>>>>>>>>>>> asked a friend of mine (Oscar) to review it, and any other
>>>>>>>> contribution
>>>>>>>>>>> is welcome!
>>>>>>>>>>> 
>>>>>>>>>>> Oscar and I are native Catalan speakers, with the C1 level
>>>>>>>> officially.
>>>>>>>>> We
>>>>>>>>>>> both work in tech and use Airflow daily.
>>>>>>>>>>> 
>>>>>>>>>>> I would like to ask for the approval to add the locale to the
>>>>> code
>>>>>>>>> base.
>>>>>>>>>>> 
>>>>>>>>>>> P.D. my apologies if the email is duplicated.
>>>>>>>>>>> 
>>>>>>>>>>> Thank you,
>>>>>>>>>>> 
>>>>>>>>>>> Eloi
>>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>> 
>>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>> 
>>> 
>>> 
>> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to