On 10/07/18 07:04, jun liu wrote: > Hi All, > > Now the community has become very active, pull requests and issues are being > reported in a certain amount every day, in contrast, our response seems not > fast enough and issues bumped up. > > I've thought of a duty table for temporarily solving this problem, committers > on duty are responsible for responding to community activities, classify > issues and resolve/assign issues, by doing that, we can guarantee at least > some of the committers devote enough time to the community every day. > > Remember that we still need to encourage users to participate in any kind of > contribution, and anyone can still participate in the community at any time. > > Here’s an example duty form: > https://github.com/apache/incubator-dubbo/wiki/Duty-Form > Remember label issues: > https://github.com/apache/incubator-dubbo/wiki/Label-an-Issue > > Do you guys have any ideas of how to achieve this goal?
Just remember that every committer is a volunteer and that they get to choose what they work on. Allocating committers to tasks isn't something that happens on an ASF project. Growing the community is the obvious answer to an increasing backlog of issues. If you haven't already seen it I strongly recommend reading this post that talks about Apache Beam's experience in this area: https://lists.apache.org/thread.html/33a6c3aa0fffa6e961aa2b861ebde333d898a5e1062d0d71d0e13d46@%3Cdev.community.apache.org%3E Mark
