-
Notifications
You must be signed in to change notification settings - Fork 134
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-11-08 #413
Comments
I propose the following guests:
Any other suggestions? |
There are currently 13 (!!!) issues labeled |
middle of the night for me, won't be making it I believe "Support both OpenSSL 1.1.0 and 1.0.2" nodejs/node#16130 can be removed from the agenda. It's non-breaking and is almost ready to land on |
Probably will have to miss this one. |
Also not going to make it to this one, I’ll be on my way home from NodeConfEU |
For other NodeConf EU attendees (me, @mhdawson, @jasnell, @mcollina), note that the meeting is during an opening between the final presentation and dinner. I get it if you have other things to attend to (especially @jasnell and @mcollina who are helping organize the thing), but hope you can make it! I expect to be able to attend. |
From our discussion last week I think we need Matteo for stream: move prefixed files into internal/streams.nodejs/node#11957 And James for meta: fix case of extensions on internal docs and move CoC to admin repo nodejs/admin#25 |
@Trott 🙌 Yes. Present. Happy to join. |
@Trott ok I'll try to make it as well. |
@Trott and thanks for creating the issue for the meeting :) |
Just to make sure there's no confusion: If you are in Ireland, the meeting is at 5PM. Since this time zone is not listed in the table above... |
Do we need to discuss the governance work? We haven't met yet so I'm not sure we have anything to discuss |
@MylesBorins Governance was labeled While you're in here: Do you agree with @rvagg that we don't need to talk about the OpenSSL issue either? |
I agree we can drop the openssl issue re: governance issue... label was added 24 days ago. In the last meeting we came to the conclusion there was nothing to discuss until the meeting was held. The only thing I think we need to discuss right now is getting a day chosen for this. If we are going to dig a bit deeper we may want to include @sarahnovotny as well. |
I might be late because of traffic |
I just added a last point to the agenda:
Hope that's OK. Not really anything to discuss, just planting the idea of another summit in peoples' heads. Will follow up in a separate issue. There's an open issue openjs-foundation/summit#56 for any discussion around that. |
Minutes PR: #416 |
Time
UTC Wed 08-Nov-2017 17:00 (05:00 PM):
Or in your local time:
Links
Agenda
Announcements
nodejs/node
Support both OpenSSL 1.1.0 and 1.0.2 Support both OpenSSL 1.1.0 and 1.0.2 node#16130nodejs/TSC
Proposal to form a Governance Working Group Proposal to form a Governance Working Group #383nodejs/admin
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.
The text was updated successfully, but these errors were encountered: