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
