Skip to content
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 timeslot #235

Closed
mhdawson opened this issue Sep 19, 2018 · 17 comments
Closed

Meeting timeslot #235

mhdawson opened this issue Sep 19, 2018 · 17 comments

Comments

@mhdawson
Copy link
Member

Review the timeslot for the diagnostic WG meeting.

Possibly have 2 timeslots.

I know the current one is a challenge for @gireeshpunathil. @gireeshpunathil can you comment with whether earlier or later would work better for you?

@mmarchini
Copy link
Contributor

A different time would work better for me as well. Either earlier or later works fine for me.

@Flarna
Copy link
Member

Flarna commented Sep 19, 2018

For me the current timeslot is also mostly impossible. it would be needed to move it for at least two hours earlier or later but I fear that this is a problem for others more involved then me.

@gireeshpunathil
Copy link
Member

thanks @mhdawson for the consideration. I have been trying my best efforts to attend this but could not (11.30 PM for me: either stay awake until this meeting, or sleep and get up at 11.30, neither of which worked).

Couple of hours earlier would be a great convenience for me. If that breaks others, even one hour would be good.

@mhdawson
Copy link
Member Author

2 hours earlier has the potential to overlap with the TSC weekly meeting, but that rotates so it would only be 1 week out of 3 that we would have to avoid. Would 12 EDT/9Pacific work for people?

@ofrobots
Copy link
Contributor

Convenience link to see 0900 PDT in local time: http://www.wolframalpha.com/input/?i=9AM+PDT+in+local+time.

It would be occasionally tricky for me to make this time as I have some childcare duties in the morning, but I am willing to give this a shot. 0930 PDT would work reliably for me.

@watson
Copy link
Member

watson commented Sep 23, 2018

I'm in CEST (currently that's UTC+2, but will soon be UTC+1 when we switch back for the winter) and I'm pretty flexible with the meeting time. Basically I can start a meeting any time between 8am and 10pm my local time.

@BridgeAR
Copy link
Member

I am also in CEST and for me it would be best to move the meeting a bit earlier. 0900 and 0930 PDT would therefore be pretty good.

@mhdawson
Copy link
Member Author

mhdawson commented Oct 17, 2018

or maybe

8a, 12p and 5p EDT
5a, 9a and 2p PDT
1p, 5p, 10p (England)

@mhdawson
Copy link
Member Author

on a cycle 1 off from the TSC meetings

@hashseed
Copy link
Member

I'm pretty flexible regarding which weekday to choose, but the current time slot is the best I can offer from my evening. I'd like to spend time with my kids until they go to bed, and have about 2 hours until I head to bed as well.

@suresh-srinivas
Copy link

or maybe

8, 12 and 5 EDT
5, 9 and 2 PDT

5am, 9am, and 2pm PDT?

1p, 5p, 10p

@mhdawson
Copy link
Member Author

@suresh-srinivas correct.

@mhdawson
Copy link
Member Author

@gireeshpunathil can you review the feedback so far and then make a proposal that reflects other meetings in the calendar?

@gireeshpunathil
Copy link
Member

@mhdawson - 9.30 AM PDT looks a perfect slot for everyone, looking at the above comments. I didn't follow the make a proposal that reflects other meetings in the calendar part properly - did you mean to ask me to raise a PR to that effect? I don't see a file that stores the calendar info. Or do you mean to ask me to make a proposal that adjusts other meetings based on this change proposal? if so what are the other meetings? please let me know.

@mcollina
Copy link
Member

mcollina commented Nov 5, 2018

+1

@mhdawson
Copy link
Member Author

Since its only a few days until the next meeting I'll leave this weeks meeting as is and I'll update the time for the meeting afterwards (Nov 28 and later)

@mike-kaufman
Copy link
Contributor

closing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests