-
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 2018-05-02 #536
Comments
I will not be able to participate because it is too late for me. |
I'm travelling on Wednesday so I don't think I'll make it. @fhinkel will Chair this week. |
I'm on vacation, so I won't be able to make it. |
I'll be at node day and will most likely not be able to make it
…On Tue, May 1, 2018, 6:01 AM Colin Ihrig ***@***.***> wrote:
I'm on vacation, so I won't be able to make it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#536 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAecV5SDazXG4aPhE7QMzkGKlKvmsA0Zks5tuDJjgaJpZM4TsfDx>
.
|
I am adding #389 to the agenda to raise awareness of #389 (comment) .
Turns out we did introduce a new module Key question: is the module id IMO We should have a consistent story around these new modules with potential namespace conflicts - with a new scope introduced or not. If a module being experimental means the module id is subject to change, then we should make the message clear, so whoever tries it would know the risk. |
As usual, this is too late for me in local time (and I have to get up early on Thursdays), so I will have to miss this. Sorry. On a side note, I suggest moving meeting times to either of these two:
Could be reproduced by copy-pasting the meeting table into https://chalker.github.io/Lliira/. |
Moderation Team Update: No Moderation Team actions to report this week. @nodejs/moderation @nodejs/tsc @nodejs/community-committee |
Minutes in #537 |
Time
UTC Wed 02-May-2018 22:00 (10: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
#389 (wrt.
fs/promises
)Invited
Observers
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.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
The text was updated successfully, but these errors were encountered: