<div dir="ltr">Hi, folks,<div><br><div>Thanks, Markus, for doing this job! I'm interested in this activity. </div><div><br></div><div>Timofey</div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Sep 5, 2016 at 7:20 PM, Sylvain Bauza <span dir="ltr"><<a href="mailto:sbauza@redhat.com" target="_blank">sbauza@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5"><br>
<br>
Le 05/09/2016 13:19, Markus Zoeller a écrit :<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
TL;DR: bug czar role for Nova is vacant from now on<br>
<br>
<br>
After doing bug triage for ~1 year, which was quiet interesting, it's<br>
time for me to move to different topics. My tasks within the company<br>
internal team are shifting too. Unfortunately less Nova for me in the<br>
next (hopefully short) time. That means I'm resigning from the bug czar<br>
role as of now.<br>
<br>
<br>
Observations in this timeframe<br>
------------------------------<br>
<br>
* The quality of most of the bug reports could be better. Very often<br>
they are not actionable. A bug report which isn't actionable burns<br>
resources without any benefit. The pattern I've seen is:<br>
* 1/3 : invalid because they are support requests or a wrong<br>
understanding<br>
* 1/3 : could be reasonable but essential information is missing<br>
* 1/3 : sounds reasonable + has a little info, should be looked at<br>
Very few follow this template which is shown when you open a new<br>
report: <a href="https://wiki.openstack.org/wiki/Nova/BugsTeam/BugReportTemplate" rel="noreferrer" target="_blank">https://wiki.openstack.org/wik<wbr>i/Nova/BugsTeam/BugReportTempl<wbr>ate</a><br>
<br>
* We get ~40 new bug reports per week. With the current number of people<br>
who do bug triage, the number of overall bug reports doesn't decline. I<br>
started collecting data 6 months ago:<br>
<br>
<a href="http://45.55.105.55:3000/dashboard/db/openstack-bugs?from=now-6M&panelId=1&fullscreen" rel="noreferrer" target="_blank">http://45.55.105.55:3000/dashb<wbr>oard/db/openstack-bugs?from=<wbr>now-6M&panelId=1&fullscreen</a><br>
<br>
* I wish the cores would engage more in bug triaging. If one core every<br>
other week would do the bug triage for 1 week, a core would have to do<br>
that only once per dev cycle. I'm aware of the review backlog though :/<br>
<br>
* I wish more non-cores would engage more in bug triaging.<br>
<br>
* We don't have contacts for a lot of areas in Nova:<br>
<a href="https://wiki.openstack.org/wiki/Nova/BugTriage#Tag_Owner_List" rel="noreferrer" target="_blank">https://wiki.openstack.org/wi<wbr>ki/Nova/BugTriage#Tag_Owner_Li<wbr>st</a><br>
<br>
* Keeping the bug reports in a consistent state is cumbersome:<br>
<a href="http://45.55.105.55:8082/bugs-dashboard.html#tabInProgressStale" rel="noreferrer" target="_blank">http://45.55.105.55:8082/<wbr>bugs-dashboard.html#tabInProgr<wbr>essStale</a><br>
We could introduce more automation here.<br>
<br>
<br>
Things we should continue<br>
-------------------------<br>
<br>
* Bug reports older that the oldest supported stable release should be<br>
expired. Maybe best when the EOL tag gets applied.<br>
<br>
<a href="https://github.com/openstack-infra/release-tools/blob/master/expire_old_bug_reports.py" rel="noreferrer" target="_blank">https://github.com/openstack-i<wbr>nfra/release-tools/blob/master<wbr>/expire_old_bug_reports.py</a><br>
<a href="http://lists.openstack.org/pipermail/openstack-dev/2016-May/095654.html" rel="noreferrer" target="_blank">http://lists.openstack.org/pi<wbr>permail/openstack-dev/2016-May<wbr>/095654.html</a><br>
<br>
* We never came to a real conclusion how the ops communicated the RFEs<br>
to us. The way of using "wishlist" bug reports wasn't successful IMO.<br>
The last proposal was to use the ops ML to bring an RFE into some<br>
actionable shape and then create a backlog spec out of it.<br>
<a href="http://lists.openstack.org/pipermail/openstack-dev/2016-March/089365.html" rel="noreferrer" target="_blank">http://lists.openstack.org/pi<wbr>permail/openstack-dev/2016-Mar<wbr>ch/089365.html</a><br>
<br>
<br>
<br>
Things we should start<br>
----------------------<br>
<br>
* A cross-project discussion of (easy) ways to collect and send debug<br>
data to upstream OpenStack. Almost no bug report in Nova had the result<br>
of "sosreport" attached although we ask for that in the report template.<br>
<br>
<br>
<br>
Some last words<br>
---------------<br>
<br>
* Whoever wants to do the job next, I offer some kind of onboarding.<br>
<br>
* I'll push a change to remove the IRC meetings in the next few days:<br>
<a href="http://eavesdrop.openstack.org/#Nova_Bugs_Team_Meeting" rel="noreferrer" target="_blank">http://eavesdrop.openstack.or<wbr>g/#Nova_Bugs_Team_Meeting</a><br>
<br>
* The tooling I used will still be available at:<br>
<a href="https://github.com/markuszoeller/openstack/tree/master/scripts/launchpad" rel="noreferrer" target="_blank">https://github.com/markuszoel<wbr>ler/openstack/tree/master/<wbr>scripts/launchpad</a><br>
<br>
* My server which hosts some dashboards will still be available at:<br>
<a href="http://45.55.105.55:3000/dashboard/db/openstack-bugs" rel="noreferrer" target="_blank">http://45.55.105.55:3000/dash<wbr>board/db/openstack-bugs</a><br>
<a href="http://45.55.105.55:8082/bugs-dashboard.html" rel="noreferrer" target="_blank">http://45.55.105.55:8082/<wbr>bugs-dashboard.html</a><br>
<a href="http://45.55.105.55:8082/bugs-stats.html" rel="noreferrer" target="_blank">http://45.55.105.55:8082/<wbr>bugs-stats.html</a><br>
<br>
* I did an evaluation of Storyboard in July 2016 and it looks promising.<br>
Give it a shot at: <a href="https://storyboard-dev.openstack.org/#!/project/2" rel="noreferrer" target="_blank">https://storyboard-dev.opensta<wbr>ck.org/#!/project/2</a> If<br>
you don't like something there, push a change, it's Python based.<br>
<br>
* I'll still hang out in the IRC channels, but don't expect much from me.<br>
<br>
<br>
Thanks a lot to the people who helped making Nova a better project by<br>
doing bug triage! Special thanks to auggy who put a lot(!) of effort<br>
into that.<br>
<br>
See you (hopefully) in Barcelona!<br>
</blockquote>
<br></div></div>
As said on IRC, hope we'll still see you around, and see you in Barcelona. You made a great job !<span class="HOEnZb"><font color="#888888"><br>
<br>
-Sylvain</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
--<br>
Regards,<br>
Markus Zoeller (markus_z)<br>
<br>
<br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
</blockquote>
<br>
<br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
</div></div></blockquote></div><br></div>