Hi, I've noticed that the response time is slow for Dubbo's core repository, including reviewing pull request, issue triage and issue cleanup, it seems that not everyone has enough time to deal with things like this.
My idea is to identify the active contributors of the community, and invite to become a committer, let more people come in and help. In addition, we should also use robot to help us. The problem is how to find such people, I think it can be collected by the data, such as GitHub activities, how often do they participate in the discussion, how often do they participate in the review code. Furthermore, I think that people who often send pull requests, and those who often participate in the community, may be two types of people. The former requires large amount of time, and the latter can participate using their fragmented time. For example, if I want to send a pr, I need to understand an issue, fix, test, which takes a lot of time. However, leaving a message on the issue, labelling an issue, or closing the issue, these tasks can be done small granularity. Maybe we know a lot about the first type of people, but we need to identify and discover the second type of people and let them come in to help manage the community. 最近Dubbo的仓库，响应比较慢，包括pr的review，issue的分类和清理，似乎没有人处理。我的想法是发展一部分活跃的contributor成为committer，让更多的人参与进来一起帮忙。另外机器人也要参与进来。现在的问题是要找到这样的人，我觉得可以通过数据反映出来，比如GitHub上经常参加讨论的，经常参与review代码的。 另外我觉得经常提pull request的人，和经常参与社区的人，可能是两类人，前者对时间的的颗粒度要求很高，后者对时间颗粒度的要求度低。 比如我要提一个pr，需要理解一个issue, 修复，测试，需要花较大的时间，而在issue上留个言，打个label，close下issue，对时间的要求相对较低。 我们对第一类人的了解是比较多的，但需要识别和发现第二类人，让他们进来帮助管理社区。 On Sat, Dec 29, 2018 at 5:13 PM Ian Luo <ian....@gmail.com> wrote: > > Hello folks, > > I'd like to apologize first since recently we are slow on issue and pull > request. We are very busy on ramping up Dubbo 2.7.0 which is expected to be > public available soon. I hope we could come back in one or two weeks so > depending on how soon we could finish. The code review for dubbo 2.7.0 > release is happening now on Github pull request. Feel free to join us to > raise issue or submit pull request against the recent code changes on the > master branch. > > You are also very welcomed to interact on other issues and pull requests > irrelevant to release 2.7.0. They are piling up and we can do nothing right > now :) > > I really hope we can ramp up release 2.7.0 very soon, and your > comments/efforts are appreciated. After that, I plan to continue the > discussion on release 3.0. > > Cheers, > -Ian. -- Best Regards！ Huxing
