Thanks! I created [1] to enable GitHub Discussions so that we can move user questions (not an issue) to a dedicated GH Discussion Chinese forum.
[1] https://github.com/apache/brpc/pull/2955 Note that issues (as part of development) should use English primarily. Best, tison. Wang,Weibing <[email protected]> 于2025年4月22日周二 11:01写道： > Hello, tison > > Thanks for your advice! > I have created an [email protected] list and redirect the issue > notifications to this list following your instructions. > PR notifications will still redirect to the dev@ list. And we will > keep PR discussions in English. > > Best regards > Weibing Wang > > On Mon, Apr 21, 2025 at 10:14 AM tison <[email protected]> wrote: > > > > I'd suggest creating an [email protected] list via [1] so we can > > redirect most GitHub activities away from dev@. > > > > [1] https://selfserve.apache.org/mailinglist-new.html > > > > Best, > > tison. > > > > > > Jerry Tan <[email protected]> 于2025年4月17日周四 20:41写道： > > > > > Good suggestion, > > > We will discuss it. > > > > > > thanks. > > > > > > On 2025/04/17 11:36:06 tison wrote: > > > > Hi, > > > > > > > > In today's ASF Board meeting, we noticed that [email protected] > [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/[email protected] > > > > > > > > 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 [email protected] to gather all the Chinese > user > > > > reports [2] > > > > * Kvrocks has a "中文" (Chinese) category on GitHub Discussions [3] > > > > > > > > [2] https://lists.apache.org/[email protected] > > > > [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 [email protected] 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. > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
