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-09-27 #363

Closed
mhdawson opened this issue Sep 25, 2017 · 10 comments
Closed

Comments

@mhdawson
Copy link
Member

mhdawson commented Sep 25, 2017

Time

UTC Wed 27-Sep-2017 17:00 (05:00 PM):

Timezone Date/Time
US / Pacific Wed 27-Sep-2017 10:00 (10:00 AM)
US / Mountain Wed 27-Sep-2017 11:00 (11:00 AM)
US / Central Wed 27-Sep-2017 12:00 (12:00 PM)
US / Eastern Wed 27-Sep-2017 13:00 (01:00 PM)
Amsterdam Wed 27-Sep-2017 19:00 (07:00 PM)
Moscow Wed 27-Sep-2017 20:00 (08:00 PM)
Chennai Wed 27-Sep-2017 22:30 (10:30 PM)
Hangzhou Thu 28-Sep-2017 01:00 (01:00 AM)
Tokyo Thu 28-Sep-2017 02:00 (02:00 AM)
Sydney Thu 28-Sep-2017 03:00 (03: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.

Workgroup Update

Release Work Group

nodejs/node

  • path: deprecate internal _makeLong, replace #14956

nodejs/TSC

nodejs/admin

  • doc: doc expectations on TSC and CommComm members #12

Initial discussion on 'values'

  • discuss, Myles may have a draft to seed the discussion.

Long term TSC goals

  • kick off discussion.

Invited

Observers

  • Bradley Meck @bmeck (GoDaddy/TC39)
  • Tracy Hinds @hackygolucky (Node.js Foundation Education Community Manager)
  • Kaitlyn Barnard @kbarnard10 (Node.js Foundation Newsletter Curator)
  • Mark Hinkle @mrhinkle (Node.js Foundation Executive Director)
  • William Kapke @williamkapke (Node.js Community Board representative)

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

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.

@mhdawson
Copy link
Member Author

Request for Release WG to do update - nodejs/Release#254

@mhdawson
Copy link
Member Author

Issues which are tsc-review for awareness:

nodejs/build

  • Dropping 32-bit builds #885

nodejs/node

  • http: send 400 bad request on parse error #15324
  • Regression: Resolution algorithm collision #14990
  • path: deprecate internal _makeLong, replace #14956
  • build: update minimum kernel version to 3.10.0 #14795
  • Buffer.isEncoding regards an empty string as a valid encoding #9654

nodejs/TSC

  • Candidate "areas" for TSC and Community Committee #278
  • Approval to move node-heapdump into foundation #257
  • create public nodejs/collaborators repo #243

nodejs/node-eps

  • Invert dependency between core and readable-stream #49

@MylesBorins
Copy link
Contributor

I can do the update from the Release WG

It would be nice if we could spend some time talking about putting together a values doc... I can maybe get some copy together for Wednesday for us to review.

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.

@mhdawson
Copy link
Member Author

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.

@mhdawson
Copy link
Member Author

mhdawson commented Sep 25, 2017

@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.

@MylesBorins
Copy link
Contributor

It would be good to have a conversation about V8 6.1 and 6.2

@jasnell
Copy link
Member

jasnell commented Sep 25, 2017

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.

Any examples to help seed the discussion? Would be good to be able to think about it in advance.

@jasnell
Copy link
Member

jasnell commented Sep 26, 2017

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.

@rvagg
Copy link
Member

rvagg commented Sep 27, 2017

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.

@mhdawson
Copy link
Member Author

Meeting minutes: #367

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