Skip to content
This repository has been archived by the owner on Nov 9, 2017. It is now read-only.

Node.js Foundation Core Technical Committee (CTC) Meeting 2017-01-11 #59

Closed
Trott opened this issue Jan 9, 2017 · 20 comments
Closed

Node.js Foundation Core Technical Committee (CTC) Meeting 2017-01-11 #59

Trott opened this issue Jan 9, 2017 · 20 comments

Comments

@Trott
Copy link
Member

Trott commented Jan 9, 2017

Time

UTC Wed 11-Jan-2017 20:00:

Timezone Date/Time
US / Pacific Wed 11-Jan-2017 12:00
US / Mountain Wed 11-Jan-2017 13:00
US / Central Wed 11-Jan-2017 14:00
US / Eastern Wed 11-Jan-2017 15:00
Amsterdam Wed 11-Jan-2017 21:00
Moscow Wed 11-Jan-2017 23:00
Chennai Thu 12-Jan-2017 01:30
Tokyo Thu 12-Jan-2017 05:00
Sydney Thu 12-Jan-2017 07:00

Or in your local time:

Links

Agenda

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

nodejs/node

nodejs/TSC

  • Updating the Copyright #174

nodejs/CTC

  • Growing the group of releasers #48

nodejs/node-eps

  • Rewrite 002 - esm #39

Invited

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.

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 CTC that's not worth putting on as a separate agenda item, this is a good place for it.

@jasnell
Copy link
Member

jasnell commented Jan 9, 2017

Let's be sure to bundle the discussion for nodejs/node#10155 and nodejs/node#10599 as they are directly related. Also, I believe that nodejs/node#10505 can be dropped.

Edit (targos): cross-ref links

@targos
Copy link
Member

targos commented Jan 9, 2017

@Trott can you please update your template regarding my CTC membership?

@bmeck
Copy link
Member

bmeck commented Jan 9, 2017

would like to add nodejs/node-eps#39 minor discussion after recent talks to the agenda

@Trott
Copy link
Member Author

Trott commented Jan 9, 2017

@bmeck Can you provide a small amount of context? Are you hoping to share information? Get feedback on something? Or have the CTC make a decision?

@targos
Copy link
Member

targos commented Jan 11, 2017

I probably won't be here today, sorry.

@indutny
Copy link
Member

indutny commented Jan 11, 2017

Sorry, I won't be able to join you today

@Fishrock123
Copy link

  • console.log and util.format should support the %i integer conversion
  • Landing npm 4 into node 7

Do these still need to be on the agenda? I can see why we'd want to keep an eye on npm 4 though.

@silverwind
Copy link

console.log and util.format should support the %i integer conversion

Is there a summary/meeting notes available on this? I'm sorry I've been absent the last weeks, so I didn't follow.

@thefourtheye
Copy link

I am so sorry, I am not feeling well and I might not join today.

@ChALkeR
Copy link
Member

ChALkeR commented Jan 11, 2017

Sorry, I will have to miss this one, too. I will return to Moscow this Friday.

@joshgav
Copy link
Contributor

joshgav commented Jan 11, 2017

@MylesBorins
Copy link

Won't be able to make it today. Will review issues and vote as necessary.

@rvagg
Copy link
Member

rvagg commented Jan 11, 2017

Sorry but I'm having some trouble on my end that's going to stop me attending. Can @Trott, or someone else chair please? Very sorry!

@jasnell
Copy link
Member

jasnell commented Jan 11, 2017

@rvagg ... with regards to #10155 and #10599, can you update us on whether there has been any review/response from the legal committee?

@joshgav
Copy link
Contributor

joshgav commented Jan 11, 2017

notes in #60

@rvagg
Copy link
Member

rvagg commented Jan 11, 2017

Re legal committee, it has to go via the board. I believe there's a meeting next week and I'm getting it onto the agenda for that.

@mikeal
Copy link

mikeal commented Jan 11, 2017

The next board meeting is on the 30th actually.

@williamkapke
Copy link

@mikeal I added the Board Meeting to the Calendar and assumed it is at 2PM PST. LMK if my assumption is wrong.

Note- there is an @nodejs/lts meeting at 1PM PST that will be using the YouTube live channel.

@mikeal
Copy link

mikeal commented Jan 12, 2017

It is indeed at 2pm :) It'll be 2 hours long.

@mikeal
Copy link

mikeal commented Jan 12, 2017

Sorry, public portion is only 1 hour :)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests