1berry/nodejs
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

doc: update links from iojs/io.js to nodejs/io.js

Browse Source 
Replaced all links in doc and comments to point to the new org.

PR-URL: https://github.com/nodejs/io.js/pull/1715
Reviewed-By: Roman Reiss <me@silverwind.io>
This commit is contained in:
Frederic Hemberger 2015-05-16 08:04:36 +02:00 committed by Roman Reiss
parent 7d90c90aaf
commit 066274794c
33 changed files with 1441 additions and 1441 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2210
CHANGELOG.md
View File

File diff suppressed because it is too large Load Diff

4
COLLABORATOR_GUIDE.md
View File

@ -96,7 +96,7 @@ information regarding the change process:
appropriate. appropriate.
See the commit log for examples such as See the commit log for examples such as
[this one](https://github.com/iojs/io.js/commit/b636ba8186) if unsure [this one](https://github.com/nodejs/io.js/commit/b636ba8186) if unsure
exactly how to format your commit messages. exactly how to format your commit messages.
Additionally: Additionally:
@ -132,7 +132,7 @@ $ git merge --ff-only origin/master
Apply external patches Apply external patches
```text ```text
$ curl -L https://github.com/iojs/io.js/pull/xxx.patch | git am --whitespace=fix $ curl -L https://github.com/nodejs/io.js/pull/xxx.patch | git am --whitespace=fix
``` ```
Check and re-review the changes Check and re-review the changes

8
CONTRIBUTING.md
View File

@ -23,13 +23,13 @@ This document will guide you through the contribution process.
### Step 1: Fork ### Step 1: Fork
Fork the project [on GitHub](https://github.com/iojs/io.js) and check out your Fork the project [on GitHub](https://github.com/nodejs/io.js) and check out your
copy locally. copy locally.
```text ```text
$ git clone git@github.com:username/io.js.git $ git clone git@github.com:username/io.js.git
$ cd io.js $ cd io.js
$ git remote add upstream git://github.com/iojs/io.js.git $ git remote add upstream git://github.com/nodejs/io.js.git
``` ```
#### Which branch? #### Which branch?
@ -54,8 +54,8 @@ in those directories or its subdirectories should be sent to their respective
projects. Do not send your patch to us, we cannot accept it. projects. Do not send your patch to us, we cannot accept it.
In case of doubt, open an issue in the In case of doubt, open an issue in the
[issue tracker](https://github.com/iojs/io.js/issues/) or contact one of the [issue tracker](https://github.com/nodejs/io.js/issues/) or contact one of the
[project Collaborators](https://github.com/iojs/io.js/#current-project-team-members) [project Collaborators](https://github.com/nodejs/io.js/#current-project-team-members)
([IRC](http://webchat.freenode.net/?channels=io.js) is often the best medium.)Especially do so if you plan to work on something big. Nothing is more ([IRC](http://webchat.freenode.net/?channels=io.js) is often the best medium.)Especially do so if you plan to work on something big. Nothing is more
frustrating than seeing your hard work go to waste because your vision frustrating than seeing your hard work go to waste because your vision
does not align with the project team. does not align with the project team.

2
GOVERNANCE.md
View File

@ -24,7 +24,7 @@ For the current list of TC members, see the project
## Collaborators ## Collaborators
The [iojs/io.js](https://github.com/iojs/io.js) GitHub repository is The [iojs/io.js](https://github.com/nodejs/io.js) GitHub repository is
maintained by the TC and additional Collaborators who are added by the maintained by the TC and additional Collaborators who are added by the
TC on an ongoing basis. TC on an ongoing basis.

4
README.md
View File

@ -1,7 +1,7 @@
io.js io.js
===== =====
[![Gitter](https://badges.gitter.im/Join Chat.svg)](https://gitter.im/iojs/io.js?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge) [![Gitter](https://badges.gitter.im/Join Chat.svg)](https://gitter.im/nodejs/io.js?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
This repository began as a GitHub fork of This repository began as a GitHub fork of
[joyent/node](https://github.com/joyent/node). [joyent/node](https://github.com/joyent/node).
@ -255,7 +255,7 @@ as `deps/icu` (You'll have: `deps/icu/source/...`)
* [GOVERNANCE.md](./GOVERNANCE.md) * [GOVERNANCE.md](./GOVERNANCE.md)
* IRC: * IRC:
[#io.js on Freenode.net](http://webchat.freenode.net?channels=io.js&uio=d4) [#io.js on Freenode.net](http://webchat.freenode.net?channels=io.js&uio=d4)
* [iojs/io.js on Gitter](https://gitter.im/iojs/io.js) * [iojs/io.js on Gitter](https://gitter.im/nodejs/io.js)

4
ROADMAP.md
View File

@ -54,13 +54,13 @@ Debugging is one of the first things from everyone's mouth, both developer and e
The goal of io.js' effort is to build a healthy debugging and tracing ecosystem and not to try and build any "silver bullet" features for core (like the domains debacle). The goal of io.js' effort is to build a healthy debugging and tracing ecosystem and not to try and build any "silver bullet" features for core (like the domains debacle).
The [Tracing WG](https://github.com/iojs/tracing-wg) is driving this effort: The [Tracing WG](https://github.com/nodejs/tracing-wg) is driving this effort:
* AsyncWrap improvements - basically just iterations based on feedback from people using it. * AsyncWrap improvements - basically just iterations based on feedback from people using it.
* async-listener - userland module that will dogfood AsyncWrap as well as provide many often requested debugging features. * async-listener - userland module that will dogfood AsyncWrap as well as provide many often requested debugging features.
* Tracing * Tracing
* Add tracing support for more platforms (LTTng, etc). * Add tracing support for more platforms (LTTng, etc).
* [Unify the Tracing endpoint](https://github.com/iojs/io.js/issues/729). * [Unify the Tracing endpoint](https://github.com/nodejs/io.js/issues/729).
* New Chrome Debugger - Google is working on a version of Chrome's debugger that is without Chrome and can be used with io.js. * New Chrome Debugger - Google is working on a version of Chrome's debugger that is without Chrome and can be used with io.js.
## Ecosystem Automation ## Ecosystem Automation

92
WORKING_GROUPS.md
View File

@ -1,7 +1,7 @@
# io.js Working Groups # io.js Working Groups
io.js Working Groups are autonomous projects created by the io.js Working Groups are autonomous projects created by the
[Technical Committee (TC)](https://github.com/iojs/io.js/blob/master/GOVERNANCE.md#technical-committee). [Technical Committee (TC)](https://github.com/nodejs/io.js/blob/master/GOVERNANCE.md#technical-committee).
Working Groups can be formed at any time but must be ratified by the TC. Working Groups can be formed at any time but must be ratified by the TC.
Once formed the work defined in the Working Group charter is the Once formed the work defined in the Working Group charter is the
@ -30,7 +30,7 @@ back in to the TC.
* [Starting a Working Group](#starting-a-wg) * [Starting a Working Group](#starting-a-wg)
* [Bootstrap Governance](#bootstrap-governance) * [Bootstrap Governance](#bootstrap-governance)
### [Website](https://github.com/iojs/website) ### [Website](https://github.com/nodejs/website)
The website working group's purpose is to build and maintain a public The website working group's purpose is to build and maintain a public
website for the `io.js` project. website for the `io.js` project.
@ -41,7 +41,7 @@ Its responsibilities are:
releases and features. releases and features.
* Foster and enable a community of translators. * Foster and enable a community of translators.
### [Streams](https://github.com/iojs/readable-stream) ### [Streams](https://github.com/nodejs/readable-stream)
The Streams WG is dedicated to the support and improvement of the Streams API The Streams WG is dedicated to the support and improvement of the Streams API
as used in io.js and the npm ecosystem. We seek to create a composable API that as used in io.js and the npm ecosystem. We seek to create a composable API that
@ -60,7 +60,7 @@ responsibilities include:
* Messaging about the future of streams to give the community advance notice of changes. * Messaging about the future of streams to give the community advance notice of changes.
### [Build](https://github.com/iojs/build) ### [Build](https://github.com/nodejs/build)
The build working group's purpose is to create and maintain a The build working group's purpose is to create and maintain a
distributed automation infrastructure. distributed automation infrastructure.
@ -72,7 +72,7 @@ Its responsibilities are:
* Creates and manages build-containers. * Creates and manages build-containers.
### [Tracing](https://github.com/iojs/tracing-wg) ### [Tracing](https://github.com/nodejs/tracing-wg)
The tracing working group's purpose is to increase the The tracing working group's purpose is to increase the
transparency of software written in io.js. transparency of software written in io.js.
@ -105,43 +105,43 @@ language.
Each language community maintains its own membership. Each language community maintains its own membership.
* [iojs-ar - Arabic (اللغة العربية)](http://github.com/iojs/iojs-ar) * [iojs-ar - Arabic (اللغة العربية)](https://github.com/nodejs/iojs-ar)
* [iojs-bg - Bulgarian (български език)](http://github.com/iojs/iojs-bg) * [iojs-bg - Bulgarian (български език)](https://github.com/nodejs/iojs-bg)
* [iojs-bn - Bengali (বাংলা)](http://github.com/iojs/iojs-bn) * [iojs-bn - Bengali (বাংলা)](https://github.com/nodejs/iojs-bn)
* [iojs-cn - Chinese (中文)](http://github.com/iojs/iojs-cn) * [iojs-cn - Chinese (中文)](https://github.com/nodejs/iojs-cn)
* [iojs-cs - Czech (Český Jazyk)](http://github.com/iojs/iojs-cs) * [iojs-cs - Czech (Český Jazyk)](https://github.com/nodejs/iojs-cs)
* [iojs-da - Danish (Dansk)](http://github.com/iojs/iojs-da) * [iojs-da - Danish (Dansk)](https://github.com/nodejs/iojs-da)
* [iojs-de - German (Deutsch)](http://github.com/iojs/iojs-de) * [iojs-de - German (Deutsch)](https://github.com/nodejs/iojs-de)
* [iojs-el - Greek (Ελληνικά)](http://github.com/iojs/iojs-el) * [iojs-el - Greek (Ελληνικά)](https://github.com/nodejs/iojs-el)
* [iojs-es - Spanish (Español)](http://github.com/iojs/iojs-es) * [iojs-es - Spanish (Español)](https://github.com/nodejs/iojs-es)
* [iojs-fa - Persian (فارسی)](http://github.com/iojs/iojs-fa) * [iojs-fa - Persian (فارسی)](https://github.com/nodejs/iojs-fa)
* [iojs-fi - Finnish (Suomi)](http://github.com/iojs/iojs-fi) * [iojs-fi - Finnish (Suomi)](https://github.com/nodejs/iojs-fi)
* [iojs-fr - French (Français)](http://github.com/iojs/iojs-fr) * [iojs-fr - French (Français)](https://github.com/nodejs/iojs-fr)
* [iojs-he - Hebrew (עברית)](http://github.com/iojs/iojs-he) * [iojs-he - Hebrew (עברית)](https://github.com/nodejs/iojs-he)
* [iojs-hi - Hindi (फिजी बात)](http://github.com/iojs/iojs-hi) * [iojs-hi - Hindi (फिजी बात)](https://github.com/nodejs/iojs-hi)
* [iojs-hu - Hungarian (Magyar)](http://github.com/iojs/iojs-hu) * [iojs-hu - Hungarian (Magyar)](https://github.com/nodejs/iojs-hu)
* [iojs-id - Indonesian (Bahasa Indonesia)](http://github.com/iojs/iojs-id) * [iojs-id - Indonesian (Bahasa Indonesia)](https://github.com/nodejs/iojs-id)
* [iojs-it - Italian (Italiano)](http://github.com/iojs/iojs-it) * [iojs-it - Italian (Italiano)](https://github.com/nodejs/iojs-it)
* [iojs-ja - Japanese (日本語)](http://github.com/iojs/iojs-ja) * [iojs-ja - Japanese (日本語)](https://github.com/nodejs/iojs-ja)
* [iojs-ka - Georgian (ქართული)](http://github.com/iojs/iojs-ka) * [iojs-ka - Georgian (ქართული)](https://github.com/nodejs/iojs-ka)
* [iojs-ko - Korean (조선말)](http://github.com/iojs/iojs-ko) * [iojs-ko - Korean (조선말)](https://github.com/nodejs/iojs-ko)
* [iojs-mk - Macedonian (Mакедонски)](http://github.com/iojs/iojs-mk) * [iojs-mk - Macedonian (Mакедонски)](https://github.com/nodejs/iojs-mk)
* [iojs-ms - Malay (بهاس ملايو)](http://github.com/iojs/iojs-ms) * [iojs-ms - Malay (بهاس ملايو)](https://github.com/nodejs/iojs-ms)
* [iojs-nl - Dutch (Nederlands)](http://github.com/iojs/iojs-nl) * [iojs-nl - Dutch (Nederlands)](https://github.com/nodejs/iojs-nl)
* [iojs-no - Norwegian (Norsk)](http://github.com/iojs/iojs-no) * [iojs-no - Norwegian (Norsk)](https://github.com/nodejs/iojs-no)
* [iojs-pl - Polish (Język Polski)](http://github.com/iojs/iojs-pl) * [iojs-pl - Polish (Język Polski)](https://github.com/nodejs/iojs-pl)
* [iojs-pt - Portuguese (Português)](http://github.com/iojs/iojs-pt) * [iojs-pt - Portuguese (Português)](https://github.com/nodejs/iojs-pt)
* [iojs-ro - Romanian (Română)](http://github.com/iojs/iojs-ro) * [iojs-ro - Romanian (Română)](https://github.com/nodejs/iojs-ro)
* [iojs-ru - Russian (Русский)](http://github.com/iojs/iojs-ru) * [iojs-ru - Russian (Русский)](https://github.com/nodejs/iojs-ru)
* [iojs-sv - Swedish (Svenska)](http://github.com/iojs/iojs-sv) * [iojs-sv - Swedish (Svenska)](https://github.com/nodejs/iojs-sv)
* [iojs-ta - Tamil (தமிழ்)](http://github.com/iojs/iojs-ta) * [iojs-ta - Tamil (தமிழ்)](https://github.com/nodejs/iojs-ta)
* [iojs-tr - Turkish (Türkçe)](http://github.com/iojs/iojs-tr) * [iojs-tr - Turkish (Türkçe)](https://github.com/nodejs/iojs-tr)
* [iojs-tw - Taiwanese (Hō-ló)](http://github.com/iojs/iojs-tw) * [iojs-tw - Taiwanese (Hō-ló)](https://github.com/nodejs/iojs-tw)
* [iojs-uk - Ukrainian (Українська)](http://github.com/iojs/iojs-uk) * [iojs-uk - Ukrainian (Українська)](https://github.com/nodejs/iojs-uk)
* [iojs-vi - Vietnamese (Tiếng Việtnam)](http://github.com/iojs/iojs-vi) * [iojs-vi - Vietnamese (Tiếng Việtnam)](https://github.com/nodejs/iojs-vi)
### [Evangelism](https://github.com/iojs/evangelism) ### [Evangelism](https://github.com/nodejs/evangelism)
The evangelism working group promotes the accomplishments The evangelism working group promotes the accomplishments
of io.js and lets the community know how they can get involved. of io.js and lets the community know how they can get involved.
@ -155,7 +155,7 @@ Their responsibilities are:
content. content.
### [Roadmap](https://github.com/iojs/roadmap) ### [Roadmap](https://github.com/nodejs/roadmap)
The roadmap working group is responsible for user community outreach The roadmap working group is responsible for user community outreach
and the translation of their concerns into a plan of action for io.js. and the translation of their concerns into a plan of action for io.js.
@ -169,7 +169,7 @@ Their responsibilities are:
* Create Pull Requests for relevant changes to [Roadmap.md](./ROADMAP.md) * Create Pull Requests for relevant changes to [Roadmap.md](./ROADMAP.md)
### [Docker](https://github.com/iojs/docker-iojs) ### [Docker](https://github.com/nodejs/docker-iojs)
The Docker working group's purpose is to build, maintain, and improve official The Docker working group's purpose is to build, maintain, and improve official
Docker images for the `io.js` project. Docker images for the `io.js` project.
@ -180,7 +180,7 @@ Their responsibilities are:
* Maintain and improve the images' documentation. * Maintain and improve the images' documentation.
### [Addon API](https://github.com/iojs/nan) ### [Addon API](https://github.com/nodejs/nan)
The Addon API Working Group is responsible for maintaining the NAN project and The Addon API Working Group is responsible for maintaining the NAN project and
corresponding _nan_ package in npm. The NAN project makes available an corresponding _nan_ package in npm. The NAN project makes available an
@ -190,9 +190,9 @@ versions of Node.js, io.js, V8 and libuv.
Their responsibilities are: Their responsibilities are:
* Maintaining the [NAN](https://github.com/iojs/nan) GitHub repository, * Maintaining the [NAN](https://github.com/nodejs/nan) GitHub repository,
including code, issues and documentation. including code, issues and documentation.
* Maintaining the [addon-examples](https://github.com/iojs/node-addon-examples) * Maintaining the [addon-examples](https://github.com/nodejs/node-addon-examples)
GitHub repository, including code, issues and documentation. GitHub repository, including code, issues and documentation.
* Maintaining the C++ Addon API within the io.js project, in subordination to * Maintaining the C++ Addon API within the io.js project, in subordination to
the io.js TC. the io.js TC.
@ -203,7 +203,7 @@ Their responsibilities are:
community advance notice of changes. community advance notice of changes.
The current members can be found in their The current members can be found in their
[README](https://github.com/iojs/nan#collaborators). [README](https://github.com/nodejs/nan#collaborators).
## Starting a WG ## Starting a WG

4
doc/releases.md
View File

@ -17,7 +17,7 @@ There are three relevant Jenkins jobs that should be used for a release flow:
**c.** **[iojs+release](https://jenkins-iojs.nodesource.com/job/iojs+release/)** does all of the work to build all required release assets. Promotion of the release files is a manual step once they are ready (see below). **c.** **[iojs+release](https://jenkins-iojs.nodesource.com/job/iojs+release/)** does all of the work to build all required release assets. Promotion of the release files is a manual step once they are ready (see below).
The [io.js build team](https://github.com/iojs/build) is able to provide this access to individuals authorized by the TC. The [io.js build team](https://github.com/nodejs/build) is able to provide this access to individuals authorized by the TC.
### 2. <iojs.org> Access ### 2. <iojs.org> Access
@ -27,7 +27,7 @@ The Jenkins release build slaves upload their artefacts to the web server as the
Nightly builds are promoted automatically on the server by a cron task for the _dist_ user. Nightly builds are promoted automatically on the server by a cron task for the _dist_ user.
Release builds require manual promotion by an individual with SSH access to the server as the _dist_ user. The [io.js build team](https://github.com/iojs/build) is able to provide this access to individuals authorized by the TC. Release builds require manual promotion by an individual with SSH access to the server as the _dist_ user. The [io.js build team](https://github.com/nodejs/build) is able to provide this access to individuals authorized by the TC.
### 3. A Publicly Listed GPG Key ### 3. A Publicly Listed GPG Key

42
doc/tc-meetings/2014-12-10.md
View File

@ -2,23 +2,23 @@
## Agenda ## Agenda
Extracted from https://github.com/iojs/io.js/labels/tc-agenda prior to meeting. Extracted from https://github.com/nodejs/io.js/labels/tc-agenda prior to meeting.
* @chrisdickinson nomination to TC https://github.com/iojs/io.js/issues/51 * @chrisdickinson nomination to TC https://github.com/nodejs/io.js/issues/51
* Move readable-stream to iojs org and make authoritative source for io.js to pull _from_ https://github.com/iojs/io.js/issues/55 * Move readable-stream to iojs org and make authoritative source for io.js to pull _from_ https://github.com/nodejs/io.js/issues/55
* Deprecate domains https://github.com/iojs/io.js/issues/66 * Deprecate domains https://github.com/nodejs/io.js/issues/66
* Decide how to go forward with caine https://github.com/iojs/io.js/issues/117 * Decide how to go forward with caine https://github.com/nodejs/io.js/issues/117
* Is it io.js, IO.js, or something else? https://github.com/iojs/io.js/issues/118 * Is it io.js, IO.js, or something else? https://github.com/nodejs/io.js/issues/118
* Build automation update * Build automation update
* extending options from a prototype * extending options from a prototype
https://github.com/iojs/io.js/issues/62 https://github.com/nodejs/io.js/issues/62
* Separate I/O tests from simple, so simple tests can be run in parallel * Separate I/O tests from simple, so simple tests can be run in parallel
* Statement / stance from TC on exposing a Promises API https://github.com/iojs/io.js/issues/11 * Statement / stance from TC on exposing a Promises API https://github.com/nodejs/io.js/issues/11
## Links ## Links
* **Google Hangouts Video**: https://www.youtube.com/watch?v=otE4IRMVUMo * **Google Hangouts Video**: https://www.youtube.com/watch?v=otE4IRMVUMo
* **GitHub Issue**: https://github.com/iojs/io.js/issues/112 * **GitHub Issue**: https://github.com/nodejs/io.js/issues/112
* **Original Minutes Google Doc**: https://www.youtube.com/watch?v=otE4IRMVUMo * **Original Minutes Google Doc**: https://www.youtube.com/watch?v=otE4IRMVUMo
## Minutes ## Minutes
@ -35,13 +35,13 @@ https://github.com/iojs/io.js/issues/62
### @chrisdickinson nomination to TC ### @chrisdickinson nomination to TC
https://github.com/iojs/io.js/issues/51 https://github.com/nodejs/io.js/issues/51
**Unanimous decision to add Chris to TC** **Unanimous decision to add Chris to TC**
### Move readable-stream to iojs org and make authoritative source for io.js to pull _from_ ### Move readable-stream to iojs org and make authoritative source for io.js to pull _from_
https://github.com/iojs/io.js/issues/55 https://github.com/nodejs/io.js/issues/55
* Chris expressed concerns on doing this, but a -0 for now, give it a go and see how it works * Chris expressed concerns on doing this, but a -0 for now, give it a go and see how it works
* Discussed the potential difference with joyent/node * Discussed the potential difference with joyent/node
@ -54,21 +54,21 @@ https://github.com/iojs/io.js/issues/55
### Deprecate domains ### Deprecate domains
https://github.com/iojs/io.js/issues/66 https://github.com/nodejs/io.js/issues/66
* Trevor: domains are horrible but we don’t have a good alternative yet * Trevor: domains are horrible but we don’t have a good alternative yet
* Ben: +1 on removal but don’t have a good story on what to tell people to use * Ben: +1 on removal but don’t have a good story on what to tell people to use
* Bert: -1, would rather clean up docs to be honest about how it doesn’t do what it was hoped to * Bert: -1, would rather clean up docs to be honest about how it doesn’t do what it was hoped to
* Trevor: domains inhibit progress because of their invasiveness * Trevor: domains inhibit progress because of their invasiveness
* Discussed how to document concerns etc. * Discussed how to document concerns etc.
* Discussed https://github.com/iojs/io.js/pull/15 which adjusts the domain.run() API * Discussed https://github.com/nodejs/io.js/pull/15 which adjusts the domain.run() API
* Agreed: * Agreed:
- Accept PR #15 - Accept PR #15
- **Document that domains are on the way out: soft deprecation** (no util.deprecate()) - **Document that domains are on the way out: soft deprecation** (no util.deprecate())
### Decide how to go forward with Caine (bot) ### Decide how to go forward with Caine (bot)
https://github.com/iojs/io.js/issues/117 https://github.com/nodejs/io.js/issues/117
* Fedor talked about _what_ caine is and _why_ it exists: too many emails from the repo, want to set up a system where relevant people are pulled into particular issues rather than having to subscribe to the repo for all notifications * Fedor talked about _what_ caine is and _why_ it exists: too many emails from the repo, want to set up a system where relevant people are pulled into particular issues rather than having to subscribe to the repo for all notifications
* Chris: primary concern with having an automated bot is the incoming experience for users (like having a join bot on IRC) * Chris: primary concern with having an automated bot is the incoming experience for users (like having a join bot on IRC)
@ -79,11 +79,11 @@ https://github.com/iojs/io.js/issues/117
### Is it io.js, IO.js, or something else? ### Is it io.js, IO.js, or something else?
https://github.com/iojs/io.js/issues/118 https://github.com/nodejs/io.js/issues/118
* Ben: lowercase is “objectively superior” (j/k) * Ben: lowercase is “objectively superior” (j/k)
* No disagreements, the name is “io.js” * No disagreements, the name is “io.js”
* Ben: binary name suggestion “iojs” with symlink to “node”, lots of discussion in https://github.com/iojs/io.js/issues/43 * Ben: binary name suggestion “iojs” with symlink to “node”, lots of discussion in https://github.com/nodejs/io.js/issues/43
* **No disagreements, binary name will be “iojs”** * **No disagreements, binary name will be “iojs”**
* Ben: how do we handle it on Windows? .bat file (problems with arg forwarding), small .exe * Ben: how do we handle it on Windows? .bat file (problems with arg forwarding), small .exe
* Agreed to open a new issue to discuss Windows compat (Ben) * Agreed to open a new issue to discuss Windows compat (Ben)
@ -91,16 +91,16 @@ https://github.com/iojs/io.js/issues/118
### Build automation update ### Build automation update
Rod gave a summary of build project status: Rod gave a summary of build project status:
- Containerized build system is being improved by an active team in the https://github.com/iojs/build-containers repo, on target to enable automatic PR tests and status reports back to GitHub (will likely just be Linux distros for the forseeable future) - Containerized build system is being improved by an active team in the https://github.com/nodejs/build-containers repo, on target to enable automatic PR tests and status reports back to GitHub (will likely just be Linux distros for the forseeable future)
- Next step is to enable committers to be able to trigger full builds across the build cluster - Next step is to enable committers to be able to trigger full builds across the build cluster
- Aiming for more automation for a mid-January release, have concerns about Windows and OSX signing and the need for signing keys and how complex they are. - Aiming for more automation for a mid-January release, have concerns about Windows and OSX signing and the need for signing keys and how complex they are.
- Chris Lea is working towards nightly builds for .deb-based systems (RHEL / Fedora based systems could come later but the assumption is that people running those systems are _less_ likely to want nightlies) - Chris Lea is working towards nightly builds for .deb-based systems (RHEL / Fedora based systems could come later but the assumption is that people running those systems are _less_ likely to want nightlies)
- https://github.com/iojs/io.js/issues/13 is an ARM build failure that still needs attention to have ARM part of the build mix and not constantly fail (see https://jenkins-node-forward.nodesource.com for some ARM failures) - https://github.com/nodejs/io.js/issues/13 is an ARM build failure that still needs attention to have ARM part of the build mix and not constantly fail (see https://jenkins-node-forward.nodesource.com for some ARM failures)
### Extending options from a prototype ### Extending options from a prototype
https://github.com/iojs/io.js/issues/62 https://github.com/nodejs/io.js/issues/62
* Chris is asking for input * Chris is asking for input
* Ben: we’re currently only looking at the object’s own properties, and ignoring properties on the prototype. * Ben: we’re currently only looking at the object’s own properties, and ignoring properties on the prototype.
@ -116,7 +116,7 @@ https://github.com/iojs/io.js/issues/62
### Statement / stance from TC on exposing a Promises API ### Statement / stance from TC on exposing a Promises API
https://github.com/iojs/io.js/issues/11 https://github.com/nodejs/io.js/issues/11
* Rod: can we come up with some kind of statement from the TC regarding the possibility of adding a Promises API to core, even if it’s vague * Rod: can we come up with some kind of statement from the TC regarding the possibility of adding a Promises API to core, even if it’s vague
* Bert: there’s a convergence of functionality around Promises that are making them more useful in conjunction with other ES6/ES7 features, TC should be _open_ to adding a Promises API in the future * Bert: there’s a convergence of functionality around Promises that are making them more useful in conjunction with other ES6/ES7 features, TC should be _open_ to adding a Promises API in the future
@ -132,7 +132,7 @@ https://github.com/iojs/io.js/issues/11
### Working with nvm, nvmw and similar installation managers ### Working with nvm, nvmw and similar installation managers
https://github.com/iojs/io.js/issues/40 https://github.com/nodejs/io.js/issues/40
* Ben: suggested a dist.iojs.org for hosting binaries * Ben: suggested a dist.iojs.org for hosting binaries
* Ben: suggested a release.txt * Ben: suggested a release.txt

16
doc/tc-meetings/2014-12-17.md
View File

@ -3,16 +3,16 @@
## Links ## Links
* **Google Hangouts Video**: https://www.youtube.com/watch?v=7s-VJLQEWXg * **Google Hangouts Video**: https://www.youtube.com/watch?v=7s-VJLQEWXg
* **GitHub Issue**: https://github.com/iojs/io.js/issues/163 * **GitHub Issue**: https://github.com/nodejs/io.js/issues/163
* **Original Minutes Google Doc**: https://docs.google.com/document/d/1PoqGfxpfTFKv5GcKmhMM2siZpPjT9Ba-ooBi-ZbYNi0 * **Original Minutes Google Doc**: https://docs.google.com/document/d/1PoqGfxpfTFKv5GcKmhMM2siZpPjT9Ba-ooBi-ZbYNi0
## Agenda ## Agenda
Extracted from https://github.com/iojs/io.js/labels/tc-agenda prior to meeting. Extracted from https://github.com/nodejs/io.js/labels/tc-agenda prior to meeting.
* Bundle tick processor with iojs #158 https://github.com/iojs/io.js/issues/158 * Bundle tick processor with iojs #158 https://github.com/nodejs/io.js/issues/158
* Release Cycle Proposal #168 https://github.com/iojs/io.js/issues/168 * Release Cycle Proposal #168 https://github.com/nodejs/io.js/issues/168
* Module search security #176 https://github.com/iojs/io.js/pull/176 * Module search security #176 https://github.com/nodejs/io.js/pull/176
* Dealing with feature requests * Dealing with feature requests
## Review of last meeting ## Review of last meeting
@ -37,7 +37,7 @@ Extracted from https://github.com/iojs/io.js/labels/tc-agenda prior to meeting.
### Bundle tick processor with iojs #158 ### Bundle tick processor with iojs #158
https://github.com/iojs/io.js/issues/158 https://github.com/nodejs/io.js/issues/158
* Bert: important because it’s tied to the version of V8, not practical to put it in npm because one is needed for each version * Bert: important because it’s tied to the version of V8, not practical to put it in npm because one is needed for each version
* Isaac: this is minimal and shouldn’t set a standard for just adding more stuff to core (i.e. keep core minimal), so +1 * Isaac: this is minimal and shouldn’t set a standard for just adding more stuff to core (i.e. keep core minimal), so +1
@ -46,7 +46,7 @@ https://github.com/iojs/io.js/issues/158
### Release Cycle Proposal #168 ### Release Cycle Proposal #168
https://github.com/iojs/io.js/issues/168 https://github.com/nodejs/io.js/issues/168
* Bert & Isaac discussed how this feeds into the ability to have frequent releases. Discussed semver plays into this. * Bert & Isaac discussed how this feeds into the ability to have frequent releases. Discussed semver plays into this.
* Rod: consensus seems to be around having stability, predictability, lead-time but more frequent releases. * Rod: consensus seems to be around having stability, predictability, lead-time but more frequent releases.
@ -54,7 +54,7 @@ https://github.com/iojs/io.js/issues/168
### Module search security #176 ### Module search security #176
https://github.com/iojs/io.js/pull/176 https://github.com/nodejs/io.js/pull/176
* Limiting node_modules search path to $HOME as a top-level * Limiting node_modules search path to $HOME as a top-level
* Isaac ~ -1 on this because EACCES already happens when you don’t have permission * Isaac ~ -1 on this because EACCES already happens when you don’t have permission

22
doc/tc-meetings/2014-12-30.md
View File

@ -3,17 +3,17 @@
## Links ## Links
* **Google Hangouts Video**: http://www.youtube.com/watch?v=O60sOsesjOo * **Google Hangouts Video**: http://www.youtube.com/watch?v=O60sOsesjOo
* **GitHub Issue**: https://github.com/iojs/io.js/issues/211 * **GitHub Issue**: https://github.com/nodejs/io.js/issues/211
* **Original Minutes Google Doc**: https://docs.google.com/document/d/1KLfX2MZQbVSIaD2lBVqOFK0Kap4uFz9cTGihnpTuvPE * **Original Minutes Google Doc**: https://docs.google.com/document/d/1KLfX2MZQbVSIaD2lBVqOFK0Kap4uFz9cTGihnpTuvPE
## Agenda ## Agenda
Extracted from https://github.com/iojs/io.js/labels/tc-agenda prior to meeting. Extracted from https://github.com/nodejs/io.js/labels/tc-agenda prior to meeting.
* sys: Remove after 3 years of deprecation #182 https://github.com/iojs/io.js/pull/182 * sys: Remove after 3 years of deprecation #182 https://github.com/nodejs/io.js/pull/182
* module: force require('process') to return a reference to process #206 https://github.com/iojs/io.js/pull/206 * module: force require('process') to return a reference to process #206 https://github.com/nodejs/io.js/pull/206
* File copyright policy #216 https://github.com/iojs/io.js/pull/216 * File copyright policy #216 https://github.com/nodejs/io.js/pull/216
* Rename v0.12 to v1.0.0 https://github.com/iojs/io.js/issues/218 * Rename v0.12 to v1.0.0 https://github.com/nodejs/io.js/issues/218
* Merge strategy (v0.10 and joyent/node) * Merge strategy (v0.10 and joyent/node)
## Minutes ## Minutes
@ -29,7 +29,7 @@ Extracted from https://github.com/iojs/io.js/labels/tc-agenda prior to meeting.
### sys: Remove after 3 years of deprecation #182 ### sys: Remove after 3 years of deprecation #182
https://github.com/iojs/io.js/pull/182 https://github.com/nodejs/io.js/pull/182
* Ben: what sort of strategy to take? Deprecated only in the docs but no warning. Looking for an official deprecation policy. * Ben: what sort of strategy to take? Deprecated only in the docs but no warning. Looking for an official deprecation policy.
* Bert: suggest we could properly deprecate but not a good case for removing it completely, Chris agreed * Bert: suggest we could properly deprecate but not a good case for removing it completely, Chris agreed
@ -44,9 +44,9 @@ https://github.com/iojs/io.js/pull/182
### module: force require('process') to return a reference to process #206 ### module: force require('process') to return a reference to process #206
https://github.com/iojs/io.js/pull/206 https://github.com/nodejs/io.js/pull/206
* #157 has a long discussion on this: https://github.com/iojs/io.js/issues/157 * #157 has a long discussion on this: https://github.com/nodejs/io.js/issues/157
* Chris: +1 on a PR adding this * Chris: +1 on a PR adding this
* Trevor: it just returns a global, no point * Trevor: it just returns a global, no point
* Bert: not the way that JS adds new features; discussed the new Intl addition to joyent/node, in favor of making more things requirable rather than adding new globals all the time * Bert: not the way that JS adds new features; discussed the new Intl addition to joyent/node, in favor of making more things requirable rather than adding new globals all the time
@ -62,14 +62,14 @@ https://github.com/iojs/io.js/pull/206
### File copyright policy #216 ### File copyright policy #216
https://github.com/iojs/io.js/pull/216 https://github.com/nodejs/io.js/pull/216
* Rod asked if there are any strong opinions about how to handle this * Rod asked if there are any strong opinions about how to handle this
* **Group agreed that Rod will take this issue and seek legal advice to find a way forward** * **Group agreed that Rod will take this issue and seek legal advice to find a way forward**
### Rename v0.12 to v1.0.0 ### Rename v0.12 to v1.0.0
https://github.com/iojs/io.js/issues/218 https://github.com/nodejs/io.js/issues/218
* Trevor: concerns about 1.0 vs 1.x branch naming with maintaining semver releases while also doing LTS, 1.x effectively becomes master until a 2.0 comes along. * Trevor: concerns about 1.0 vs 1.x branch naming with maintaining semver releases while also doing LTS, 1.x effectively becomes master until a 2.0 comes along.
* Bert: -1 * Bert: -1

26
doc/tc-meetings/2015-01-07.md
View File

@ -3,18 +3,18 @@
## Links ## Links
* **Google Hangouts Video**: http://www.youtube.com/watch?v=hWDSToC9EV8 * **Google Hangouts Video**: http://www.youtube.com/watch?v=hWDSToC9EV8
* **GitHub Issue**: https://github.com/iojs/io.js/issues/230 * **GitHub Issue**: https://github.com/nodejs/io.js/issues/230
* **Original Minutes Google Doc**: https://docs.google.com/document/d/1j7Sdui5DqHE8GZHxuoAaoIQ4jlntacZI285OCfVa-Eo * **Original Minutes Google Doc**: https://docs.google.com/document/d/1j7Sdui5DqHE8GZHxuoAaoIQ4jlntacZI285OCfVa-Eo
## Agenda ## Agenda
Extracted from https://github.com/iojs/io.js/labels/tc-agenda prior to meeting. Extracted from https://github.com/nodejs/io.js/labels/tc-agenda prior to meeting.
* Invite Colin Ihrig to the TC #223 https://github.com/iojs/io.js/issues/223 * Invite Colin Ihrig to the TC #223 https://github.com/nodejs/io.js/issues/223
* File copyright policy #216 https://github.com/iojs/io.js/issues/216 * File copyright policy #216 https://github.com/nodejs/io.js/issues/216
* Doc: clarified & split up contribution docs #233 https://github.com/iojs/io.js/pull/233 * Doc: clarified & split up contribution docs #233 https://github.com/nodejs/io.js/pull/233
* Governance: Add new Collaborators #234 https://github.com/iojs/io.js/issues/234 * Governance: Add new Collaborators #234 https://github.com/nodejs/io.js/issues/234
* deps: upgrade v8 to 3.31.74.1 #243 https://github.com/iojs/io.js/pull/243 * deps: upgrade v8 to 3.31.74.1 #243 https://github.com/nodejs/io.js/pull/243
* Build * Build
* Intl - defaults * Intl - defaults
* Merge v0.10 * Merge v0.10
@ -42,7 +42,7 @@ Extracted from https://github.com/iojs/io.js/labels/tc-agenda prior to meeting.
* colin: triaging issues in io.js and joyent/node. helping with merge of 0.12 to 0.10 * colin: triaging issues in io.js and joyent/node. helping with merge of 0.12 to 0.10
* isaac: no io.js, vacation * isaac: no io.js, vacation
* mikeal: nada * mikeal: nada
* rod: build build build ci ci ci. re-did all the build slaves on Jenkins, introduced a bunch more. Ansible scripts for linux machines (CentOS 5,6,7, Ubuntu all LTS + Current 14.10 +32bit versions, 2 ARM v7s one virtual one physical, 2 of each Windows 2012,2008, a couple interim OS X machines more permanent ones coming from Voxer soon). https://github.com/iojs/build Still lacking specific Jenkins setup and secrets. Working on release process. * rod: build build build ci ci ci. re-did all the build slaves on Jenkins, introduced a bunch more. Ansible scripts for linux machines (CentOS 5,6,7, Ubuntu all LTS + Current 14.10 +32bit versions, 2 ARM v7s one virtual one physical, 2 of each Windows 2012,2008, a couple interim OS X machines more permanent ones coming from Voxer soon). https://github.com/nodejs/build Still lacking specific Jenkins setup and secrets. Working on release process.
mikeal: issue re release? mikeal: issue re release?
rod: not yet, a lot of little bugs to get CI working consistently. No grand plan for what’s in release yet. rod: not yet, a lot of little bugs to get CI working consistently. No grand plan for what’s in release yet.
@ -57,7 +57,7 @@ Extracted from https://github.com/iojs/io.js/labels/tc-agenda prior to meeting.
### Invite Colin Ihrig to the TC #223 ### Invite Colin Ihrig to the TC #223
https://github.com/iojs/io.js/issues/223 https://github.com/nodejs/io.js/issues/223
Asked for vote Asked for vote
@ -67,7 +67,7 @@ Some discussion about TC member addition process
### File copyright policy #216 ### File copyright policy #216
https://github.com/iojs/io.js/issues/216 https://github.com/nodejs/io.js/issues/216
* Rod: got feedback from NodeSource GC on this, recommendation is to keep the copyright but removal of the license notice is acceptable * Rod: got feedback from NodeSource GC on this, recommendation is to keep the copyright but removal of the license notice is acceptable
* Mikeal & Isaac: removing the copyright should be OK because we have full git record of who made & edited the file, it’s a PITA * Mikeal & Isaac: removing the copyright should be OK because we have full git record of who made & edited the file, it’s a PITA
@ -77,7 +77,7 @@ https://github.com/iojs/io.js/issues/216
### Doc: clarified & split up contribution docs #233 ### Doc: clarified & split up contribution docs #233
https://github.com/iojs/io.js/pull/233 https://github.com/nodejs/io.js/pull/233
* Rod: discussed changes introduced in #233, this is in TC because there are some minor modifications to the governance structure. Recommended that we deal with further changes to governance as a separate discussion. * Rod: discussed changes introduced in #233, this is in TC because there are some minor modifications to the governance structure. Recommended that we deal with further changes to governance as a separate discussion.
* Fedor: remove caine block from CONTRIBUTING.md * Fedor: remove caine block from CONTRIBUTING.md
@ -87,7 +87,7 @@ https://github.com/iojs/io.js/pull/233
### Governance: Add new Collaborators #234 ### Governance: Add new Collaborators #234
https://github.com/iojs/io.js/issues/234 https://github.com/nodejs/io.js/issues/234
Rod discussed the generation of the list of proposed collaborators. Rod discussed the generation of the list of proposed collaborators.
@ -107,7 +107,7 @@ Long discussion:
### deps: upgrade v8 to 3.31.74.1 #243 ### deps: upgrade v8 to 3.31.74.1 #243
https://github.com/iojs/io.js/pull/243 https://github.com/nodejs/io.js/pull/243
* Ben: clean compile, apparently a clean upgrade. It does break postmortem support so Ben removed it completely. Asked who was using it. * Ben: clean compile, apparently a clean upgrade. It does break postmortem support so Ben removed it completely. Asked who was using it.
* Ben: adds new features: * Ben: adds new features:

34
doc/tc-meetings/2015-01-13.md
View File

@ -3,16 +3,16 @@
## Links ## Links
* **Google Hangouts Video**: http://www.youtube.com/watch?v=Z0KHYPlFI3E * **Google Hangouts Video**: http://www.youtube.com/watch?v=Z0KHYPlFI3E
* **GitHub Issue**: https://github.com/iojs/io.js/issues/300 * **GitHub Issue**: https://github.com/nodejs/io.js/issues/300
* **Original Minutes Google Doc**: https://docs.google.com/document/d/1HDUayYxTjolYZhu_hGm9hc-6MGAwWrHlNGT2Zo708ck * **Original Minutes Google Doc**: https://docs.google.com/document/d/1HDUayYxTjolYZhu_hGm9hc-6MGAwWrHlNGT2Zo708ck
## Agenda ## Agenda
Extracted from https://github.com/iojs/io.js/labels/tc-agenda prior to meeting. Extracted from https://github.com/nodejs/io.js/labels/tc-agenda prior to meeting.
* File copyright policy #216 https://github.com/iojs/io.js/issues/216 * File copyright policy #216 https://github.com/nodejs/io.js/issues/216
* governance: Add new Collaborators #234 https://github.com/iojs/io.js/issues/234 * governance: Add new Collaborators #234 https://github.com/nodejs/io.js/issues/234
* The state of ES6 on io.js _(re V8 upgrade policy)_ #251 https://github.com/iojs/io.js/issues/251 * The state of ES6 on io.js _(re V8 upgrade policy)_ #251 https://github.com/nodejs/io.js/issues/251
Quick recap: Quick recap:
- Whether if it is ok to release 1.0.0 with V8 3.31.74 minus ES6 Classes and Object Literals Extensions, considering that the initial version of io.js will be "beta" quality and probably the stable version will coincide with the stable release of V8 3.31 (~6 weeks), which will have these features reinstated. - Whether if it is ok to release 1.0.0 with V8 3.31.74 minus ES6 Classes and Object Literals Extensions, considering that the initial version of io.js will be "beta" quality and probably the stable version will coincide with the stable release of V8 3.31 (~6 weeks), which will have these features reinstated.
- How to handle V8 updates with semver so that if the same issue arised with a different timing it could mean a bump to 2.0.0. - How to handle V8 updates with semver so that if the same issue arised with a different timing it could mean a bump to 2.0.0.
@ -20,7 +20,7 @@ Extracted from https://github.com/iojs/io.js/labels/tc-agenda prior to meeting.
* Different version naming (e.g. 1.x+v8beta, 1.x+v8dev, 1.x+v8canary) * Different version naming (e.g. 1.x+v8beta, 1.x+v8dev, 1.x+v8canary)
* Avoid BC by moving from tip-of-stable-Chrome-branch to the next tip-of-stable-Chrome-branch (~6 weeks release cycle) * Avoid BC by moving from tip-of-stable-Chrome-branch to the next tip-of-stable-Chrome-branch (~6 weeks release cycle)
- How do nightly builds fit into the process. - How do nightly builds fit into the process.
* 1.0.0 release checklist https://github.com/iojs/io.js/issues/302 * 1.0.0 release checklist https://github.com/nodejs/io.js/issues/302
## Minutes ## Minutes
@ -42,25 +42,25 @@ Extracted from https://github.com/iojs/io.js/labels/tc-agenda prior to meeting.
### Review of last meeting ### Review of last meeting
* Invite Colin Ihrig to the TC #223 https://github.com/iojs/io.js/issues/223 * Invite Colin Ihrig to the TC #223 https://github.com/nodejs/io.js/issues/223
* File copyright policy #216 https://github.com/iojs/io.js/issues/216 * File copyright policy #216 https://github.com/nodejs/io.js/issues/216
* Doc: clarified & split up contribution docs #233 https://github.com/iojs/io.js/pull/233 * Doc: clarified & split up contribution docs #233 https://github.com/nodejs/io.js/pull/233
* Governance: Add new Collaborators #234 https://github.com/iojs/io.js/issues/234 * Governance: Add new Collaborators #234 https://github.com/nodejs/io.js/issues/234
* deps: upgrade v8 to 3.31.74.1 #243 https://github.com/iojs/io.js/pull/243 * deps: upgrade v8 to 3.31.74.1 #243 https://github.com/nodejs/io.js/pull/243
* Build & release (& Intl) * Build & release (& Intl)
### File copyright policy #216 ### File copyright policy #216
https://github.com/iojs/io.js/issues/216 https://github.com/nodejs/io.js/issues/216
Rod: prepared a proposed new LICENSE file, needed for release, adds a new license block for io.js at the top, shifts the Joyent copyright block down but still acknowledges their claim on inherited work. https://github.com/iojs/io.js/pull/294 Rod: prepared a proposed new LICENSE file, needed for release, adds a new license block for io.js at the top, shifts the Joyent copyright block down but still acknowledges their claim on inherited work. https://github.com/nodejs/io.js/pull/294
Group agreed to merge for now until a better (or more legally appropriate) solution is proposed. Group agreed to merge for now until a better (or more legally appropriate) solution is proposed.
### governance: Add new Collaborators #234 ### governance: Add new Collaborators #234
https://github.com/iojs/io.js/issues/234 https://github.com/nodejs/io.js/issues/234
Rod asked if we should punt to next meeting since the group was small and we’re 1.0.0 obsessed. Rod asked if we should punt to next meeting since the group was small and we’re 1.0.0 obsessed.
@ -68,7 +68,7 @@ Group agreed.
### The state of ES6 on io.js _(re V8 upgrade policy)_ #251 ### The state of ES6 on io.js _(re V8 upgrade policy)_ #251
https://github.com/iojs/io.js/issues/251 https://github.com/nodejs/io.js/issues/251
Rod: this is about V8 version matching and V8 version stability. We’re going live with 3.31. Rod: this is about V8 version matching and V8 version stability. We’re going live with 3.31.
@ -78,7 +78,7 @@ Group agreed to stick with 3.31, too late to do otherwise. Come up with a more s
### v1.0.0 release checklist ### v1.0.0 release checklist
https://github.com/iojs/io.js/issues/302 https://github.com/nodejs/io.js/issues/302
* Rod will land LICENSE change after meeting * Rod will land LICENSE change after meeting
* Bert spoke about the v0.10 and the things that remain unmerged * Bert spoke about the v0.10 and the things that remain unmerged
@ -88,7 +88,7 @@ https://github.com/iojs/io.js/issues/302
- re timers slowness - Bert and Ben don’t like the 0.10 fix, need to find our own - not landing in 1.0.0, probably our own fix in 1.0.1 - re timers slowness - Bert and Ben don’t like the 0.10 fix, need to find our own - not landing in 1.0.0, probably our own fix in 1.0.1
* Bert spoke about node.exe, has code for it but it’s crashy, could release with a symlink for 1.0.0. Asked for input on the approach. * Bert spoke about node.exe, has code for it but it’s crashy, could release with a symlink for 1.0.0. Asked for input on the approach.
* Discussed node-gyp - Ben to PR node-gyp (and maybe land a modified version in io.js codebase) for iojs.org/dist/vx.y.z/... for source tarball. * Discussed node-gyp - Ben to PR node-gyp (and maybe land a modified version in io.js codebase) for iojs.org/dist/vx.y.z/... for source tarball.
- discussed process.versions.iojs property, https://github.com/iojs/io.js/issues/269 - group agreed to do nothing on this. Rod to find discussion or create issue to have discussion on this. - discussed process.versions.iojs property, https://github.com/nodejs/io.js/issues/269 - group agreed to do nothing on this. Rod to find discussion or create issue to have discussion on this.
- discussed visual assets not being in the repo, currently copied by CI manually into src, Rod to land a PR with them - discussed visual assets not being in the repo, currently copied by CI manually into src, Rod to land a PR with them
* Rod: Changelog, we don’t have one. * Rod: Changelog, we don’t have one.
- https://github.com/joyent/node/wiki/API-changes-between-v0.10-and-v0.12 - https://github.com/joyent/node/wiki/API-changes-between-v0.10-and-v0.12

26
doc/tc-meetings/2015-01-21.md
View File

@ -3,18 +3,18 @@
## Links ## Links
* **Google Hangouts Video**: http://www.youtube.com/watch?v=OUoWlIshY9s * **Google Hangouts Video**: http://www.youtube.com/watch?v=OUoWlIshY9s
* **GitHub Issue**: https://github.com/iojs/io.js/issues/509 * **GitHub Issue**: https://github.com/nodejs/io.js/issues/509
* **Original Minutes Google Doc**: https://docs.google.com//document/d/1yOS17cUt7QUHJXxdVmEpS1ZS_N32HMO9QTHb2qL-KHk * **Original Minutes Google Doc**: https://docs.google.com//document/d/1yOS17cUt7QUHJXxdVmEpS1ZS_N32HMO9QTHb2qL-KHk
## Agenda ## Agenda
Extracted from https://github.com/iojs/io.js/labels/tc-agenda prior to meeting. Extracted from https://github.com/nodejs/io.js/labels/tc-agenda prior to meeting.
* Invite Domenic Denicola to the TC Meetings (https://github.com/iojs/io.js/issues/403) * Invite Domenic Denicola to the TC Meetings (https://github.com/nodejs/io.js/issues/403)
* Governance: Add new collaborators (https://github.com/iojs/io.js/issues/234) * Governance: Add new collaborators (https://github.com/nodejs/io.js/issues/234)
* Stabilization and Release Cycles and Process (https://github.com/iojs/io.js/issues/405) * Stabilization and Release Cycles and Process (https://github.com/nodejs/io.js/issues/405)
* also: the state of ES6 on io.js (re: V8 upgrade policy) (https://github.com/iojs/io.js/issues/251) * also: the state of ES6 on io.js (re: V8 upgrade policy) (https://github.com/nodejs/io.js/issues/251)
* doc: bump punycode api stability to ‘stable’ (https://github.com/iojs/io.js/issues/470) * doc: bump punycode api stability to ‘stable’ (https://github.com/nodejs/io.js/issues/470)
* Working group reports * Working group reports
* Streams * Streams
* Website * Website
@ -59,13 +59,13 @@ Extracted from https://github.com/iojs/io.js/labels/tc-agenda prior to meeting.
### Invite Domenic Denicola to the TC Meetings ### Invite Domenic Denicola to the TC Meetings
(https://github.com/iojs/io.js/issues/403) (https://github.com/nodejs/io.js/issues/403)
Enough agreement on GitHub and in private communications amongst TC. **Done.** Enough agreement on GitHub and in private communications amongst TC. **Done.**
### Governance: Add new collaborators ### Governance: Add new collaborators
(https://github.com/iojs/io.js/issues/234) (https://github.com/nodejs/io.js/issues/234)
* Mikeal: Proposed Chris leads an onboarding process, do a Hangout with a group of people from the original list who are willing to go through the process and take them in the first week and iterate from there. * Mikeal: Proposed Chris leads an onboarding process, do a Hangout with a group of people from the original list who are willing to go through the process and take them in the first week and iterate from there.
* Bert: +1 for an onboarding process, more interested in handing out voting rights to a larger group. * Bert: +1 for an onboarding process, more interested in handing out voting rights to a larger group.
@ -86,7 +86,7 @@ Passed
### Stabilization and Release Cycles and Process ### Stabilization and Release Cycles and Process
(https://github.com/iojs/io.js/issues/405) (https://github.com/nodejs/io.js/issues/405)
#### V8 #### V8
@ -129,13 +129,13 @@ Passed
### also: the state of ES6 on io.js (re: V8 upgrade policy) ### also: the state of ES6 on io.js (re: V8 upgrade policy)
(https://github.com/iojs/io.js/issues/251) (https://github.com/nodejs/io.js/issues/251)
Part of previous discussion Part of previous discussion
### doc: bump punycode api stability to ‘stable’ ### doc: bump punycode api stability to ‘stable’
(https://github.com/iojs/io.js/issues/470) (https://github.com/nodejs/io.js/issues/470)
* **Agreement** * **Agreement**
@ -144,7 +144,7 @@ Part of previous discussion
* Mikeal and Chris to semi-formalise the model * Mikeal and Chris to semi-formalise the model
* Mikeal: 6 people actively engaged and growing, “could not be going better” * Mikeal: 6 people actively engaged and growing, “could not be going better”
* Chris: streams group has initial set of members, some discussions going on, first meeting pending * Chris: streams group has initial set of members, some discussions going on, first meeting pending
* initial set of members: https://github.com/iojs/readable-stream/issues/97#issuecomment-70399923 * initial set of members: https://github.com/nodejs/readable-stream/issues/97#issuecomment-70399923
* Rod: * Rod:
- The Docker sub-group is going great and has even got the docker-iojs images accepted as the official Docker "iojs" images. - The Docker sub-group is going great and has even got the docker-iojs images accepted as the official Docker "iojs" images.
- Other "build" efforts are all release-focused for now, trying to streamline the process to make it possible to have multiple people able to cut releases. - Other "build" efforts are all release-focused for now, trying to streamline the process to make it possible to have multiple people able to cut releases.

58
doc/tc-meetings/2015-01-28.md
View File

@ -3,23 +3,23 @@
## Links ## Links
* **Google Hangouts Video**: http://www.youtube.com/watch?v=k27NObxy0ps * **Google Hangouts Video**: http://www.youtube.com/watch?v=k27NObxy0ps
* **GitHub Issue**: https://github.com/iojs/io.js/issues/565 * **GitHub Issue**: https://github.com/nodejs/io.js/issues/565
* **Original Minutes Google Doc**: https://docs.google.com/document/d/1IIfubVivCORgP0nQfo8Mf4gXhwBrndRm9cwmNGBXmtE * **Original Minutes Google Doc**: https://docs.google.com/document/d/1IIfubVivCORgP0nQfo8Mf4gXhwBrndRm9cwmNGBXmtE
## Agenda ## Agenda
Extracted from https://github.com/iojs/io.js/labels/tc-agenda prior to meeting. Extracted from https://github.com/nodejs/io.js/labels/tc-agenda prior to meeting.
* governance: Add new Collaborators [#234](https://github.com/iojs/io.js/issues/234) / feedback and more contribs / @chrisdickinson * governance: Add new Collaborators [#234](https://github.com/nodejs/io.js/issues/234) / feedback and more contribs / @chrisdickinson
* Stabilization and Release Cycles and Process [#405](https://github.com/iojs/io.js/issues/405) / further discussion / @iojs/tc * Stabilization and Release Cycles and Process [#405](https://github.com/nodejs/io.js/issues/405) / further discussion / @iojs/tc
- doc: add releases document detail release cycle [#630](https://github.com/iojs/io.js/issues/630) / proposal from @chrisdickinson - doc: add releases document detail release cycle [#630](https://github.com/nodejs/io.js/issues/630) / proposal from @chrisdickinson
* dgram: implicit binds should be exclusive [#325](https://github.com/iojs/io.js/issues/325) / minor version bump / @bnoordhuis * dgram: implicit binds should be exclusive [#325](https://github.com/nodejs/io.js/issues/325) / minor version bump / @bnoordhuis
* buffer: implement `iterable` interface [#525](https://github.com/iojs/io.js/issues/525) / minor version bump / @bnoordhuis * buffer: implement `iterable` interface [#525](https://github.com/nodejs/io.js/issues/525) / minor version bump / @bnoordhuis
* replace util.isType() with typeof [#607](https://github.com/iojs/io.js/issues/607) / general use of util.is*() in core re perf * replace util.isType() with typeof [#607](https://github.com/nodejs/io.js/issues/607) / general use of util.is*() in core re perf
* docs: lower the maximum stability level to "stable" [#633](https://github.com/iojs/io.js/pull/633) * docs: lower the maximum stability level to "stable" [#633](https://github.com/nodejs/io.js/pull/633)
* maintain our own package registries for io.js related packages [#640](https://github.com/iojs/io.js/issues/640#issuecomment-71882645) * maintain our own package registries for io.js related packages [#640](https://github.com/nodejs/io.js/issues/640#issuecomment-71882645)
* Working Groups PR [#599](https://github.com/iojs/io.js/pull/599) * Working Groups PR [#599](https://github.com/nodejs/io.js/pull/599)
* Remove “unstable” from messaging [#108](https://github.com/iojs/website/issues/108) * Remove “unstable” from messaging [#108](https://github.com/nodejs/website/issues/108)
## Minutes ## Minutes
@ -52,11 +52,11 @@ Apologies from:
### Review of last meeting ### Review of last meeting
* Invite Domenic Denicola to the TC Meetings (https://github.com/iojs/io.js/issues/403) * Invite Domenic Denicola to the TC Meetings (https://github.com/nodejs/io.js/issues/403)
* Governance: Add new collaborators (https://github.com/iojs/io.js/issues/234) * Governance: Add new collaborators (https://github.com/nodejs/io.js/issues/234)
* Stabilization and Release Cycles and Process (https://github.com/iojs/io.js/issues/405) * Stabilization and Release Cycles and Process (https://github.com/nodejs/io.js/issues/405)
* also: the state of ES6 on io.js (re: V8 upgrade policy) (https://github.com/iojs/io.js/issues/251) * also: the state of ES6 on io.js (re: V8 upgrade policy) (https://github.com/nodejs/io.js/issues/251)
* doc: bump punycode api stability to ‘stable’ (https://github.com/iojs/io.js/issues/470) * doc: bump punycode api stability to ‘stable’ (https://github.com/nodejs/io.js/issues/470)
* Working group reports * Working group reports
* Streams * Streams
* Website * Website
@ -64,7 +64,7 @@ Apologies from:
### governance: Add new Collaborators ### governance: Add new Collaborators
[#234](https://github.com/iojs/io.js/issues/234) / feedback and more contribs / @chrisdickinson [#234](https://github.com/nodejs/io.js/issues/234) / feedback and more contribs / @chrisdickinson
* Chris: Onboarded 2 groups of 4 new collaborators last week. (first group: @vkurchatkin, @micnic, @seishun, @brendanashworth, second group: @evanlucas, @Fishrock123, @Qard, @thlorenz) * Chris: Onboarded 2 groups of 4 new collaborators last week. (first group: @vkurchatkin, @micnic, @seishun, @brendanashworth, second group: @evanlucas, @Fishrock123, @Qard, @thlorenz)
- 30 min summary of how everything works, gov, git, etc. - 30 min summary of how everything works, gov, git, etc.
@ -76,13 +76,13 @@ Apologies from:
### Stabilization and Release Cycles and Process ### Stabilization and Release Cycles and Process
[#405](https://github.com/iojs/io.js/issues/405) / further discussion / @iojs/tc [#405](https://github.com/nodejs/io.js/issues/405) / further discussion / @iojs/tc
***Also:*** doc: add releases document detail release cycle [#630](https://github.com/iojs/io.js/issues/630) / proposal from @chrisdickinson ***Also:*** doc: add releases document detail release cycle [#630](https://github.com/nodejs/io.js/issues/630) / proposal from @chrisdickinson
Moved straight to Chris’ proposal: Moved straight to Chris’ proposal:
* Chris discussed thoughts in his proposal @ https://github.com/iojs/io.js/issues/630 * Chris discussed thoughts in his proposal @ https://github.com/nodejs/io.js/issues/630
* Mikeal: would rather not have a static number/list of supported versions, let that be dynamic as people & companies step up to help support them * Mikeal: would rather not have a static number/list of supported versions, let that be dynamic as people & companies step up to help support them
* Ben: “stable” and “next” would be easiest to reason about * Ben: “stable” and “next” would be easiest to reason about
* Chris: “dev” is for ad-hoc semver releases, replaces nightlies with a better train system. * Chris: “dev” is for ad-hoc semver releases, replaces nightlies with a better train system.
@ -94,19 +94,19 @@ Moved straight to Chris’ proposal:
### dgram: implicit binds should be exclusive ### dgram: implicit binds should be exclusive
[#325](https://github.com/iojs/io.js/issues/325) / minor version bump / @bnoordhuis [#325](https://github.com/nodejs/io.js/issues/325) / minor version bump / @bnoordhuis
* Ben: this is about minor version bump, that’s been decided and we’re doing a 1.1.0 so this is being merged and released * Ben: this is about minor version bump, that’s been decided and we’re doing a 1.1.0 so this is being merged and released
### buffer: implement `iterable` interface ### buffer: implement `iterable` interface
[#525](https://github.com/iojs/io.js/issues/525) / minor version bump / @bnoordhuis [#525](https://github.com/nodejs/io.js/issues/525) / minor version bump / @bnoordhuis
* Ben: same as previous issue, resolved * Ben: same as previous issue, resolved
### replace util.isType() with typeof ### replace util.isType() with typeof
[#607](https://github.com/iojs/io.js/issues/607) / general use of util.is*() in core re perf [#607](https://github.com/nodejs/io.js/issues/607) / general use of util.is*() in core re perf
* Bert: find with direct comparisons and checks where it makes sense (undefined, simple stuff) * Bert: find with direct comparisons and checks where it makes sense (undefined, simple stuff)
* Isaac: hate it all, they are difficult to inline so manually inline--pick one and use it across all * Isaac: hate it all, they are difficult to inline so manually inline--pick one and use it across all
@ -124,7 +124,7 @@ Moved straight to Chris’ proposal:
### docs: lower the maximum stability level to "stable" ### docs: lower the maximum stability level to "stable"
[#633](https://github.com/iojs/io.js/issues/633) [#633](https://github.com/nodejs/io.js/issues/633)
* General disagreement about this * General disagreement about this
* Mikeal suggested moving things that are likely to change into vendored packages (like streams) * Mikeal suggested moving things that are likely to change into vendored packages (like streams)
@ -135,14 +135,14 @@ Moved straight to Chris’ proposal:
### maintain our own package registries for io.js related packages ### maintain our own package registries for io.js related packages
[#640](https://github.com/iojs/io.js/issues/640) [#640](https://github.com/nodejs/io.js/issues/640)
* Mikeal: each distro (Homebrew, Debian, etc.) has their own conception of “stable”, suggestion is to maintain them under io.js and instruct people how to do this. e.g. using our own custom Homebrew end-point and instruct people how to use it with `brew`. Also could bring in complicated packages from the community. * Mikeal: each distro (Homebrew, Debian, etc.) has their own conception of “stable”, suggestion is to maintain them under io.js and instruct people how to do this. e.g. using our own custom Homebrew end-point and instruct people how to use it with `brew`. Also could bring in complicated packages from the community.
* Mikeal: Should come under the Build WG for now, ideally a single repo where external projects can put in a single PR to update their stuff. * Mikeal: Should come under the Build WG for now, ideally a single repo where external projects can put in a single PR to update their stuff.
### Working Groups PR ### Working Groups PR
[#599](https://github.com/iojs/io.js/issues/599) [#599](https://github.com/nodejs/io.js/issues/599)
* Mikeal introduced his proposal: if you’re going to do the work in a WG then you can spin that up as a separate concern * Mikeal introduced his proposal: if you’re going to do the work in a WG then you can spin that up as a separate concern
* Ben asked for clarification about whether WGs get a free-pass in core * Ben asked for clarification about whether WGs get a free-pass in core
@ -153,7 +153,7 @@ Moved straight to Chris’ proposal:
### Remove “unstable” from messaging ### Remove “unstable” from messaging
[#108](https://github.com/iojs/io.js/issues/108) [#108](https://github.com/nodejs/io.js/issues/108)
* Remove “unstable” from the website but not say it’s “stable” * Remove “unstable” from the website but not say it’s “stable”
* Bert: big +1, use semver, don’t try and message something else, only concern is the version of V8 we are using * Bert: big +1, use semver, don’t try and message something else, only concern is the version of V8 we are using
@ -161,7 +161,7 @@ Moved straight to Chris’ proposal:
### Node.js and io.js should not break each other (no, they shouldn't) ### Node.js and io.js should not break each other (no, they shouldn't)
[#631](https://github.com/iojs/io.js/issues/631) [#631](https://github.com/nodejs/io.js/issues/631)
Rod brought this up for quick discussion and draw attention to TC members for possible input. Rod brought this up for quick discussion and draw attention to TC members for possible input.
* Mikeal suggested that this should be taken to the website WG for better documentation * Mikeal suggested that this should be taken to the website WG for better documentation

42
doc/tc-meetings/2015-02-04.md
View File

@ -3,16 +3,16 @@
## Links ## Links
* **Google Hangouts Video**: http://www.youtube.com/watch?v=k27NObxy0ps * **Google Hangouts Video**: http://www.youtube.com/watch?v=k27NObxy0ps
* **GitHub Issue**: https://github.com/iojs/io.js/issues/509 * **GitHub Issue**: https://github.com/nodejs/io.js/issues/509
* **Original Minutes Google Doc**: https://docs.google.com/document/d/1IIfubVivCORgP0nQfo8Mf4gXhwBrndRm9cwmNGBXmtE * **Original Minutes Google Doc**: https://docs.google.com/document/d/1IIfubVivCORgP0nQfo8Mf4gXhwBrndRm9cwmNGBXmtE
## Agenda ## Agenda
Extracted from https://github.com/iojs/io.js/labels/tc-agenda prior to meeting. Extracted from https://github.com/nodejs/io.js/labels/tc-agenda prior to meeting.
* assert: don't compare object `prototype` property [#636](https://github.com/iojs/io.js/pull/636) _and_ assert: introduce `deepStrictEqual` [#639](https://github.com/iojs/io.js/pull/639) / @vkurchatkin * assert: don't compare object `prototype` property [#636](https://github.com/nodejs/io.js/pull/636) _and_ assert: introduce `deepStrictEqual` [#639](https://github.com/nodejs/io.js/pull/639) / @vkurchatkin
* Release PGP key strategy and policy [#709](https://github.com/iojs/io.js/issues/709) * Release PGP key strategy and policy [#709](https://github.com/nodejs/io.js/issues/709)
* If time: vm bugs? [#548](https://github.com/iojs/io.js/issues/548), [joyent/node#9084](https://github.com/joyent/node/issues/9084) * If time: vm bugs? [#548](https://github.com/nodejs/io.js/issues/548), [joyent/node#9084](https://github.com/joyent/node/issues/9084)
## Minutes ## Minutes
### Present ### Present
@ -41,16 +41,16 @@ Extracted from https://github.com/iojs/io.js/labels/tc-agenda prior to meeting.
### Review of last meeting ### Review of last meeting
* governance: Add new Collaborators [#234](https://github.com/iojs/io.js/issues/234) / feedback and more contribs / @chrisdickinson * governance: Add new Collaborators [#234](https://github.com/nodejs/io.js/issues/234) / feedback and more contribs / @chrisdickinson
* Stabilization and Release Cycles and Process [#405](https://github.com/iojs/io.js/issues/405) / further discussion / @iojs/tc * Stabilization and Release Cycles and Process [#405](https://github.com/nodejs/io.js/issues/405) / further discussion / @iojs/tc
- doc: add releases document detail release cycle [#630](https://github.com/iojs/io.js/issues/630) / proposal from @chrisdickinson - doc: add releases document detail release cycle [#630](https://github.com/nodejs/io.js/issues/630) / proposal from @chrisdickinson
* dgram: implicit binds should be exclusive [#325](https://github.com/iojs/io.js/issues/325) / minor version bump / @bnoordhuis * dgram: implicit binds should be exclusive [#325](https://github.com/nodejs/io.js/issues/325) / minor version bump / @bnoordhuis
* buffer: implement `iterable` interface [#525](https://github.com/iojs/io.js/issues/525) / minor version bump / @bnoordhuis * buffer: implement `iterable` interface [#525](https://github.com/nodejs/io.js/issues/525) / minor version bump / @bnoordhuis
* replace util.isType() with typeof [#607](https://github.com/iojs/io.js/issues/607) / general use of util.is*() in core re perf * replace util.isType() with typeof [#607](https://github.com/nodejs/io.js/issues/607) / general use of util.is*() in core re perf
* docs: lower the maximum stability level to "stable" (https://github.com/iojs/io.js/pull/633) * docs: lower the maximum stability level to "stable" (https://github.com/nodejs/io.js/pull/633)
* maintain our own package registries for io.js related packages (https://github.com/iojs/io.js/issues/640#issuecomment-71882645) * maintain our own package registries for io.js related packages (https://github.com/nodejs/io.js/issues/640#issuecomment-71882645)
* Working Groups PR (https://github.com/iojs/io.js/pull/599) * Working Groups PR (https://github.com/nodejs/io.js/pull/599)
* Remove “unstable” from messaging (https://github.com/iojs/website/issues/108) * Remove “unstable” from messaging (https://github.com/nodejs/website/issues/108)
* Node.js and io.js should not break each other (no, they shouldn't) * Node.js and io.js should not break each other (no, they shouldn't)
* Working group reports * Working group reports
@ -62,7 +62,7 @@ Extracted from https://github.com/iojs/io.js/labels/tc-agenda prior to meeting.
* relationship between assert and CommonJS Unit Testing spec; * relationship between assert and CommonJS Unit Testing spec;
* particular #636 bug; * particular #636 bug;
* what "deep equality" means and how it should deal with prototypes; * what "deep equality" means and how it should deal with prototypes;
* [#639](https://github.com/iojs/io.js/pull/639) proposal * [#639](https://github.com/nodejs/io.js/pull/639) proposal
* Isaac: CommonJS is gone & dead, good ideas have to stand on their own * Isaac: CommonJS is gone & dead, good ideas have to stand on their own
* Mikeal: assert probably shouldn’t be in core * Mikeal: assert probably shouldn’t be in core
@ -76,10 +76,10 @@ Extracted from https://github.com/iojs/io.js/labels/tc-agenda prior to meeting.
Conclusion: accept both of Conclusion: accept both of
- [#636](https://github.com/iojs/io.js/pull/636) - [#636](https://github.com/nodejs/io.js/pull/636)
- [#639](https://github.com/iojs/io.js/pull/639) - [#639](https://github.com/nodejs/io.js/pull/639)
(Contrast #636 with [#621](https://github.com/iojs/io.js/pull/621), which is a more ambitious change and probably not a good idea.) (Contrast #636 with [#621](https://github.com/nodejs/io.js/pull/621), which is a more ambitious change and probably not a good idea.)
1. deepEqual = No prototype checking 1. deepEqual = No prototype checking
2. deepStrictEqual = proper prototype checking 2. deepStrictEqual = proper prototype checking
@ -87,14 +87,14 @@ Passed without objection
### Release PGP key strategy and policy / @rvagg ### Release PGP key strategy and policy / @rvagg
[#709](https://github.com/iojs/io.js/issues/709) [#709](https://github.com/nodejs/io.js/issues/709)
* Rod summarised how the current release key strategy works and is documented on the README. Asked for feedback on: * Rod summarised how the current release key strategy works and is documented on the README. Asked for feedback on:
- Which keyserver(s) to use - Which keyserver(s) to use
- Whether to go with a master/sub key design for the project - Whether to go with a master/sub key design for the project
* No strong opinions, nothing actionable here * No strong opinions, nothing actionable here
### VM bugs? [#548](https://github.com/iojs/io.js/issues/548) / @domenic ### VM bugs? [#548](https://github.com/nodejs/io.js/issues/548) / @domenic
[joyent/node#9084](https://github.com/joyent/node/issues/9084) [joyent/node#9084](https://github.com/joyent/node/issues/9084)

36
doc/tc-meetings/2015-02-18.md
View File

@ -4,23 +4,23 @@
* **Public YouTube feed**: http://www.youtube.com/watch?v=jeBPYLJ2_Yc * **Public YouTube feed**: http://www.youtube.com/watch?v=jeBPYLJ2_Yc
* **Google Plus Event page**: https://plus.google.com/events/ccrkam8uup1k8qbo0fmcea0n2v4 * **Google Plus Event page**: https://plus.google.com/events/ccrkam8uup1k8qbo0fmcea0n2v4
* **GitHub Issue**: https://github.com/iojs/io.js/issues/509 * **GitHub Issue**: https://github.com/nodejs/io.js/issues/509
* **Original Minutes Google Doc**: https://docs.google.com/document/d/1JnujRu6Rfnp6wvbvwCfxXnsjLySunQ_yah91pkvSFdQ * **Original Minutes Google Doc**: https://docs.google.com/document/d/1JnujRu6Rfnp6wvbvwCfxXnsjLySunQ_yah91pkvSFdQ
## Agenda ## Agenda
Extracted from https://github.com/iojs/io.js/labels/tc-agenda prior to meeting. Extracted from https://github.com/nodejs/io.js/labels/tc-agenda prior to meeting.
* util: fixed behavior of isObject() [#822](https://github.com/iojs/io.js/issues/822) / @chrisdickinson / major version release * util: fixed behavior of isObject() [#822](https://github.com/nodejs/io.js/issues/822) / @chrisdickinson / major version release
* Translate installers for OS X and Windows [#819](https://github.com/iojs/io.js/issues/819) / @rvagg / maintenance overhead * Translate installers for OS X and Windows [#819](https://github.com/nodejs/io.js/issues/819) / @rvagg / maintenance overhead
* lib: fix process.send() sync i/o regression [#774](https://github.com/iojs/io.js/issues/774) / @bnoordhuis * lib: fix process.send() sync i/o regression [#774](https://github.com/nodejs/io.js/issues/774) / @bnoordhuis
* Implement unhandled rejection tracking [#758](https://github.com/iojs/io.js/issues/758) / @rvagg / how can we help this land * Implement unhandled rejection tracking [#758](https://github.com/nodejs/io.js/issues/758) / @rvagg / how can we help this land
* Logo / Brand Treatment * Logo / Brand Treatment
[website/181](https://github.com/iojs/website/issues/181) @ mikeal [website/181](https://github.com/nodejs/website/issues/181) @ mikeal
https://www.behance.net/gallery/23269525/IOJS-logo-concept https://www.behance.net/gallery/23269525/IOJS-logo-concept
* Stability Policy/Statement & Roadmap * Stability Policy/Statement & Roadmap
[#725](https://github.com/iojs/io.js/issues/725) / @mikeal [#725](https://github.com/nodejs/io.js/issues/725) / @mikeal
[roadmap/14](https://github.com/iojs/roadmap/issues/14) / @mikeal [roadmap/14](https://github.com/nodejs/roadmap/issues/14) / @mikeal
## Minutes ## Minutes
@ -51,9 +51,9 @@ https://www.behance.net/gallery/23269525/IOJS-logo-concept
* assert: don't compare object `prototype` property _and_ assert: introduce `deepStrictEqual` / @vkurchatkin * assert: don't compare object `prototype` property _and_ assert: introduce `deepStrictEqual` / @vkurchatkin
* Release PGP key strategy and policy / @rvagg * Release PGP key strategy and policy / @rvagg
* VM bugs? [#548](https://github.com/iojs/io.js/issues/548) / @domenic * VM bugs? [#548](https://github.com/nodejs/io.js/issues/548) / @domenic
### util: fixed behavior of isObject() [#822](https://github.com/iojs/io.js/issues/822) / @chrisdickinson / major version release ### util: fixed behavior of isObject() [#822](https://github.com/nodejs/io.js/issues/822) / @chrisdickinson / major version release
* Chris: Requires semver-major, what’s the vibe on bumping major at this stage? * Chris: Requires semver-major, what’s the vibe on bumping major at this stage?
* Chris: isObject() would now return true when checking for functions * Chris: isObject() would now return true when checking for functions
@ -71,7 +71,7 @@ https://www.behance.net/gallery/23269525/IOJS-logo-concept
* Chris: difference between Mikeal’s proposal and the original proposal is having a “canary” branch that stuff gets merged in to and eventually is merged in to master, original proposal merged new stuff in to master and used the time delay as “canary” (like Chrome) * Chris: difference between Mikeal’s proposal and the original proposal is having a “canary” branch that stuff gets merged in to and eventually is merged in to master, original proposal merged new stuff in to master and used the time delay as “canary” (like Chrome)
* Rod: proposal is to tag this issue as a milestone for now and punt until we have more substantive changes - no disagreements, passed * Rod: proposal is to tag this issue as a milestone for now and punt until we have more substantive changes - no disagreements, passed
### Translate installers for OS X and Windows [#819](https://github.com/iojs/io.js/issues/819) / @rvagg / maintenance overhead ### Translate installers for OS X and Windows [#819](https://github.com/nodejs/io.js/issues/819) / @rvagg / maintenance overhead
* Rod: concern here is the maintenance overhead in keeping all of the translations in sync, are we happy to have that headache in core? * Rod: concern here is the maintenance overhead in keeping all of the translations in sync, are we happy to have that headache in core?
* Mikeal: let English be the default and let the translation teams be responsible for watching for changes and making updates as appropriate * Mikeal: let English be the default and let the translation teams be responsible for watching for changes and making updates as appropriate
@ -81,11 +81,11 @@ https://www.behance.net/gallery/23269525/IOJS-logo-concept
* Bert: if there is no technical issue then OK with landing this, the responsibility for translation will have to be with that community * Bert: if there is no technical issue then OK with landing this, the responsibility for translation will have to be with that community
* Resolution: allow this to land unless there are going to be technical blockers to future installer changes needing to wait for translations to be updated * Resolution: allow this to land unless there are going to be technical blockers to future installer changes needing to wait for translations to be updated
### lib: fix process.send() sync i/o regression [#774](https://github.com/iojs/io.js/issues/774) / @bnoordhuis ### lib: fix process.send() sync i/o regression [#774](https://github.com/nodejs/io.js/issues/774) / @bnoordhuis
* Ben’s issue, punt till next meeting, note in “known issues” for releases * Ben’s issue, punt till next meeting, note in “known issues” for releases
### Implement unhandled rejection tracking [#758](https://github.com/iojs/io.js/issues/758) / @rvagg / how can we help this land ### Implement unhandled rejection tracking [#758](https://github.com/nodejs/io.js/issues/758) / @rvagg / how can we help this land
* Rod: Brought to TC to get some more engagement and help get this landed unless there are any major objections * Rod: Brought to TC to get some more engagement and help get this landed unless there are any major objections
* Domenic: PR looks good, it’s mainly a matter of code quality, doesn’t add any default handlers which is a good incremental way of adding this * Domenic: PR looks good, it’s mainly a matter of code quality, doesn’t add any default handlers which is a good incremental way of adding this
@ -97,7 +97,7 @@ https://www.behance.net/gallery/23269525/IOJS-logo-concept
- No objections - No objections
### Logo / Brand Treatment ### Logo / Brand Treatment
[website/181](https://github.com/iojs/website/issues/181) @ mikeal [website/181](https://github.com/nodejs/website/issues/181) @ mikeal
https://www.behance.net/gallery/23269525/IOJS-logo-concept https://www.behance.net/gallery/23269525/IOJS-logo-concept
* Mikeal discussed the proposed website changes and logo choice @ https://www.behance.net/gallery/23269525/IOJS-logo-concept * Mikeal discussed the proposed website changes and logo choice @ https://www.behance.net/gallery/23269525/IOJS-logo-concept
@ -111,8 +111,8 @@ https://www.behance.net/gallery/23269525/IOJS-logo-concept
* Agreed to delegate to the website WG to make this decision * Agreed to delegate to the website WG to make this decision
### Stability Policy/Statement & Roadmap ### Stability Policy/Statement & Roadmap
[#725](https://github.com/iojs/io.js/issues/725) / @mikeal [#725](https://github.com/nodejs/io.js/issues/725) / @mikeal
[roadmap/14](https://github.com/iojs/roadmap/issues/14) / @mikeal [roadmap/14](https://github.com/nodejs/roadmap/issues/14) / @mikeal
* Mikeal: none of this is fixed in stone, we can change it in the future if we decide it won’t work * Mikeal: none of this is fixed in stone, we can change it in the future if we decide it won’t work
- one change still to go in is that the wording on stability should be that “we won’t remove an API” - one change still to go in is that the wording on stability should be that “we won’t remove an API”
@ -120,7 +120,7 @@ https://www.behance.net/gallery/23269525/IOJS-logo-concept
* Bert: concerned about this being a reflection of the way we work rather than enforcing new behaviors * Bert: concerned about this being a reflection of the way we work rather than enforcing new behaviors
* Discussion around breaking / removing APIs and how firm this policy is going forward * Discussion around breaking / removing APIs and how firm this policy is going forward
* Rod asked for specific things that need to be resolved now vs punting to a later meeting * Rod asked for specific things that need to be resolved now vs punting to a later meeting
* Mikeal: https://github.com/iojs/roadmap/commit/190690a1b5f206c22f64adc3d29d10c4b08cb8cd * Mikeal: https://github.com/nodejs/roadmap/commit/190690a1b5f206c22f64adc3d29d10c4b08cb8cd
* Group discussed presentations, no major objections so the blessing was given for Mikeal to move forward with ratifying that, expect further discussion on the broader topic next meeting. * Group discussed presentations, no major objections so the blessing was given for Mikeal to move forward with ratifying that, expect further discussion on the broader topic next meeting.
### Next meeting ### Next meeting

44
doc/tc-meetings/2015-03-04.md
View File

@ -4,19 +4,19 @@
* **Public YouTube feed**: http://www.youtube.com/watch?v=vxX2CkFPEtk * **Public YouTube feed**: http://www.youtube.com/watch?v=vxX2CkFPEtk
* **Google Plus Event page**: https://plus.google.com/events/c9ijr7edl14im7dspk5njktmjq4 * **Google Plus Event page**: https://plus.google.com/events/c9ijr7edl14im7dspk5njktmjq4
* **GitHub Issue**: https://github.com/iojs/io.js/issues/1053 * **GitHub Issue**: https://github.com/nodejs/io.js/issues/1053
* **Original Minutes Google Doc**: https://docs.google.com/document/d/1RoIE68l8B2iWLdEPM7ApSN2FxFDd3OY0wfTeqUh-K9w * **Original Minutes Google Doc**: https://docs.google.com/document/d/1RoIE68l8B2iWLdEPM7ApSN2FxFDd3OY0wfTeqUh-K9w
## Agenda ## Agenda
Extracted from https://github.com/iojs/io.js/labels/tc-agenda prior to meeting. Extracted from https://github.com/nodejs/io.js/labels/tc-agenda prior to meeting.
* lib: fix process.send() sync i/o regression [#774](https://github.com/iojs/io.js/issues/774) / @bnoordhuis * lib: fix process.send() sync i/o regression [#774](https://github.com/nodejs/io.js/issues/774) / @bnoordhuis
* iojs: introduce internal modules [#848](https://github.com/iojs/io.js/issues/848) / @chrisdickinson / @trevnorris / (@vkurchatkin) * iojs: introduce internal modules [#848](https://github.com/nodejs/io.js/issues/848) / @chrisdickinson / @trevnorris / (@vkurchatkin)
* url: significantly improve the performance of the url module [#933](https://github.com/iojs/io.js/issues/933) / @mikeal * url: significantly improve the performance of the url module [#933](https://github.com/nodejs/io.js/issues/933) / @mikeal
* Ship websockets in core [#1010](https://github.com/iojs/io.js/issues/1010) / @piscisaureus * Ship websockets in core [#1010](https://github.com/nodejs/io.js/issues/1010) / @piscisaureus
* RFC: upgrade to V8 4.2? [#1026](https://github.com/iojs/io.js/issues/1026) / @bnoordhuis * RFC: upgrade to V8 4.2? [#1026](https://github.com/nodejs/io.js/issues/1026) / @bnoordhuis
* Colin resigning from TC [#1056](https://github.com/iojs/io.js/pull/1056) * Colin resigning from TC [#1056](https://github.com/nodejs/io.js/pull/1056)
## Minutes ## Minutes
@ -47,23 +47,23 @@ Extracted from https://github.com/iojs/io.js/labels/tc-agenda prior to meeting.
### Review of last meeting ### Review of last meeting
* util: fixed behavior of isObject() [#822](https://github.com/iojs/io.js/issues/822) / @chrisdickinson / major version release * util: fixed behavior of isObject() [#822](https://github.com/nodejs/io.js/issues/822) / @chrisdickinson / major version release
* Translate installers for OS X and Windows [#819](https://github.com/iojs/io.js/issues/819) / @rvagg / maintenance overhead * Translate installers for OS X and Windows [#819](https://github.com/nodejs/io.js/issues/819) / @rvagg / maintenance overhead
* lib: fix process.send() sync i/o regression [#774](https://github.com/iojs/io.js/issues/774) / @bnoordhuis * lib: fix process.send() sync i/o regression [#774](https://github.com/nodejs/io.js/issues/774) / @bnoordhuis
* Implement unhandled rejection tracking [#758](https://github.com/iojs/io.js/issues/758) / @rvagg / how can we help this land * Implement unhandled rejection tracking [#758](https://github.com/nodejs/io.js/issues/758) / @rvagg / how can we help this land
* Logo / Brand Treatment * Logo / Brand Treatment
[website/181] https://github.com/iojs/website/issues/181 @ mikeal [website/181] https://github.com/nodejs/website/issues/181 @ mikeal
https://www.behance.net/gallery/23269525/IOJS-logo-concept https://www.behance.net/gallery/23269525/IOJS-logo-concept
* Stability Policy/Statement & Roadmap * Stability Policy/Statement & Roadmap
[#725](https://github.com/iojs/io.js/issues/725) / @mikeal [#725](https://github.com/nodejs/io.js/issues/725) / @mikeal
[roadmap/14](https://github.com/iojs/roadmap/issues/14) / @mikeal [roadmap/14](https://github.com/nodejs/roadmap/issues/14) / @mikeal
### Colin resigning from TC [#1056](https://github.com/iojs/io.js/pull/1056) ### Colin resigning from TC [#1056](https://github.com/nodejs/io.js/pull/1056)
### lib: fix process.send() sync i/o regression ### lib: fix process.send() sync i/o regression
[#774](https://github.com/iojs/io.js/issues/774) / @bnoordhuis [#774](https://github.com/nodejs/io.js/issues/774) / @bnoordhuis
* Ben: @orangemocha did some work on Windows for libuv, unsure if this helps. * Ben: @orangemocha did some work on Windows for libuv, unsure if this helps.
* Bert: process.send() has been made sync on *nix because otherwise it’s a breaking change, but on Windows it’s always been async so changing it to sync would also be a breaking change. So the situation is crazy. * Bert: process.send() has been made sync on *nix because otherwise it’s a breaking change, but on Windows it’s always been async so changing it to sync would also be a breaking change. So the situation is crazy.
@ -75,7 +75,7 @@ https://www.behance.net/gallery/23269525/IOJS-logo-concept
### iojs: introduce internal modules ### iojs: introduce internal modules
[#848](https://github.com/iojs/io.js/issues/848) / @chrisdickinson / @trevnorris / (@vkurchatkin) [#848](https://github.com/nodejs/io.js/issues/848) / @chrisdickinson / @trevnorris / (@vkurchatkin)
Chris: lets us have modules that can’t be required from outside of core. I’m in favor; it’s a nice insurance policy, especially in light of the stability policy that we will try not to make any breaking changes to the JavaScript API. Chris: lets us have modules that can’t be required from outside of core. I’m in favor; it’s a nice insurance policy, especially in light of the stability policy that we will try not to make any breaking changes to the JavaScript API.
@ -104,12 +104,12 @@ Ben: not sure that’s quite sufficient…
Domenic: seems like a pure win because it allows you not to have to put everything in one file to keep things private. Domenic: seems like a pure win because it allows you not to have to put everything in one file to keep things private.
### url: significantly improve the performance of the url module ### url: significantly improve the performance of the url module
[#933](https://github.com/iojs/io.js/issues/933) / @mikeal [#933](https://github.com/nodejs/io.js/issues/933) / @mikeal
This will get rolled in to the major version issue Chris is putting together. This will get rolled in to the major version issue Chris is putting together.
### Ship websockets in core ### Ship websockets in core
[#1010](https://github.com/iojs/io.js/issues/1010) / @piscisaureus [#1010](https://github.com/nodejs/io.js/issues/1010) / @piscisaureus
Bert: I’m not sure I believe in this any more; the major reason I wanted this was that building native addons is terrible, but people brought up that the native part of the web socket implementations only do some bitwise buffer stuff and so we could probably just add *those* to core. Bert: I’m not sure I believe in this any more; the major reason I wanted this was that building native addons is terrible, but people brought up that the native part of the web socket implementations only do some bitwise buffer stuff and so we could probably just add *those* to core.
@ -140,9 +140,9 @@ We should start an issue in NG about the core modules/modernity stuff.
We should publicly state that we’re interested in supporting HTTP/2 in the related issue thread, although we’re not sure about implementation strategy and want to see experiments. We should publicly state that we’re interested in supporting HTTP/2 in the related issue thread, although we’re not sure about implementation strategy and want to see experiments.
### RFC: upgrade to V8 4.2? ### RFC: upgrade to V8 4.2?
[#1026](https://github.com/iojs/io.js/issues/1026) / @bnoordhuis [#1026](https://github.com/nodejs/io.js/issues/1026) / @bnoordhuis
* Ben: V8 4.1 has gone gold/stable so we should probably upgrade by un-floating a revert we placed on top of it. I propose we revert that revert, so that we get 4.1-as-shipped-in-Chrome. [#952](https://github.com/iojs/io.js/pull/952) for details on the floating revert. * Ben: V8 4.1 has gone gold/stable so we should probably upgrade by un-floating a revert we placed on top of it. I propose we revert that revert, so that we get 4.1-as-shipped-in-Chrome. [#952](https://github.com/nodejs/io.js/pull/952) for details on the floating revert.
* Domenic: do we have clarity about ABI vs. API implications for io.js major version? * Domenic: do we have clarity about ABI vs. API implications for io.js major version?
* Ben: ABI change means everyone has to recompile their add-ons so we should bump the minor. * Ben: ABI change means everyone has to recompile their add-ons so we should bump the minor.
* Fedor: this feels more like a major version? * Fedor: this feels more like a major version?

34
doc/tc-meetings/2015-03-18.md
View File

@ -4,17 +4,17 @@
* **Public YouTube feed**: http://www.youtube.com/watch?v=tQwVcuYCiZ4 * **Public YouTube feed**: http://www.youtube.com/watch?v=tQwVcuYCiZ4
* **Google Plus Event page**: https://plus.google.com/events/cneon2drmol62u4drm8aegjnrkk * **Google Plus Event page**: https://plus.google.com/events/cneon2drmol62u4drm8aegjnrkk
* **GitHub Issue**: https://github.com/iojs/io.js/issues/1187 * **GitHub Issue**: https://github.com/nodejs/io.js/issues/1187
* **Original Minutes Google Doc**: https://docs.google.com/document/d/1It6PTEBQ7OjW8P88hCLoXvcWKA3Q8dY2eYEHIF6FvS4 * **Original Minutes Google Doc**: https://docs.google.com/document/d/1It6PTEBQ7OjW8P88hCLoXvcWKA3Q8dY2eYEHIF6FvS4
## Agenda ## Agenda
Extracted from https://github.com/iojs/io.js/labels/tc-agenda prior to meeting. Extracted from https://github.com/nodejs/io.js/labels/tc-agenda prior to meeting.
* [#1134](https://github.com/iojs/io.js/pull/1134) Add Docker working group * [#1134](https://github.com/nodejs/io.js/pull/1134) Add Docker working group
* [#1140](https://github.com/iojs/io.js/pull/1140) Revert stream base / @piscisaureus / merge policy questions * [#1140](https://github.com/nodejs/io.js/pull/1140) Revert stream base / @piscisaureus / merge policy questions
* [#1130](https://github.com/iojs/io.js/pull/1130) Nominating Jeremiah Senkpiel @Fishrock123 to the TC * [#1130](https://github.com/nodejs/io.js/pull/1130) Nominating Jeremiah Senkpiel @Fishrock123 to the TC
* [#1077](https://github.com/iojs/io.js/pull/1077) Pass args to process.nextTick() / @trevnorris * [#1077](https://github.com/nodejs/io.js/pull/1077) Pass args to process.nextTick() / @trevnorris
## Minutes ## Minutes
@ -38,19 +38,19 @@ Extracted from https://github.com/iojs/io.js/labels/tc-agenda prior to meeting.
### Review of last meeting ### Review of last meeting
* lib: fix process.send() sync i/o regression [#774](https://github.com/iojs/io.js/issues/774) / @bnoordhuis * lib: fix process.send() sync i/o regression [#774](https://github.com/nodejs/io.js/issues/774) / @bnoordhuis
* iojs: introduce internal modules [#848](https://github.com/iojs/io.js/issues/848) / @chrisdickinson / @trevnorris / (@vkurchatkin) * iojs: introduce internal modules [#848](https://github.com/nodejs/io.js/issues/848) / @chrisdickinson / @trevnorris / (@vkurchatkin)
* url: significantly improve the performance of the url module [#933](https://github.com/iojs/io.js/issues/933) / @mikeal * url: significantly improve the performance of the url module [#933](https://github.com/nodejs/io.js/issues/933) / @mikeal
* Ship websockets in core [#1010](https://github.com/iojs/io.js/issues/1010) / @piscisaureus * Ship websockets in core [#1010](https://github.com/nodejs/io.js/issues/1010) / @piscisaureus
* RFC: upgrade to V8 4.2? [#1026](https://github.com/iojs/io.js/issues/1026) / @bnoordhuis * RFC: upgrade to V8 4.2? [#1026](https://github.com/nodejs/io.js/issues/1026) / @bnoordhuis
* Colin resigning from TC [#1056](https://github.com/iojs/io.js/pull/1056) * Colin resigning from TC [#1056](https://github.com/nodejs/io.js/pull/1056)
### [#1134](https://github.com/iojs/io.js/pull/1134) Add Docker working group ### [#1134](https://github.com/nodejs/io.js/pull/1134) Add Docker working group
* Rod: originally conceived to be a “sub-WG” of Build WG but this makes sense because there is little overlap with the Build team or skills required for the Build team. * Rod: originally conceived to be a “sub-WG” of Build WG but this makes sense because there is little overlap with the Build team or skills required for the Build team.
* Rod: this group is already maintaining official Docker images or io.js located at https://github.com/iojs/docker-iojs which are also the “official” Docker images for io.js. * Rod: this group is already maintaining official Docker images or io.js located at https://github.com/nodejs/docker-iojs which are also the “official” Docker images for io.js.
### [#1140](https://github.com/iojs/io.js/pull/1140) Revert stream base / @piscisaureus / merge policy questions ### [#1140](https://github.com/nodejs/io.js/pull/1140) Revert stream base / @piscisaureus / merge policy questions
* Bert: in favour of stream_base now and don’t want it reverted given the fixes that have been made. The real problem was the introduction of a major change that lead to a lot of breakage and a lot of fix commits. Proposed that we have a “ng” (or similar) branch with releases for testing before merging. * Bert: in favour of stream_base now and don’t want it reverted given the fixes that have been made. The real problem was the introduction of a major change that lead to a lot of breakage and a lot of fix commits. Proposed that we have a “ng” (or similar) branch with releases for testing before merging.
* Chris: agree that we need a canary policy of some kind to deal with this * Chris: agree that we need a canary policy of some kind to deal with this
@ -65,14 +65,14 @@ Extracted from https://github.com/iojs/io.js/labels/tc-agenda prior to meeting.
* Discussion about test coverage * Discussion about test coverage
* Rod asked OpenSSL fix: agreed to punt on a release until OpenSSL fix has been released and go immediately after that. * Rod asked OpenSSL fix: agreed to punt on a release until OpenSSL fix has been released and go immediately after that.
### [#1130](https://github.com/iojs/io.js/pull/1130) Nominating Jeremiah Senkpiel @Fishrock123 to the TC ### [#1130](https://github.com/nodejs/io.js/pull/1130) Nominating Jeremiah Senkpiel @Fishrock123 to the TC
* Rod: there was some off-record discussion about TC membership process related to #1130 and #1131. * Rod: there was some off-record discussion about TC membership process related to #1130 and #1131.
- Neither individual was asked and it would be good to at least have it passed by them first - Neither individual was asked and it would be good to at least have it passed by them first
- Would be good to have a smooth on-boarding mechanism to bringing someone on to meetings before officially making them TC, agreed to invite Jeremiah to next TC _if_ he’s interested in being involved. - Would be good to have a smooth on-boarding mechanism to bringing someone on to meetings before officially making them TC, agreed to invite Jeremiah to next TC _if_ he’s interested in being involved.
- Generally agreed that increasing the size of the TC is a good thing (minus the meeting-overhead added by more people) - Generally agreed that increasing the size of the TC is a good thing (minus the meeting-overhead added by more people)
### [#1077](https://github.com/iojs/io.js/pull/1077) Pass args to process.nextTick() / @trevnorris ### [#1077](https://github.com/nodejs/io.js/pull/1077) Pass args to process.nextTick() / @trevnorris
* Trevor: passing arguments / context through process.nextTick() in core is common and would be significantly faster if we use a setArgs() feature. * Trevor: passing arguments / context through process.nextTick() in core is common and would be significantly faster if we use a setArgs() feature.
* Chris: needed in readable-stream * Chris: needed in readable-stream

28
doc/tc-meetings/2015-04-01.md
View File

@ -4,18 +4,18 @@
* **Public YouTube feed**: http://www.youtube.com/watch?v=B1pTT60E73M * **Public YouTube feed**: http://www.youtube.com/watch?v=B1pTT60E73M
* **Google Plus Event page**: https://plus.google.com/events/cneon2drmol62u4drm8aegjnrkk * **Google Plus Event page**: https://plus.google.com/events/cneon2drmol62u4drm8aegjnrkk
* **GitHub Issue**: https://github.com/iojs/io.js/issues/1311 * **GitHub Issue**: https://github.com/nodejs/io.js/issues/1311
* **Original Minutes Google Doc**: https://docs.google.com/document/d/1iEzSiQpB3me-x1R0_FzlMtGuPmgxR2x7NMITp779690 * **Original Minutes Google Doc**: https://docs.google.com/document/d/1iEzSiQpB3me-x1R0_FzlMtGuPmgxR2x7NMITp779690
## Agenda ## Agenda
Extracted from https://github.com/iojs/io.js/labels/tc-agenda prior to meeting. Extracted from https://github.com/nodejs/io.js/labels/tc-agenda prior to meeting.
* reconciliation update (Mikeal and Bert) * reconciliation update (Mikeal and Bert)
* doc: add NAN WG [#1226](https://github.com/iojs/io.js/issues/1226) * doc: add NAN WG [#1226](https://github.com/nodejs/io.js/issues/1226)
* Proposal: Authorise @Fishrock123 to create releases [#1225](https://github.com/iojs/io.js/issues/1225) * Proposal: Authorise @Fishrock123 to create releases [#1225](https://github.com/nodejs/io.js/issues/1225)
* governance: Raise the bar for changes in membership and governance policy [#1222](https://github.com/iojs/io.js/issues/1222) * governance: Raise the bar for changes in membership and governance policy [#1222](https://github.com/nodejs/io.js/issues/1222)
* Nominating Rod Vagg @rvagg to the TC [#1134](https://github.com/iojs/io.js/issues/1131) * Nominating Rod Vagg @rvagg to the TC [#1134](https://github.com/nodejs/io.js/issues/1131)
## Minutes ## Minutes
@ -45,10 +45,10 @@ Extracted from https://github.com/iojs/io.js/labels/tc-agenda prior to meeting.
### Review of last meeting ### Review of last meeting
* [#1134](https://github.com/iojs/io.js/pull/1134) Add Docker working group * [#1134](https://github.com/nodejs/io.js/pull/1134) Add Docker working group
* [#1140](https://github.com/iojs/io.js/pull/1140) Revert stream base / @piscisaureus / merge policy questions * [#1140](https://github.com/nodejs/io.js/pull/1140) Revert stream base / @piscisaureus / merge policy questions
* [#1130](https://github.com/iojs/io.js/pull/1130) Nominating Jeremiah Senkpiel @Fishrock123 to the TC * [#1130](https://github.com/nodejs/io.js/pull/1130) Nominating Jeremiah Senkpiel @Fishrock123 to the TC
* [#1077](https://github.com/iojs/io.js/pull/1077) Pass args to process.nextTick() / @trevnorris * [#1077](https://github.com/nodejs/io.js/pull/1077) Pass args to process.nextTick() / @trevnorris
* Major version bump * Major version bump
@ -65,7 +65,7 @@ Extracted from https://github.com/iojs/io.js/labels/tc-agenda prior to meeting.
* Mikeal: they will be taken care of by an LTS schedule * Mikeal: they will be taken care of by an LTS schedule
* Bert: IBM agrees that there should be a fast-moving tip and they just use an LTS. Board could also assert influence by way of a corporation threatening to withdraw backing. * Bert: IBM agrees that there should be a fast-moving tip and they just use an LTS. Board could also assert influence by way of a corporation threatening to withdraw backing.
### doc: add NAN WG [#1226](https://github.com/iojs/io.js/issues/1226) ### doc: add NAN WG [#1226](https://github.com/nodejs/io.js/issues/1226)
* Rod: discussed proposed move of rvagg/nan and rvagg/node-addon-examples to iojs to be governed by an “Addons API Working Group” * Rod: discussed proposed move of rvagg/nan and rvagg/node-addon-examples to iojs to be governed by an “Addons API Working Group”
@ -75,11 +75,11 @@ Fedor: +1
Ben: +1 Ben: +1
Trevor: +1 Trevor: +1
### Proposal: Authorise @Fishrock123 to create releases [#1225](https://github.com/iojs/io.js/issues/1225) ### Proposal: Authorise @Fishrock123 to create releases [#1225](https://github.com/nodejs/io.js/issues/1225)
* No disagreement, lots of +1s, good to go * No disagreement, lots of +1s, good to go
### governance: Raise the bar for changes in membership and governance policy [#1222](https://github.com/iojs/io.js/issues/1222) ### governance: Raise the bar for changes in membership and governance policy [#1222](https://github.com/nodejs/io.js/issues/1222)
* Mikeal: the PR is a bit stale because of a miscount, just want to make sure that there are no concerns with this even though it may not end up being required given the movements with the TC. * Mikeal: the PR is a bit stale because of a miscount, just want to make sure that there are no concerns with this even though it may not end up being required given the movements with the TC.
* Rod: requested that we not hold up progress in io.js pending movement on the JNAB / Foundation process and we should treat that as a separate thing that may or may not happen. * Rod: requested that we not hold up progress in io.js pending movement on the JNAB / Foundation process and we should treat that as a separate thing that may or may not happen.
@ -87,7 +87,7 @@ Trevor: +1
* Mikeal: just a miscount, needs to be changed, wanted to test if people are OK with this once we have more people on the TC. Main point was to flush out any concerns about raising the bar. * Mikeal: just a miscount, needs to be changed, wanted to test if people are OK with this once we have more people on the TC. Main point was to flush out any concerns about raising the bar.
* Ben: suggested that it become 2 PRs, make the 2/3rds thing a separate issue. * Ben: suggested that it become 2 PRs, make the 2/3rds thing a separate issue.
### Nominating Rod Vagg @rvagg to the TC [#1134](https://github.com/iojs/io.js/issues/1131) ### Nominating Rod Vagg @rvagg to the TC [#1134](https://github.com/nodejs/io.js/issues/1131)
* Rod: fine with this * Rod: fine with this
* Discussed meeting facilitation, agreed that it wasn’t a strictly defined role but it would be good to share it around a bit. * Discussed meeting facilitation, agreed that it wasn’t a strictly defined role but it would be good to share it around a bit.

26
doc/tc-meetings/2015-04-08.md
View File

@ -4,17 +4,17 @@
* **Public YouTube feed**: http://www.youtube.com/watch?v=OjlK8k10oyo * **Public YouTube feed**: http://www.youtube.com/watch?v=OjlK8k10oyo
* **Google Plus Event page**: https://plus.google.com/events/c1c3234uog6svplgrapqucb557k * **Google Plus Event page**: https://plus.google.com/events/c1c3234uog6svplgrapqucb557k
* **GitHub Issue**: https://github.com/iojs/io.js/issues/1369 * **GitHub Issue**: https://github.com/nodejs/io.js/issues/1369
* **Original Minutes Google Doc**: https://docs.google.com/document/d/1EsDjfRGpVKFABH4LcNXNxsAsBTnHsU-i5cehmAcp1A8 * **Original Minutes Google Doc**: https://docs.google.com/document/d/1EsDjfRGpVKFABH4LcNXNxsAsBTnHsU-i5cehmAcp1A8
## Agenda ## Agenda
Extracted from https://github.com/iojs/io.js/labels/tc-agenda prior to meeting. Extracted from https://github.com/nodejs/io.js/labels/tc-agenda prior to meeting.
* [#1101](https://github.com/iojs/io.js/pull/1101) http: allow HTTP to return an HTTPS server / @silverwind / the use of a `tls` option to trigger `https` module functionality * [#1101](https://github.com/nodejs/io.js/pull/1101) http: allow HTTP to return an HTTPS server / @silverwind / the use of a `tls` option to trigger `https` module functionality
* [#1301](https://github.com/iojs/io.js/pull/1301) Util(.is*) Deprecations / @Fishrock123 & @brendanashworth / [this comment](https://github.com/iojs/io.js/pull/1301#issuecomment-90829575) asking for an opinion from the TC on how to move forward * [#1301](https://github.com/nodejs/io.js/pull/1301) Util(.is*) Deprecations / @Fishrock123 & @brendanashworth / [this comment](https://github.com/nodejs/io.js/pull/1301#issuecomment-90829575) asking for an opinion from the TC on how to move forward
* Discuss https://github.com/jasnell/dev-policy [[comment by @mikeal]](https://github.com/iojs/io.js/issues/1369#issuecomment-90955688) * Discuss https://github.com/jasnell/dev-policy [[comment by @mikeal]](https://github.com/nodejs/io.js/issues/1369#issuecomment-90955688)
* Discuss / Review the `require(‘.’)` situation [[comments by @silverwind and @Fishrock123]](https://github.com/iojs/io.js/issues/1369#issuecomment-90933134) * Discuss / Review the `require(‘.’)` situation [[comments by @silverwind and @Fishrock123]](https://github.com/nodejs/io.js/issues/1369#issuecomment-90933134)
### Present ### Present
@ -31,10 +31,10 @@ Extracted from https://github.com/iojs/io.js/labels/tc-agenda prior to meeting.
### Review of last meeting ### Review of last meeting
* reconciliation update (Mikeal and Bert) * reconciliation update (Mikeal and Bert)
* doc: add NAN WG [#1226](https://github.com/iojs/io.js/issues/1226) * doc: add NAN WG [#1226](https://github.com/nodejs/io.js/issues/1226)
* Proposal: Authorise @Fishrock123 to create releases [#1225](https://github.com/iojs/io.js/issues/1225) * Proposal: Authorise @Fishrock123 to create releases [#1225](https://github.com/nodejs/io.js/issues/1225)
* governance: Raise the bar for changes in membership and governance policy. [#1222](https://github.com/iojs/io.js/issues/1222) * governance: Raise the bar for changes in membership and governance policy. [#1222](https://github.com/nodejs/io.js/issues/1222)
* Nominating Rod Vagg @rvagg to the TC [#1134](https://github.com/iojs/io.js/issues/1131) * Nominating Rod Vagg @rvagg to the TC [#1134](https://github.com/nodejs/io.js/issues/1131)
### Quick stand-up ### Quick stand-up
@ -49,7 +49,7 @@ Extracted from https://github.com/iojs/io.js/labels/tc-agenda prior to meeting.
## Minutes ## Minutes
### [#1101](https://github.com/iojs/io.js/pull/1101) http: allow HTTP to return an HTTPS server ### [#1101](https://github.com/nodejs/io.js/pull/1101) http: allow HTTP to return an HTTPS server
***@silverwind / the use of a `tls` option to trigger `https` module functionality*** ***@silverwind / the use of a `tls` option to trigger `https` module functionality***
@ -79,9 +79,9 @@ Ben: what happens when iojs is compiled without TLS support?
**Conclusion**: punt on this. Initial feedback is that if we were to go down this route, we would slightly prefer the explicit tls option; however, there needs to be a discussion about the listen() idea, and also about compilation without TLS. **Conclusion**: punt on this. Initial feedback is that if we were to go down this route, we would slightly prefer the explicit tls option; however, there needs to be a discussion about the listen() idea, and also about compilation without TLS.
### [#1301](https://github.com/iojs/io.js/pull/1301) Util(.is*) Deprecations ### [#1301](https://github.com/nodejs/io.js/pull/1301) Util(.is*) Deprecations
***@Fishrock123 & @brendanashworth / [this comment](https://github.com/iojs/io.js/pull/1301#issuecomment-90829575) asking for an opinion from the TC on how to move forward*** ***@Fishrock123 & @brendanashworth / [this comment](https://github.com/nodejs/io.js/pull/1301#issuecomment-90829575) asking for an opinion from the TC on how to move forward***
Bert: what’s the point? Bert: what’s the point?

24
doc/tc-meetings/2015-04-15.md
View File

@ -4,16 +4,16 @@
* **Public YouTube feed**: http://www.youtube.com/watch?v=lsRu_of0Xp8 * **Public YouTube feed**: http://www.youtube.com/watch?v=lsRu_of0Xp8
* **Google Plus Event page**: https://plus.google.com/events/cdinisa9mlisv81um91h71g3css * **Google Plus Event page**: https://plus.google.com/events/cdinisa9mlisv81um91h71g3css
* **GitHub Issue**: https://github.com/iojs/io.js/issues/1431 * **GitHub Issue**: https://github.com/nodejs/io.js/issues/1431
* **Original Minutes Google Doc**: https://docs.google.com/document/d/1zlYeYS0LCyIjN4KsjXh9d46hNjp302M6L1K_-_OckzQ * **Original Minutes Google Doc**: https://docs.google.com/document/d/1zlYeYS0LCyIjN4KsjXh9d46hNjp302M6L1K_-_OckzQ
## Agenda ## Agenda
Extracted from https://github.com/iojs/io.js/labels/tc-agenda prior to meeting. Extracted from https://github.com/nodejs/io.js/labels/tc-agenda prior to meeting.
* [#1393](https://github.com/iojs/io.js/issues/1393) Ready to upgrade to V8 4.2? * [#1393](https://github.com/nodejs/io.js/issues/1393) Ready to upgrade to V8 4.2?
* [#1413](https://github.com/iojs/io.js/issues/1413) combining TC and Node core call * [#1413](https://github.com/nodejs/io.js/issues/1413) combining TC and Node core call
* [#1416](https://github.com/iojs/io.js/issues/1416) io.js diff node.js foundation * [#1416](https://github.com/nodejs/io.js/issues/1416) io.js diff node.js foundation
### Present ### Present
@ -28,11 +28,11 @@ Extracted from https://github.com/iojs/io.js/labels/tc-agenda prior to meeting.
### Review of last meeting ### Review of last meeting
* [#1101](https://github.com/iojs/io.js/pull/1101) http: allow HTTP to return an HTTPS server * [#1101](https://github.com/nodejs/io.js/pull/1101) http: allow HTTP to return an HTTPS server
* [#1301](https://github.com/iojs/io.js/pull/1301) Util(.is*) Deprecations * [#1301](https://github.com/nodejs/io.js/pull/1301) Util(.is*) Deprecations
* [Dev Policy](https://github.com/jasnell/dev-policy) * [Dev Policy](https://github.com/jasnell/dev-policy)
* Isaac * Isaac
* [#1365](https://github.com/iojs/io.js/issues/1356) `require('.')` * [#1365](https://github.com/nodejs/io.js/issues/1356) `require('.')`
### Quick stand-up ### Quick stand-up
@ -48,14 +48,14 @@ Extracted from https://github.com/iojs/io.js/labels/tc-agenda prior to meeting.
## Minutes ## Minutes
### [#1393](https://github.com/iojs/io.js/issues/1393) Ready to upgrade to V8 4.2? ### [#1393](https://github.com/nodejs/io.js/issues/1393) Ready to upgrade to V8 4.2?
* Ben: `next` branch should be ready to go though needs to be upgraded to 4.2.77.14, C++ changes are fairly minimal. * Ben: `next` branch should be ready to go though needs to be upgraded to 4.2.77.14, C++ changes are fairly minimal.
* Discussed potentially bumping major: * Discussed potentially bumping major:
- Mikeal: there was a meeting where it was generally agreed that an ABI change would warrant a version bump - Mikeal: there was a meeting where it was generally agreed that an ABI change would warrant a version bump
- Rod & Isaac suggested that ABI changes shouldn’t bump major - Rod & Isaac suggested that ABI changes shouldn’t bump major
- Discussion came around to most members agreeing that ABI change _should_ bump major. Rod voted 0 on this, everyone else apparently +1. - Discussion came around to most members agreeing that ABI change _should_ bump major. Rod voted 0 on this, everyone else apparently +1.
- Discussed semver-major changes including process.send() sync regressions, agreed that https://github.com/iojs/io.js/milestones/2.0.0 represents the best info on what’s mergable - Discussed semver-major changes including process.send() sync regressions, agreed that https://github.com/nodejs/io.js/milestones/2.0.0 represents the best info on what’s mergable
* Discussed git, agreed that we should move back to master, Chris to handle git changes * Discussed git, agreed that we should move back to master, Chris to handle git changes
* Discussed RC build, could use nightly or next-nightly but officially link it off the website and maybe label it differently. Rod to figure this out. * Discussed RC build, could use nightly or next-nightly but officially link it off the website and maybe label it differently. Rod to figure this out.
@ -66,13 +66,13 @@ Actions:
- Rod to figure out how to do and publish an RC build that’s not just “nightly-xxxxxxxxxxxxxx” - Rod to figure out how to do and publish an RC build that’s not just “nightly-xxxxxxxxxxxxxx”
- Chris will test packages against URL PR and write up results - Chris will test packages against URL PR and write up results
### [#1413](https://github.com/iojs/io.js/issues/1413) combining TC and Node core call ### [#1413](https://github.com/nodejs/io.js/issues/1413) combining TC and Node core call
* Mikeal: last dev-policy call brought up the suggestion of combining TC calls for both projects, with an eye on merging it would be good to understand what both groups do. Single meeting for both would be good. * Mikeal: last dev-policy call brought up the suggestion of combining TC calls for both projects, with an eye on merging it would be good to understand what both groups do. Single meeting for both would be good.
* Discussed timing - we span more timezones than they do so our slot of 1pm PST makes more sense to get Rod and Fedor in at the same time. Could either be Tue or Wed UTC, they have a meeting the day before us. * Discussed timing - we span more timezones than they do so our slot of 1pm PST makes more sense to get Rod and Fedor in at the same time. Could either be Tue or Wed UTC, they have a meeting the day before us.
* No strong disagreement * No strong disagreement
### [#1416](https://github.com/iojs/io.js/issues/1416) io.js diff node.js foundation ### [#1416](https://github.com/nodejs/io.js/issues/1416) io.js diff node.js foundation
* Mikeal: Foundation doc is huge compared to ours and also contains some formalisation of our process that we just haven’t formalised yet. The diff contains a lot of those and some _actual_ changes too. Open for discussion amongst the community. * Mikeal: Foundation doc is huge compared to ours and also contains some formalisation of our process that we just haven’t formalised yet. The diff contains a lot of those and some _actual_ changes too. Open for discussion amongst the community.
* Rod: LTS discussion starting next week. * Rod: LTS discussion starting next week.

40
doc/tc-meetings/2015-04-22.md
View File

@ -4,20 +4,20 @@
* **Public YouTube feed**: http://www.youtube.com/watch?v=s7LIMsTFaps * **Public YouTube feed**: http://www.youtube.com/watch?v=s7LIMsTFaps
* **Google Plus Event page**: https://plus.google.com/events/co7i7pv2a51270jat7jvkfcue64 * **Google Plus Event page**: https://plus.google.com/events/co7i7pv2a51270jat7jvkfcue64
* **GitHub Issue**: https://github.com/iojs/io.js/issues/1502 * **GitHub Issue**: https://github.com/nodejs/io.js/issues/1502
* **Original Minutes Google Doc**: https://docs.google.com/document/d/1G4aJ2OwiW2WphW7Vz2OW56VRot8xRBFitluKsuYPxk0 * **Original Minutes Google Doc**: https://docs.google.com/document/d/1G4aJ2OwiW2WphW7Vz2OW56VRot8xRBFitluKsuYPxk0
## Agenda ## Agenda
Extracted from https://github.com/iojs/io.js/labels/tc-agenda prior to meeting. Extracted from https://github.com/nodejs/io.js/labels/tc-agenda prior to meeting.
* [#1130](https://github.com/iojs/io.js/issues/1130) Nominating Jeremiah Senkpiel @Fishrock123 to the TC * [#1130](https://github.com/nodejs/io.js/issues/1130) Nominating Jeremiah Senkpiel @Fishrock123 to the TC
* [#1481](https://github.com/iojs/io.js/issues/1481) Nominating @mikeal to the TC * [#1481](https://github.com/nodejs/io.js/issues/1481) Nominating @mikeal to the TC
* [#1500](https://github.com/iojs/io.js/issues/1500) Nominating Brian White @mscdex to the TC * [#1500](https://github.com/nodejs/io.js/issues/1500) Nominating Brian White @mscdex to the TC
* [#1501](https://github.com/iojs/io.js/issues/1501) Nominating Shigeki Ohtsu @shigeki to the TC * [#1501](https://github.com/nodejs/io.js/issues/1501) Nominating Shigeki Ohtsu @shigeki to the TC
* [#1393](https://github.com/iojs/io.js/issues/1393) Ready to upgrade to V8 4.2? * [#1393](https://github.com/nodejs/io.js/issues/1393) Ready to upgrade to V8 4.2?
* [#1413](https://github.com/iojs/io.js/issues/1413) Combined node.js/io.js TC/Core Call * [#1413](https://github.com/nodejs/io.js/issues/1413) Combined node.js/io.js TC/Core Call
* [#1416](https://github.com/iojs/io.js/issues/1416) Diffing io.js and the Node.js Foundation * [#1416](https://github.com/nodejs/io.js/issues/1416) Diffing io.js and the Node.js Foundation
### Present ### Present
@ -34,9 +34,9 @@ Extracted from https://github.com/iojs/io.js/labels/tc-agenda prior to meeting.
### Review of last meeting ### Review of last meeting
* [#1393](https://github.com/iojs/io.js/issues/1393) Ready to upgrade to V8 4.2? * [#1393](https://github.com/nodejs/io.js/issues/1393) Ready to upgrade to V8 4.2?
* [#1413](https://github.com/iojs/io.js/issues/1413) combining TC and Node core call * [#1413](https://github.com/nodejs/io.js/issues/1413) combining TC and Node core call
* [#1416](https://github.com/iojs/io.js/issues/1416) io.js diff node.js foundation * [#1416](https://github.com/nodejs/io.js/issues/1416) io.js diff node.js foundation
### Quick stand-up ### Quick stand-up
@ -53,7 +53,7 @@ Extracted from https://github.com/iojs/io.js/labels/tc-agenda prior to meeting.
## Minutes ## Minutes
### [#1130](https://github.com/iojs/io.js/issues/1130) Nominating Jeremiah Senkpiel @Fishrock123 to the TC ### [#1130](https://github.com/nodejs/io.js/issues/1130) Nominating Jeremiah Senkpiel @Fishrock123 to the TC
Voted: Voted:
@ -66,21 +66,21 @@ Voted:
**Action: Jeremiah Senkpiel is now a member of the io.js Technical Committee!** **Action: Jeremiah Senkpiel is now a member of the io.js Technical Committee!**
### [#1481](https://github.com/iojs/io.js/issues/1481) Nominating @mikeal to the TC ### [#1481](https://github.com/nodejs/io.js/issues/1481) Nominating @mikeal to the TC
* Bert, Rod: Discussion regarding the potential consequences of expanding the TC and how that might work if a merger with node happens. * Bert, Rod: Discussion regarding the potential consequences of expanding the TC and how that might work if a merger with node happens.
Discussed consequences of expansion for merger and for the practicalities of meeting. Discussed consequences of expansion for merger and for the practicalities of meeting.
### [#1500](https://github.com/iojs/io.js/issues/1500) Nominating Brian White @mscdex to the TC ### [#1500](https://github.com/nodejs/io.js/issues/1500) Nominating Brian White @mscdex to the TC
_See above_ _See above_
### [#1501](https://github.com/iojs/io.js/issues/1501) Nominating Shigeki Ohtsu @shigeki to the TC ### [#1501](https://github.com/nodejs/io.js/issues/1501) Nominating Shigeki Ohtsu @shigeki to the TC
_See above_ _See above_
### [#1393](https://github.com/iojs/io.js/issues/1393) Ready to upgrade to V8 4.2? ### [#1393](https://github.com/nodejs/io.js/issues/1393) Ready to upgrade to V8 4.2?
Rod: no formal “RC” builds yet but master is now going out on nightlies, they have a 2.0.0-pre version string now. Discussed whether we want formal RC builds or not. No strong opinions. Rod: no formal “RC” builds yet but master is now going out on nightlies, they have a 2.0.0-pre version string now. Discussed whether we want formal RC builds or not. No strong opinions.
@ -100,17 +100,17 @@ Rod: any other breaking changes worth discussing?
Ben: process.send() ready but not merged, any objections? - no objections. Ben: process.send() ready but not merged, any objections? - no objections.
Chris: https://github.com/iojs/io.js/milestones/2.0.0 new label “land-on-master” to indicate PRs that are still targeting the v1.x branch. Chris: https://github.com/nodejs/io.js/milestones/2.0.0 new label “land-on-master” to indicate PRs that are still targeting the v1.x branch.
Ben & Bert discussed Ben’s possible timers rewrite - Ben implemented a heap and red-black tree in JS, turned out to be a bit faster but not complete yet and Ben has been distracted on other projects. ** Ben & Bert discussed Ben’s possible timers rewrite - Ben implemented a heap and red-black tree in JS, turned out to be a bit faster but not complete yet and Ben has been distracted on other projects. **
### [#1413](https://github.com/iojs/io.js/issues/1413) Combined node.js/io.js TC/Core Call ### [#1413](https://github.com/nodejs/io.js/issues/1413) Combined node.js/io.js TC/Core Call
Bert: probably not this week, intent is for next week. Bert: probably not this week, intent is for next week.
Jeremiah: there had been discussion around forming a convergence WG to handle some of this so as to not require everyone’s time except when necessary. Jeremiah: there had been discussion around forming a convergence WG to handle some of this so as to not require everyone’s time except when necessary.
### [#1416](https://github.com/iojs/io.js/issues/1416) Diffing io.js and the Node.js Foundation ### [#1416](https://github.com/nodejs/io.js/issues/1416) Diffing io.js and the Node.js Foundation
_Nothing new to discuss_ _Nothing new to discuss_

32
doc/tc-meetings/2015-04-29.md
View File

@ -4,17 +4,17 @@
* **Public YouTube feed**: http://www.youtube.com/watch?v=-e675TT4WEA * **Public YouTube feed**: http://www.youtube.com/watch?v=-e675TT4WEA
* **Google Plus Event page**: https://plus.google.com/events/cei87pqnichrtt4qggbbo656bpk * **Google Plus Event page**: https://plus.google.com/events/cei87pqnichrtt4qggbbo656bpk
* **GitHub Issue**: https://github.com/iojs/io.js/issues/1557 * **GitHub Issue**: https://github.com/nodejs/io.js/issues/1557
* **Original Minutes Google Doc**: https://docs.google.com/document/d/1C9nfm_5EhNz1jifITbtQcnGBX4R9vktoZ9KsFiCU7sQ * **Original Minutes Google Doc**: https://docs.google.com/document/d/1C9nfm_5EhNz1jifITbtQcnGBX4R9vktoZ9KsFiCU7sQ
## Agenda ## Agenda
Extracted from https://github.com/iojs/io.js/labels/tc-agenda prior to meeting. Extracted from https://github.com/nodejs/io.js/labels/tc-agenda prior to meeting.
* Release Proposal: v2.0.0 [#1532](https://github.com/iojs/io.js/pull/1532) * Release Proposal: v2.0.0 [#1532](https://github.com/nodejs/io.js/pull/1532)
* Forward-port from v1.x [#1559](https://github.com/iojs/io.js/pull/1559) * Forward-port from v1.x [#1559](https://github.com/nodejs/io.js/pull/1559)
* Convergence plan (https://github.com/jasnell/dev-policy/pull/66) * Convergence plan (https://github.com/jasnell/dev-policy/pull/66)
* Combined node.js/io.js TC/core call about convergence doc [#1413](https://github.com/iojs/io.js/issues/1413) * Combined node.js/io.js TC/core call about convergence doc [#1413](https://github.com/nodejs/io.js/issues/1413)
### Present ### Present
@ -31,13 +31,13 @@ Extracted from https://github.com/iojs/io.js/labels/tc-agenda prior to meeting.
### Review of last meeting ### Review of last meeting
* [#1130](https://github.com/iojs/io.js/issues/1130) Nominating Jeremiah Senkpiel @Fishrock123 to the TC * [#1130](https://github.com/nodejs/io.js/issues/1130) Nominating Jeremiah Senkpiel @Fishrock123 to the TC
* [#1481](https://github.com/iojs/io.js/issues/1481) Nominating @mikeal to the TC * [#1481](https://github.com/nodejs/io.js/issues/1481) Nominating @mikeal to the TC
* [#1500](https://github.com/iojs/io.js/issues/1500) Nominating Brian White @mscdex to the TC * [#1500](https://github.com/nodejs/io.js/issues/1500) Nominating Brian White @mscdex to the TC
* [#1501](https://github.com/iojs/io.js/issues/1501) Nominating Shigeki Ohtsu @shigeki to the TC * [#1501](https://github.com/nodejs/io.js/issues/1501) Nominating Shigeki Ohtsu @shigeki to the TC
* [#1393](https://github.com/iojs/io.js/issues/1393) Ready to upgrade to V8 4.2? * [#1393](https://github.com/nodejs/io.js/issues/1393) Ready to upgrade to V8 4.2?
* [#1413](https://github.com/iojs/io.js/issues/1413) Combined node.js/io.js TC/Core Call * [#1413](https://github.com/nodejs/io.js/issues/1413) Combined node.js/io.js TC/Core Call
* [#1416](https://github.com/iojs/io.js/issues/1416) Diffing io.js and the Node.js Foundation * [#1416](https://github.com/nodejs/io.js/issues/1416) Diffing io.js and the Node.js Foundation
### Quick stand-up ### Quick stand-up
@ -55,7 +55,7 @@ Extracted from https://github.com/iojs/io.js/labels/tc-agenda prior to meeting.
## Minutes ## Minutes
### Release Proposal: v2.0.0 [#1532](https://github.com/iojs/io.js/pull/1532) ### Release Proposal: v2.0.0 [#1532](https://github.com/nodejs/io.js/pull/1532)
* Domenic: * Domenic:
- v8 changes merged - v8 changes merged
@ -77,7 +77,7 @@ Extracted from https://github.com/iojs/io.js/labels/tc-agenda prior to meeting.
Chris, Trevor: discussion about how the `master` and `next` branches are used. Chris, Trevor: discussion about how the `master` and `next` branches are used.
* process.send changes will slip for v2.0 * process.send changes will slip for v2.0
* waiting for Petka’s comment and review on url changes (https://github.com/iojs/io.js/pull/1561) * waiting for Petka’s comment and review on url changes (https://github.com/nodejs/io.js/pull/1561)
* release 2.x asap (friday) * release 2.x asap (friday)
After the release: After the release:
@ -86,7 +86,7 @@ After the release:
* api-breaking changes will land on the ‘next’ branch alongside v8 upgrades. master will be merged into next regularly * api-breaking changes will land on the ‘next’ branch alongside v8 upgrades. master will be merged into next regularly
* fixes are backported to the maintenance (v1.x) branch * fixes are backported to the maintenance (v1.x) branch
### Forward-port from v1.x [#1559](https://github.com/iojs/io.js/pull/1559) ### Forward-port from v1.x [#1559](https://github.com/nodejs/io.js/pull/1559)
Discussed current plan for backporting patches to maintenance patches. Discussed current plan for backporting patches to maintenance patches.
@ -94,7 +94,7 @@ Discussed current plan for backporting patches to maintenance patches.
### Convergence plan (https://github.com/jasnell/dev-policy/pull/66) ### Convergence plan (https://github.com/jasnell/dev-policy/pull/66)
### Combined node.js/io.js TC/core call [#1413](https://github.com/iojs/io.js/issues/1413) ### Combined node.js/io.js TC/core call [#1413](https://github.com/nodejs/io.js/issues/1413)
## Next meeting ## Next meeting

2
src/node.cc
View File

@ -3603,7 +3603,7 @@ void Init(int* argc,
defined(__ARM_ARCH_6T2__) || \ defined(__ARM_ARCH_6T2__) || \
defined(__ARM_ARCH_6ZK__) || \ defined(__ARM_ARCH_6ZK__) || \
defined(__ARM_ARCH_6Z__) defined(__ARM_ARCH_6Z__)
// See https://github.com/iojs/io.js/issues/1376 // See https://github.com/nodejs/io.js/issues/1376
// and https://code.google.com/p/v8/issues/detail?id=4019 // and https://code.google.com/p/v8/issues/detail?id=4019
// TODO(bnoordhuis): Remove test/parallel/test-arm-math-exp-regress-1376.js // TODO(bnoordhuis): Remove test/parallel/test-arm-math-exp-regress-1376.js
// and this workaround when v8:4019 has been fixed and the patch back-ported. // and this workaround when v8:4019 has been fixed and the patch back-ported.

2
test/parallel/test-arm-math-exp-regress-1376.js
View File

@ -1,4 +1,4 @@
// See https://github.com/iojs/io.js/issues/1376 // See https://github.com/nodejs/io.js/issues/1376
// and https://code.google.com/p/v8/issues/detail?id=4019 // and https://code.google.com/p/v8/issues/detail?id=4019
Math.abs(-0.5); Math.abs(-0.5);

2
test/parallel/test-buffer.js
View File

@ -1172,7 +1172,7 @@ assert.throws(function() {
b.equals('abc'); b.equals('abc');
}); });
// Regression test for https://github.com/iojs/io.js/issues/649. // Regression test for https://github.com/nodejs/io.js/issues/649.
assert.throws(function() { Buffer(1422561062959).toString('utf8'); }); assert.throws(function() { Buffer(1422561062959).toString('utf8'); });
var ps = Buffer.poolSize; var ps = Buffer.poolSize;

2
test/parallel/test-event-emitter-get-max-listeners.js
View File

@ -12,7 +12,7 @@ assert.strictEqual(emitter.getMaxListeners(), 0);
emitter.setMaxListeners(3); emitter.setMaxListeners(3);
assert.strictEqual(emitter.getMaxListeners(), 3); assert.strictEqual(emitter.getMaxListeners(), 3);
// https://github.com/iojs/io.js/issues/523 - second call should not throw. // https://github.com/nodejs/io.js/issues/523 - second call should not throw.
var recv = {}; var recv = {};
EventEmitter.prototype.on.call(recv, 'event', function() {}); EventEmitter.prototype.on.call(recv, 'event', function() {});
EventEmitter.prototype.on.call(recv, 'event', function() {}); EventEmitter.prototype.on.call(recv, 'event', function() {});

2
test/parallel/test-preload.js
View File

@ -81,7 +81,7 @@ child_process.exec(nodeBinary + ' '
assert.ok(/worker terminated with code 43/.test(stdout)); assert.ok(/worker terminated with code 43/.test(stdout));
}); });
// https://github.com/iojs/io.js/issues/1691 // https://github.com/nodejs/io.js/issues/1691
var originalCwd = process.cwd(); var originalCwd = process.cwd();
process.chdir(path.join(__dirname, '../fixtures/')); process.chdir(path.join(__dirname, '../fixtures/'));
child_process.exec(nodeBinary + ' ' child_process.exec(nodeBinary + ' '

2
test/parallel/test-stringbytes-external.js
View File

@ -107,7 +107,7 @@ var PRE_3OF4_APEX = Math.ceil((EXTERN_APEX / 4) * 3) - RADIOS;
} }
})(); })();
// https://github.com/iojs/io.js/issues/1024 // https://github.com/nodejs/io.js/issues/1024
(function() { (function() {
var a = Array(1 << 20).join('x'); var a = Array(1 << 20).join('x');
var b = Buffer(a, 'ucs2').toString('ucs2'); var b = Buffer(a, 'ucs2').toString('ucs2');

2
test/parallel/test-tls-connect-no-host.js
View File

@ -13,7 +13,7 @@ var path = require('path');
var cert = fs.readFileSync(path.join(common.fixturesDir, 'test_cert.pem')); var cert = fs.readFileSync(path.join(common.fixturesDir, 'test_cert.pem'));
var key = fs.readFileSync(path.join(common.fixturesDir, 'test_key.pem')); var key = fs.readFileSync(path.join(common.fixturesDir, 'test_key.pem'));
// https://github.com/iojs/io.js/issues/1489 // https://github.com/nodejs/io.js/issues/1489
// tls.connect(options) with no options.host should accept a cert with // tls.connect(options) with no options.host should accept a cert with
// CN:'localhost' // CN:'localhost'
tls.createServer({ tls.createServer({

2
test/parallel/test-url.js
View File

@ -1562,7 +1562,7 @@ relativeTests2.forEach(function(relativeTest) {
// https://github.com/iojs/io.js/pull/1036 // https://github.com/nodejs/io.js/pull/1036
var throws = [ var throws = [
undefined, undefined,
null, null,

4
test/parallel/test-vm-debug-context.js
View File

@ -27,7 +27,7 @@ assert.strictEqual(vm.runInDebugContext(0), 0);
assert.strictEqual(vm.runInDebugContext(null), null); assert.strictEqual(vm.runInDebugContext(null), null);
assert.strictEqual(vm.runInDebugContext(undefined), undefined); assert.strictEqual(vm.runInDebugContext(undefined), undefined);
// See https://github.com/iojs/io.js/issues/1190, accessing named interceptors // See https://github.com/nodejs/io.js/issues/1190, accessing named interceptors
// and accessors inside a debug event listener should not crash. // and accessors inside a debug event listener should not crash.
(function() { (function() {
var Debug = vm.runInDebugContext('Debug'); var Debug = vm.runInDebugContext('Debug');
@ -51,7 +51,7 @@ assert.strictEqual(vm.runInDebugContext(undefined), undefined);
assert.equal(breaks, 1); assert.equal(breaks, 1);
})(); })();
// See https://github.com/iojs/io.js/issues/1190, fatal errors should not // See https://github.com/nodejs/io.js/issues/1190, fatal errors should not
// crash the process. // crash the process.
var script = common.fixturesDir + '/vm-run-in-debug-context.js'; var script = common.fixturesDir + '/vm-run-in-debug-context.js';
var proc = spawn(process.execPath, [script]); var proc = spawn(process.execPath, [script]);