-
Notifications
You must be signed in to change notification settings - Fork 30k
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 Foundation CTC Meeting 2015-12-23 #4398
Comments
The only thing new on here is "Nominating new Release team members #4319", the other stuff is just updates for the legal matters which I can sum up two sentences: the Foundation Board passed it to the Legal Committee which ran out of time during its last meeting so it'll have to wait to be discussed in early January. They are likely to want to pass the request for advice to an outside party who will be able to provide formal advice back to us on the matters we asked about. It's my daughter's birthday tomorrow, it's Christmas Eve for me and the house is filling up with family so I'm going to have to opt out of the meeting. In the interests of saving everyone some time during the holiday season can I suggest we cancel this week's meeting? If enough people decide to go ahead and have a quorum for a meeting, Uberconference will record it automatically. (Trying to catch up on my meeting minutes & recording backlog is near the top of my TODO list for this week.) |
I won't be able to attend either. |
I'm fine with canceling this week. |
+1 to pushing to next week.
|
Yeah let's just do it next week |
Time
UTC Wed 23-Dec-2015 20:00:
Or in your local time:
Links
Agenda
Extracted from ctc-agenda labelled issues and pull requests from the nodejs org prior to the meeting.
nodejs/node
Invited
Notes
The agenda comes from issues labelled with
ctc-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. I'm using a tool to fetch the list so it's not a big deal to collate.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: