Hi, Justin, First of all, I agree with you that I think it is unacceptable to close these issues or pull requests without any response to them.
The reason why I propose to create a bot is to automatically close those issues or pull requests which we had response to and need more information from the author. Maybe we can discuss in the mailing list with the standard about whether we can close an issue. In my opinion, if a issue has the following characteristics we can close it - A bug report issue without detailed information, and there are already one or more contributors trying to reply to it, but due to the insufficient information we can not solve it. We can attach a label to this issue like `waiting-for-feedback`. After several weeks, the author does not reply. - An already solved usage problem. There are a lot of issues which are solved by contributors, also the detailed solution has been commented on. After several weeks, the author does not ask for more question or close the issue. Maybe there are many situations where we can close an issue, I hope we can discuss it under this mail thread or we can create a new mail thread for it. Also, I think we should take each problem seriously, and reply to them one by one. Thanks, Albumen. Justin Mclean <[email protected]> 于2021年1月29日周五 下午5:38写道： > HI, > > > - We can introduce a bot to automatically close these issues and pull > > requests if the original author does not reply for a long time. > > I suggest you don’t this this as it discourages people from contributing > and you more more committers and grow the community so you have more people > who can respond to PR in a more timely manner. I would try to come up with > ways to review the back log of requests and be more responsive to the > communities PRs. > > Thanks, > Justin Justin Mclean <[email protected]> 于2021年1月29日周五 下午5:38写道： > HI, > > > - We can introduce a bot to automatically close these issues and pull > > requests if the original author does not reply for a long time. > > I suggest you don’t this this as it discourages people from contributing > and you more more committers and grow the community so you have more people > who can respond to PR in a more timely manner. I would try to come up with > ways to review the back log of requests and be more responsive to the > communities PRs. > > Thanks, > Justin
