fuchanghai opened a new issue, #15158: URL: https://github.com/apache/dolphinscheduler/issues/15158
### 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 ``` 我希望我们按照每月一个的频率新建一个issue收集各种用户产生的问题。committer 可以自己判断这个是否是bug,如果是则新开一个issue描述这个问题，社区运营每月可以整理这个issue ，贡献者也可以在这个issue下留下自己的意见，这将会产生如下好处 1.使得用户提出的一些问题能够在指定的期限前的到回复（大家群很多，有时候会忽略掉用户的问题，比如微信和slack 实际上回复的很少） 2.鼓励更广泛的群体参与进来，能够产生更多的非代码贡献者 3.如果再加一个issue作为历史目录，将各月份的issue串联起来，能够将大家解决问题的经验组织起来。避免各位使用者各自独立解决 4.对于新用户更加友好。更容易发现问题。 5.在统一的Issue下处理讨论，运营收集的问题更全面，查找问题的用户也能够更清晰的查看整个讨论流程 ``` ``` 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]
