[cinder] changing the weekly meeting time
(Just to be completely clear -- we're only gathering information at this point. The Cinder weekly meeting is still Wednesdays at 16:00 UTC.)
As we discussed at today's meeting [0], a request has been made to hold the weekly meeting earlier so that it would be friendlier for people in Asia time zones.
Based on the people in attendance today, it seems that a move to 14:00 UTC is not out of the question.
Thus, the point of this email is to solicit comments on whether we should change the meeting time to 14:00 UTC. As you consider the impact on yourself, if you are in a TZ that observes Daylight Savings Time, keep in mind that most TZs go back to standard time over the next few weeks.
(I was going to insert an opinion here, but I will wait and respond in this thread like everyone else.)
cheers, brian
[0] http://eavesdrop.openstack.org/meetings/cinder/2019/cinder.2019-10-23-16.00....
Hi Brian,
It's great that the change in weekly meeting time is considered, here are my opinions on the same from the perspective of Asian countries (having active upstream developers)
Current meeting time (16:00 - 17:00 UTC)
INDIA : is 9:30 - 10:30 PM IST (UTC+05:30) is a little late but manageable.
CHINA : is 12:00 - 01:00 AM CST (UTC+08:00) is almost impossible to attend.
JAPAN : is 01:00 - 02:00 AM JST (UTC+09:00) similar to the case as China.
IMO shifting the meeting time 2 hours earlier (UTC 14:00) might bring more participation and would ease out timings for some (including me) but these are just my thoughts.
Thanks and Regards Rajat Dhasmana
On Thu, Oct 24, 2019 at 3:05 AM Brian Rosmaita rosmaita.fossdev@gmail.com wrote:
(Just to be completely clear -- we're only gathering information at this point. The Cinder weekly meeting is still Wednesdays at 16:00 UTC.)
As we discussed at today's meeting [0], a request has been made to hold the weekly meeting earlier so that it would be friendlier for people in Asia time zones.
Based on the people in attendance today, it seems that a move to 14:00 UTC is not out of the question.
Thus, the point of this email is to solicit comments on whether we should change the meeting time to 14:00 UTC. As you consider the impact on yourself, if you are in a TZ that observes Daylight Savings Time, keep in mind that most TZs go back to standard time over the next few weeks.
(I was going to insert an opinion here, but I will wait and respond in this thread like everyone else.)
cheers, brian
[0]
http://eavesdrop.openstack.org/meetings/cinder/2019/cinder.2019-10-23-16.00....
Hi Brian,
I agree with Rajat. Meeting happened in mid-night will prevent people to attend, except they have topics that must to talk with team. Openstack is widely used in Asia, but there’s no much core from Asia (in countries that the meeting in mid-night). Meeting time is one of the reason😊 Nova have two meetings, two time zone friendly. But I don’t like to divide the meeting to two.
Regards Liang From: Rajat Dhasmana rajatdhasmana@gmail.com Sent: Thursday, October 31, 2019 12:54 AM To: Brian Rosmaita rosmaita.fossdev@gmail.com Cc: openstack-discuss@lists.openstack.org Subject: Re: [cinder] changing the weekly meeting time
Hi Brian,
It's great that the change in weekly meeting time is considered, here are my opinions on the same from the perspective of Asian countries (having active upstream developers)
Current meeting time (16:00 - 17:00 UTC)
INDIA : is 9:30 - 10:30 PM IST (UTC+05:30) is a little late but manageable.
CHINA : is 12:00 - 01:00 AM CST (UTC+08:00) is almost impossible to attend.
JAPAN : is 01:00 - 02:00 AM JST (UTC+09:00) similar to the case as China.
IMO shifting the meeting time 2 hours earlier (UTC 14:00) might bring more participation and would ease out timings for some (including me) but these are just my thoughts.
Thanks and Regards Rajat Dhasmana
On Thu, Oct 24, 2019 at 3:05 AM Brian Rosmaita <rosmaita.fossdev@gmail.commailto:rosmaita.fossdev@gmail.com> wrote: (Just to be completely clear -- we're only gathering information at this point. The Cinder weekly meeting is still Wednesdays at 16:00 UTC.)
As we discussed at today's meeting [0], a request has been made to hold the weekly meeting earlier so that it would be friendlier for people in Asia time zones.
Based on the people in attendance today, it seems that a move to 14:00 UTC is not out of the question.
Thus, the point of this email is to solicit comments on whether we should change the meeting time to 14:00 UTC. As you consider the impact on yourself, if you are in a TZ that observes Daylight Savings Time, keep in mind that most TZs go back to standard time over the next few weeks.
(I was going to insert an opinion here, but I will wait and respond in this thread like everyone else.)
cheers, brian
[0] http://eavesdrop.openstack.org/meetings/cinder/2019/cinder.2019-10-23-16.00....
On 10/30/19 10:45 PM, Fang, Liang A wrote:
Hi Brian,
I agree with Rajat. Meeting happened in mid-night will prevent people to attend, except they have topics that must to talk with team.
Openstack is widely used in Asia, but there’s no much core from Asia (in countries that the meeting in mid-night). Meeting time is one of the reason😊
I agree, the current meeting time is not Asia-friendly. If we move the meeting 2 hours earlier (14:00 UTC), that's 6:00 a.m. on USA Pacific Coast, which is on the verge of not being Silicon Valley-friendly. So it would be good to hear from our Silicon Valley time zone contributors (we have at least 3 who attend fairly regularly).
Nova have two meetings, two time zone friendly. But I don’t like to divide the meeting to two.
I agree, I'd prefer not to do this unless there's no other way to work out a suitable time. Here's a chart that shows you what we're up against:
https://www.timeanddate.com/worldclock/meetingtime.html?iso=20191120&p1=...
We discussed this issue briefly at this week's Cinder meeting, and since we're hoping to pick up some new contributors at the Summit/PTG next week, we agreed to take a poll after the PTG so that new contributors can represent their respective time zones.
In the meantime, it would be good to keep this ML discussion going -- maybe someone will have a creative idea for a solution that won't adversely impact any contributors!
Regards
Liang
*From:* Rajat Dhasmana rajatdhasmana@gmail.com *Sent:* Thursday, October 31, 2019 12:54 AM *To:* Brian Rosmaita rosmaita.fossdev@gmail.com *Cc:* openstack-discuss@lists.openstack.org *Subject:* Re: [cinder] changing the weekly meeting time
Hi Brian,
It's great that the change in weekly meeting time is considered, here are my opinions on the same from the perspective of Asian countries (having active upstream developers)
Current meeting time (16:00 - 17:00 UTC)
INDIA : is 9:30 - 10:30 PM IST (UTC+05:30) is a little late but manageable.
CHINA : is 12:00 - 01:00 AM CST (UTC+08:00) is almost impossible to attend.
JAPAN : is 01:00 - 02:00 AM JST (UTC+09:00) similar to the case as China.
IMO shifting the meeting time 2 hours earlier (UTC 14:00) might bring more participation and would ease out timings for some (including me) but these are just my thoughts.
Thanks and Regards
Rajat Dhasmana
On Thu, Oct 24, 2019 at 3:05 AM Brian Rosmaita <rosmaita.fossdev@gmail.com mailto:rosmaita.fossdev@gmail.com> wrote:
(Just to be completely clear -- we're only gathering information at this point. The Cinder weekly meeting is still Wednesdays at 16:00 UTC.) As we discussed at today's meeting [0], a request has been made to hold the weekly meeting earlier so that it would be friendlier for people in Asia time zones. Based on the people in attendance today, it seems that a move to 14:00 UTC is not out of the question. Thus, the point of this email is to solicit comments on whether we should change the meeting time to 14:00 UTC. As you consider the impact on yourself, if you are in a TZ that observes Daylight Savings Time, keep in mind that most TZs go back to standard time over the next few weeks. (I was going to insert an opinion here, but I will wait and respond in this thread like everyone else.) cheers, brian [0] http://eavesdrop.openstack.org/meetings/cinder/2019/cinder.2019-10-23-16.00.log.html#l-166
participants (3)
-
Brian Rosmaita
-
Fang, Liang A
-
Rajat Dhasmana