Roughly an hour a day, and super useful. I’d echo that anyone can volunteer, since a lot of the job is reaching out to various folks for input (docs/policies/neutron-teams.rst is the map of truth.)
I found a lot of bugs that I care about in the pre-mitaka backlog, that I didn’t know existed. This has been an education process for me, and I’ve been trying to triage one pre-mitaka bug for every mitaka one. A rotating RFE deputy from the drivers team might also be useful, so the first pass isn’t always the drivers meeting. I tend to pay attention more when it’s my “assigned” turn. I shouldn’t, but I do. Thanks, doug > On Dec 3, 2015, at 9:29 AM, Kyle Mestery <[email protected]> wrote: > > On Wed, Dec 2, 2015 at 10:49 AM, Armando M. <[email protected] > <mailto:[email protected]>> wrote: > Hi neutrinos, > > It's been a couple of months that the Bug deputy process has been in place > [1,2]. Since the beginning of Mitaka we have collected the following > statistics (for neutron and neutronclient): > > Total bug reports: 373 > Fix committed: 144 > Unassigned: 73 > New: 17 > Incomplete: 20 > Confirmed: 27 > Triaged: 6 > > At first, it is clear that we do not fix issues nearly as fast as they come > in, but at least we managed to keep the number of unassigned/unvetted bugs > relatively small, so kudos to you all who participated in this experiment. I > don't have data based on older releases, so I can't see whether we've > improved or worsened, and I'd like to ask for feedback from the people who > played with this first hand, especially on the amount of time that has taken > them to do deputy duty for their assigned week. > ihrachys > regXboi > markmcclain > mestery > mangelajo > garyk > rossella_s > dougwig > Many thanks, > Armando > > > I've found the process to be super useful. I found that by volunteering to be > the bug deputy it forced me to spend about an hour a day going through > incoming bugs. But the result is faster triage, and I was able to point some > bugs directly at people for quick resolution. Thanks for driving this > important initiative! > > One concern I have is ensuring we rotate people, because it does take some > time, and if the same handful of rotate, they will burn out. So I actively > encourage more people to volunteer, you don't even have to be a Neutron core > reviewer to do this! > > Thanks! > Kyle > > [1] https://wiki.openstack.org/wiki/Network/Meetings#Bug_deputy > <https://wiki.openstack.org/wiki/Network/Meetings#Bug_deputy> > [2] > http://docs.openstack.org/developer/neutron/policies/bugs.html#neutron-bug-deputy > > <http://docs.openstack.org/developer/neutron/policies/bugs.html#neutron-bug-deputy> > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > <http://[email protected]/?subject:unsubscribe> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev> > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected] > <mailto:[email protected]>?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
