<div dir="ltr">Markus,<div><br></div><div>If you van connect me with someone who can tell me what needs the most attention and how to get started, I'd be happy to help.</div><div><br></div><div>//adam</div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><font><div style="font-family:arial;font-size:small"><b><i><br>Adam Lawson</i></b></div><div><font><font color="#666666" size="1"><div style="font-family:arial"><br></div><div style="font-family:arial;font-size:small">AQORN, Inc.</div><div style="font-family:arial;font-size:small">427 North Tatnall Street</div><div style="font-family:arial;font-size:small">Ste. 58461</div><div style="font-family:arial;font-size:small">Wilmington, Delaware 19801-2230</div><div style="font-family:arial;font-size:small">Toll-free: (844) 4-AQORN-NOW ext. 101</div><div style="font-family:arial;font-size:small">International: +1 302-387-4660</div></font><font color="#666666" size="1"><div style="font-family:arial;font-size:small">Direct: +1 916-246-2072</div></font></font></div></font></div></div></div></div></div></div>
<br><div class="gmail_quote">On Fri, Apr 1, 2016 at 3:46 AM, Markus Zoeller <span dir="ltr"><<a href="mailto:mzoeller@de.ibm.com" target="_blank">mzoeller@de.ibm.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">TL;DR: * The Nova bugs team needs more members<br>
* Tasks: <a href="https://wiki.openstack.org/wiki/BugTriage" rel="noreferrer" target="_blank">https://wiki.openstack.org/wiki/BugTriage</a><br>
* Cleanup: <a href="http://45.55.105.55:8082/bugs-dashboard.html" rel="noreferrer" target="_blank">http://45.55.105.55:8082/bugs-dashboard.html</a><br>
* Meeting: <a href="https://wiki.openstack.org/wiki/Meetings/Nova/BugsTeam" rel="noreferrer" target="_blank">https://wiki.openstack.org/wiki/Meetings/Nova/BugsTeam</a><br>
* Etherpad: <a href="https://etherpad.openstack.org/p/nova-bugs-team" rel="noreferrer" target="_blank">https://etherpad.openstack.org/p/nova-bugs-team</a><br>
<br>
<br>
The Nova project has a large backlog of open bug reports. Around 5 new<br>
bug reports get created everyday. It is not possible to make a<br>
reasonable progress with the current number of people. The nova bugs<br>
team needs to play a more active role and it needs more people for that.<br>
<br>
<br>
What's in for you?<br>
------------------<br>
As bugs are in every software in every place, you will get around a lot.<br>
Having a specific issue makes it also easier to ping other folks to<br>
discuss this issue. Bug fixes also don't have the hard deadlines<br>
imposed on feature patches. Being once on the bug triage side will<br>
improve the quality of your future bug reports which will make them<br>
more likely to get solved.<br>
<br>
<br>
Current Status<br>
--------------<br>
The main issue which slows down all following steps are bug reports<br>
without the essential informations [1]:<br>
* versions (nova, hypervisor, database, ...)<br>
* steps-to-reproduce (with actual data)<br>
* expected behavior<br>
* actual observed behavior<br>
* logs (in debug mode)<br>
* topology (for example: nova-network vs. neutron)<br>
Although this gets asked for when creating a bug report, the vast<br>
majority of bug reports lack this information. Usually it takes one<br>
to three roundtrips to get this information from the reporter. This<br>
is time consuming. As we focus less on new features in Newton [2] I<br>
have the hope that the bug list will get more attention.<br>
<br>
<br>
Tasks<br>
-----<br>
The tasks are listed in the wiki [3]. They "just" need to be done.<br>
Repeatedly. Some on a daily basis, some less frequently. The cleanup<br>
dashboard [4] is a tool I use personally but can be used by you too.<br>
<br>
The Neutron folks introduced a weekly rotating bug skimming duty and<br>
they've made good experiences with it. This involves 1-3 people who<br>
check new bugs reports if they are valid and provide the essential<br>
information. We should adapt that [5].<br>
<br>
In general we should aim for:<br>
* respond to new bugs in a timely manner to get high quality reports<br>
* clean up the "old stuff" (>= 1.5 years)<br>
* spread the effort to multiple shoulders<br>
* rotate the different efforts to prevent exhaustion and tunnel vision<br>
<br>
There is an ongoing effort to move the RFEs (request for feature<br>
enhancements) away from the bug list [6] to allow us to be more<br>
focused on faulty behavior of existing features people already rely on.<br>
<br>
<br>
Organization<br>
------------<br>
* The nova bugs team has an IRC meeting [7] which allows us to sync<br>
with each other.<br>
* The cleanup dashboard [4] shows bug reports which need a check<br>
based on the tasks [3].<br>
* The etherpad [8] can be used to avoid an overlap of efforts of<br>
different people.<br>
<br>
<br>
Education<br>
---------<br>
It's possible to use the nova bugs team IRC meeting for education<br>
sessions if this helps you.<br>
I will also attend the summit in Austin in a few weeks. We can do an<br>
unofficial "bugs mgmt process" crash course there if you like. Just<br>
talk to me there (or beforehand in IRC) and we will find the time<br>
and space.<br>
At last I can offer a Google Hangout session if some are interested<br>
in that.<br>
<br>
<br>
How to Join?<br>
------------<br>
* Join the nova-bugs Launchpad group [9]<br>
* Familiarize with the process [10]<br>
* Attend the bugs meeting [7]<br>
<br>
With a few people who are willing to spent a few hours per week we<br>
can create a well maintained bug list where issues get addressed<br>
in a timely manner to consistently improve the quality of Nova.<br>
<br>
<br>
References<br>
----------<br>
[1] "working on bug reports; what blocks you?":<br>
<a href="http://lists.openstack.org/pipermail/openstack-dev/2016-March/089677.html" rel="noreferrer" target="_blank">http://lists.openstack.org/pipermail/openstack-dev/2016-March/089677.html</a><br>
[2] "No spec approvals for new things until after the summit":<br>
<a href="http://lists.openstack.org/pipermail/openstack-dev/2016-March/090370.html" rel="noreferrer" target="_blank">http://lists.openstack.org/pipermail/openstack-dev/2016-March/090370.html</a><br>
[3] <a href="https://wiki.openstack.org/wiki/BugTriage" rel="noreferrer" target="_blank">https://wiki.openstack.org/wiki/BugTriage</a><br>
[4] <a href="http://45.55.105.55:8082/bugs-dashboard.html" rel="noreferrer" target="_blank">http://45.55.105.55:8082/bugs-dashboard.html</a><br>
[5]<br>
<a href="https://wiki.openstack.org/wiki/Nova/BugTriage#Weekly_bug_skimming_duty" rel="noreferrer" target="_blank">https://wiki.openstack.org/wiki/Nova/BugTriage#Weekly_bug_skimming_duty</a><br>
[6] "Wishlist bugs == (trivial) blueprint?":<br>
<a href="http://lists.openstack.org/pipermail/openstack-dev/2016-March/089365.html" rel="noreferrer" target="_blank">http://lists.openstack.org/pipermail/openstack-dev/2016-March/089365.html</a><br>
[7] <a href="https://wiki.openstack.org/wiki/Meetings/Nova/BugsTeam" rel="noreferrer" target="_blank">https://wiki.openstack.org/wiki/Meetings/Nova/BugsTeam</a><br>
[8] <a href="https://etherpad.openstack.org/p/nova-bugs-team" rel="noreferrer" target="_blank">https://etherpad.openstack.org/p/nova-bugs-team</a><br>
[9] <a href="https://launchpad.net/~nova-bugs" rel="noreferrer" target="_blank">https://launchpad.net/~nova-bugs</a><br>
[10] <a href="http://markuszoeller.github.io/posts/2015/12/01/openstack-bugs/" rel="noreferrer" target="_blank">http://markuszoeller.github.io/posts/2015/12/01/openstack-bugs/</a><br>
<br>
<br>
Regards, Markus Zoeller (markus_z)<br>
<br>
<br>
__________________________________________________________________________<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.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div><br></div>