4 days pass. We have 3 PMC members supporting. Let's ask the INFRA to open this on the main repo? And also, we need to add the link on the website menu.
Sheng Wu 吴晟 Twitter, wusheng1108 Daming <[email protected]> 于2021年8月16日周一 下午3:32写道： > > +1 > > An issue is to discuss specific issues, and DISCUSSION will take about a > topic. > A few days ago, the same discussion[1] happened at APISIX community. The vote > passed and the thread was here[2]. > > > 1. https://www.mail-archive.com/[email protected]/msg03325.html > 2. > https://lists.apache.org/thread.html/r792a361c62b54058f6d378213a5bbc1cabdc7df188e5be8ff9270eaf%40%3Cdev.apisix.apache.org%3E > > <https://lists.apache.org/thread.html/r792a361c62b54058f6d378213a5bbc1cabdc7df188e5be8ff9270eaf@%3Cdev.apisix.apache.org%3E> > > —— > Haochao Zhuang > > > 2021年8月14日 下午2:33，Sheng Wu <[email protected]> 写道： > > > > But you forget what is the side effect we 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? > > We insisted in back to when SkyWalking is much younger, and less users. Why > > we change this? Evem we have known this would not have good effect in long > > term. > > > > SkyWalking has been a good example, and other community sees the solution > > out, and learn from us, including TiDB, and other TLPs initialzied in > > China. > > Now, we give up? Please don't. > > > > The base line is, this is never a foundation requirement. See Dubbo, it > > could nearly work only in Chinese, except official announcement. If we give > > up global community, we could. > > > > But I would never support this direction. We cost too much to be here. > > > > > > kezhenxu94 <[email protected]>于2021年8月14日 周六上午10:28写道： > > > >> I’m big +1 to enable it, the reason why I haven’t proposed it until now is > >> that I doubt that whether users will use it to ask question, if users still > >> ask questions in GitHub issues, should we transfer it to Discussions > >> (GitHub provides a one-click transfer from issue to discussion though)? > >> That would be a workload too. Anyway it is better we enable it now than > >> later and users may adopt it quicker. > >> > >> Sheng wrote: > >>> Futher, if we allow this officially, this wouldn't lower the load, > >> instead, > >> we double the load for ourselves > >> > >> In my opinion, the only reason not to allow non-English is from ASF > >> perspective, if it’s from maintainers’, I think force Chinese users to use > >> English will double our load as many of them use poorly-composed English > >> words / sentences / Chinglish and that needs maintainers to translate it > >> back to Chinese, what’s worse, they didn’t make them clear until the > >> conversation goes back and forth for several rounds. > >> > >> ———————————— > >> 柯振旭 (@kezhenxu94) > >> Apache SkyWalking PMC > >> Apache Incubator PMC and Mentor > >> > >>> On Aug 14, 2021, at 08:51, Chen Yihao <[email protected]> wrote: > >>> > >>> Hello all, this is a proposal on enabling the `GitHub Discussions` > >> Feature for the SkyWalking main repository. > >>> > >>> First, a bit of background, this feature adds a new `Discussions` tab to > >> the repository next to Pull requests. The aim is to facilitate the > >> socio-technical growth of the SkyWalking Ecosystem. > >>> > >>> "GitHub Discussions is a collaborative communication forum for the > >> community around an open-source project. Discussions are for conversations > >> that need to be transparent and accessible but do not need to be tracked on > >> a project board and are not related to code, unlike GitHub Issues. > >> Discussions enable fluid, open conversation in a public forum." -- GitHub( > >> https://docs.github.com/en/discussions/quickstart) > >>> > >>> Now, with a fast-growing user base, it is observed that duplicated > >> questions are flooding our QQ chat groups, Slack and even the Issues > >> section. The original intent of issues was tracking code-related matters, > >> defects and tasks. It is frustrating for the maintainers having to monitor > >> and handle unrelated/ duplicated questions in the decentralized channels > >> mentioned above, while on the other hand, newcomers face trouble digging > >> helpful info -> asking more duplicated questions. > >>> > >>> Thus, I propose turning on this feature as a new channel for threads > >> that are not closely coupled with code. Stakeholders could freely discuss > >> their use cases, present new ideas and seek help from the community. Our > >> `Discussions` tab could serve a purpose as a hybrid of Stack Overflow and a > >> Forum. I believe doing so will further boost the community health, spark > >> some great ideas, and most importantly, attract more contributors to > >> SkyWalking. > >>> > >>> We may also want to consider the language scope allowed in this new > >> section. `Discussions` being a less formal ground, more language diversity > >> could help more users(SEO-wise) and contributors who are unfamiliar with > >> English. Therefore, I propose opening up language-specific `categories`, if > >> a mixed-language form isn't desirable. ( > >> https://docs.github.com/en/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository > >> ) > >>> > >>> The above summarizes my proposal; I appreciate your thoughts, and please > >> vote on the matter. > >>> > >>> Many thanks. > >>> > >>> Yihao Chen 陈意昊 > >>> GitHub @ Superskyyy > >> > >> -- > > Sheng Wu 吴晟 > > > > Apache SkyWalking > > Apache Incubator > > Apache ShardingSphere, ECharts, DolphinScheduler podlings > > Zipkin > > Twitter, wusheng1108 >
