You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
We have an informal item to continue discussing around #35 which is about finding a basis on which to make more objective decisions about expansion of the projects which are managed under the foundation. A basic why that we can refer to when we are discussing new projects that are wanting to join. The why should also inform most of our other actions, including going out and proactively taking actions to meet those goals, perhaps creating short-lived inquiries lead by subject matter experts to advise us on courses of action in particular areas.
The more that can join for this discussion the better of course.
We've talked a lot in a few issues on here, I'd like to discuss further on the call today but not try to arrive at any decision until we've made some more iterations in the PRs.
Time
UTC Thu 28-Jan-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: