Open Stack

Hi,

So today we decided to have an extra meeting timeslot first Thursday of 
every month at 8:00 UTC on #openstack-nova on the OFTC IRC server. So 
the first such meeting will happen on Thursday 2021.06.03.

I've update the meeting wiki with the new timings and pushed a patch to 
add the meeting to the IRC meeting schedule[2].

See you on the meeting!

Cheers,
gibi

[1] https://wiki.openstack.org/wiki/Meetings/Nova
[2] https://review.opendev.org/c/opendev/irc-meetings/+/794010

On Wed, May 26, 2021 at 09:50, Balazs Gibizer <balazs.gibizer at est.tech> 
wrote:
> Hi,
> 
> On Tue, May 25, 2021 at 07:10, Sam Su (苏正伟) 
> <suzhengwei at inspur.com> wrote:
>> Hi, gibi:
>> 	I'm very sorry for respone later.
>> 	A meeting around 8:00 UTC seems very appropriate to us. It is 
>> afternoon work time in East Asian when 8:00 UTC.
>> 	Now my colleague, have some work on Cyborg across with Nova, 
>> passthroug device, TPM and so on. If they can join the irc meeting 
>> talking with the community , it will be much helpful.
>> 
> 
> @Sam: We discussed your request yesterday[1] and it seems that the 
> team is not objecting against a monthly office hour in 
> #openstack-nova around UTC 8 or UTC 9. But we did not agreed which 
> day we should have it so I set up a poll[2].
> 
> @Team: As we discussed yesterday I opened a poll to agree on the day 
> of the week and the exact start time for the Asia friendly office 
> hours slot. Please vote in the poll[2] before next Tuesday.
> 
> Cheers,
> gibi
> 
> [1] 
> http://eavesdrop.openstack.org/meetings/nova/2021/nova.2021-05-25-16.00.log.html#l-100
> [2] https://doodle.com/poll/svrnmrtn6nnknzqp
> 
>> 
>> -----邮件原件-----
>> 发件人: Balazs Gibizer [mailto:balazs.gibizer at est.tech]
>> 发送时间: 2021年5月14日 14:12
>> 收件人: Sam Su (苏正伟) <suzhengwei at inspur.com>
>> 抄送: alifshit at redhat.com; openstack-discuss at lists.openstack.org
>> 主题: Re: [Nova] Meeting time poll
>> 
>> 
>> 
>> On Fri, May 14, 2021 at 01:23, Sam Su (苏正伟)
>> <suzhengwei at inspur.com> wrote:
>>>  From: Sam Su (苏正伟)
>>>  Sent: Friday, May 14, 2021 03:23
>>>  To: alifshit at redhat.com
>>>  Cc: openstack-discuss at lists.openstack.org
>>>  Subject: Re: [Nova] Meeting time poll
>>> 
>>>  Hi, Nova team：
>> 
>> Hi Sam!
>> 
>>>          There are many asian developers for Openstack community. I
>>>  found the current IRC time of Nova is not friendly to them, 
>>> especially
>>>  to East Asian.
>>>  If they
>>>  can take part in the IRC meeting, the Nova may have more 
>>> developers.
>>>  Of
>>>  cource, Central Europe and NA West Coast is firstly considerable. 
>>> If
>>>  the team could schedule the meeting once per month, time suitable 
>>> for
>>>  asians, more people would participate in the meeting discussion.
>> 
>> You have a point. In the past Nova had alternating meeting time 
>> slots one for EU+NA and one for the NA+Asia timezones. Our 
>> experience was that the NA+Asia meeting time slot was mostly 
>> lacking participants. So we merged the two slots. But I can imagine 
>> that the situation has changed since and there might be need for an 
>> alternating meeting again.
>> 
>> We can try what you suggest and do an Asia friendly meeting once a 
>> month. The next question is what time you would like to have that 
>> meeting. Or more specifically which part of the nova team you would 
>> like to meet more?
>> 
>> * Do a meeting around 8:00 UTC to meet Nova devs from the EU
>> 
>> * Do a meeting around 0:00 UTC to meet Nova devs from North America
>> 
>> If we go for the 0:00 UTC time slot then I need somebody to chair 
>> that meeting as I'm from the EU.
>> 
>> Alternatively to having a formal meeting I can offer to hold a free 
>> style office hour each Thursday 8:00 UTC in #openstack-nova. I made 
>> the same offer when we moved the nova meeting to be a non 
>> alternating one.
>> But honestly I don't remember ever having discussion happening 
>> specifically due to that office hour in #openstack-nova.
>> 
>> Cheers,
>> gibi
>> 
>> p.s.: the smime in your mail is not really mailing list friendly. 
>> Your mail does not appear properly in the archive.
>> 
>> 
>> 
>> 
> 
> 
>