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

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

PR-URL: nodejs/node#1715
Reviewed-By: Roman Reiss <me@silverwind.io>

COLLABORATOR_GUIDE.md

@@ -96,7 +96,7 @@ information regarding the change process:
   appropriate.
 
 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.
 
 Additionally:

ROADMAP.md

@@ -60,7 +60,7 @@ The [Tracing WG](https://github.com/nodejs/tracing-wg) is driving this effort:
 * async-listener - userland module that will dogfood AsyncWrap as well as provide many often requested debugging features.
 * Tracing
   * Add tracing support for more platforms (LTTng, etc).
-  * [Unify the Tracing endpoint](https://github.com/nodejs/node/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 Node.js.
 
 ## Ecosystem Automation

WORKING_GROUPS.md

@@ -105,41 +105,40 @@ language.
 
 Each language community maintains its own membership.
 
-* [iojs-ar - Arabic (اللغة العربية)](http://github.com/nodejs/iojs-ar)
-* [iojs-bg - Bulgarian (български език)](http://github.com/nodejs/iojs-bg)
-* [iojs-bn - Bengali (বাংলা)](http://github.com/nodejs/iojs-bn)
-* [iojs-cn - Chinese (中文)](http://github.com/nodejs/iojs-cn)
-* [iojs-cs - Czech (Český Jazyk)](http://github.com/nodejs/iojs-cs)
-* [iojs-da - Danish (Dansk)](http://github.com/nodejs/iojs-da)
-* [iojs-de - German (Deutsch)](http://github.com/nodejs/iojs-de)
-* [iojs-el - Greek (Ελληνικά)](http://github.com/nodejs/iojs-el)
-* [iojs-es - Spanish (Español)](http://github.com/nodejs/iojs-es)
-* [iojs-fa - Persian (فارسی)](http://github.com/nodejs/iojs-fa)
-* [iojs-fi - Finnish (Suomi)](http://github.com/nodejs/iojs-fi)
-* [iojs-fr - French (Français)](http://github.com/nodejs/iojs-fr)
-* [iojs-he - Hebrew (עברית)](http://github.com/nodejs/iojs-he)
-* [iojs-hi - Hindi (फिजी बात)](http://github.com/nodejs/iojs-hi)
-* [iojs-hu - Hungarian (Magyar)](http://github.com/nodejs/iojs-hu)
-* [iojs-id - Indonesian (Bahasa Indonesia)](http://github.com/nodejs/iojs-id)
-* [iojs-it - Italian (Italiano)](http://github.com/nodejs/iojs-it)
-* [iojs-ja - Japanese (日本語)](http://github.com/nodejs/iojs-ja)
-* [iojs-ka - Georgian (ქართული)](http://github.com/nodejs/iojs-ka)
-* [iojs-ko - Korean (조선말)](http://github.com/nodejs/iojs-ko)
-* [iojs-mk - Macedonian (Mакедонски)](http://github.com/nodejs/iojs-mk)
-* [iojs-ms - Malay (بهاس ملايو)](http://github.com/nodejs/iojs-ms)
-* [iojs-nl - Dutch (Nederlands)](http://github.com/nodejs/iojs-nl)
-* [iojs-no - Norwegian (Norsk)](http://github.com/nodejs/iojs-no)
-* [iojs-pl - Polish (Język Polski)](http://github.com/nodejs/iojs-pl)
-* [iojs-pt - Portuguese (Português)](http://github.com/nodejs/iojs-pt)
-* [iojs-ro - Romanian (Română)](http://github.com/nodejs/iojs-ro)
-* [iojs-ru - Russian (Русский)](http://github.com/nodejs/iojs-ru)
-* [iojs-sv - Swedish (Svenska)](http://github.com/nodejs/iojs-sv)
-* [iojs-ta - Tamil (தமிழ்)](http://github.com/nodejs/iojs-ta)
-* [iojs-tr - Turkish (Türkçe)](http://github.com/nodejs/iojs-tr)
-* [iojs-tw - Taiwanese (Hō-ló)](http://github.com/nodejs/iojs-tw)
-* [iojs-uk - Ukrainian (Українська)](http://github.com/nodejs/iojs-uk)
-* [iojs-vi - Vietnamese (Tiếng Việtnam)](http://github.com/nodejs/iojs-vi)
-
+* [iojs-ar - Arabic (اللغة العربية)](https://github.com/nodejs/iojs-ar)
+* [iojs-bg - Bulgarian (български език)](https://github.com/nodejs/iojs-bg)
+* [iojs-bn - Bengali (বাংলা)](https://github.com/nodejs/iojs-bn)
+* [iojs-cn - Chinese (中文)](https://github.com/nodejs/iojs-cn)
+* [iojs-cs - Czech (Český Jazyk)](https://github.com/nodejs/iojs-cs)
+* [iojs-da - Danish (Dansk)](https://github.com/nodejs/iojs-da)
+* [iojs-de - German (Deutsch)](https://github.com/nodejs/iojs-de)
+* [iojs-el - Greek (Ελληνικά)](https://github.com/nodejs/iojs-el)
+* [iojs-es - Spanish (Español)](https://github.com/nodejs/iojs-es)
+* [iojs-fa - Persian (فارسی)](https://github.com/nodejs/iojs-fa)
+* [iojs-fi - Finnish (Suomi)](https://github.com/nodejs/iojs-fi)
+* [iojs-fr - French (Français)](https://github.com/nodejs/iojs-fr)
+* [iojs-he - Hebrew (עברית)](https://github.com/nodejs/iojs-he)
+* [iojs-hi - Hindi (फिजी बात)](https://github.com/nodejs/iojs-hi)
+* [iojs-hu - Hungarian (Magyar)](https://github.com/nodejs/iojs-hu)
+* [iojs-id - Indonesian (Bahasa Indonesia)](https://github.com/nodejs/iojs-id)
+* [iojs-it - Italian (Italiano)](https://github.com/nodejs/iojs-it)
+* [iojs-ja - Japanese (日本語)](https://github.com/nodejs/iojs-ja)
+* [iojs-ka - Georgian (ქართული)](https://github.com/nodejs/iojs-ka)
+* [iojs-ko - Korean (조선말)](https://github.com/nodejs/iojs-ko)
+* [iojs-mk - Macedonian (Mакедонски)](https://github.com/nodejs/iojs-mk)
+* [iojs-ms - Malay (بهاس ملايو)](https://github.com/nodejs/iojs-ms)
+* [iojs-nl - Dutch (Nederlands)](https://github.com/nodejs/iojs-nl)
+* [iojs-no - Norwegian (Norsk)](https://github.com/nodejs/iojs-no)
+* [iojs-pl - Polish (Język Polski)](https://github.com/nodejs/iojs-pl)
+* [iojs-pt - Portuguese (Português)](https://github.com/nodejs/iojs-pt)
+* [iojs-ro - Romanian (Română)](https://github.com/nodejs/iojs-ro)
+* [iojs-ru - Russian (Русский)](https://github.com/nodejs/iojs-ru)
+* [iojs-sv - Swedish (Svenska)](https://github.com/nodejs/iojs-sv)
+* [iojs-ta - Tamil (தமிழ்)](https://github.com/nodejs/iojs-ta)
+* [iojs-tr - Turkish (Türkçe)](https://github.com/nodejs/iojs-tr)
+* [iojs-tw - Taiwanese (Hō-ló)](https://github.com/nodejs/iojs-tw)
+* [iojs-uk - Ukrainian (Українська)](https://github.com/nodejs/iojs-uk)
+* [iojs-vi - Vietnamese (Tiếng Việtnam)](https://github.com/nodejs/iojs-vi)
 
 ### [Evangelism](https://github.com/nodejs/evangelism)
 

doc/tc-meetings/2014-12-10.md

@@ -2,23 +2,23 @@
 
 ## 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 
-* Move readable-stream to iojs org and make authoritative source for io.js to pull _from_ https://github.com/iojs/io.js/issues/55 
-* Deprecate domains https://github.com/iojs/io.js/issues/66 
-* Decide how to go forward with caine https://github.com/iojs/io.js/issues/117 
-*  Is it io.js, IO.js, or something else? https://github.com/iojs/io.js/issues/118
+* @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/nodejs/io.js/issues/55
+* Deprecate domains https://github.com/nodejs/io.js/issues/66
+* 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/nodejs/io.js/issues/118
 * Build automation update
 * 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
-* 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
 
 * **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
 
 ## Minutes
@@ -35,13 +35,13 @@ https://github.com/iojs/io.js/issues/62
 
 ### @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**
 
 ### 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
 * Discussed the potential difference with joyent/node
@@ -54,21 +54,21 @@ https://github.com/iojs/io.js/issues/55
 
 ### 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
 * 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
 * Trevor: domains inhibit progress because of their invasiveness
 * 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:
   - Accept PR #15
   - **Document that domains are on the way out: soft deprecation** (no util.deprecate())
 
 ### 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
 * Chris: primary concern with having an automated bot is the incoming experience for users (like having a join bot on IRC)
@@ -79,28 +79,28 @@ https://github.com/iojs/io.js/issues/117
 
 ### 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)
 * 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”**
 * 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)
 
 ### Build automation update
 
 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
  - 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)
- - 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
 
-https://github.com/iojs/io.js/issues/62
+https://github.com/nodejs/io.js/issues/62 
 
 * Chris is asking for input
 * 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
 
-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
 * 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,8 +132,8 @@ https://github.com/iojs/io.js/issues/11
 
 ###  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 release.txt 
+* Ben: suggested a release.txt
 * Rod: **leave it up to the build team to work out the mechanics of releases and release.txt and/or release.json and come back to TC for approval or adjustments prior to formal release** (i.e. no need to bikeshed on this here right now)

doc/tc-meetings/2014-12-17.md

@@ -3,16 +3,16 @@
 ## Links
 
 * **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
 
 ## 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
-* Release Cycle Proposal #168 https://github.com/iojs/io.js/issues/168
-* Module search security #176 https://github.com/iojs/io.js/pull/176 
+* Bundle tick processor with iojs #158 https://github.com/nodejs/io.js/issues/158
+* Release Cycle Proposal #168 https://github.com/nodejs/io.js/issues/168
+* Module search security #176 https://github.com/nodejs/io.js/pull/176 
 * Dealing with feature requests 
 
 ## 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 
 
-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
 * 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,15 +46,15 @@ https://github.com/iojs/io.js/issues/158
 
 ### 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.
 * Rod: consensus seems to be around having stability, predictability, lead-time but more frequent releases.
 * **Bert: Move discussion to #168. Still premature to discuss here.**
 
 ### 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
 * Isaac ~ -1 on this because EACCES already happens when you don’t have permission

doc/tc-meetings/2014-12-30.md

@@ -3,17 +3,17 @@
 ## Links
 
 * **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
 
 ## 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
-* module: force require('process') to return a reference to process #206 https://github.com/iojs/io.js/pull/206
-* File copyright policy #216 https://github.com/iojs/io.js/pull/216
-* Rename v0.12 to v1.0.0 https://github.com/iojs/io.js/issues/218
+* 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/nodejs/io.js/pull/206
+* File copyright policy #216 https://github.com/nodejs/io.js/pull/216
+* Rename v0.12 to v1.0.0 https://github.com/nodejs/io.js/issues/218
 * Merge strategy (v0.10 and joyent/node)
 
 ## 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 
 
-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.
 * 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
 
-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
 * 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
@@ -62,14 +62,14 @@ https://github.com/iojs/io.js/pull/206
 
 ### 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
 * **Group agreed that Rod will take this issue and seek legal advice to find a way forward**
 
 ### 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.
 * Bert: -1