Node.js Foundation Core Technical Committee (CTC) Meeting 2016-01-13

[rvagg]

Time

UTC Wed 13-Jan-2016 20:00:

• San Francisco: Wed 13-Jan-2016 12:00
• New York: Wed 13-Jan-2016 15:00
• Amsterdam: Wed 13-Jan-2016 21:00
• Moscow: Wed 13-Jan-2016 23:00
• Sydney: Thu 14-Jan-2016 07:00
• Tokyo: Thu 14-Jan-2016 05:00

Or in your local time:

• http://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Core%20Technical%20Committee%20(CTC)+Meeting+2016-01-13&iso=20160113T20
• or http://www.wolframalpha.com/input/?i=8pm+UTC%2C+Jan+13%2C+2016+in+local+time

Links

• Minutes Google Doc: https://docs.google.com/document/d/1uvPCwzW5Y3bE0kBNqXOJzsUSgyZwcUEA4JTRcQYGZ1U
• Previous Minutes Google Doc: https://docs.google.com/document/d/1LyECbnYZcxPoBal9JA8quGEvie1Rj_ofKn4CVMni9eY

Agenda

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

nodejs/node

• doc: add Docs working group #4244
• Seek legal advice on LICENSE and copyright blocks in code #3979

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

[rvagg]

Agenda is light, I don't have anything to update on legals and doc: add Docs working group #4244 may not require another discussion. Might be a quick meeting .. although we could run some circles around new Buffer(Number) #4660.

[piscisaureus]

I can't make it to this call, but I'll be back next week.

[jasnell]

@rvagg ... I went ahead and tagged #4660 with ctc-agenda. It would be good to at least have a discussion on it.

[shigeki]

I can't make it this week, sorry.

[bnoordhuis]

I'm going to have to skip this one, I'm in bed with the flu.

[orangemocha]

I will have to excuse myself too.

[chrisdickinson]

I may not be able to make the meeting today. If not, here's a docs WG update:

1. Call for contributors:
   1. I've sent out an email to all current website and core collaborators that have touched the doc subdirectory in the last 6 months. This contains links to the relevant issues for joining.
   2. I've opened issues on the Website and Core trackers calling for new members.
   3. I tweeted about the same.
2. Update to membership info in GOVERNANCE.md
   1. This defines what membership entails — it's up for discussion!
   2. When I initially went to add members I found the details on membership were pretty vague, so it was hard to know I was adding folks correctly and hard to communicate what they'd be doing within the WG once added.
   3. I would love your thoughts on this!
3. A docs WG slack has been started to coordinate on Docs WG issues and documentation editing.
   1. @distracteddev is working on getting an integration set up for that.
4. There's a meeting scheduled to discuss ratification and other issues, to be held after we close this round of "call for contributors."
5. Our current operating procedure is to operate as if we've been ratified — that is, you should see (or continue to see) members of the Docs WG commenting on issues and PRs tagged with docs or @nodejs/documentation.
6. Later this week I'll add folks to the WG.

[jasnell]

given the number of folks who cannot make it, would it make sense to push off a week?

[cjihrig]

I'm fine with skipping this week.

[mikeal]

we don't have anything new from the legal committee to report and we need @chrisdickinson to handle the other agenda item so it makes sense to defer this meeting.

[Fishrock123]

Eh, I think we can probably discuss the other issues at hand lightly unless a couple others drop. I also have a quick thing for the private bit.

@mikeal We'd be discussing the buffers and util._extends things

[jasnell]

Turns out I need to miss also, unfortunately. Sorry for the last minute notice.

[Fishrock123]

Short meeting, just discussed the thing I wanted to briefly. More news on that TBD.