-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Meeting times post US DST changes Nov 2020 #442
Comments
The time in the calendar is ok for me, being on the half hour is a bit awkward as it's more likely to conflict with meetings in both hours that it spans. |
|
So shift off the half-hour mark, and earlier? Do we want to do half an hour earlier? Or a full hour and a half earlier? I can definitely do half an hour earlier. An hour and a half...well...I'll make it work, but I suck at mornings. 😆 |
As mentioned already in similar queries evening slots in CET are hard for me. But I will monitor as I did it in the past. |
Half hour earlier works for me but 1 and 1/2 hours would conflict often with other meetings I have. |
Half an hour earlier works for me too (it's the earliest I can go for a meeting) |
Do we have enough of a distribution of people that we should start alternating? Would we have more people if, for example, we timed it 12 hours later? |
I think we have 6 active members who have shown interest in joining meeting, on either slot we can get up to 4 members attending I think (that's mostly my guess, might be less for one of the slots). |
For me is a bad time (too late) |
12 hours later would be out for me (middle of the night). |
Maybe we should gather timezones to figure out what if any overlap there is. |
I'm on UTC+8. After the daylight saving time change the meeting time will be 1:30AM. I can manage to attend if the meeting is before 1AM (not a good rest time though 😅). |
I'm on PST (UTC-8) @nodejs/diagnostics if you would like to join the meetings moving forward, please share your timezone here :) |
I'm in EST (UTC -5) |
I'm in CET (UTC+1) |
UTC-8 also. |
I'm in UTC-3. |
Ok, so this is the current time for everyone based on comments from this thread: We can move it back half an hour, which would look like this: Or one hour: Or one hour and a half: I'm fine with all options, I would just ask someone else to host for the last two (moving back one hour or one hour and a half).I checked and 8am PST on Wednesdays doesn't conflict with other Node.js or OpenJSF meetings Let's use reactions on this issue to vote for a new time @nodejs/diagnostics! 👀 move back half an hour |
I can do that, if we end up picking up one of those |
I'd like to add 😄 to the votes for "all are fine with me" |
So the current results are:
I think I should've been more clear on the instructions: please vote on all times you can join the meeting, not your preference, otherwise it will be hand to find a time that works for most people. I'll give a couple more days in case folks want to update their votes. |
Results are: Move back half an hour: 1 votes With that, moving back one hour and a half is the winner. @mhdawson can you update the calendar (or point me to where I can update it)? |
Is it ok if we also shift 1 week? I have a conflict every week at the new time on the current weeks, but if it was shifted 1 week I'd be able to make it. So moved back 1 1/2 hours and shifted a week ok? If so I'd make the next one Feb 10 at 11 ET and then it would be every 2 weeks after that? |
sounds good to me |
SGTM |
I'm fine with shifting a week. 👍 |
Calendar updated, closing. |
It's that time of the year again. Please answer the following questions, so we can decide if a time change is necessary as well as how to proceed:
@nodejs/diagnostics please answer so we can create a Doodle to find a new time if necessary.
The text was updated successfully, but these errors were encountered: