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.

Sign up for GitHub

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

Jump to bottom

Node.js Foundation Technical Steering Committee (TSC) Meeting 2018-03-07 #500

Closed
mhdawson opened this issue Mar 5, 2018 · 18 comments
Closed

Node.js Foundation Technical Steering Committee (TSC) Meeting 2018-03-07 #500

mhdawson opened this issue Mar 5, 2018 · 18 comments
Assignees
@mhdawson
Labels
tsc-meeting

Comments

@mhdawson
Copy link
Member

mhdawson commented Mar 5, 2018 •
edited by fhinkel
Loading

Time

UTC Wed 07-Mar-2018 12:00 (12:00 PM):

Timezone Date/Time
US / Pacific Wed 07-Mar-2018 04:00 (04:00 AM)
US / Mountain Wed 07-Mar-2018 05:00 (05:00 AM)
US / Central Wed 07-Mar-2018 06:00 (06:00 AM)
US / Eastern Wed 07-Mar-2018 07:00 (07:00 AM)
London Wed 07-Mar-2018 12:00 (12:00 PM)
Amsterdam Wed 07-Mar-2018 13:00 (01:00 PM)
Moscow Wed 07-Mar-2018 15:00 (03:00 PM)
Chennai Wed 07-Mar-2018 17:30 (05:30 PM)
Hangzhou Wed 07-Mar-2018 20:00 (08:00 PM)
Tokyo Wed 07-Mar-2018 21:00 (09:00 PM)
Sydney Wed 07-Mar-2018 23:00 (11:00 PM)

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

  • Nominating Thomas Watson (@watson) as a Collaborator #18943
  • Nominate MoonBall as a collaborator #18793
  • buffer: runtime-deprecate Buffer ctor by default #15346
  • Distrust Symantec root certs in 10.0/11.0 #14537
  • Tracking Issue for Runtime Deprecation of Buffer constructor #19079

nodejs/TSC

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

Invited

Observers

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

https://zoom.us/webinar/221426990

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 Mar 5, 2018
@MylesBorins
Copy link
Contributor

MylesBorins commented Mar 5, 2018 via email

@mhdawson
Copy link
Member Author

mhdawson commented Mar 5, 2018

Added zoom link https://zoom.us/webinar/221426990

@mhdawson
Copy link
Member Author

mhdawson commented Mar 5, 2018

Samed password as last week for TSC members.

@mhdawson
Copy link
Member Author

mhdawson commented Mar 5, 2018

Adding #501 for awareness. Would like to discuss and if there are no objections submit PR to remove experimental status later in the week.

@Trott
Copy link
Member

Trott commented Mar 5, 2018

Can someone point me to the documentation that suggests adding collaborators nominations to the tsc agenda? It's not in GOVERNANCE.md. Is it some recent-ish stuff that @joyeecheung wrote up maybe?

@Trott
Copy link
Member

Trott commented Mar 5, 2018

Not sure if they're available or willing, but perhaps @seishun should be invited as a guest if we're going to talk about the Buffer constructor stuff?

@joyeecheung
Copy link
Member

@Trott See https://github.com/nodejs/node/blob/master/doc/onboarding.md#one-week-before-the-onboarding-session

Announce the accepted nomination in a TSC meeting and in the TSC mailing list.

@Trott
Copy link
Member

Trott commented Mar 6, 2018

@joyeecheung Thanks!

It seems like it can be mentioned in the Announcements portion of the minutes/meeting, but I suppose there's no harm in putting it on the agenda either. I thought it was put on the agenda for discussion but it seems to be to announce it only. In which case, hey cool.

@mhdawson
Copy link
Member Author

mhdawson commented Mar 6, 2018

Removed #501 from agenda as looks like we'll have agreement without discussion in the meeting.

@mhdawson
Copy link
Member Author

mhdawson commented Mar 6, 2018

I won't be able to make the meeting as its too early for me (although I think its going to be an hour later after the time change so I might be able to make it in the future).

@mhdawson
Copy link
Member Author

mhdawson commented Mar 6, 2018

And should have noted @fhinkel will be chairing.

@rvagg
Copy link
Member

rvagg commented Mar 7, 2018

I think I'll probably have to skip this one, it's 11pm and I have a sleep debt to make up.

I did want to draw attention to nodejs/node#18998 however. My suspicion is that we have at least one problem that's causing regular crashes (segfaults) on Linux but it's showing up in different tests and on different Linuxes. From my non-scientific observation it appears that it might be more common on Alpine (all versions) and Debian (8 & 9) on x64 and in the Docker containers which run Ubuntu 16.04. On some of these systems the output says "CRASHED" (you see this on Alpine), but on others it is just an empty mystery output. I don't know if this is getting more frequent, it certainly feels that way, but it could be that as we iron out infra-related CI problems that this is just the next thing at the top of the list that we're seeing causing CI reds.

These are being reported against specific tests https://github.com/nodejs/node/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+crashed but I believe it may be something more fundamental not related to the tests themselves.

@evanlucas
Copy link
Contributor

I’ll likely miss this week

@jasnell
Copy link
Member

jasnell commented Mar 7, 2018

I'll be missing. 4am is rather early.

@cjihrig
Copy link
Contributor

cjihrig commented Mar 7, 2018

I'll miss the 7am meeting time.

@addaleax
Copy link
Member

addaleax commented Mar 7, 2018

I’ll be joining in a bit, sorry for being late!

@Trott
Copy link
Member

Trott commented Mar 8, 2018

Minutes in #502

@Trott Trott closed this as completed Mar 8, 2018
@Trott
Copy link
Member

Trott commented Mar 8, 2018

@nodejs/tsc @nodejs/community-committee I forgot to post the Moderation Team update for the week. So here it is:

  • One user's GitHub comments were deleted for being insulting and non-productive. Details were logged in the moderation repository issue 165.

  • One Collaborator requested review of another Collaborator's comment. There was some review and discussion, but no action was taken as the two Collaborators appeared to come to an understanding in the ensuing conversation. Moderation repo issue 180.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mhdawson mhdawson

Labels
tsc-meeting
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
10 participants
@ChALkeR @jasnell @rvagg @MylesBorins @evanlucas @Trott @addaleax @cjihrig @joyeecheung @mhdawson