-
Notifications
You must be signed in to change notification settings - Fork 96
Node Foundation TSC Meeting 2015-06-03 #47
Comments
/cc @nodejs/collaborators: I've just realised that some of you may not be watching this repo yet and may not be aware that we've moved these over here now |
On the joyent/node side there are no significant issues that I'm aware of that need to be discussed. One general topic with considering is if we need some set of best practices for determining whether and when to backport commits from io.js into either v0.10 or v0.12. But that's something we can discuss in github. On a personal note, I'm on vacation for two weeks starting this Friday so will not be attending the next two TSC meetings after today. |
Sorry for the late note, but it may be useful to review were we are on the bar mitzva fix for 0.12.X and 0.10.X |
@rvagg how do I find this meeting on soundcloud? |
@sam-github The soundcloud account is here, but the 6/3 meeting is not up there yet. |
Time
UTC Wed 03-Jun-15 20:00:
Or in your local time:
Links
Attendees will be given a conference number to dial in to.
Agenda
Extracted from tsc-agenda labelled issues and pull requests prior to meeting.
nodejs/node
nodejs/io.js
deepEqual
anddeepStrictEqual
inutil
. #1172 #1177joyent/node
Invited
Notes
The agenda now comes from issues labelled with
tsc-agenda
in all 3 repositories listed above. Please label any additional issues that should be on the agenda before the meeting starts. I'm using a tool to fetch the list so it's not a big deal to collate.This meeting will be held via Uberconference. I won't be attempting to live-stream to YouTube this time, it was too difficult last time because I had to have my microphone on. I am continuing to explore other options for broadcasing live; I don't want to completely lose that! So, there won't be a live QA on #io.js this time, very sorry, but please comment here if you have something to query.
The recording will go up on Soundcloud straight afterwards.
The text was updated successfully, but these errors were encountered: