Node Foundation CTC Meeting 2015-10-28

[rvagg]

Time

UTC Wed 28-Oct-2015 20:00:

• San Francisco: Wed 28-Oct-2015 13:00
• New York: Wed 28-Oct-2015 16:00
• Amsterdam: Wed 28-Oct-2015 21:00
• Moscow: Wed 28-Oct-2015 23:00
• Sydney: Thu 29-Oct-2015 07:00
• Tokyo: Thu 29-Oct-2015 05:00

Or in your local time:

• http://www.timeanddate.com/worldclock/fixedtime.html?msg=Node+Foundation+CTC+Meeting+2015-10-28&iso=20151028T20
• or http://www.wolframalpha.com/input/?i=8pm+UTC%2C+Oct+28%2C+2015+in+local+time

Links

• Minutes Google Doc: https://docs.google.com/document/d/1GsTF3no6bimA20hi9i5aTBudBSM8jzPvuODR01hOltc
• Previous Minutes Google Doc: https://docs.google.com/document/d/1ad8Xlza_B-iWexdlAd1Z5muzBy_HH88t_iSD31OUepA

Agenda

Extracted from tsc-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/node

• Load JSON-LD in the same way as JSON #3502
• fs: decode filenames using UTF-8 in fs.watch #3401
• WG: Considering a new HTTP WG #3214

nodejs/TSC

• Travel fund for foundation members. #5

Invited

• @bnoordhuis (CTC)
• @chrisdickinson (CTC)
• @cjihrig (CTC)
• @domenic (observer)
• @Fishrock123 (CTC)
• @indutny (CTC)
• @jasnell (CTC)
• @mhdawson (observer)
• @misterdjules (CTC)
• @mikeal (observer)
• @mscdex (CTC)
• @orangemocha (CTC)
• @piscisaureus (CTC)
• @rvagg (CTC)
• @shigeki (CTC)
• @srl295 (observer)
• @trevnorris (CTC)

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. I'm using a tool to fetch the list so it's not a big deal to collate.

Joining the meeting

Uberconference; participants should have the link & numbers, contact me if you don't.

[mscdex]

Should we be using ctc-agenda and ctc-meeting labels now?

[mhdawson]

Out at a conference, won't be able to make it this week.

[shigeki]

Sorry, I can't attend the meeting this week.

[whitlockjc]

What are the chances of me attending as an observer?

[whitlockjc]

This was discussed offline, no need to respond here.

[rvagg]

Audio now available @ https://soundcloud.com/node-foundation/ctc-meeting-2015-10-28

[rvagg]

@nodejs/collaborators note that we now have a ctc-meeting label as well as a tsc-meeting label. The CTC is the "Core Technical Committee" and basically what the TSC has been doing until now. The TSC is currently the same group but is moving to more of an umbrella and organisational role so there will still be a need for the tsc-agenda label but it'll be the non-technical organisation items that this label will be used for.

Also note that I've cleaned up and published my agenda generating tool so you can use it to help organise your working group meetings if you need it. See [here] for details. It does this kind of thing, fetching issues from across all repos in the nodejs org:

$ node-meeting-agenda lts-agenda
### nodejs/node-v0.x-archive

* Deprecate Array#values() in 0.12.x [#25877](https://github.com/nodejs/node-v0.x-archive/issues/25877)
* Deprecate smalloc in v0.12 [#25784](https://github.com/nodejs/node-v0.x-archive/issues/25784)

### nodejs/LTS

* tls: make server not use DHE in less than 1014 bits [#49](https://github.com/nodejs/LTS/issues/49)
* Charter this [#48](https://github.com/nodejs/LTS/issues/48)
* npm in 0.10 LTS [#37](https://github.com/nodejs/LTS/issues/37)
* npm LTS [#14](https://github.com/nodejs/LTS/issues/14)
* Breaking changes between v0.12.x and next LTS releases cycle [#10](https://github.com/nodejs/LTS/issues/10)

[thefourtheye]

tsc-agenda label but it'll be the non-technical organisation items

Then why do we call it as "Technical Steering Committee"?

[Trott]

See [here] for details.

@rvagg Looks like you may have omitted a link.

[rvagg]

https://github.com/rvagg/iojs-tools/tree/master/node-meeting-agenda sorry

[sam-github]

re: #3561 (comment), I find the CTC/TSC split confusing. I can kindof see the goal, I guess it was to distinguish somehow between overall Node.js steering, and the nodejs/node repo steering, but the terms still seem muddled across the docs. Some questions:

• The CTC and TSC membership is identical ATM, right?
• Is that a matter of policy (being on one makes you be a member of the other?), or just how it is at the moment?
• Is there a TSC meeting and a CTC meeting?
• Should https://github.com/nodejs/TSC link to a list of who is in the TSC?
• And should the TSC list in the Node.js TLP (oh no, another TLA) be updated to mention that this is the CTC, not the TSC? Or that it is the CTC and the TSC (if thats the case)?

/to @mikeal

[jasnell]

Yes, the membership is currently identical but will diverge as we bring on
new top level projects.
On Nov 28, 2015 8:04 AM, "Sam Roberts" [email protected] wrote:

re: #3561 (comment)
#3561 (comment), I
find the CTC/TSC split confusing. I can kindof see the goal, I guess it was
to distinguish somehow between overall Node.js steering, and the
nodejs/node repo steering, but the terms still seem muddled across the
docs. Some questions:

• The CTC and TSC membership is identical ATM, right?
• Is that a matter of policy (being on one makes you be a member of
  the other?), or just how it is at the moment?
• Is there a TSC meeting and a CTC meeting?
• Should https://github.com/nodejs/TSC link to a list of who is in the
  TSC?
• And should the TSC list in the Node.js TLP
  https://github.com/nodejs/node#tsc-technical-steering-committee (oh
  no, another TLA) be updated to mention that this is the CTC, not the TSC?
  Or that it is the CTC and the TSC (if thats the case)?

/to @mikeal https://github.com/mikeal

—
Reply to this email directly or view it on GitHub
#3561 (comment).

[rvagg]

To expand, @sam-github:

The CTC and TSC membership is identical ATM, right?

Right

Is that a matter of policy (being on one makes you be a member of the other?), or just how it is at the moment?

Not at all. Just a matter of mechanics. It's anticipated that over the next few months the CTC will probably not change much (I'd still like to expand it further) but the TSC will trim down as it starts having meetings and focuses on non-technical matters that would bore and/or frustrate some of the existing members who really don't want to be involved in that kind of bikeshedding. The TSC will also expand as it the list of top-level projects (TLPs), either from what we have now in the org or new projects coming in. I think that it's set up so that its membership is exclusively made up of representatives of TLPs.

Is there a TSC meeting and a CTC meeting?

We've tentatively reserved the slot after the current CTC meeting for the TSC meeting, I'm not sure if we've had any meetings yet (I don't recall being in one anyway).

Should https://github.com/nodejs/TSC link to a list of who is in the TSC?

Probably. It's also unresolved how it should be documented on the nodejs/node README, should that list just the CTC or the TSC also? My guess is that it'll become more clear over time as we do some actual business.

And should the TSC list in the Node.js TLP (oh no, another TLA) be updated to mention that this is the CTC, not the TSC? Or that it is the CTC and the TSC (if thats the case)?

Matters to be resolved. It's so early that nothing much has really changed. As the membership of the two groups diverge and the business they attend to differ it'll clear up. Also, this process is not set in stone, there's lots of discussion to be had so if you have concerns or more questions then feel free to fire away and hopefully answers can be found.

[sam-github]

OK, @rvagg that answers my questions, including the meta-question of why this isn't clearer in the READMEs (because its a WIP). But I see the direction we are going, thank you.