-
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 2016-02-04 #41
Comments
Most likely we'll still be having foundational discussion preparing a path to properly consider new projects. Homework if you're going to attend probably should include #35 and #40 as these begin to address what we need, although IMO they don't go far enough back in to first-principles (values, reason for the Node.js Foundation to exist, what guides us in making decisions and enforcing acceptable boundaries for TLPs, etc.). The more help on this from existing members the better. |
Right, the thing I'm working on is still a half-written mess, maybe I'll get it done today, I'm not sure. |
I'll have the express application updated in time for the call. Let's make
|
Minutes added in #111 |
Time
UTC Thu 04-Feb-2016 20:00:
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/TSC
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, contact me if you don't.
The text was updated successfully, but these errors were encountered: