<div dir="ltr">Hey, <div><br></div><div> Finally we took over the channel for 1h. mostly because the time was already agreed between many people on opposed timezones and it was a bit late to cancel it.</div><div><br></div><div> The first point was finding a suitable timeslot for a biweekly meeting -for some time- and alternatively following up on email. We should not take over the neutron channel for these meetings anymore, I'm sorry for the inconvenience.</div><div><br></div><div> Please find the summary here:</div><div><br></div><div><a href="http://eavesdrop.openstack.org/meetings/network_common_flow_classifier/2016/network_common_flow_classifier.2016-05-17-17.02.html">http://eavesdrop.openstack.org/meetings/network_common_flow_classifier/2016/network_common_flow_classifier.2016-05-17-17.02.html</a><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, May 17, 2016 at 8:10 PM, Kevin Benton <span dir="ltr"><<a href="mailto:kevin@benton.pub" target="_blank">kevin@benton.pub</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Yeah, no meetings in #openstack-neutron please. It leaves us nowhere to discuss development stuff during that hour.</div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Tue, May 17, 2016 at 2:54 AM, Miguel Angel Ajo Pelayo <span dir="ltr"><<a href="mailto:majopela@redhat.com" target="_blank">majopela@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 dir="ltr">I agree, let's try to find a timeslot that works.<div><br></div><div>using #openstack-neutron with the meetbot works, but it's going to generate a lot of noise.</div></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, May 17, 2016 at 11:47 AM, Ihar Hrachyshka <span dir="ltr"><<a href="mailto:ihrachys@redhat.com" target="_blank">ihrachys@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span><br>
> On 16 May 2016, at 15:47, Takashi Yamamoto <<a href="mailto:yamamoto@midokura.com" target="_blank">yamamoto@midokura.com</a>> wrote:<br>
><br>
> On Mon, May 16, 2016 at 10:25 PM, Takashi Yamamoto<br>
> <<a href="mailto:yamamoto@midokura.com" target="_blank">yamamoto@midokura.com</a>> wrote:<br>
>> hi,<br>
>><br>
>> On Mon, May 16, 2016 at 9:00 PM, Ihar Hrachyshka <<a href="mailto:ihrachys@redhat.com" target="_blank">ihrachys@redhat.com</a>> wrote:<br>
>>> +1 for earlier time. But also, have we booked any channel for the meeting? Hijacking #openstack-neutron may not work fine during such a busy (US) time. I suggest we propose a patch for <a href="https://github.com/openstack-infra/irc-meetings" rel="noreferrer" target="_blank">https://github.com/openstack-infra/irc-meetings</a><br>
>><br>
>> i agree and submitted a patch.<br>
>> <a href="https://review.openstack.org/#/c/316830/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/316830/</a><br>
><br>
> oops, unfortunately there seems no meeting channel free at the time slot.<br>
<br>
</span>This should be solved either by changing the slot, or by getting a new channel registered for meetings. Using unregistered channels, especially during busy hours, is not effective, and is prone to overlaps for relevant meetings. The meetings will also not get a proper slot at <a href="http://eavesdrop.openstack.org" rel="noreferrer" target="_blank">eavesdrop.openstack.org</a>.<br>
<span><font color="#888888"><br>
Ihar<br>
</font></span><div><div>__________________________________________________________________________<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>
</div></div></blockquote></div><br></div>
</div></div><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>
<br></blockquote></div><br></div>
</div></div><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>
<br></blockquote></div><br></div>