CANCELLED - Node.js Foundation Technical Steering Committee (TSC) Meeting 2018-11-14 #630
Comments
|
4am PST is too early for me, but I accept any decision on nodejs/node#24012 as long as developers have a way to find out about editor configs from Node.js core. |
|
@trivikr If there's no rush and if you'd rather be able to take part in the conversation, I don't think there'd be any objection to pushing nodejs/node#24012 to the next meeting's agenda. Would you prefer that? |
|
@thefourtheye Is nodejs/node#23433 pretty much resolved at this point, and just waiting for the implementation to land? Or is there something for the TSC to decide there? |
|
@nodejs/tsc It would seem silly to have to talk about #625 at the meeting rather than getting it resolved in GitHub. @mcollina has offered to chair the meetings in that time slot when he is able to. It seems like all that is needed to close that issue is someone else to volunteer to be the back-up chair when @mcollina can't do it. Any volunteers? As someone who has chaired a fair amount, I can tell you that it is not difficult or time-consuming. YOU CAN DO THIS!!! |
|
While we're at it, I'd like to prod strategic initiative and board updates to be something that get done in advance. Leave a comment here and it can be read at the meeting and copy/pasted into the minutes. And then the update happens even if you don't make it to the meeting. HOW COOL IS THAT??!! |
|
@Trott There's no rush, and nodejs/node#24012 can be pushed to next week. |
|
We can push out #625 if its the only thing left on the agenda. |
|
+1 for pushing out nodejs/node#24012, unless anybody objects I'll remove from this weeks agenda tomorrow. |
|
@Trott Yup, Option 1 in nodejs/node#23433 has got majority (Out of the twelve TSC members' opinion, Option 1 got 9 supporters). We would be going with Option 1, unless there are any objections from @nodejs/tsc. We are in the process of ironing out @ChALkeR's suggestion, which can be done in GitHub itself, I believe. So it can be removed from the agenda. |
|
Looks like we can cancel this meeting. Would still be useful/good IMO if standing issue updates could be placed here. |
|
Ok, I'm good to cancel :). Iif people could update the minutes with the updates for the board update/strategic initiatives update I'll capture the minutes and add into the repo along with an indication that the actual meeting was canceled. I'm going to leave the issue open until we do that, but will update to show as cancelled. |
mhdawson
changed the title
|
What do people think about removing the calendar entry? I can't quite decide if it is better to leave it in or remove it. |
|
Better remove it I presume.
Il giorno mar 13 nov 2018 alle ore 22:52 Michael Dawson <
[email protected]> ha scritto:
… What do people think about removing the calendar entry? I can't quite
decide if it is better to leave it in or remove it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#630 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AADL49nydWbaphEwmitntvxn5ujt4wiPks5uuz8kgaJpZM4YZm_N>
.
|
|
ok removed for now. |
|
+1 to cancel
Il giorno mar 13 nov 2018 alle 22:44 Michael Dawson <
[email protected]> ha scritto:
… Ok, I'm good to cancel :). Going to close but if people could update the
minutes with the updates for the board update/strategic initiatives update
I'll capture the minutes and add into the repo along with an indication
that the actual meeting was canceled.
I'm going to leave the issue open until we do that, but will update to
show as cancelled.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#630 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AADL4x5_Aq70uM6WpZFlvlRqcHXyDuDvks5uuz0qgaJpZM4YZm_N>
.
|
|
I don't see any updates beyond N-API in the minutes so I'm not sure it's worth capturing them. Will leave for another day or so and if there are no updates just close. |
|
I added my update:
|
|
Moderation Team Update:
@nodejs/tsc @nodejs/community-committee @nodejs/moderation |
|
I think this is supposed to stay open until the minutes PR is opened. (No meeting, but minutes to record strategic initiatives updates.) Obviously, close again if I'm mistaken. |
|
PR for minutes - #635 |
Cancelled based on limited agenda and agreement in issue
Time
UTC Wed 14-Nov-2018 12:00 (12:00 PM):
Or in your local time:
Links
Agenda
Extracted from tsc-agenda labelled issues and pull requests from the nodejs org prior to the meeting.
nodejs/node
nodejs/TSC
Invited
Observers/Guests
Notes
The agenda comes from issues labelled with
tsc-agendaacross 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
Zoom link: https://zoom.us/j/611357642
Regular password
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 that.
Invitees
Please use the following emoji reactions in this post to indicate your
availability.
The text was updated successfully, but these errors were encountered: