Repository navigation
io.js TC Meeting 2014-12-17 #163
Description
Activity
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:
- Release Cycle Proposal Release Cycle Proposal #168
- Bundle tick processor with iojs RFC: bundle tick processor with iojs #158
I'm not sure if I'll be able to attend, one of my kids is ill.
- I added Module search security 8830 #176 (module search security) following a suggestion by @bnoordhuis to add it to the tc agenda.
- 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.
@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.
Can we have a label for meeting announcements and other meeting metadata? Suggestions:
tc-meeting,tc-meetings.- added a commit that references this issue
on Apr 6, 2017
This week UTC Wed 17-Dec-14 19:00:
Or in your local time:
Public YouTube feed: http://www.youtube.com/watch?v=7s-VJLQEWXg
Invited: @bnoordhuis (TC), @piscisaureus (TC), @indutny (TC), @isaacs (TC), @trevnorris (TC), @chrisdickinson (TC), @mikeal, @rvagg (build)
Agenda and minutes doc, editable by TC, commentable by everyone else: https://docs.google.com/document/d/1PoqGfxpfTFKv5GcKmhMM2siZpPjT9Ba-ooBi-ZbYNi0/edit (written in markdown so we can put it straight into the repo -- TC members please give me your default Google logins so you can edit rather than comment / suggest)
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.