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
Agenda so far: none, will be lifted from issues marked with _tc-agenda_, please label, or ask to have issues labeled if they need to be elevated to TC discussion.
I kind of regret adding Release Cycle Proposal #168 to the tc agenda; if nobody wants to talk about it we can cut it short.
Exchange thoughts on iojs/node releationship.
If time permits: iojs is attracting a lot of feature requests. In order to avoid bulking up issues, we need to think of a plan for dealing with them. Maybe we can take a diverse sample and see how we would want to deal with them. This helps the community too because it shows what will be considered and what won't.
Activity
rvagg commentedon Dec 17, 2014
Participate: most participants will also be in #io.js on Freenode during the meeting so feel free to participate there during the meeting.
Apology for this meeting received from @mikeal due to illness.
Agenda so far:
bnoordhuis commentedon Dec 17, 2014
I'm not sure if I'll be able to attend, one of my kids is ill.
piscisaureus commentedon Dec 17, 2014
wraithan commentedon Dec 17, 2014
@piscisaureus I wrote up #168 because A) I care, B) @bnoordhuis told me if I wrote it up he'd bring it up at the next TC meeting.
bengl commentedon Dec 17, 2014
Can we have a label for meeting announcements and other meeting metadata? Suggestions:
tc-meeting,tc-meetings.Add warning about experimental status (nodejs#163)