FYI: We can easily convert GitHub issue to GitHub Discussion [1] Or create a GitHub issue based on GitHub Discussion [2]
[1] https://docs.github.com/en/discussions/managing-discussions-for-your-community/moderating-discussions#converting-an-issue-to-a-discussion [2] https://github.com/github/feedback/discussions/2861#discussioncomment-696235 ZhengSong Tu <tzssanggl...@gmail.com> 于2021年8月3日周二 上午10:22写道： > There is a clear standard that the question is asked by a user to other > users. > > for example, users may ask questions such as: > - Anyone have any practical information on apisix as a gateway? I would > like to learn how it is used in real business; > - I'm curious if people are deploying production with a separate set of > environments or if they are doing it directly on top of the original k8s; > - Anyone still use apisix with a preexisting nginx proxy or is it a > straightforward solution to replace nginx; > - Let me ask anyone a question, all etcd configuration centres or consul > registry data are pulled by the timer, there is no wactch callback like in > other high level languages; > > There is also clear standard that the question is divisive within the > community and need more users to be involved in the discussion. In the > Github Discussions this can be a hot topic, such as: > - need to support https requests that do not pass SNI > > Normally such questions would be discussed on a mailing list, but Github > Discussions can gather feedback from more users, and there is no > contradiction between mailing lists and Github Discussions. > > Here's what I think, does anyone have anything to add or modify? > > *ZhengSong Tu* > My GitHub: https://github.com/tzssangglass <https://github.com/membphis> > Apache APISIX: https://github.com/apache/apisix > > > Zexuan Luo <spacewan...@apache.org> 于2021年8月3日周二 上午9:00写道： > > > > If we see questions in the issue, IM, that is suitable for discussion > in > > GitHub Discussions, we can direct users to it. > > > > What's the standard for "suitable"? > > > > ZhengSong Tu <tzssanggl...@gmail.com> 于2021年8月2日周一 下午9:44写道： > > > > > > Thanks Zexuan. > > > > > > Some details were not organized in the first email, my mistake. > > > > > > Our existing discussion of the places with their boundaries: > > > > > > 1. mail list: project questions and answers, code-related discussions, > > > project management activities, technical discussions, release vote, > etc. > > > The boundary of the mail list are: things that are directly related to > > the > > > development of the project, things that lend themselves to asynchronous > > > discussion, and other things not listed that are stated in the Apache > Way > > > culture. > > > > > > 2. issue: bug report, feature, improve docs, request help, etc. > > > The boundary of the issue are: details on the development of the > > > implementation process after the mailing list discussion, issues > arising > > > from the user practice process, etc. > > > issue is more suitable for tracking project development progress and > > > solving specific problems. It is also a community portal on Github. > > > > > > 3. IM: now we have public Slack channels, Wechat, etc., but we never > > > discuss specific issues here. > > > > > > Problem: > > > issue have become a channel between project developers and users. When > an > > > issue is closed, it means that the discussion of the matter is > > > over. However, we have many useful tips scattered in different issues. > > > New users are constantly joining the community and encountering > > > questions that previous users have encountered. These questions may be > > > solved in the issue, but because users don't know how to use search or > > use > > > the wrong keywords, they can't find the answers they want. So they will > > ask > > > similar questions again. > > > Our current approach is to distill duplicate issues and add them to the > > > FAQ. But this solves only part of the problem. Some of the user's > > questions > > > have no unique answer, or no answer at all, and these questions need to > > be > > > discussed by the user. > > > Now we also lack a channel for user-to-user communication. mail list > can > > do > > > this, but too few users are willing to do so due to their usage habits. > > > > > > Proposal: > > > Perhaps GitHub Discussions is a better solution to the problem > mentioned > > > above. > > > The boundary of the GitHub Discussions are: guide for newcomers to > > APISIX, > > > technical articles about APISIX, experience of using APISIX, exchange > of > > > knowledge on custom plugin development, highly available solutions, > etc. > > > GitHub Discussion makes it easier for community users to find topics > they > > > are interested in, and learn from each other. > > > The best content from GitHub Discussions, which can be fed back into > the > > > project. > > > > > > How to direct users to GitHub Discussions? > > > > > > It is a real problem. > > > If we see questions in the issue, IM, that is suitable for discussion > in > > > GitHub Discussions, we can direct users to it. > > > But I think it's more important that GitHub Discussions have content > that > > > users are interested in, like issue deposits, links to various learning > > > resources related to the project, and those mentioned in the Proposal. > > > More discussion is needed on this problem. > > > > > > > > > *ZhengSong Tu* > > > My GitHub: https://github.com/tzssangglass < > https://github.com/membphis> > > > Apache APISIX: https://github.com/apache/apisix > > > > > > > > > Zexuan Luo <spacewan...@apache.org> 于2021年8月2日周一 下午4:22写道： > > > > > > > Is there a guideline for where the discussion happens? > > > > Now we will have three places to discuss things: > > > > 1. mail list > > > > 2. issue > > > > 3. GitHub discussion > > > > > > > > How can users know why to put their discussion to? > > > > > > > > tzssangglass <tzssanggl...@apache.org> 于2021年8月2日周一 下午12:38写道： > > > > > > > > > > Hi, Community, > > > > > > > > > > As more and more users are using APISIX, they ask a lot of > > questions, not > > > > > only about bugs, features, etc., but also about non-code-related > > issues > > > > > such as high availability solutions, best practices in different > > > > scenarios, > > > > > questions related to the technology stack derived from APISIX, etc. > > > > > > > > > > These issues are not suitable for hosting in issues, but rather in > > GitHub > > > > > Discussions. > > > > > > > > > > I recommend using GitHub Discussions on the APISIX project. > > > > > > > > > > This is the introduction to GitHub Discussions: > > > > > *“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.”* > > > > > > > > > > What's your opinion? > > > > > > > > > > Reference: > > > > > - GitHub Discussions: > > https://docs.github.com/en/discussions/quickstart > > > > > > >
