Moving community meeting to 16:00 UTC
Hi all, Melissa brought up that we should reschedule the bi-weekly community meeting to the same time slot at the triage meeting: Wednesdays 16:00 UTC (9 am Pacific time) [1] This will simplify attending for those in Europe and allow a more reasonable time including for India. As of now, all regular attendees are happy with this move. But the original idea was that we could also alternate between two times, the current time is e.g. impossible to make from east Asia. Please let me/us know if you prefer a different schedule now (or later!). The idea is that these meetings are accessible to anyone interested. Without any comments, I will announce and change the calendar starting with next weeks meeting. Cheers, Sebastian [1] I have to see whether we will stick with UTC or do any daylight savings.
On Wed, Sep 22, 2021 at 8:31 PM Sebastian Berg
Hi all,
Melissa brought up that we should reschedule the bi-weekly community meeting to the same time slot at the triage meeting:
Wednesdays 16:00 UTC (9 am Pacific time) [1]
This will simplify attending for those in Europe and allow a more reasonable time including for India.
As of now, all regular attendees are happy with this move.
I have a structural conflict at that time, I'd only be able to make the second half of the meeting. Perhaps we could make it 16:30 UTC (= 10pm in India), or otherwise 15:00 or 16:00 UTC on Tuesdays? But the original idea was that we could also alternate between two times,
the current time is e.g. impossible to make from east Asia.
Yes, the current time is very late and was only chosen to make it 6am in Australia (which is no longer needed) - we should move it forward even if we end up alternating between two times. Cheers, Ralf
Please let me/us know if you prefer a different schedule now (or later!). The idea is that these meetings are accessible to anyone interested. Without any comments, I will announce and change the calendar starting with next weeks meeting.
Cheers,
Sebastian
[1] I have to see whether we will stick with UTC or do any daylight savings. _______________________________________________ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-leave@python.org https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ Member address: ralf.gommers@googlemail.com
On Wed, 2021-09-22 at 21:11 +0200, Ralf Gommers wrote:
On Wed, Sep 22, 2021 at 8:31 PM Sebastian Berg < sebastian@sipsolutions.net> wrote:
Hi all,
Melissa brought up that we should reschedule the bi-weekly community meeting to the same time slot at the triage meeting:
Wednesdays 16:00 UTC (9 am Pacific time) [1]
This will simplify attending for those in Europe and allow a more reasonable time including for India.
As of now, all regular attendees are happy with this move.
I have a structural conflict at that time, I'd only be able to make the second half of the meeting.
Perhaps we could make it 16:30 UTC (= 10pm in India), or otherwise 15:00 or 16:00 UTC on Tuesdays?
Sorry about that, lets go with 16:30 UTC then, at least for now. I will announce that later for tomorrow. If that ends up bad for anyone (or the situation just changes) we can still move it. Cheers, Sebastian
But the original idea was that we could also alternate between two times,
the current time is e.g. impossible to make from east Asia.
Yes, the current time is very late and was only chosen to make it 6am in Australia (which is no longer needed) - we should move it forward even if we end up alternating between two times.
Cheers, Ralf
Please let me/us know if you prefer a different schedule now (or later!). The idea is that these meetings are accessible to anyone interested. Without any comments, I will announce and change the calendar starting with next weeks meeting.
Cheers,
Sebastian
[1] I have to see whether we will stick with UTC or do any daylight savings. _______________________________________________ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-leave@python.org https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ Member address: ralf.gommers@googlemail.com
_______________________________________________ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-leave@python.org https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ Member address: sebastian@sipsolutions.net
On Tue, Sep 28, 2021 at 7:20 PM Sebastian Berg
On Wed, 2021-09-22 at 21:11 +0200, Ralf Gommers wrote:
On Wed, Sep 22, 2021 at 8:31 PM Sebastian Berg < sebastian@sipsolutions.net> wrote:
Hi all,
Melissa brought up that we should reschedule the bi-weekly community meeting to the same time slot at the triage meeting:
Wednesdays 16:00 UTC (9 am Pacific time) [1]
This will simplify attending for those in Europe and allow a more reasonable time including for India.
As of now, all regular attendees are happy with this move.
I have a structural conflict at that time, I'd only be able to make the second half of the meeting.
Perhaps we could make it 16:30 UTC (= 10pm in India), or otherwise 15:00 or 16:00 UTC on Tuesdays?
Sorry about that, lets go with 16:30 UTC then, at least for now. I will announce that later for tomorrow. If that ends up bad for anyone (or the situation just changes) we can still move it.
Thanks! Ralf
Cheers,
Sebastian
But the original idea was that we could also alternate between two times,
the current time is e.g. impossible to make from east Asia.
Yes, the current time is very late and was only chosen to make it 6am in Australia (which is no longer needed) - we should move it forward even if we end up alternating between two times.
Cheers, Ralf
Please let me/us know if you prefer a different schedule now (or later!). The idea is that these meetings are accessible to anyone interested. Without any comments, I will announce and change the calendar starting with next weeks meeting.
Cheers,
Sebastian
[1] I have to see whether we will stick with UTC or do any daylight savings. _______________________________________________ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-leave@python.org https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ Member address: ralf.gommers@googlemail.com
_______________________________________________ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-leave@python.org https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ Member address: sebastian@sipsolutions.net
_______________________________________________ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-leave@python.org https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ Member address: ralf.gommers@gmail.com
On Tue, Sep 28, 2021 at 7:20 PM Sebastian Berg
Sorry about that, lets go with 16:30 UTC then, at least for now. I will announce that later for tomorrow. If that ends up bad for anyone (or the situation just changes) we can still move it.
Could someone modify the community calendar appropriately? Thanks, Matti
participants (5)
-
Darrell Grimm -
Hailey Brown -
Matti Picus -
Ralf Gommers -
Sebastian Berg