Skip to content
This repository has been archived by the owner on Feb 29, 2020. It is now read-only.

Restart Intl meetings - Jan 16 2017 #33

Closed
srl295 opened this issue May 3, 2016 · 15 comments
Closed

Restart Intl meetings - Jan 16 2017 #33

srl295 opened this issue May 3, 2016 · 15 comments

Comments

@srl295
Copy link
Member

srl295 commented May 3, 2016

Monday Jan 16th https://time.is/915am_16_Jan_2017_in_PT?Node.js_Intl_WG

Plan is for the meetings to be monthly.

@martinheidegger
Copy link

Which poll?

@srl295
Copy link
Member Author

srl295 commented May 3, 2016

@martinheidegger that would help, wouldn't it. Updated, above.

@srl295
Copy link
Member Author

srl295 commented May 15, 2016

OK- think we have a time. http://time.is/900_19_May_2016_in_PT

@srl295
Copy link
Member Author

srl295 commented May 15, 2016

@martinheidegger
Copy link

martinheidegger commented May 20, 2016

Note: I again missed the day because the timestamp was at 1:00 in the night and it showed Friday in the google calendar. (Now it`s friday at 1 o'clock at night and I just realized that this means I only missed the meeting by 24hours ...) I wonder if this is a hint that I am really bad at internationalisation and should give up my efforts?

screenshot 2016-05-21 00 31 48

@srl295
Copy link
Member Author

srl295 commented May 20, 2016

@martinheidegger sorry to have missed you ! Does this link work- http://time.is/900_19_May_2016_in_PT should show a time 24 hours ago

@martinheidegger
Copy link

martinheidegger commented May 20, 2016

@srl295 My intelligence just didn't pick apart that Friday 1:00 means "In the night between thursday and friday". That is the usual meaning but in TV time: 0:00~6:00 are usually attributed to the previous day... again: my bad. But I do find my incompetency amusing.

@srl295
Copy link
Member Author

srl295 commented May 20, 2016

@martinheidegger don't take it too bad — Call it an i18n occupational hazard. I orchestrated another multi-continent multi-timezone meeting … and then mis-TYPED (<-- there's the problem) the invitees email addresses.

@srl295
Copy link
Member Author

srl295 commented Oct 31, 2016

Let's re-restart in early December or January?

@srl295
Copy link
Member Author

srl295 commented Oct 31, 2016

OK, please fill this out with times that work for you - http://doodle.com/poll/p6exrs3qzeakq2kf

9:00 AM PT is what worked before, which means it would need to be Monday for me. Probably a monthly meeting would be the cadence for now. I also added 1 hour on either side just in case that works better. If we don't get good dates, please indicates so, and we can re evaluate. Thanks!

@srl295
Copy link
Member Author

srl295 commented Dec 15, 2016

9:00 AM (PT) on the 9th? https://time.is/0900_9_Jan_2017_in_PT?Intl_WG

@srl295
Copy link
Member Author

srl295 commented Jan 13, 2017

Sorry I have had some illness over the new year.

Let's try again this Monday - https://time.is/915am_16_Jan_2017_in_PT?Node.js_Intl_WG
We can refine the time in the future, but I'd like to get this going again.

@srl295 srl295 changed the title Restart Intl meetings Restart Intl meetings - Jan 16 2017 Jan 13, 2017
@srl295
Copy link
Member Author

srl295 commented Jan 16, 2017

Thanks @watilde for joining. You can see the meeting minutes https://goo.gl/0LNd1n for some of the issues we talked through.

Let's do it again… maybe next month?

@martinheidegger
Copy link

Oh man, I really need to set an alert for those meetings 🤦‍♂️

@srl295
Copy link
Member Author

srl295 commented Jan 18, 2017

@martinheidegger Next time.

For now: mission accomplished 💯

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

No branches or pull requests

2 participants