github-actions[bot] commented on issue #15158: URL: https://github.com/apache/dolphinscheduler/issues/15158#issuecomment-1809638760
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement. ### Description ``` I hope we can create a new issue once a month to collect issues raised by various users. The committer can judge by himself whether this is a bug. If so, he will open a new issue to describe the problem. Community operations can organize this issue every month. Contributors can also leave their own opinions under this issue, which will produce the following benefits. 1. Enable some questions raised by users to be answered before the specified deadline (there are many people in the group, and sometimes users’ questions are ignored, such as WeChat and Slack, which actually receive very few replies) 2. Encourage a wider group to participate, which can generate more non-code contributors 3. If you add another issue as a historical directory and connect the issues in each month, you can organize everyone's experience in solving problems. Prevent each user from solving the problem independently 4. More friendly to new users. It's easier to spot problems. 5. Process discussions under a unified Issue, the issues collected by operations are more comprehensive, and users looking for issues can also view the entire discussion process more clearly. ``` ``` I hope we can create a new issue once a month to collect issues raised by various users. The committer can judge by himself whether this is a bug. If so, he will open a new issue to describe the problem. Community operations can organize this issue every month. Contributors can also leave their own opinions under this issue, which will produce the following benefits. 1. Enable some questions raised by users to be answered before the specified deadline 2. Encourage a wider group to participate, which can generate more non-code contributors 3. If you add another issue as a directory and connect the issues in each month, you can organize everyone's experience in solving problems. Prevent each user from solving the problem independently 4. More friendly to new users. It's easier to spot problems. 5. Process discussions under a unified Issue, the issues collected by operations are more comprehensive, and users looking for issues can also view the entire discussion process more clearly. ``` cc @EricGao888 @davidzollo @Niko-Zeng @Radeity @ruanwenjun @zhongjiajie @caishunfeng @Gallardot ### Are you willing to submit a PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
