UTC Thu 25-Jan-2018 17:00 (05:00 PM):
| Timezone | Date/Time |
|---------------|-----------------------|
| US / Pacific | Thu 25-Jan-2018 09:00 (09:00 AM) |
| US / Mountain | Thu 25-Jan-2018 10:00 (10:00 AM) |
| US / Central | Thu 25-Jan-2018 11:00 (11:00 AM) |
| US / Eastern | Thu 25-Jan-2018 12:00 (12:00 PM) |
| Amsterdam | Thu 25-Jan-2018 18:00 (06:00 PM) |
| Moscow | Thu 25-Jan-2018 20:00 (08:00 PM) |
| Chennai | Thu 25-Jan-2018 22:30 (10:30 PM) |
| Hangzhou | Fri 26-Jan-2018 01:00 (01:00 AM) |
| Tokyo | Fri 26-Jan-2018 02:00 (02:00 AM) |
| Sydney | Fri 26-Jan-2018 04:00 (04:00 AM) |
In your local time:
Extracted from cc-agenda labelled issues and pull requests from the nodejs org prior to the meeting.
Note: I trimmed several observers from this list who have not attended much/at all since they were initially added as observers. If you are one of the observers who was trimmed, please reach out if you'd still like to participate as an observer.
The agenda comes from issues labelled with cc-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.
Zoom Meeting; a link will be posted here shortly before the meeting starts.
A standing invitation exists for all @nodejs/TSC members who are not also CommComm members to attend in observer capacity.
We stream our conference call straight to YouTube so anyone can listen to it live, it should start playing at https://www.youtube.com/channel/UCQPYJluYC_sn_Qz_XE-YbTQ/live when we turn it on. There's usually a short cat-herding time at the start of the meeting and then occasionally we have some quick private business to attend to before we can start recording & streaming. So be patient and it should show up.
Added "Current Strategic Initiatives Review #222" to the agenda.
If I may suggest, the issue I opened yesterday (#224 ) may be relevant for today, since the topic seem quite in line with #117 and #143
If not, that's not a problem at all and we can keep it via text only!
@Tiriel Unfortunately both @bnb and me are concerned that adding #224 to the agenda might end up misrepresenting the issue at hand here, since we don't have a lot of time to explain and it's a very context-sensitive issue. The best option would be to hold an entirely separate meeting over this.
That does make perfect sense, this issue is indeed of importance and may end up taking too much time.
Thanks! I'll keep it warm for another meeting then :smile:
EDIT: Oh and by the way, will be here !
Join link for members and observers: https://zoom.us/j/209550902
@bnb unfortunately I won't participate on this meeting. Currently I've been only able to listen to the meetings via the YouTube link.
@DiegoZoracKy no worries - thanks for letting us know ๐
just noticed I'm somehow not in the invited list of CommComm members.... ๐ข
Added you to the notes for today at least @pup. ๐
Oh no, @pup! Apologies! I did a ton of wrangling with the list to add the new members, I may have messed yours up by mistake ๐
Edit: Added you ๐ฌ
Most helpful comment
Join link for members and observers: https://zoom.us/j/209550902