+1, We can see the Apache Way of SkyWalking and Flink.
Apache Flink is a project from German and was bought by a Chinese company, but the discussion is always in English. Actually I think it is OK for Chinese users to use Google Translate or Baidu Translate and polish the result for PR and issues. And it can be written in both English and Chinese if necessary (sometimes machine translation is not so good). Because it will be more comfortable to the users all over the world . e.g. 2 Apache mentors of Apache Dolphin Scheduler is not Chinese people, and they would not know what happened if people wrote in Chinese. So we should insist English as the main Language in the Community. Apache Software Foundation Member, DolphinScheduler PMC William Guo [email protected] 发件人： Sheng Wu 发送时间： 2021-10-08 20:02 收件人： dev 主题： Re: 回复： [DISCUSS] Do not support not english issue or PR anymore Considering our experiences of SkyWalking, which initiated in China too. Please think from load of community. Another new language means 100% more workload on document. Calvin Kirs <[email protected]>于2021年10月8日 周五下午7:42写道： > hi, > simsicon <[email protected]> 于2021年10月8日周五 下午5:58写道： > > > Hi all, > > > > I understand the urge to eliminate the non-English usage of the project, > > and I like to communicate technical problems in English, however I would > > like to remind you guys that the project was born in China and still has > a > > lot of Chinese users, it's a feature of the project. > > > > We should add more Chinese content, attract more native users rather than > > just ignore non-English support requests, and would you ignore a > > French/Spanish/Japanese request as well? > > > > Regarding the documentation, we can support multiple languages, depending > on the community of users as well as contributors. > > > > > > I think open source is an opportunity to be open rather than close. Thank > > you. > > > about communication, I insist on English only, you forget what is the side > effect people read answers. If they > asked in Chinese, we answer in English. The whole context is pointless. > Even the unperfect English statement is better than nothing. If we don't > push, who will? > > you think open source is an opportunity to be open rather than close, But > regarding the use of multilingualism in the discussion, it seems to be > open, but in fact, it is closed. > > > > > > > On Thu, Sep 30, 2021 at 9:32 PM zhang junfan <[email protected]> > > wrote: > > > > > Pity! > > > If you disagree, please give the reason instead of being so rude. > > > > > > 获取 Outlook for iOS<https://aka.ms/o0ukef> > > > ________________________________ > > > 发件人: 感谢政府 <[email protected]> > > > 发送时间: Thursday, September 30, 2021 3:02:25 PM > > > 收件人: dev <[email protected]> > > > 主题: 回复： [DISCUSS] Do not support not english issue or PR anymore > > > > > > 一帮假洋鬼子，去找你的English爸爸吧 > > > > > > > > > > > > > > > ------------------ 原始邮件 ------------------ > > > 发件人: > > > "dev" > > > < > > > [email protected]>; > > > 发送时间: 2021年9月30日(星期四) 下午2:04 > > > 收件人: "dev"<[email protected]>; > > > > > > 主题: Re: [DISCUSS] Do not support not english issue or PR anymore > > > > > > > > > > > > Yeah, I think we ask them change to English , beside issue or PR, > > > we should also keep our github discussions and mailiing-list too. > > > > > > Best Wish > > > — Jiajie > > > > > > > When found no use of English description issues or PR, we can > leave > > a > > > message for him to make changes, we will close it after the message and > > he > > > can reopen it when the changes are done. > > > > > > > > > -- > > > > Thanks&Best Regards > > > > Zhang Zheng > > > > Going back to my earliest reply, other items are OK, why can't we? > > > -- > Best wishes！ > CalvinKirs > -- Sheng Wu 吴晟 Apache SkyWalking Apache Incubator Apache ShardingSphere, ECharts, DolphinScheduler podlings Zipkin Twitter, wusheng1108
