Hi, In today's ASF Board meeting, we noticed that dev@brpc.apache.org [1] continues to have a majority of traffic in Chinese, making it inaccessible to people who don't speak Chinese.
[1] https://lists.apache.org/list.html?dev@brpc.apache.org In the ASF, though we welcome people fluent in all languages, the development takes place in English. However, a dedicated user community for Chinese is fine; what we should do is to separate it from dev@. Some examples you can refer to are: * Flink uses a user...@flink.apache.org to gather all the Chinese user reports [2] * Kvrocks has a "中文" (Chinese) category on GitHub Discussions [3] [2] https://lists.apache.org/list.html?user...@flink.apache.org [3] https://github.com/apache/kvrocks/discussions/categories/%E4%B8%AD%E6%96%87 Thus, I'd start this thread to discuss how bRPC can always use English for development, and optionally support dedicated Chinese user discussion. Here is my rough thought, you can make use of: 1. Create an iss...@brpc.apache.org and redirect all the issues and PRs to that list. 2. Enable GitHub Discussions and create a dedicated "中文" (Chinese) category. 3. When community members create an issue: a. If it's a user question, move it to the 中文 Discussions forum and tell the reporter to use the 中文 category the next time. b. If it's a dev item (task, feature request, bug report, etc.), urge the reporter to report it in English; or a committer should rework it in English. Looking forward to your feedback. Note that although this is not urgent, it's an issue that should be resolved to ensure the development takes place in English, basically for being inclusive. Best, tison.
