+1 That's cool to support the Discussions feature on GitHub, here has one sample repo: https://github.com/vercel/next.js/discussions
Best Regards! @ Zhiyuan Ju <https://github.com/juzhiyuan> ZhengSong Tu <tzssanggl...@gmail.com> 于2021年8月2日周一 下午2:03写道： > Of course, GitHub discussions do not cover topics with code-related > discussions and project management activities. > > *ZhengSong Tu* > My GitHub: https://github.com/tzssangglass <https://github.com/membphis> > Apache APISIX: https://github.com/apache/apisix > > > Ming Wen <wenm...@apache.org> 于2021年8月2日周一 下午1:23写道： > > > looks good to me. > > And all code-related discussions and project management activities must > be > > on the mailing list. > > > > Thanks, > > Ming Wen, Apache APISIX PMC Chair > > Twitter: _WenMing > > > > > > 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 > > > > > >
