-
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-03-23 #227
Comments
I’ll try to but i might not be able to make it tomorrow. |
I'll probably have to miss the first 30 minutes. Do we actually have anything to discuss though? I don't see anything on the agenda that calls for a vote. |
Carrying over from #228 (comment):
There were still one or two unresolved issues last time I looked, however. |
Yeah you're right there is still one issue that I can remember still being unresolved, but I'd like to use the TSC meeting to get everything resolved so that we can get the changes landed quickly so we can put this before the board on Monday. |
notes in #229 |
Time
UTC Thu 23-Mar-2017 20:00 (08: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/summit
nodejs/TSC
nodejs/community-committee
Invited
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
Uberconference; participants should have the link & numbers.
The text was updated successfully, but these errors were encountered: