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 2018-10-17 #612

Closed
mhdawson opened this issue Oct 15, 2018 · 14 comments
Closed
Assignees

Comments

@mhdawson
Copy link
Member

Time

UTC Wed 17-Oct-2018 21:00 (09:00 PM):

Timezone Date/Time
US / Pacific Wed 17-Oct-2018 14:00 (02:00 PM)
US / Mountain Wed 17-Oct-2018 15:00 (03:00 PM)
US / Central Wed 17-Oct-2018 16:00 (04:00 PM)
US / Eastern Wed 17-Oct-2018 17:00 (05:00 PM)
London Wed 17-Oct-2018 22:00 (10:00 PM)
Amsterdam Wed 17-Oct-2018 23:00 (11:00 PM)
Moscow Thu 18-Oct-2018 00:00 (12:00 AM)
Chennai Thu 18-Oct-2018 02:30 (02:30 AM)
Hangzhou Thu 18-Oct-2018 05:00 (05:00 AM)
Tokyo Thu 18-Oct-2018 06:00 (06:00 AM)
Sydney Thu 18-Oct-2018 08:00 (08: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/node

  • doc: formalize non-const reference usage in C++ style guide #23155

nodejs/TSC

  • Tracking issue for updating TSC on Board Meetings #476
  • Strategic Initiatives - Tracking Issue #423

Invited

Observers/Guests

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.

Joining the meeting

Zoom link: https://zoom.us/j/611357642
Regular password

Public participation

We stream our conference call straight to YouTube so anyone can listen to it live, it should start playing at https://www.youtube.com/c/nodejs+foundation/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.

Many of us will be on IRC in #node-dev on Freenode if you'd like to interact, we have a Q/A session scheduled at the end of the meeting if you'd like us to discuss anything in particular. @nodejs/collaborators in particular if there's anything you need from the TSC that's not worth putting on as a separate agenda item, this is a good place for that

@mhdawson mhdawson self-assigned this Oct 15, 2018
@mcollina
Copy link
Member

Unfortunately I will not be able to partecipate.

@Trott
Copy link
Member

Trott commented Oct 15, 2018

Unfortunately I will not be able to partecipate.

@mcollina and everyone else: If you can't make it, please use a thumbs-down response on the original post. 👍 for you will attend, 👎 for you won't attend, and 😕 if you're not sure if you can make it or not. Thanks!

@Trott
Copy link
Member

Trott commented Oct 15, 2018

^^^^ We should probably put that in the meeting issue template so it's not folk knowledge that has to be passed on in comments. 😄

@mhdawson
Copy link
Member Author

@Trott agreed, PR's welcome otherwise I'll try to get to it sometime.

@Trott
Copy link
Member

Trott commented Oct 15, 2018

@Trott agreed, PR's welcome otherwise I'll try to get to it sometime.

For anyone feeling more ambitious right now than either @mhdawson or me: https://github.com/nodejs/create-node-meeting-artifacts is the repo....

@thefourtheye
Copy link
Contributor

Can nodejs/node#23433 be discussed? The expected behaviour is different among people. This has been discussed multiple times in the past but we didn't settle it for good.

@Trott
Copy link
Member

Trott commented Oct 16, 2018

If @addaleax can make this meeting time, then we should invite @refack for nodejs/node#23155 per nodejs/node#23155 (comment).

@mhdawson
Copy link
Member Author

@addaleax if you let me know that you can make it I'll send @refack the info needed to connect.

@addaleax
Copy link
Member

@mhdawson Yes, I should be able to make it.

@fhinkel
Copy link
Member

fhinkel commented Oct 17, 2018

Sorry I can't make it today because I'm traveling for NodeConf Argentina.

@jasnell
Copy link
Member

jasnell commented Oct 17, 2018

Unable to make it due to last minute scheduling conflict.

@mhdawson
Copy link
Member Author

PR for minutes: #613

@thefourtheye
Copy link
Contributor

Sorry, I was not able to join today. Let me bring up nodejs/node#23433 in the next week's call.

@thefourtheye
Copy link
Contributor

Moderation team report: In the past two weeks

  1. There were two spam comments deleted (Issues https://github.com/nodejs/moderation/issues/234 and https://github.com/nodejs/moderation/issues/235)
  2. We officially onboarded @gdams and @dshaw 🎉

@nodejs/tsc @nodejs/community-committee @nodejs/moderation

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

No branches or pull requests

7 participants