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 times #146

Closed
badboy opened this issue Mar 13, 2017 · 8 comments
Closed

Meeting times #146

badboy opened this issue Mar 13, 2017 · 8 comments

Comments

@badboy
Copy link
Member

badboy commented Mar 13, 2017

Current time: 5pm UTC

https://www.worldtimebuddy.com/?qm=1&lid=2656046,2179537,5128581,5391959&h=2656046&date=2017-3-13&sln=17-18

US already jumped ahead with their clock, Europe and other parts will follow soon.

We might need to re-evaluate the time of the meeting

@erickt
Copy link
Contributor

erickt commented Mar 15, 2017

Good idea. I'm fine shifting to 4pm UTC if that works for everyone until this daylight savings time mess resolves itself.

@edunham
Copy link
Member

edunham commented Mar 15, 2017

I made a thing (https://github.com/rust-community/team/wiki/Meeting-Availability) and emailed the list about it to try to solve the general case of this problem.

@skade
Copy link
Contributor

skade commented Jul 29, 2017

@rust-community/community-team Is this still a topic of debate?

Otherwise, I'll close.

@ashleygwilliams
Copy link
Member

this appears to be stale but i'll bring it up in the next meeting to see if we need to do anything

@Manishearth
Copy link
Contributor

I'm going to be in GMT+5:30 till February. Current times kind of work for the first meeting.

@ashleygwilliams
Copy link
Member

@Manishearth is there a better time for you? attendance at the second meeting is much lower so its possible that we could move it

@Manishearth
Copy link
Contributor

So I'll mention this at the outset that as far as meeting scheduling is concerned, there's going to be at least one band of timezones that gets the short straw. India usually ends up here, being almost 12 hours off from PST. So I'm largely used to this and can probably make it still work by pre/post/async communicating provided we have agendas set (which we do!). So we shouldn't have to worry about this much.

That said, if the late meeting was four hours later that would work for me. It would suck for EST though :)

The morning (morning PST) meeting is attendable for me so I don't think we need to change anything here.

@ashleygwilliams
Copy link
Member

👍 i'm going to close this for the moment then. thanks for the thoughtful response @Manishearth

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

6 participants