Open Stack

Hi Ian,

I agree, let’s have a meeting next Tuesday and we can agree on the logistics there.

Thanks,
Ildikó


> On 2016. Nov 10., at 19:10, Ian Y. Choi <ianyrchoi at gmail.com> wrote:
> 
> Ildiko Vancsa wrote on 11/10/2016 4:57 AM:
>> Hi,
>> 
>> I like the ISO week numbers better. I think it’s more consistent, gives a regular cadence and does not cause confusions with having a meeting on the 5th week or not for instance.
>> 
>> My 2 cents.
> Make sense. Then IMO changing [1] with biweekly-odd or documenting this as description would be good.
> For monthly meeting occurrence idea, I would like to follow another mail thread [2].
> 
> Although the next week is even according to ISO week numbers, let's have training-guides meeting
> on next Tuesday 13:00 UTC and make accordance for that, since there were no training-guides team meeting for latest 3 weeks.
> 
> Is this okay for all training-guides meeting attendees?
> 
> 
> [1] http://git.openstack.org/cgit/openstack-infra/irc-meetings/tree/meetings/training-guides-team-meeting.yaml <http://git.openstack.org/cgit/openstack-infra/irc-meetings/tree/meetings/training-guides-team-meeting.yaml>
> [2] http://lists.openstack.org/pipermail/openstack-infra/2016-November/004835.html <http://lists.openstack.org/pipermail/openstack-infra/2016-November/004835.html>
> 
> 
> With many thanks,
> 
> /Ian
>> 
>> Thanks and Best Regards,
>> Ildikó
>> 
>> 
>>> On 2016. Nov 9., at 20:21, Ian Y. Choi <ianyrchoi at gmail.com <mailto:ianyrchoi at gmail.com>> wrote:
>>> 
>>> Hello,
>>> 
>>> IMO if there is an IRC meeting on every week with alternating times for odd and even weeks,
>>> having two bi-weekly schedules with alternating times would be self-explanatory.
>>> However, if the meeting frequency would be just one or two in a month,
>>> then referring such as n-th week in every month would be more intuitive I think.
>>> 
>>> Unfortunately current yaml2ical does not support such logistics,
>>> but my WIP patch ( https://review.openstack.org/#/c/395762/ <https://review.openstack.org/#/c/395762/> ) will make a clue
>>> to support such logistics in the near future I think :)
>>> 
>>> Note that I suggest not to consider 5th weeks because some months do not have 5th weeks.
>>> 
>>> 
>>> With many thanks,
>>> 
>>> /Ian
>>> 
>>> Jeremy Stanley wrote on 11/9/2016 10:45 PM:
>>>> On 2016-11-09 13:34:34 +0900 (+0900), Ian Y. Choi wrote:
>>>>> My understanding of *odd* weeks is the 1st and 3rd weeks in every month,
>>>>> since we actually had training-guides meetings with such logistics a few
>>>>> months ago.
>>>> [...]
>>>> 
>>>> So you skip 5th weeks when those happen? Or you have back-to-back
>>>> meeting weeks in those cases?
>>>> 
>>>> The way alternating weeks are usually interpreted (and handled in
>>>> the IRC meeting scheduling automation we have) is based on even or
>>>> odd ISO week numbers:
>>>> 
>>>> http://git.openstack.org/cgit/openstack-infra/yaml2ical/tree/README.rst?id=c29e042#n163 <http://git.openstack.org/cgit/openstack-infra/yaml2ical/tree/README.rst?id=c29e042#n163>
>>>> 
>>>> https://en.wikipedia.org/wiki/ISO_week_date <https://en.wikipedia.org/wiki/ISO_week_date>
>>>> 
>>> 
>>> 
>>> _______________________________________________
>>> OpenStack-Infra mailing list
>>> OpenStack-Infra at lists.openstack.org <mailto:OpenStack-Infra at lists.openstack.org>
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra>
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-infra/attachments/20161111/64b43c13/attachment-0001.html>