Node.js Foundation Technical Steering Committee (TSC) Meeting 2017-09-27 #363
Comments
|
Request for Release WG to do update - nodejs/Release#254 |
|
Issues which are tsc-review for awareness: nodejs/build
nodejs/node
nodejs/TSC
nodejs/node-eps
|
|
I can do the update from the Release WG It would be nice if we could spend some time talking about putting together a One other thing that would be nice to put on the agenda if we have time would be to discuss some goals for the TSC and what the committee would like to be focusing its time on. Personally I'd like to see the committee focus on some more pro-active long term projects, and I'd like to get feedback on that concept. Finally, I think we can drop / close #243 for now. I'm not convinced that we should be opening up new collaborator spaces yet. |
|
I'm +1 for discussion on some more pro-active long term projects. I'll add to the agenda along with time to discuss the values doc. |
|
@MylesBorins interms of #243 I would just comment in the issue as its not on the agenda, was only a FYI on the ctc-review issues. |
|
It would be good to have a conversation about V8 6.1 and 6.2 |
Any examples to help seed the discussion? Would be good to be able to think about it in advance. |
|
I will be on a plane and unable to join the call. re: path: deprecate internal _makeLong, replace #14956 I'm +1 on this one, but then again I opened the PR. re: doc: doc expectations on TSC and CommComm members #12 No position, and I abstain from any vote that may be necessary. |
|
3am for me, won't be joining; plus I'm unwell atm anyway. @MylesBorins I agree re #243, perhaps you could go close it or remove it from tsc-review? Re values, I'm very interested to see what possible values folks think we might be able to align on. Please keep in mind that we have a very diverse range of views and personal values on the team and attempts to force anything controversial may land us in some heated waters. It'd be best to try and do this as gently as possible and stick to the obvious common denominators for now. I'm pretty sure that most of us are fatigued from having the broader culture wars encroach on our work together, it's distracting us from the obvious shared goal (value?) of shipping a quality product, so let's try and tread carefully please. |
|
Meeting minutes: #367 |
Time
UTC Wed 27-Sep-2017 17:00 (05: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.
Workgroup Update
Release Work Group
nodejs/node
nodejs/TSC
nodejs/admin
Initial discussion on 'values'
Long term TSC goals
Invited
Observers
Notes
The agenda comes from issues labelled with
tsc-agendaacross 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
Uberconference; participants should have the link & numbers, contact me if you don't.
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 it.
The text was updated successfully, but these errors were encountered: