Lee-W commented on code in PR #55122: URL: https://github.com/apache/airflow/pull/55122#discussion_r2331165355
########## .github/CODEOWNERS: ########## @@ -50,8 +50,10 @@ airflow-core/src/airflow/ui/public/i18n/locales/ko/ @jscheffl @potiuk # + @choo1 airflow-core/src/airflow/ui/public/i18n/locales/nl/ @BasPH # + @DjVinnii airflow-core/src/airflow/ui/public/i18n/locales/pl/ @potiuk @mobuchowski # + @kacpermuda airflow-core/src/airflow/ui/public/i18n/locales/tr/ @bugraoz93 # +@hasancatalgol +airflow-core/src/airflow/ui/public/i18n/locales/zh-CN/ @<some-commiter-id> # + @Fortytwoo Review Comment: > Thank you for your promotion of this PR. I have been wondering whether direct @ is not in line with community etiquette. I had no idea. Thank you hahaha. It really depends on who you tag and the context of the questions, but I usually don't mind at all! I really appreciate your thoughtfulness, too. š --- First of all, I am grateful for your offer regarding this PR. I apologize for my delayed response; I was recently involved in an important annual event in Taiwan, where I served both as an organizer and a speaker. It was quite overwhelming, and I struggled to keep up with everything. I hope you all understand. ### `TL;DR`: After reviewing the discussion, I want to clarify that I am not that capable of doing it, don't have the capacity to do it right, and I'm not convinced it's the right time for me to be the sponsor. (PR reviews and suggestions are totally fine though; please tag me if there are things you'd like me to revisit.) #### "I am not that capable of doing it." While I can understand Mandarin Chinese, I lack the proficiency and expertise to do it correctly. The languages began to diverge long ago, and today, many terms can differ significantly, sometimes even having entirely different meanings. This phenomenon is even more severe in the tech world, largely because it is a relatively new phenomenon. If I am allowed to create a direct translation based on Taiwanese Mandarin, it wouldn't be too burdensome for me, and I would likely be more willing to help. While I'm not in a position to speak on behalf of others, I doubt that this approach aligns with what the Chinese audience would prefer. If I'm not allowed to do it in this way, I will need to conduct additional research and verification. Even translating Taiwanese Mandarin accurately is not an easy task for me. Understanding a term and translating something correctly are two completely different things. I can't imagine it would be any easier if I were to take on responsibilities related to Chinese Mandarin. #### I'm unsure if this is the right time for me to take this on. I just revisited our policy once more https://github.com/apache/airflow/tree/main/airflow-core/src/airflow/ui/public/i18n. > * Code owners who act as translation sponsors are also responsible for: > * Ensuring that the translation owner is active and able to maintain the translation. > * Act according to section 6.4 when the translation owner relinquishes their role or become inactive. I genuinely appreciate your politeness and want to express my concerns respectfully. Since we're still getting to know each other and I haven't seen you actively participating in the community just yet, Iām a bit not sure about how to ensure the translation owner can maintain their role. This isn't your fault ā it's just the way the policy requires sponsors to act. But, I'm glad to see that @potiuk has found a way to make it work! To clarify: 1. I am **not** against adding this new language to Airflow. 2. I am **not** blocking the merging of this PR. 3. I'm happy to assist with discussions on translations if my bandwidth allows (I might be a bit busy until around the Airflow Summit, so feel free to tag me if I miss anything š¤¦āāļø). 4. I **might** be more willing to serve as a sponsor (if my bandwidth allows) if we collaborate in the Airflow community for a bit and build some great teamwork together. That said, I'm just not convinced about supporting something that I'm uncertain about at the moment. Thank you all for your understanding! -- 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: commits-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
