On 03/25/2013 10:39 PM, Valerie Juarez wrote:
We triaged 31 bug reports on the bug day [3]. Contributors triaged
reports throughout the week as well, but not all of their contributions were captured on the etherpad, so that's harder to measure.
Or maybe not, at least for old bugs which are less likely to have activity without these Bug Days:
As a reference:
80 LQT reports changed during the week: http://bit.ly/XDaxO6
From those 20 changed resolution:
FIXED 3 DUPLICATE 1 WORKSFORME 14
We could even look how many off those changes happened before / during/ after the bug day during that week to see the impact of that day vs the rest of the week.
Being myself a potential contributor, I could scratch only 1 hour during the official hours since it was during office time and there were other things going on. But then in the evenings and weekend I found more time. I guess this pattern might apply to others as well.
Triaging at the same time than others and chatting it's nice, but you can also do quite a lot alone. Bug changes trigger email notifications and in many cases you get other people involved that way.
I would still pick a few hours during the week for team work, but these "Bug Days" maybe need to be called "Bug Weeks" and plan accordingly...