ISSUE will eventually be archived by mail. Therefore, all our communications on ISSUE and PR can be viewed by email.
OK, let's come back to this question. If you want to open it, I suggest that we still insist on using English to communicate on "GITHUB DISCUSS". Best Wishes！ CalvinKirs On 08/26/2021 13:16，David Dai<[email protected]> wrote： hi， of course, the important and deep question should happen in the mailing list, I think github discussion can help us move to be a global project, maybe some users will move from wechat group to here anyway, I think we can have a try, github discussion is new and our hope! Best Regards --------------- Apache DolphinScheduler PMC Chair David Dai [email protected] Linkedin: https://www.linkedin.com/in/dailidong Twitter: @WorkflowEasy <https://twitter.com/WorkflowEasy> --------------- On Thu, Aug 26, 2021 at 9:34 AM CalvinKirs <[email protected]> wrote: Hi, wenjun Very good suggestion, but I want to determine whether his content will be included in the mailing list, if not, then I think there may be no need, he will cause us to waste a lot of energy, and can not form effective precipitation. Best Wishes！ CalvinKirs, Apache DolphinScheduler PMC On 08/26/2021 01:27，wenjun<[email protected]> wrote： Hi community, This email is aimed to discuss enabling GitHub Discussions[1] on the DolphinScheduler repository. Most of the time, we hope to use the GitHub Issue to trace a bug or a specific new feature. A GitHub Issue needs to list the details of a specific problem in a standard way, this may prevent new users from discussing questions. And we also don't want to see too many questions in the Issue list. GitHub Discussions is a new way to communicate the project in the community, and it can help contributors to discuss an idea or ask a question easily. And it provides many operations for the community to manage the Discussions. The main concern is that we need to spend extra time to maintain the Discussions, but I think it's worth doing. Welcome to discuss this. [1] https://docs.github.com/en/discussions Thanks, Wenjun Ruan
