On 2016/01/12 7:14, Armando M. wrote:
On 11 January 2016 at 13:54, Hirofumi Ichihara
<ichihara.hirof...@lab.ntt.co.jp
<mailto:ichihara.hirof...@lab.ntt.co.jp>> wrote:
On 2016/01/12 5:14, Armando M. wrote:
On 11 January 2016 at 12:04, Carl Baldwin <c...@ecbaldwin.net
<mailto:c...@ecbaldwin.net>> wrote:
What do we do? My calendar was set up with the sane
bi-weekly thing
and it shows the meeting for tomorrow. The last word from our
fearless leader is that we'll have it today. So, I'll be
there today
unless instructed otherwise.
The ics file now seems to reset the cadence beginning today
at 2100
and next Tuesday, the 19th, at 1400. I guess we should
either hold
the meeting today and reset the cadence or fix the ics file.
This is what I would like to do now:
https://review.openstack.org/#/c/266019
I personally haven't seen that much of an attendance difference
anyway, and at this point, it'll simplify our lives and avoid
grief going forward.
I like it.
However, we have gathered from all over the world because neutron
is big project. Should we have the choice so that more people get
attendance opportunity?
This time, the return to the normal schedule was a disaster, plus
every time we switch to daylight savings, or every time there's a
holiday break/summit we have twice the chances to screw up if we keep
the bi-weekly schedule.
If I go and look at the logs [1] I don't have hard evidence that the
bi-weekly schedule does indeed help the attendance of friendlier
timezones, so I wonder...what's the point?
You're right. My reply was just general opinion. I think that most
regular folks probably attend both days now. I actually do as well.
I was worried that sometimes there are developers who introduce his bug
or ask core to review although they usually don't attend. However, we
have openstack-neutron channel for it.
A.
[1] http://eavesdrop.openstack.org/meetings/networking/
Carl
On Mon, Jan 11, 2016 at 12:09 PM, Kevin Benton
<blak...@gmail.com <mailto:blak...@gmail.com>> wrote:
> The issue is simply that you have a sane bi-weekly thing
setup in your
> calendar. What we have for Neutron is apparently defined as
“odd and even
> weeks when weeks are represented as an short integer
counting from the first
> of the year”, a.k.a. “bi-weekly” as a robot might define it. :)
>
>
> On Jan 11, 2016, at 11:00 AM, Kyle Mestery
<mest...@mestery.com <mailto:mest...@mestery.com>> wrote:
>
> On Mon, Jan 11, 2016 at 12:57 PM, Kyle Mestery
<mest...@mestery.com <mailto:mest...@mestery.com>> wrote:
>>
>> On Mon, Jan 11, 2016 at 12:45 PM, Armando M.
<arma...@gmail.com <mailto:arma...@gmail.com>> wrote:
>>>
>>> Disregard the email subject.
>>>
>>> I stand corrected. Let's meet today.
>>>
>>
>> Something is wrong, I have the meeting on my google
calendar, and it shows
>> up as tomorrow for this week. I've had these setup as
rotating for a while
>> now, so something is fishy with the .ics files.
>
>
> If you look here [1], the meeting cadence was:
>
> 12-15-2015: Tuesday
> 12-21-2015: Monday
> 12-29-2015: Tuesday (skipped)
> 01-04-2016: Monday (skipped)
> 01-12-2016 Tuesday
>
> The meeting is tomorrow.
>
> [1] http://eavesdrop.openstack.org/meetings/networking/2015/
>>
>>
>>>
>>> On 11 January 2016 at 10:24, Ihar Hrachyshka
<ihrac...@redhat.com <mailto:ihrac...@redhat.com>> wrote:
>>>>
>>>> Armando M. <arma...@gmail.com
<mailto:arma...@gmail.com>> wrote:
>>>>
>>>>> Hi neutrinos,
>>>>>
>>>>> A kind reminder for tomorrow's meeting at 1400UTC.
>>>>>
>>>>> Cheers,
>>>>> Armando
>>>>>
>>>>> [1] https://wiki.openstack.org/wiki/Network/Meetings
>>>>>
>>>>>
__________________________________________________________________________
>>>>> OpenStack Development Mailing List (not for usage
questions)
>>>>> Unsubscribe:
>>>>>
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
>>>>>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>>
>>>>
>>>> Is it just me, or when you use .ics file from eavesdrop,
it says the
>>>> meeting is today?
>>>>
>>>>
http://eavesdrop.openstack.org/calendars/neutron-team-meeting.ics
>>>>
>>>> Is it the same issue as described in:
>>>>
>>>>
>>>>
http://lists.openstack.org/pipermail/openstack-dev/2015-December/082902.html
>>>>
>>>> and that is suggested to fix by readding your events
from updated .ics
>>>> file:
>>>>
>>>>
>>>>
http://lists.openstack.org/pipermail/openstack-dev/2016-January/083216.html
>>>>
>>>> Ihar
>>>>
>>>>
>>>>
__________________________________________________________________________
>>>> OpenStack Development Mailing List (not for usage questions)
>>>> Unsubscribe:
>>>>
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
<http://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://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://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://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://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
<mailto: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://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
