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

Node.js Foundation Technical Steering Committee (TSC) Meeting 2017-08-17 #306

Closed
jasnell opened this issue Aug 10, 2017 · 11 comments
Closed

Comments

@jasnell
Copy link
Member

jasnell commented Aug 10, 2017

Sorry for this being late all...

Time

UTC Thu 17-Aug-2017 20:00 (08:00 PM):

Timezone Date/Time
US / Pacific Thu 17-Aug-2017 13:00 (01:00 PM)
US / Mountain Thu 17-Aug-2017 14:00 (02:00 PM)
US / Central Thu 17-Aug-2017 15:00 (03:00 PM)
US / Eastern Thu 17-Aug-2017 16:00 (04:00 PM)
Amsterdam Thu 17-Aug-2017 22:00 (10:00 PM)
Moscow Thu 17-Aug-2017 23:00 (11:00 PM)
Chennai Fri 18-Aug-2017 01:30 (01:30 AM)
Hangzhou Fri 18-Aug-2017 04:00 (04:00 AM)
Tokyo Fri 18-Aug-2017 05:00 (05:00 AM)
Sydney Fri 18-Aug-2017 06:00 (06:00 AM)

Or in your local time:

Links

Agenda

Extracted from tsc-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/TSC

  • 2FA for the entire org #301
  • Candidate "areas" for TSC and Community Committee #278
  • Copyright Date #195
  • Regular roll-up reporting for active working groups #109

Invited

Notes

The agenda comes from issues labelled with tsc-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.

For review

Not on agenda but labeled tsc-review for awareness:

  • Approval to move node-heapdump into foundation #257
  • Define Travel Fund approval requirements #254
  • Add quorum rules #253
  • Request: Asset audit report #249
  • create public nodejs/collaborators repo #243
  • Rotating meeting times #198

Joining the meeting

Uberconference as usual.

@nebrius
Copy link
Contributor

nebrius commented Aug 10, 2017

I'm afraid I'm going to have to miss this one, I'm going on stage at SeattleJS part way through this meeting.

@jasnell
Copy link
Member Author

jasnell commented Aug 10, 2017

We are rescheduling this to next week due to lack of quorum (only myself, @addaleax, @MylesBorins, @cjihrig and @rvagg were on)

@jasnell jasnell changed the title Node.js Foundation Technical Steering Committee (TSC) Meeting 2017-08-10 Node.js Foundation Technical Steering Committee (TSC) Meeting 2017-08-17 Aug 10, 2017
@mhdawson
Copy link
Member

It will conflict with the ComCom meeting at the same time on the 17th which starts at 4:30. But we could try to fit it into the first 1/2 hour.

@nebrius
Copy link
Contributor

nebrius commented Aug 16, 2017

As it turns out, we may not have a CommComm meeting that day because there's nothing on the agenda (yet?). Watch nodejs/community-committee#108 for further updates.

@mhdawson
Copy link
Member

Updated agenda to reflect currently tagged issues.

@nebrius
Copy link
Contributor

nebrius commented Aug 17, 2017

FYI we have decided to officially skip this week's CommComm meeting, so there's no longer a conflict.

@nebrius
Copy link
Contributor

nebrius commented Aug 17, 2017

Also a heads up, I'm at another event that's running late, so I may be 10-15 minutes late to this meeting.

@mhdawson
Copy link
Member

OK, we waited until 10 after and there was only three of us, the issues on the agenda were not time critical so we decided to cancel.

We'll plan to meet at the next regularly scheduled date/time at Thursday Sep 9 at 4 EST.

@rvagg
Copy link
Member

rvagg commented Aug 17, 2017

Doh! Sorry folks, I'm too calendar driven and booked up this slot without realising it since it's off-cycle and doesn't have an entry. I also misinterpreted this thread when I read it so got it wrong. Apologies for this one but I won't be able to make it.

@rvagg
Copy link
Member

rvagg commented Aug 17, 2017

Actually that's not quite right now that I'm more awake and see a calendar entry has shown and actually read the text of this thread! It's an hour earlier than I thought (6am). I didn't book anything up (that's for 7am), I was asleep and didn't set an alarm for this because it wasn't on my radar. Sorry!

@mhdawson
Copy link
Member

closing

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

5 participants