Update all 'iojs' GitHub links to 'nodejs' organization

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:
@@ -132,7 +132,7 @@ $ git merge --ff-only origin/master
 Apply external patches
 
 ```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

CONTRIBUTING.md

@@ -23,13 +23,13 @@ This document will guide you through the contribution process.
 
 ### 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.
 
 ```text
 $ git clone git@github.com:username/io.js.git
 $ 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?
@@ -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.
 
 In case of doubt, open an issue in the
-[issue tracker](https://github.com/iojs/io.js/issues/) or contact one of the
-[project Collaborators](https://github.com/iojs/io.js/#current-project-team-members)
+[issue tracker](https://github.com/nodejs/io.js/issues/) or contact one of the
+[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
 frustrating than seeing your hard work go to waste because your vision
 does not align with the project team.

GOVERNANCE.md

@@ -24,7 +24,7 @@ For the current list of TC members, see the project
 
 ## 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
 TC on an ongoing basis.
 

README.md

@@ -1,7 +1,7 @@
 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
 [joyent/node](https://github.com/joyent/node).
@@ -255,7 +255,7 @@ as `deps/icu` (You'll have: `deps/icu/source/...`)
 * [GOVERNANCE.md](./GOVERNANCE.md)
 * IRC:
   [#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)
 
 
 

ROADMAP.md

@@ -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 [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.
 * 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/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.
 
 ## Ecosystem Automation

WORKING_GROUPS.md

@@ -1,7 +1,7 @@
 # io.js Working Groups
 
 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.
 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)
 * [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
 website for the `io.js` project.
@@ -41,7 +41,7 @@ Its responsibilities are:
 releases and features.
 * 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
 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.
 
 
-### [Build](https://github.com/iojs/build)
+### [Build](https://github.com/nodejs/build)
 
 The build working group's purpose is to create and maintain a
 distributed automation infrastructure.
@@ -72,7 +72,7 @@ Its responsibilities are:
 * 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
 transparency of software written in io.js.
@@ -105,43 +105,43 @@ language.
 
 Each language community maintains its own membership.
 
-* [iojs-ar - Arabic (اللغة العربية)](http://github.com/iojs/iojs-ar)
-* [iojs-bg - Bulgarian (български език)](http://github.com/iojs/iojs-bg)
-* [iojs-bn - Bengali (বাংলা)](http://github.com/iojs/iojs-bn)
-* [iojs-cn - Chinese (中文)](http://github.com/iojs/iojs-cn)
-* [iojs-cs - Czech (Český Jazyk)](http://github.com/iojs/iojs-cs)
-* [iojs-da - Danish (Dansk)](http://github.com/iojs/iojs-da)
-* [iojs-de - German (Deutsch)](http://github.com/iojs/iojs-de)
-* [iojs-el - Greek (Ελληνικά)](http://github.com/iojs/iojs-el)
-* [iojs-es - Spanish (Español)](http://github.com/iojs/iojs-es)
-* [iojs-fa - Persian (فارسی)](http://github.com/iojs/iojs-fa)
-* [iojs-fi - Finnish (Suomi)](http://github.com/iojs/iojs-fi)
-* [iojs-fr - French (Français)](http://github.com/iojs/iojs-fr)
-* [iojs-he - Hebrew (עברית)](http://github.com/iojs/iojs-he)
-* [iojs-hi - Hindi (फिजी बात)](http://github.com/iojs/iojs-hi)
-* [iojs-hu - Hungarian (Magyar)](http://github.com/iojs/iojs-hu)
-* [iojs-id - Indonesian (Bahasa Indonesia)](http://github.com/iojs/iojs-id)
-* [iojs-it - Italian (Italiano)](http://github.com/iojs/iojs-it)
-* [iojs-ja - Japanese (日本語)](http://github.com/iojs/iojs-ja)
-* [iojs-ka - Georgian (ქართული)](http://github.com/iojs/iojs-ka)
-* [iojs-ko - Korean (조선말)](http://github.com/iojs/iojs-ko)
-* [iojs-mk - Macedonian (Mакедонски)](http://github.com/iojs/iojs-mk)
-* [iojs-ms - Malay (بهاس ملايو)](http://github.com/iojs/iojs-ms)
-* [iojs-nl - Dutch (Nederlands)](http://github.com/iojs/iojs-nl)
-* [iojs-no - Norwegian (Norsk)](http://github.com/iojs/iojs-no)
-* [iojs-pl - Polish (Język Polski)](http://github.com/iojs/iojs-pl)
-* [iojs-pt - Portuguese (Português)](http://github.com/iojs/iojs-pt)
-* [iojs-ro - Romanian (Română)](http://github.com/iojs/iojs-ro)
-* [iojs-ru - Russian (Русский)](http://github.com/iojs/iojs-ru)
-* [iojs-sv - Swedish (Svenska)](http://github.com/iojs/iojs-sv)
-* [iojs-ta - Tamil (தமிழ்)](http://github.com/iojs/iojs-ta)
-* [iojs-tr - Turkish (Türkçe)](http://github.com/iojs/iojs-tr)
-* [iojs-tw - Taiwanese (Hō-ló)](http://github.com/iojs/iojs-tw)
-* [iojs-uk - Ukrainian (Українська)](http://github.com/iojs/iojs-uk)
-* [iojs-vi - Vietnamese (Tiếng Việtnam)](http://github.com/iojs/iojs-vi)
-
-
-### [Evangelism](https://github.com/iojs/evangelism)
+* [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)
 
 The evangelism working group promotes the accomplishments
 of io.js and lets the community know how they can get involved.
@@ -155,7 +155,7 @@ Their responsibilities are:
 content.
 
 
-### [Roadmap](https://github.com/iojs/roadmap)
+### [Roadmap](https://github.com/nodejs/roadmap)
 
 The roadmap working group is responsible for user community outreach
 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)
 
 
-### [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
 Docker images for the `io.js` project.
@@ -180,7 +180,7 @@ Their responsibilities are:
 * 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
 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:
 
-* 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.
-* 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.
 * Maintaining the C++ Addon API within the io.js project, in subordination to
   the io.js TC.
@@ -203,7 +203,7 @@ Their responsibilities are:
   community advance notice of changes.
 
 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
 

doc/releases.md

@@ -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).
 
-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
 
@@ -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.
 
-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