<div dir="ltr">Hi Mike,<div><br></div><div>This works for me. We can refine/discuss at the bug squashing event.</div><div><br></div><div>Thanks!</div><div>--ruby</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Apr 11, 2018 at 2:53 PM, Michael Turek <span dir="ltr"><<a href="mailto:mjturek@linux.vnet.ibm.com" target="_blank">mjturek@linux.vnet.ibm.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Sorry this is so late but as for the format of the event I think we should do something like this:<br>
<br>
1) Go through new bugs<br>
-This is doable in storyboard. Sort by creation date<br>
-Should be a nice warm up activity!<br>
2) Go through oldest bugs<br>
-Again, doable in storyboard. Sort by last updated.<br>
-Older bugs are usually candidates for some clean up. We'll decide if bugs are still valid<br>
or if we need to reassign/poke owners.<br>
3) Open Floor<br>
-If you have a bug that you'd like to discuss, bring it up here!<br>
4) Storyboard discussion<br>
-One of the reasons we are doing this is to get our feet wet in storyboard. Let's spend<br>
10 to 20 minutes discussing what we need out of the tool after playing with it.<br>
<br>
Originally I was hoping that we could sort by task priority but that currently seems to be<br>
unavailable, or well hidden, in storyboard . If someone knows how to do this, please reply.<br>
<br>
Does anyone else have any ideas on how to structure bug day?<br>
<br>
Thanks!<br>
Mike <mjturek><br>
<br>
<br>
On 4/11/18 9:47 AM, Michael Turek wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hey all,<br>
<br>
Ironic Bug Day is happening tomorrow, April 12th at 1:00 PM - 3:00 PM (UTC)<br>
<br>
We will be meeting on Julia's bluejeans line: <a href="https://bluejeans.com/5548595878" rel="noreferrer" target="_blank">https://bluejeans.com/55485958<wbr>78</a><br>
<br>
Hope to see everyone there!<br>
<br>
Thanks,<br>
Mike Turek <mjturek><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>
</blockquote></div><br></div>