|
| 1 | +# io.js TC Meeting 2015-05-13 |
| 2 | + |
| 3 | +## Links |
| 4 | + |
| 5 | +* **Public YouTube feed**: http://www.youtube.com/watch?v=UbYiFLf7MpU |
| 6 | +* **Google Plus Event page**: https://plus.google.com/events/cu606mlllfehl11u8kcj7q2407k |
| 7 | +* **GitHub Issue**: https://github.com/iojs/io.js/issues/1689 |
| 8 | +* **Original Minutes Google Doc**: https://docs.google.com/document/d/15Y_kJlYm-8cIf-alniaqUWMM-TjGISCqLf40G3pv4sM |
| 9 | + |
| 10 | +## Agenda |
| 11 | + |
| 12 | +Extracted from https://github.com/iojs/io.js/labels/tc-agenda prior to meeting. |
| 13 | + |
| 14 | +* V8 4.4 to remove indexed properties via external data [#1451](https://github.com/iojs/io.js/issues/1451) |
| 15 | +* NODE_PATH deprecation [#1627](https://github.com/iojs/io.js/issues/1627) |
| 16 | +* Join the Node Foundation? [#1664](https://github.com/iojs/io.js/issues/1664) |
| 17 | +* Put `*Sync` methods behind a flag in some future major version [#1665](https://github.com/iojs/io.js/issues/1665) |
| 18 | +* TC Nominations |
| 19 | + - Shigeki Ohtsu @shigeki [#1501](https://github.com/iojs/io.js/issues/1501) |
| 20 | + - Brian White @mscdex [#1500](https://github.com/iojs/io.js/issues/1500) |
| 21 | + - @mikeal [#1481](https://github.com/iojs/io.js/issues/1481) |
| 22 | +* Public QA via #io.js channel on Freenode |
| 23 | + |
| 24 | +### Present |
| 25 | + |
| 26 | +* Ben (TC) |
| 27 | +* Bert (TC) |
| 28 | +* Brian |
| 29 | +* Chris (TC) |
| 30 | +* Domenic |
| 31 | +* Jeremiah (TC) |
| 32 | +* Mikeal |
| 33 | +* Rod (TC) |
| 34 | +* Shigeki |
| 35 | +* Trevor (TC) |
| 36 | + |
| 37 | +### Quick stand-up |
| 38 | + |
| 39 | +* Ben: Upgraded V8, upgraded cares for the first time in 2 years, reviewed pull requests |
| 40 | +* Bert: Played Keen, not much io.js stuff; last Monday met with James, Mikeal about convergence |
| 41 | +* Brian: looking over potential optimizations in the JS codebase, started working on a DNS resolver as a potential replacement for cares |
| 42 | +* Chris: fixing race conditions in the REPL, poking at adding Ctrl-R history searching to readline |
| 43 | +* Domenic: working with V8 team in Munich, working on v8-extras feature, putting large portions of things into snapshot to speed up startup and other things: https://groups.google.com/forum/#!topic/v8-users/D6FmTwlvCgk |
| 44 | +* Jeremiah: issue management, working on tooling for automatic dependency upgrades, see [#1688](https://github.com/iojs/io.js/pull/1688) |
| 45 | +* Mikeal: Foundation stuff, getting ducks in a row |
| 46 | +* Shigeki: holiday in JP, fix TLS bug involving edge-case, needs review |
| 47 | +* Trevor: Helped with re-enabling snapshots, looking at changing the Buffer APIs to use TypedArrays |
| 48 | +* Rod: Been doing lots of little things, working on the CI and build cluster |
| 49 | + |
| 50 | +### Review of last meeting |
| 51 | + |
| 52 | +* Release Proposal: v2.0.0 [#1532](https://github.com/iojs/io.js/pull/1532) |
| 53 | +* Forward-port from v1.x [#1559](https://github.com/iojs/io.js/pull/1559) |
| 54 | +* Convergence plan (https://github.com/jasnell/dev-policy/pull/66) |
| 55 | +* Combined node.js/io.js TC/core call [#1413](https://github.com/iojs/io.js/issues/1413) |
| 56 | + |
| 57 | +## Minutes |
| 58 | + |
| 59 | +* Discussed creating a more formal deprecation policy, chris to open an issue. |
| 60 | + |
| 61 | +### V8 4.4 to remove indexed properties via external data [#1451](https://github.com/iojs/io.js/issues/1451) |
| 62 | + |
| 63 | +* ‘smalloc’ has to go away when we land this V8, thankfully it’s not been around for long but this is a forced deprecation & removal. |
| 64 | +* currently usage of ‘smalloc’ gives a deprecation warning, as of v2.0.0 |
| 65 | +* @jeisinger has been backporting some APIs needed for Buffer, NAN will have to catch up but @kkoopa is involved |
| 66 | +* Domenic: V8 4.3 will be next week, 7 weeks from now will be 4.4 (~1 week behind Chrome release) |
| 67 | +* Trevor: no major problems with JS API, most problems will be in the C++ API, should be able to shim to ease it |
| 68 | + |
| 69 | +### NODE_PATH deprecation [#1627](https://github.com/iojs/io.js/issues/1627) |
| 70 | + |
| 71 | +* Jeremiah: there was a suggestion to deprecate NODE_PATH entirely, debate is over deprecation or not, lots of people appear to be finding novel uses of it. |
| 72 | +* Domenic: maybe we should document it |
| 73 | +* Chris: it is documented, Googling shows that it’s been ingrained into the Node background, there’s lots of info out there about how it’s used |
| 74 | +* Domenic: https://iojs.org/api/modules.html#modules_loading_from_the_global_folders |
| 75 | +* Mikeal: maybe write docs about how it exists but you shouldn’t use it |
| 76 | + |
| 77 | +**Action: Mikeal to open an issue to change the docs to talk about how you probably shouldn’t use them** (note: it might be as simple as styling!) |
| 78 | + |
| 79 | +### Join the Node Foundation? [#1664](https://github.com/iojs/io.js/issues/1664) |
| 80 | + |
| 81 | +* Mikeal: Mostly a consensus in the issue about joining |
| 82 | +* Mikeal: Next step is to move the “iojs” org to “nodejs”, then move the convergence repo in to be “node” to be the new tip: https://github.com/jasnell/node.js-convergence |
| 83 | + |
| 84 | +Lots of discussions about process and what needs to happen & when, Mikeal pushing for a vote to get the org moved. |
| 85 | + |
| 86 | +**Voting Question**: The io.js TC agrees to: |
| 87 | + 1. have the io.js project join the Node Foundation |
| 88 | + 2. rename the entire “iojs” GitHub org to be “nodejs” |
| 89 | + 3. invite the the current Node.js TC on to our TC to form the basis of a Node Foundation TSC under the policies of the Node Foundation |
| 90 | + 4. moving the io.js Working Groups to be under the Node Foundation |
| 91 | + |
| 92 | +**Voting Results**: |
| 93 | + |
| 94 | +* Fedor: 0 |
| 95 | +* Ben: +1 |
| 96 | +* Bert: +1 |
| 97 | +* Chris: +1 |
| 98 | +* Jeremiah: +1 |
| 99 | +* Trevor: +1 |
| 100 | +* Rod: +1 |
| 101 | + |
| 102 | +Action: Mikeal to make the move happen in a coordinated way so we get redirects and whatnot |
| 103 | + |
| 104 | +### Put `*Sync` methods behind a flag in some future major version [#1665](https://github.com/iojs/io.js/issues/1665) |
| 105 | + |
| 106 | +* Ben: some people feel that `fs.*Sync()` methods are harmful and would like to see them go away and be behind a flag |
| 107 | +* Bert: don’t agree with deprecating but agree with a flag |
| 108 | +* Rod: agree with Bert, but would like to see doc changes |
| 109 | +* Trevor: working on a flag to print a stack trace |
| 110 | + |
| 111 | +### TC Nominations |
| 112 | + |
| 113 | +* Shigeki Ohtsu @shigeki [#1501](https://github.com/iojs/io.js/issues/1501) |
| 114 | +* Brian White @mscdex [#1500](https://github.com/iojs/io.js/issues/1500) |
| 115 | +* @mikeal [#1481](https://github.com/iojs/io.js/issues/1481) |
| 116 | + |
| 117 | +* Mikeal: joining |
| 118 | +* Rod: timing is awkward with convergence but I’d like to make sure that Shigeki and Brian have a path to join the TC and not have that delayed too much |
| 119 | + |
| 120 | +### Public QA via #io.js channel on Freenode |
| 121 | + |
| 122 | +* `<therebelrobot> After the converged release, will io.js/node still be semver? for example, the history would be node 0.10, 0.12, iojs 1.x 2.x then the converged one would be node 3.x?` |
| 123 | + - Mikeal: the dev policy says so, there’s nobody advocating not to |
| 124 | +* `<evanlucas> Are there plans to symlink node to iojs in the installers after the first converged release?` |
| 125 | + - Bert: undecided. We should figure out a way to allow users to “node lts” and “node bleeding edge” side by side. |
| 126 | + - Mikeal: part of the above is covered by a thread in NG about localizing the node installation to global modules. |
| 127 | +* `<phpnode> will members of the core team be able to revive io.js if they disagree with the direction of the project in future` |
| 128 | + - (Group) Yes |
| 129 | +* `<skinan5> any plans for nan resolution?` |
| 130 | + - Rod: it’s just a header file and you need it for older versions of Node so it doesn’t make sense to _not_ use it from npm |
| 131 | + - Ben: current NAN isn’t suitable for bringing in |
| 132 | + - Trevor: would support bringing in something that would provide proper ABI support |
| 133 | + - Action: Trevor to open an issue on the NAN repo to talk about a stable C++ layer |
| 134 | + |
| 135 | +## Next meeting |
| 136 | + |
| 137 | +* May 20th, invite joyent/node TC members, figure out who that is and if this timeslot works for them when we have a combined call tomorrow (14th) |
0 commit comments