Hey, 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.
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. Please find the summary here: http://eavesdrop.openstack.org/meetings/network_common_flow_classifier/2016/network_common_flow_classifier.2016-05-17-17.02.html On Tue, May 17, 2016 at 8:10 PM, Kevin Benton <ke...@benton.pub> wrote: > Yeah, no meetings in #openstack-neutron please. It leaves us nowhere to > discuss development stuff during that hour. > > On Tue, May 17, 2016 at 2:54 AM, Miguel Angel Ajo Pelayo < > majop...@redhat.com> wrote: > >> I agree, let's try to find a timeslot that works. >> >> using #openstack-neutron with the meetbot works, but it's going to >> generate a lot of noise. >> >> On Tue, May 17, 2016 at 11:47 AM, Ihar Hrachyshka <ihrac...@redhat.com> >> wrote: >> >>> >>> > On 16 May 2016, at 15:47, Takashi Yamamoto <yamam...@midokura.com> >>> wrote: >>> > >>> > On Mon, May 16, 2016 at 10:25 PM, Takashi Yamamoto >>> > <yamam...@midokura.com> wrote: >>> >> hi, >>> >> >>> >> On Mon, May 16, 2016 at 9:00 PM, Ihar Hrachyshka <ihrac...@redhat.com> >>> wrote: >>> >>> +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 >>> https://github.com/openstack-infra/irc-meetings >>> >> >>> >> i agree and submitted a patch. >>> >> https://review.openstack.org/#/c/316830/ >>> > >>> > oops, unfortunately there seems no meeting channel free at the time >>> slot. >>> >>> 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 >>> eavesdrop.openstack.org. >>> >>> Ihar >>> >>> __________________________________________________________________________ >>> OpenStack Development Mailing List (not for usage questions) >>> Unsubscribe: >>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>> >> >> >> __________________________________________________________________________ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: >> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev