Repository navigation
Cancelled - Node.js Foundation Technical Steering Committee (TSC) Meeting 2018-11-21 #633
Description
Time
UTC Wed 21-Nov-2018 16:00 (04:00 PM):
| Timezone | Date/Time |
|---|---|
| US / Pacific | Wed 21-Nov-2018 08:00 (08:00 AM) |
| US / Mountain | Wed 21-Nov-2018 09:00 (09:00 AM) |
| US / Central | Wed 21-Nov-2018 10:00 (10:00 AM) |
| US / Eastern | Wed 21-Nov-2018 11:00 (11:00 AM) |
| London | Wed 21-Nov-2018 16:00 (04:00 PM) |
| Amsterdam | Wed 21-Nov-2018 17:00 (05:00 PM) |
| Moscow | Wed 21-Nov-2018 19:00 (07:00 PM) |
| Chennai | Wed 21-Nov-2018 21:30 (09:30 PM) |
| Hangzhou | Thu 22-Nov-2018 00:00 (12:00 AM) |
| Tokyo | Thu 22-Nov-2018 01:00 (01:00 AM) |
| Sydney | Thu 22-Nov-2018 03:00 (03:00 AM) |
Or in your local time:
- http://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Technical%20Steering%20Committee%20(TSC)+Meeting+2018-11-21&iso=20181121T16
- or http://www.wolframalpha.com/input/?i=04PM+UTC%2C+Nov+21%2C+2018+in+local+time
Links
- Minutes Google Doc: https://docs.google.com/document/d/1nPsN-Gld6mq49XJKGhbtnlJrW3BwxyLsbTH5E9NMbhA/edit
Agenda
Extracted from tsc-agenda labelled issues and pull requests from the nodejs org prior to the meeting.
nodejs/node
- doc: add link to VSCode config in testing #24012
nodejs/TSC
Invited
- Anna Henningsen @addaleax (TSC)
- Anatoli Papirovski @apapirovski (TSC)
- Сковорода Никита Андреевич @ChALkeR (TSC)
- Colin Ihrig @cjihrig (TSC)
- Daniel Bevenius @danbev (TSC)
- Franziska Hinkelmann @fhinkel (TSC)
- Gabriel Schulhof @gabrielschulhof (TSC)
- Jeremiah Senkpiel @Fishrock123 (TSC)
- James M Snell @jasnell (TSC)
- Joyee Cheung @joyeecheung (TSC)
- Matteo Collina @mcollina (TSC)
- Michael Dawson @mhdawson (TSC)
- Myles Borins @MylesBorins (TSC)
- Ali Ijaz Sheikh @ofrobots (TSC)
- Rod Vagg @rvagg (TSC)
- Michaël Zasso @targos (TSC)
- Sakthipriyan Vairamani @thefourtheye (TSC)
- Timothy Gu @TimothyGu (TSC)
- Rich Trott @Trott (TSC)
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.
Invitees
Please use the following emoji reactions in this post to indicate your
availability.
- 👍 - Attending
- 👎 - Not attending
- 😕 - Not sure yet
Activity
Trott commentedon Nov 19, 2018
Regarding the only non-standing issue currently on the agenda (nodejs/node#24012), here's @trivikr's explanation of why it's on the agenda and my recommendations:
It looks like this is being discussed in nodejs/admin#260. In that issue, @refack suggested node-code-ide-configs, and two Collaborators gave that a thumbs up reaction. No one else has suggested another name, and that name seems good to me. We can always change the name later.
My opinion only but I'm going to guess this is the broader TSC opinion: Go with that. This doesn't seem to need TSC attention. (If any TSC members have opinions about the name, they can put it in that admin repo issue.)
Looking at that issue, I'd say rename the repo
node-code-ide-configsper above.If it's a single sentence, open a PR adding it to CONTRIBUTING.md and let's see what happens. If it's going to be a few paragraphs or more, create a separate guide in
doc/guidesand add a link to it in CONTRIBUTING.md. If it's going to be more than a single sentence but less than a few paragraphs, pick one. Either way, open a PR and let's see what happens.The main thing is that there is a lot of resistance (in the PR comments) to putting it in BUILDING.md (including from me) so let's not do that.
@nodejs/tsc Does this all seem about correct to you? If so, can you 👍 this and if not, please comment. (If there's consensus that this all makes sense, we can ask @trivikr to remove the tsc-agenda label and cancel this week's meeting.) If you disagree, of course, leave a comment. Thanks.
mhdawson commentedon Nov 20, 2018
Since I don't see any objections @trivikr are you ok with removing the tsc-agenda label?
trivikr commentedon Nov 20, 2018
Yup! I also vote for the name
node-code-ide-configsCan someone rename the repo? I don't have permissions.
Refs: nodejs/node-code-ide-configs#1
Removed tsc-agenda label for nodejs/node#24012
mhdawson commentedon Nov 20, 2018
Ok canceling the meeting for tomorrow. Will remove from Calendar. If people have any significant updates for the strategic initiatives let me know and I'll capture the minutes.
[-]Node.js Foundation Technical Steering Committee (TSC) Meeting 2018-11-21[/-][+]Cancelled - Node.js Foundation Technical Steering Committee (TSC) Meeting 2018-11-21[/+]mhdawson commentedon Nov 21, 2018
No updates to strategic initiatives, closing.