-
Notifications
You must be signed in to change notification settings - Fork 19
Meeting #2 #9
Comments
Actually, let's make it February 5 instead of January 29. This way, we have plenty of time to Doodle poll another time if it doesn't work for people. How's February 5? (I'll edit the previous comment with that info.) |
Works for me
|
The proposed time works for me |
I'll be on vacation on the 5th. Don't let that stop anything. |
Ok for me too |
It works for me too |
Here's the Hangout link for when the time comes. https://plus.google.com/hangouts/_/hoaevent/AP36tYfglMbvBYj7QiiI8rG_a4xAgRhemvuKSExpp6-mxPK9-qPcLw?hl=en&authuser=0 |
Please tag existing or new issues with Agenda items so far: |
Hello all. Sorry for the late notice, but an unavoidable personal matter has come up and I won't be able to make it :(. I'll try to comment on the issues though. |
Google Doc for minutes: https://docs.google.com/document/d/1U1wMVYLLO2HGmmZrobxhbQazpPRRfA0prvT7O-MzJ28/edit Send me your Google user name (here or in IRC or email or whatever), and I'll enabled editing for you so we can all try to keep things up to date during the meeting. (Mostly, it's useful so you can fill in your own stuff for the standup part.) |
@nodejs/testing Should we keep the meeting at the same time/day as before, or should I launch a Doodle poll to pick another time?
If we keep it at the same time, we're looking at:
UTC: Friday, February 5, 2016 at 6:00:00 PM
Pacific Time (San Francisco): Friday, February 5, 2016 at 10:00:00 AM
Eastern Time (Pittsburgh): Friday, February 5, 2016 at 1:00:00 PM
Central European Time (Madrid): Friday, February 5, 2016 at 7:00:00 PM
Western European Time (Lisbon): Friday, February 5, 2016 at 6:00:00 PM
I'll open issues for agenda items that I have, and everyone else should of course feel free to do the same...
The text was updated successfully, but these errors were encountered: