lukechilds
/
node
mirror of https://github.com/lukechilds/node.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
14886 Commits
131 Branches
446 Tags
325 MiB
Tree: c775514e56
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'c775514e56'
${ noResults }
node/README.md

394 lines
17 KiB
Raw Normal View History

doc: use consistent markdown in README Improve markdown practices in README: * consistent header indicators * consistent emphasis indicators * wrap bare URLs in `<` and `>` * wrap at 80 chars * specifying language in fenced code PR-URL: https://github.com/nodejs/node/pull/7971 Reviewed-By: Сковорода Никита Андреевич <chalkerx@gmail.com> Reviewed-By: Michaël Zasso <mic.besace@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
9 years ago
# Node.js
tools: add release tool and docs, remove old tools Also added binary download documentation to the README.md and GPG release key fingerprint for @rvagg. PR-URL: https://github.com/iojs/io.js/pull/681 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Fedor Indutny <fedor@indutny.com>
10 years ago
Add CII Best Practices badge to README.md Node.js has earned the Linux Foundation Core Infrastructure Initiative (CII) best practices badge. This change lets people see that, including a link for more information. The badge lets users and potential users of Node.js know that Node.js follows best practices. It may also help spur other projects to follow Node.js's lead. My thanks to Rod Vagg, who did the work to see that Node.js earned the badge. PR-URL: https://github.com/nodejs/node/pull/6819 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Rod Vagg <rod@vagg.org> Reviewed-By: Myles Borins <myles.borins@gmail.com>
9 years ago
[![Gitter](https://badges.gitter.im/Join Chat.svg)](https://gitter.im/nodejs/node?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge) [![CII Best Practices](https://bestpractices.coreinfrastructure.org/projects/29/badge)](https://bestpractices.coreinfrastructure.org/projects/29)
newcomer resources in README Closes GH-579.
14 years ago
doc: add brief Node.js overview to README Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com> PR-URL: https://github.com/nodejs/node/pull/4174
9 years ago
Node.js is a JavaScript runtime built on Chrome's V8 JavaScript engine. Node.js
uses an event-driven, non-blocking I/O model that makes it lightweight and
efficient. The Node.js package ecosystem, npm, is the largest ecosystem of open
source libraries in the world.
doc: replace head of readme with updated text PR-URL: https://github.com/nodejs/node/pull/3482 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com>
9 years ago
The Node.js project is supported by the
[Node.js Foundation](https://nodejs.org/en/foundation/). Contributions,
policies and releases are managed under an
[open governance model](./GOVERNANCE.md). We are also bound by a
[Code of Conduct](./CODE_OF_CONDUCT.md).
docs: simple project messaging. Reviewed-By: Fedor Indutny <fedor@indutny.com> PR-URL: https://github.com/iojs/io.js/pull/24
10 years ago
doc: replace head of readme with updated text PR-URL: https://github.com/nodejs/node/pull/3482 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com>
9 years ago
If you need help using or installing Node.js, please use the
[nodejs/help](https://github.com/nodejs/help) issue tracker.
docs: improve discoverability of Code of Conduct - move CoC from CONTRIBUTING to top-level, separate COC file - add note/link in CONTRIBUTING - add note/link in README (both at top, and newcomer resources) - move CoC section in CONTRIBUTING to top of file PR-URL: https://github.com/nodejs/node/pull/3774 Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>
9 years ago
doc: move the readme newcomers section Move the newcomers section to be more noticeable to those who it will be needed by. Also removed some entries that are now effectively duplicates. They are all in the above section. PR-URL: https://github.com/nodejs/node/pull/6681 Reviewed-By: Myles Borins <myles.borins@gmail.com> Reviewed-By: Minwoo Jung <jmwsoft@gmail.com> Reviewed-By: Alexander Makarenko <estliberitas@gmail.com>
9 years ago
## Resources for Newcomers
doc: clarify that the node.js irc channel is not under tsc oversight There has been some question about whether the #node.js irc channel falls under the TSC oversight or not. See: https://github.com/nodejs/node/issues/7746 This clarifies that the #node.js irc channel is a community provided resource that is not currently directly under the oversight of the TSC/CTC. PR-URL: https://github.com/nodejs/node/pull/7810 Reviewed-By: Bryan Hughes <bryan@nebri.us> Reviewed-By: Julien Gilli <jgilli@nodejs.org> Reviewed-By: Сковорода Никита Андреевич <chalkerx@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com>
9 years ago
### Official Resources
* [Website][]
doc: add link to help repo in README Include link to Node.js help repo (for end user questions on how to use Node.js) in the README. PR-URL: https://github.com/nodejs/node/pull/8570 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Teddy Katz <teddy.katz@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Сковорода Никита Андреевич <chalkerx@gmail.com>
8 years ago
* [Node.js Help][]
doc: clarify that the node.js irc channel is not under tsc oversight There has been some question about whether the #node.js irc channel falls under the TSC oversight or not. See: https://github.com/nodejs/node/issues/7746 This clarifies that the #node.js irc channel is a community provided resource that is not currently directly under the oversight of the TSC/CTC. PR-URL: https://github.com/nodejs/node/pull/7810 Reviewed-By: Bryan Hughes <bryan@nebri.us> Reviewed-By: Julien Gilli <jgilli@nodejs.org> Reviewed-By: Сковорода Никита Андреевич <chalkerx@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com>
9 years ago
* [Contributing to the project][]
* IRC (node core development): [#node-dev on chat.freenode.net][]
### Unofficial Resources
* IRC (general questions): [#node.js on chat.freenode.net][]. Please see
doc: use consistent markdown in README Improve markdown practices in README: * consistent header indicators * consistent emphasis indicators * wrap bare URLs in `<` and `>` * wrap at 80 chars * specifying language in fenced code PR-URL: https://github.com/nodejs/node/pull/7971 Reviewed-By: Сковорода Никита Андреевич <chalkerx@gmail.com> Reviewed-By: Michaël Zasso <mic.besace@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
9 years ago
<http://nodeirc.info/> for more information regarding the `#node.js` IRC
channel.
doc: clarify that the node.js irc channel is not under tsc oversight There has been some question about whether the #node.js irc channel falls under the TSC oversight or not. See: https://github.com/nodejs/node/issues/7746 This clarifies that the #node.js irc channel is a community provided resource that is not currently directly under the oversight of the TSC/CTC. PR-URL: https://github.com/nodejs/node/pull/7810 Reviewed-By: Bryan Hughes &lt;bryan@nebri.us&gt; Reviewed-By: Julien Gilli &lt;jgilli@nodejs.org&gt; Reviewed-By: Сковорода Никита Андреевич &lt;chalkerx@gmail.com&gt; Reviewed-By: Rich Trott &lt;rtrott@gmail.com&gt;
9 years ago
doc: use consistent markdown in README Improve markdown practices in README: * consistent header indicators * consistent emphasis indicators * wrap bare URLs in `&lt;` and `&gt;` * wrap at 80 chars * specifying language in fenced code PR-URL: https://github.com/nodejs/node/pull/7971 Reviewed-By: Сковорода Никита Андреевич &lt;chalkerx@gmail.com&gt; Reviewed-By: Michaël Zasso &lt;mic.besace@gmail.com&gt; Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt;
9 years ago
_Please note that unofficial resources are neither managed by (nor necessarily
doc: clarify that the node.js irc channel is not under tsc oversight There has been some question about whether the #node.js irc channel falls under the TSC oversight or not. See: https://github.com/nodejs/node/issues/7746 This clarifies that the #node.js irc channel is a community provided resource that is not currently directly under the oversight of the TSC/CTC. PR-URL: https://github.com/nodejs/node/pull/7810 Reviewed-By: Bryan Hughes &lt;bryan@nebri.us&gt; Reviewed-By: Julien Gilli &lt;jgilli@nodejs.org&gt; Reviewed-By: Сковорода Никита Андреевич &lt;chalkerx@gmail.com&gt; Reviewed-By: Rich Trott &lt;rtrott@gmail.com&gt;
9 years ago
endorsed by) the Node.js TSC/CTC. Specifically, such resources are not
currently covered by the [Node.js Moderation Policy][] and the selection and
doc: use consistent markdown in README Improve markdown practices in README: * consistent header indicators * consistent emphasis indicators * wrap bare URLs in `&lt;` and `&gt;` * wrap at 80 chars * specifying language in fenced code PR-URL: https://github.com/nodejs/node/pull/7971 Reviewed-By: Сковорода Никита Андреевич &lt;chalkerx@gmail.com&gt; Reviewed-By: Michaël Zasso &lt;mic.besace@gmail.com&gt; Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt;
9 years ago
actions of resource operators/moderators are not subject to TSC/CTC oversight._
doc: move the readme newcomers section Move the newcomers section to be more noticeable to those who it will be needed by. Also removed some entries that are now effectively duplicates. They are all in the above section. PR-URL: https://github.com/nodejs/node/pull/6681 Reviewed-By: Myles Borins &lt;myles.borins@gmail.com&gt; Reviewed-By: Minwoo Jung &lt;jmwsoft@gmail.com&gt; Reviewed-By: Alexander Makarenko &lt;estliberitas@gmail.com&gt;
9 years ago
doc: document release types in readme PR-URL: https://github.com/nodejs/node/pull/3482 Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt; Reviewed-By: Rich Trott &lt;rtrott@gmail.com&gt;
9 years ago
## Release Types
The Node.js project maintains multiple types of releases:
doc: change references to Stable to Current With v6 we plan to rename the Stable release line to Current. This commit updates all references to Stable in the codebase. It will have to land along side updates to other repos within the org. Refs: https://github.com/nodejs/nodejs.org/issues/669 PR-URL: https://github.com/nodejs/node/pull/6318 Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt; Reviewed-By: Сковорода Никита Андреевич &lt;chalkerx@gmail.com&gt; Reviewed-By: Evan Lucas &lt;evanlucas@me.com&gt;
9 years ago
* **Current**: Released from active development branches of this repository,
doc: document release types in readme PR-URL: https://github.com/nodejs/node/pull/3482 Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt; Reviewed-By: Rich Trott &lt;rtrott@gmail.com&gt;
9 years ago
versioned by [SemVer](http://semver.org/) and signed by a member of the
[Release Team](#release-team).
doc: change references to Stable to Current With v6 we plan to rename the Stable release line to Current. This commit updates all references to Stable in the codebase. It will have to land along side updates to other repos within the org. Refs: https://github.com/nodejs/nodejs.org/issues/669 PR-URL: https://github.com/nodejs/node/pull/6318 Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt; Reviewed-By: Сковорода Никита Андреевич &lt;chalkerx@gmail.com&gt; Reviewed-By: Evan Lucas &lt;evanlucas@me.com&gt;
9 years ago
Code for Current releases is organized in this repository by major version
doc: document release types in readme PR-URL: https://github.com/nodejs/node/pull/3482 Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt; Reviewed-By: Rich Trott &lt;rtrott@gmail.com&gt;
9 years ago
number, For example: [v4.x](https://github.com/nodejs/node/tree/v4.x).
doc: change references to Stable to Current With v6 we plan to rename the Stable release line to Current. This commit updates all references to Stable in the codebase. It will have to land along side updates to other repos within the org. Refs: https://github.com/nodejs/nodejs.org/issues/669 PR-URL: https://github.com/nodejs/node/pull/6318 Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt; Reviewed-By: Сковорода Никита Андреевич &lt;chalkerx@gmail.com&gt; Reviewed-By: Evan Lucas &lt;evanlucas@me.com&gt;
9 years ago
The major version number of Current releases will increment every 6 months
doc: document release types in readme PR-URL: https://github.com/nodejs/node/pull/3482 Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt; Reviewed-By: Rich Trott &lt;rtrott@gmail.com&gt;
9 years ago
allowing for breaking changes to be introduced. This happens in April and
doc: change references to Stable to Current With v6 we plan to rename the Stable release line to Current. This commit updates all references to Stable in the codebase. It will have to land along side updates to other repos within the org. Refs: https://github.com/nodejs/nodejs.org/issues/669 PR-URL: https://github.com/nodejs/node/pull/6318 Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt; Reviewed-By: Сковорода Никита Андреевич &lt;chalkerx@gmail.com&gt; Reviewed-By: Evan Lucas &lt;evanlucas@me.com&gt;
9 years ago
October every year. Current release lines beginning in October each year have
a maximum support life of 8 months. Current release lines beginning in April
doc: document release types in readme PR-URL: https://github.com/nodejs/node/pull/3482 Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt; Reviewed-By: Rich Trott &lt;rtrott@gmail.com&gt;
9 years ago
each year will convert to LTS (see below) after 6 months and receive further
support for 30 months.
* **LTS**: Releases that receive Long-term Support, with a focus on stability
doc: change references to Stable to Current With v6 we plan to rename the Stable release line to Current. This commit updates all references to Stable in the codebase. It will have to land along side updates to other repos within the org. Refs: https://github.com/nodejs/nodejs.org/issues/669 PR-URL: https://github.com/nodejs/node/pull/6318 Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt; Reviewed-By: Сковорода Никита Андреевич &lt;chalkerx@gmail.com&gt; Reviewed-By: Evan Lucas &lt;evanlucas@me.com&gt;
9 years ago
and security. Every second Current release line (major version) will become an
doc: document release types in readme PR-URL: https://github.com/nodejs/node/pull/3482 Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt; Reviewed-By: Rich Trott &lt;rtrott@gmail.com&gt;
9 years ago
LTS line and receive 18 months of _Active LTS_ support and a further 12
months of _Maintenance_. LTS release lines are given alphabetically
doc: fix typo in Readme.md Spelling mistake - `begining` &gt; `beginning` PR-URL: https://github.com/nodejs/node/pull/5017 Reviewed-By: Rich Trott &lt;rtrott@gmail.com&gt; Reviewed-By: Sakthipriyan Vairamani &lt;thechargingvolcano@gmail.com&gt; Reviewed-By: Michaël Zasso &lt;mic.besace@gmail.com&gt;
9 years ago
ordered codenames, beginning with v4 Argon. LTS releases are less frequent
doc: document release types in readme PR-URL: https://github.com/nodejs/node/pull/3482 Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt; Reviewed-By: Rich Trott &lt;rtrott@gmail.com&gt;
9 years ago
and will attempt to maintain consistent major and minor version numbers,
only incrementing patch version numbers. There are no breaking changes or
feature additions, except in some special circumstances. More information
can be found in the [LTS README](https://github.com/nodejs/LTS/).
doc: change references to Stable to Current With v6 we plan to rename the Stable release line to Current. This commit updates all references to Stable in the codebase. It will have to land along side updates to other repos within the org. Refs: https://github.com/nodejs/nodejs.org/issues/669 PR-URL: https://github.com/nodejs/node/pull/6318 Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt; Reviewed-By: Сковорода Никита Андреевич &lt;chalkerx@gmail.com&gt; Reviewed-By: Evan Lucas &lt;evanlucas@me.com&gt;
9 years ago
* **Nightly**: Versions of code in this repository on the current Current
doc: document release types in readme PR-URL: https://github.com/nodejs/node/pull/3482 Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt; Reviewed-By: Rich Trott &lt;rtrott@gmail.com&gt;
9 years ago
branch, automatically built every 24-hours where changes exist. Use with
caution.
tools: add release tool and docs, remove old tools Also added binary download documentation to the README.md and GPG release key fingerprint for @rvagg. PR-URL: https://github.com/iojs/io.js/pull/681 Reviewed-By: Ben Noordhuis &lt;info@bnoordhuis.nl&gt; Reviewed-By: Fedor Indutny &lt;fedor@indutny.com&gt;
10 years ago
## Download
doc: add comma in README to increase clarity Minor change to increase clarity of what is being referenced to.
10 years ago
Binaries, installers, and source tarballs are available at
node: rename from io.js to node This commit replaces instances of io.js with Node.js, based on the recent convergence. There are some remaining instances of io.js, related to build and the installer. Fixes: https://github.com/nodejs/node/issues/2361 PR-URL: https://github.com/nodejs/node/pull/2367 Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt; Reviewed-By: João Reis &lt;reis@janeasystems.com&gt;
10 years ago
<https://nodejs.org>.
tools: add release tool and docs, remove old tools Also added binary download documentation to the README.md and GPG release key fingerprint for @rvagg. PR-URL: https://github.com/iojs/io.js/pull/681 Reviewed-By: Ben Noordhuis &lt;info@bnoordhuis.nl&gt; Reviewed-By: Fedor Indutny &lt;fedor@indutny.com&gt;
10 years ago
doc: change references to Stable to Current With v6 we plan to rename the Stable release line to Current. This commit updates all references to Stable in the codebase. It will have to land along side updates to other repos within the org. Refs: https://github.com/nodejs/nodejs.org/issues/669 PR-URL: https://github.com/nodejs/node/pull/6318 Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt; Reviewed-By: Сковорода Никита Андреевич &lt;chalkerx@gmail.com&gt; Reviewed-By: Evan Lucas &lt;evanlucas@me.com&gt;
9 years ago
**Current** and **LTS** releases are available at
doc: document release types in readme PR-URL: https://github.com/nodejs/node/pull/3482 Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt; Reviewed-By: Rich Trott &lt;rtrott@gmail.com&gt;
9 years ago
<https://nodejs.org/download/release/>, listed under their version strings.
The [latest](https://nodejs.org/download/release/latest/) directory is an
doc: change references to Stable to Current With v6 we plan to rename the Stable release line to Current. This commit updates all references to Stable in the codebase. It will have to land along side updates to other repos within the org. Refs: https://github.com/nodejs/nodejs.org/issues/669 PR-URL: https://github.com/nodejs/node/pull/6318 Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt; Reviewed-By: Сковорода Никита Андреевич &lt;chalkerx@gmail.com&gt; Reviewed-By: Evan Lucas &lt;evanlucas@me.com&gt;
9 years ago
alias for the latest Current release. The latest LTS release from an LTS
doc: fix description about the latest-codename fix description about the latest LTS release download page to make it clear PR-URL: https://github.com/nodejs/node/pull/4583 Reviewed-By: Rod Vagg &lt;rod@vagg.org&gt; Reviewed-By: Colin Ihrig &lt;cjihrig@gmail.com&gt; Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt;
9 years ago
line is available in the form: latest-_codename_. For example:
<https://nodejs.org/download/release/latest-argon>
tools: add release tool and docs, remove old tools Also added binary download documentation to the README.md and GPG release key fingerprint for @rvagg. PR-URL: https://github.com/iojs/io.js/pull/681 Reviewed-By: Ben Noordhuis &lt;info@bnoordhuis.nl&gt; Reviewed-By: Fedor Indutny &lt;fedor@indutny.com&gt;
10 years ago
**Nightly** builds are available at
node: rename from io.js to node This commit replaces instances of io.js with Node.js, based on the recent convergence. There are some remaining instances of io.js, related to build and the installer. Fixes: https://github.com/nodejs/node/issues/2361 PR-URL: https://github.com/nodejs/node/pull/2367 Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt; Reviewed-By: João Reis &lt;reis@janeasystems.com&gt;
10 years ago
<https://nodejs.org/download/nightly/>, listed under their version
tools: add release tool and docs, remove old tools Also added binary download documentation to the README.md and GPG release key fingerprint for @rvagg. PR-URL: https://github.com/iojs/io.js/pull/681 Reviewed-By: Ben Noordhuis &lt;info@bnoordhuis.nl&gt; Reviewed-By: Fedor Indutny &lt;fedor@indutny.com&gt;
10 years ago
string which includes their date (in UTC time) and the commit SHA at
the HEAD of the release.
**API documentation** is available in each release and nightly
doc: document release types in readme PR-URL: https://github.com/nodejs/node/pull/3482 Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt; Reviewed-By: Rich Trott &lt;rtrott@gmail.com&gt;
9 years ago
directory under _docs_. <https://nodejs.org/api/> points to the API
documentation of the latest stable version.
tools: add release tool and docs, remove old tools Also added binary download documentation to the README.md and GPG release key fingerprint for @rvagg. PR-URL: https://github.com/iojs/io.js/pull/681 Reviewed-By: Ben Noordhuis &lt;info@bnoordhuis.nl&gt; Reviewed-By: Fedor Indutny &lt;fedor@indutny.com&gt;
10 years ago
### Verifying Binaries
doc: use consistent markdown in README Improve markdown practices in README: * consistent header indicators * consistent emphasis indicators * wrap bare URLs in `&lt;` and `&gt;` * wrap at 80 chars * specifying language in fenced code PR-URL: https://github.com/nodejs/node/pull/7971 Reviewed-By: Сковорода Никита Андреевич &lt;chalkerx@gmail.com&gt; Reviewed-By: Michaël Zasso &lt;mic.besace@gmail.com&gt; Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt;
9 years ago
Current, LTS and Nightly download directories all contain a _SHASUM256.txt_
tools: add release tool and docs, remove old tools Also added binary download documentation to the README.md and GPG release key fingerprint for @rvagg. PR-URL: https://github.com/iojs/io.js/pull/681 Reviewed-By: Ben Noordhuis &lt;info@bnoordhuis.nl&gt; Reviewed-By: Fedor Indutny &lt;fedor@indutny.com&gt;
10 years ago
file that lists the SHA checksums for each file available for
doc: add copy about how to curl SHA256.txt Currently we include instructions on how to check the sha of a downloaded tar-ball, but do not include instruction on how to get the `SHA256.txt` file. This has led to confusion with people thinking that the SHA256.txt is included in that tarball. This commit includes instructions on how to use curl to download the `SHA256.txt` prior to the instructions on how to verify the sha. Refs: https://github.com/nodejs/help/issues/113 Refs: https://github.com/nodejs/help/issues/137 PR-URL: https://github.com/nodejs/node/pull/6120 Reviewed-By: Colin Ihrig &lt;cjihrig@gmail.com&gt; Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt;
9 years ago
download.
doc: use consistent markdown in README Improve markdown practices in README: * consistent header indicators * consistent emphasis indicators * wrap bare URLs in `&lt;` and `&gt;` * wrap at 80 chars * specifying language in fenced code PR-URL: https://github.com/nodejs/node/pull/7971 Reviewed-By: Сковорода Никита Андреевич &lt;chalkerx@gmail.com&gt; Reviewed-By: Michaël Zasso &lt;mic.besace@gmail.com&gt; Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt;
9 years ago
The _SHASUM256.txt_ can be downloaded using curl.
doc: add copy about how to curl SHA256.txt Currently we include instructions on how to check the sha of a downloaded tar-ball, but do not include instruction on how to get the `SHA256.txt` file. This has led to confusion with people thinking that the SHA256.txt is included in that tarball. This commit includes instructions on how to use curl to download the `SHA256.txt` prior to the instructions on how to verify the sha. Refs: https://github.com/nodejs/help/issues/113 Refs: https://github.com/nodejs/help/issues/137 PR-URL: https://github.com/nodejs/node/pull/6120 Reviewed-By: Colin Ihrig &lt;cjihrig@gmail.com&gt; Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt;
9 years ago
doc: use consistent markdown in README Improve markdown practices in README: * consistent header indicators * consistent emphasis indicators * wrap bare URLs in `&lt;` and `&gt;` * wrap at 80 chars * specifying language in fenced code PR-URL: https://github.com/nodejs/node/pull/7971 Reviewed-By: Сковорода Никита Андреевич &lt;chalkerx@gmail.com&gt; Reviewed-By: Michaël Zasso &lt;mic.besace@gmail.com&gt; Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt;
9 years ago
```console
doc: add copy about how to curl SHA256.txt Currently we include instructions on how to check the sha of a downloaded tar-ball, but do not include instruction on how to get the `SHA256.txt` file. This has led to confusion with people thinking that the SHA256.txt is included in that tarball. This commit includes instructions on how to use curl to download the `SHA256.txt` prior to the instructions on how to verify the sha. Refs: https://github.com/nodejs/help/issues/113 Refs: https://github.com/nodejs/help/issues/137 PR-URL: https://github.com/nodejs/node/pull/6120 Reviewed-By: Colin Ihrig &lt;cjihrig@gmail.com&gt; Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt;
9 years ago
$ curl -O https://nodejs.org/dist/vx.y.z/SHASUMS256.txt
```
To check that a downloaded file matches the checksum, run
tools: add release tool and docs, remove old tools Also added binary download documentation to the README.md and GPG release key fingerprint for @rvagg. PR-URL: https://github.com/iojs/io.js/pull/681 Reviewed-By: Ben Noordhuis &lt;info@bnoordhuis.nl&gt; Reviewed-By: Fedor Indutny &lt;fedor@indutny.com&gt;
10 years ago
it through `sha256sum` with a command such as:
doc: use consistent markdown in README Improve markdown practices in README: * consistent header indicators * consistent emphasis indicators * wrap bare URLs in `&lt;` and `&gt;` * wrap at 80 chars * specifying language in fenced code PR-URL: https://github.com/nodejs/node/pull/7971 Reviewed-By: Сковорода Никита Андреевич &lt;chalkerx@gmail.com&gt; Reviewed-By: Michaël Zasso &lt;mic.besace@gmail.com&gt; Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt;
9 years ago
```console
node: rename from io.js to node This commit replaces instances of io.js with Node.js, based on the recent convergence. There are some remaining instances of io.js, related to build and the installer. Fixes: https://github.com/nodejs/node/issues/2361 PR-URL: https://github.com/nodejs/node/pull/2367 Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt; Reviewed-By: João Reis &lt;reis@janeasystems.com&gt;
10 years ago
$ grep node-vx.y.z.tar.gz SHASUMS256.txt | sha256sum -c -
tools: add release tool and docs, remove old tools Also added binary download documentation to the README.md and GPG release key fingerprint for @rvagg. PR-URL: https://github.com/iojs/io.js/pull/681 Reviewed-By: Ben Noordhuis &lt;info@bnoordhuis.nl&gt; Reviewed-By: Fedor Indutny &lt;fedor@indutny.com&gt;
10 years ago
```
node: rename from io.js to node This commit replaces instances of io.js with Node.js, based on the recent convergence. There are some remaining instances of io.js, related to build and the installer. Fixes: https://github.com/nodejs/node/issues/2361 PR-URL: https://github.com/nodejs/node/pull/2367 Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt; Reviewed-By: João Reis &lt;reis@janeasystems.com&gt;
10 years ago
_(Where "node-vx.y.z.tar.gz" is the name of the file you have
tools: add release tool and docs, remove old tools Also added binary download documentation to the README.md and GPG release key fingerprint for @rvagg. PR-URL: https://github.com/iojs/io.js/pull/681 Reviewed-By: Ben Noordhuis &lt;info@bnoordhuis.nl&gt; Reviewed-By: Fedor Indutny &lt;fedor@indutny.com&gt;
10 years ago
downloaded)_
doc: change references to Stable to Current With v6 we plan to rename the Stable release line to Current. This commit updates all references to Stable in the codebase. It will have to land along side updates to other repos within the org. Refs: https://github.com/nodejs/nodejs.org/issues/669 PR-URL: https://github.com/nodejs/node/pull/6318 Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt; Reviewed-By: Сковорода Никита Андреевич &lt;chalkerx@gmail.com&gt; Reviewed-By: Evan Lucas &lt;evanlucas@me.com&gt;
9 years ago
Additionally, Current and LTS releases (not Nightlies) have GPG signed
doc: document release types in readme PR-URL: https://github.com/nodejs/node/pull/3482 Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt; Reviewed-By: Rich Trott &lt;rtrott@gmail.com&gt;
9 years ago
copies of SHASUM256.txt files available as SHASUM256.txt.asc. You can use
`gpg` to verify that the file has not been tampered with.
tools: add release tool and docs, remove old tools Also added binary download documentation to the README.md and GPG release key fingerprint for @rvagg. PR-URL: https://github.com/iojs/io.js/pull/681 Reviewed-By: Ben Noordhuis &lt;info@bnoordhuis.nl&gt; Reviewed-By: Fedor Indutny &lt;fedor@indutny.com&gt;
10 years ago
To verify a SHASUM256.txt.asc, you will first need to import all of
the GPG keys of individuals authorized to create releases. They are
doc: reorg release team to separate section included: * commands to run to import all active keys * list of previous Node.js releasers key details PR-URL: https://github.com/nodejs/node/pull/2455 Reviewed-By: Colin Ihrig &lt;cjihrig@gmail.com&gt;
9 years ago
listed at the bottom of this README under [Release Team](#release-team).
Use a command such as this to import the keys:
tools: add release tool and docs, remove old tools Also added binary download documentation to the README.md and GPG release key fingerprint for @rvagg. PR-URL: https://github.com/iojs/io.js/pull/681 Reviewed-By: Ben Noordhuis &lt;info@bnoordhuis.nl&gt; Reviewed-By: Fedor Indutny &lt;fedor@indutny.com&gt;
10 years ago
doc: use consistent markdown in README Improve markdown practices in README: * consistent header indicators * consistent emphasis indicators * wrap bare URLs in `&lt;` and `&gt;` * wrap at 80 chars * specifying language in fenced code PR-URL: https://github.com/nodejs/node/pull/7971 Reviewed-By: Сковорода Никита Андреевич &lt;chalkerx@gmail.com&gt; Reviewed-By: Michaël Zasso &lt;mic.besace@gmail.com&gt; Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt;
9 years ago
```console
$ gpg --keyserver pool.sks-keyservers.net --recv-keys DD8F2338BAE7501E3DD5AC78C273792F7D83545D
tools: add release tool and docs, remove old tools Also added binary download documentation to the README.md and GPG release key fingerprint for @rvagg. PR-URL: https://github.com/iojs/io.js/pull/681 Reviewed-By: Ben Noordhuis &lt;info@bnoordhuis.nl&gt; Reviewed-By: Fedor Indutny &lt;fedor@indutny.com&gt;
10 years ago
```
doc: reorg release team to separate section included: * commands to run to import all active keys * list of previous Node.js releasers key details PR-URL: https://github.com/nodejs/node/pull/2455 Reviewed-By: Colin Ihrig &lt;cjihrig@gmail.com&gt;
9 years ago
_(See the bottom of this README for a full script to import active
release keys)_
tools: add release tool and docs, remove old tools Also added binary download documentation to the README.md and GPG release key fingerprint for @rvagg. PR-URL: https://github.com/iojs/io.js/pull/681 Reviewed-By: Ben Noordhuis &lt;info@bnoordhuis.nl&gt; Reviewed-By: Fedor Indutny &lt;fedor@indutny.com&gt;
10 years ago
You can then use `gpg --verify SHASUMS256.txt.asc` to verify that the
node: rename from io.js to node This commit replaces instances of io.js with Node.js, based on the recent convergence. There are some remaining instances of io.js, related to build and the installer. Fixes: https://github.com/nodejs/node/issues/2361 PR-URL: https://github.com/nodejs/node/pull/2367 Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt; Reviewed-By: João Reis &lt;reis@janeasystems.com&gt;
10 years ago
file has been signed by an authorized member of the Node.js team.
tools: add release tool and docs, remove old tools Also added binary download documentation to the README.md and GPG release key fingerprint for @rvagg. PR-URL: https://github.com/iojs/io.js/pull/681 Reviewed-By: Ben Noordhuis &lt;info@bnoordhuis.nl&gt; Reviewed-By: Fedor Indutny &lt;fedor@indutny.com&gt;
10 years ago
Once verified, use the SHASUMS256.txt.asc file to get the checksum for
the binary verification command above.
doc: move build instructions to a new document This makes README.md easier to consume and likely less confusing for people that get it as part of a binary download. PR-URL: https://github.com/nodejs/node/pull/5634 Reviewed-By: Rich Trott &lt;rtrott@gmail.com&gt; Reviewed-By: Brian White &lt;mscdex@mscdex.net&gt; Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt;
9 years ago
## Building Node.js
doc: clarified &amp; split up contribution docs - clarified the role of &#34;collaborators&#34; - split out a governance doc - split out a collaborator guide - cleaned up the contributing doc - cleaned up the readme &amp; added collaborators list PR-URL: https://github.com/iojs/io.js/pull/233 Reviewed-By: Chris Dickinson &lt;christopher.s.dickinson@gmail.com&gt; Reviewed-By: Mikeal Rogers &lt;mikeal.rogers@gmail.com&gt; (Note: no explicit &#34;LGTM&#34; from Mikeal) Discussed at TC meeting 2015-01-07, agreed to push further amendments to governance to future PRs.
10 years ago
doc: move build instructions to a new document This makes README.md easier to consume and likely less confusing for people that get it as part of a binary download. PR-URL: https://github.com/nodejs/node/pull/5634 Reviewed-By: Rich Trott &lt;rtrott@gmail.com&gt; Reviewed-By: Brian White &lt;mscdex@mscdex.net&gt; Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt;
9 years ago
See [BUILDING.md](BUILDING.md) for instructions on how to build
Node.js from source.
merge vcbuild.bat and generate_projects.bat
14 years ago
doc: add security section to README.md PR-URL: https://github.com/nodejs/io.js/pull/1948 Reviewed-By: Ben Noordhuis &lt;info@bnoordhuis.nl&gt; Reviewed-By: Johan Bergström &lt;bugs@bergstroem.nu&gt; Reviewed-By: Jeremiah Senkpiel &lt;fishrock123@rocketmail.com&gt;
10 years ago
## Security
doc: clarified &amp; split up contribution docs - clarified the role of &#34;collaborators&#34; - split out a governance doc - split out a collaborator guide - cleaned up the contributing doc - cleaned up the readme &amp; added collaborators list PR-URL: https://github.com/iojs/io.js/pull/233 Reviewed-By: Chris Dickinson &lt;christopher.s.dickinson@gmail.com&gt; Reviewed-By: Mikeal Rogers &lt;mikeal.rogers@gmail.com&gt; (Note: no explicit &#34;LGTM&#34; from Mikeal) Discussed at TC meeting 2015-01-07, agreed to push further amendments to governance to future PRs.
10 years ago
doc: s/node.js/Node.js in readme PR-URL: https://github.com/nodejs/node/pull/3998 Reviewed-By: Colin Ihrig &lt;cjihrig@gmail.com&gt; Reviewed-By: Sakthipriyan Vairamani &lt;thechargingvolcano@gmail.com&gt; Reviewed-By: Сковорода Никита Андреевич &lt;chalkerx@gmail.com&gt; Reviewed-By: Minwoo Jung &lt;jmwsoft@gmail.com&gt;
9 years ago
All security bugs in Node.js are taken seriously and should be reported by
node: rename from io.js to node This commit replaces instances of io.js with Node.js, based on the recent convergence. There are some remaining instances of io.js, related to build and the installer. Fixes: https://github.com/nodejs/node/issues/2361 PR-URL: https://github.com/nodejs/node/pull/2367 Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt; Reviewed-By: João Reis &lt;reis@janeasystems.com&gt;
10 years ago
emailing security@nodejs.org. This will be delivered to a subset of the project
doc: add security section to README.md PR-URL: https://github.com/nodejs/io.js/pull/1948 Reviewed-By: Ben Noordhuis &lt;info@bnoordhuis.nl&gt; Reviewed-By: Johan Bergström &lt;bugs@bergstroem.nu&gt; Reviewed-By: Jeremiah Senkpiel &lt;fishrock123@rocketmail.com&gt;
10 years ago
team who handle security issues. Please don't disclose security bugs
doc: fix typo in README PR-URL: https://github.com/nodejs/node/pull/4000 Reviewed-By: Colin Ihrig &lt;cjihrig@gmail.com&gt; Reviewed-By: Saúl Ibarra Corretgé &lt;saghul@gmail.com&gt;
9 years ago
publicly until they have been handled by the security team.
doc: add security section to README.md PR-URL: https://github.com/nodejs/io.js/pull/1948 Reviewed-By: Ben Noordhuis &lt;info@bnoordhuis.nl&gt; Reviewed-By: Johan Bergström &lt;bugs@bergstroem.nu&gt; Reviewed-By: Jeremiah Senkpiel &lt;fishrock123@rocketmail.com&gt;
10 years ago
Your email will be acknowledged within 24 hours, and you’ll receive a more
detailed response to your email within 48 hours indicating the next steps in
handling your report.
doc: clarified &amp; split up contribution docs - clarified the role of &#34;collaborators&#34; - split out a governance doc - split out a collaborator guide - cleaned up the contributing doc - cleaned up the readme &amp; added collaborators list PR-URL: https://github.com/iojs/io.js/pull/233 Reviewed-By: Chris Dickinson &lt;christopher.s.dickinson@gmail.com&gt; Reviewed-By: Mikeal Rogers &lt;mikeal.rogers@gmail.com&gt; (Note: no explicit &#34;LGTM&#34; from Mikeal) Discussed at TC meeting 2015-01-07, agreed to push further amendments to governance to future PRs.
10 years ago
## Current Project Team Members
node: rename from io.js to node This commit replaces instances of io.js with Node.js, based on the recent convergence. There are some remaining instances of io.js, related to build and the installer. Fixes: https://github.com/nodejs/node/issues/2361 PR-URL: https://github.com/nodejs/node/pull/2367 Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt; Reviewed-By: João Reis &lt;reis@janeasystems.com&gt;
10 years ago
The Node.js project team comprises a group of core collaborators and a sub-group
doc: use consistent markdown in README Improve markdown practices in README: * consistent header indicators * consistent emphasis indicators * wrap bare URLs in `&lt;` and `&gt;` * wrap at 80 chars * specifying language in fenced code PR-URL: https://github.com/nodejs/node/pull/7971 Reviewed-By: Сковорода Никита Андреевич &lt;chalkerx@gmail.com&gt; Reviewed-By: Michaël Zasso &lt;mic.besace@gmail.com&gt; Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt;
9 years ago
that forms the _Core Technical Committee_ (CTC) which governs the project. For
more information about the governance of the Node.js project, see
doc: clarified &amp; split up contribution docs - clarified the role of &#34;collaborators&#34; - split out a governance doc - split out a collaborator guide - cleaned up the contributing doc - cleaned up the readme &amp; added collaborators list PR-URL: https://github.com/iojs/io.js/pull/233 Reviewed-By: Chris Dickinson &lt;christopher.s.dickinson@gmail.com&gt; Reviewed-By: Mikeal Rogers &lt;mikeal.rogers@gmail.com&gt; (Note: no explicit &#34;LGTM&#34; from Mikeal) Discussed at TC meeting 2015-01-07, agreed to push further amendments to governance to future PRs.
10 years ago
[GOVERNANCE.md](./GOVERNANCE.md).
doc: update repo docs to use &#39;CTC&#39; PR-URL: https://github.com/nodejs/node/pull/5304 Reviewed-By: Colin Ihrig &lt;cjihrig@gmail.com&gt; Reviewed-By: Jeremiah Senkpiel &lt;fishrock123@rocketmail.com&gt; Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt;
9 years ago
### CTC (Core Technical Committee)
doc: add TSC members from the combined project These members were collaborators on the old joyent/node repo prior to convergence of the Node.js and io.js projects under the Node Foundation. This updates our list to represent that they are now also part of the TSC (Technical Steering Committee), which was previously known as the io.js TC. PR-URL: https://github.com/nodejs/io.js/pull/2085 Reviewed-By: Mikeal Rogers &lt;mikeal.rogers@gmail.com&gt; Reviewed-By: Rod Vagg &lt;rod@vagg.org&gt; Membership changes also previously reviewed by many more TSC &amp; former TC members in https://github.com/nodejs/io.js/pull/1710
10 years ago
doc: use consistent markdown in README Improve markdown practices in README: * consistent header indicators * consistent emphasis indicators * wrap bare URLs in `&lt;` and `&gt;` * wrap at 80 chars * specifying language in fenced code PR-URL: https://github.com/nodejs/node/pull/7971 Reviewed-By: Сковорода Никита Андреевич &lt;chalkerx@gmail.com&gt; Reviewed-By: Michaël Zasso &lt;mic.besace@gmail.com&gt; Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt;
9 years ago
* [addaleax](https://github.com/addaleax) -
**Anna Henningsen** &lt;anna@addaleax.net&gt;
* [bnoordhuis](https://github.com/bnoordhuis) -
**Ben Noordhuis** &lt;info@bnoordhuis.nl&gt;
* [ChALkeR](https://github.com/ChALkeR) -
**Сковорода Никита Андреевич** &lt;chalkerx@gmail.com&gt;
* [chrisdickinson](https://github.com/chrisdickinson) -
**Chris Dickinson** &lt;christopher.s.dickinson@gmail.com&gt;
* [cjihrig](https://github.com/cjihrig) -
**Colin Ihrig** &lt;cjihrig@gmail.com&gt;
* [evanlucas](https://github.com/evanlucas) -
**Evan Lucas** &lt;evanlucas@me.com&gt;
* [fishrock123](https://github.com/fishrock123) -
**Jeremiah Senkpiel** &lt;fishrock123@rocketmail.com&gt;
* [indutny](https://github.com/indutny) -
**Fedor Indutny** &lt;fedor.indutny@gmail.com&gt;
* [jasnell](https://github.com/jasnell) -
**James M Snell** &lt;jasnell@gmail.com&gt;
* [mhdawson](https://github.com/mhdawson) -
**Michael Dawson** &lt;michael_dawson@ca.ibm.com&gt;
* [misterdjules](https://github.com/misterdjules) -
**Julien Gilli** &lt;jgilli@nodejs.org&gt;
* [mscdex](https://github.com/mscdex) -
**Brian White** &lt;mscdex@mscdex.net&gt;
* [ofrobots](https://github.com/ofrobots) -
**Ali Ijaz Sheikh** &lt;ofrobots@google.com&gt;
* [rvagg](https://github.com/rvagg) -
**Rod Vagg** &lt;rod@vagg.org&gt;
* [shigeki](https://github.com/shigeki) -
**Shigeki Ohtsu** &lt;ohtsu@iij.ad.jp&gt;
doc: add Myles Borins to the CTC PR-URL: https://github.com/nodejs/node/pull/8260 Reviewed-By: Сковорода Никита Андреевич &lt;chalkerx@gmail.com&gt; Reviewed-By: Anna Henningsen &lt;anna@addaleax.net&gt; Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt; Reviewed-By: Myles Borins &lt;myles.borins@gmail.com&gt;
8 years ago
* [TheAlphaNerd](https://github.com/TheAlphaNerd) -
**Myles Borins** &lt;myles.borins@gmail.com&gt;
doc: use consistent markdown in README Improve markdown practices in README: * consistent header indicators * consistent emphasis indicators * wrap bare URLs in `&lt;` and `&gt;` * wrap at 80 chars * specifying language in fenced code PR-URL: https://github.com/nodejs/node/pull/7971 Reviewed-By: Сковорода Никита Андреевич &lt;chalkerx@gmail.com&gt; Reviewed-By: Michaël Zasso &lt;mic.besace@gmail.com&gt; Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt;
9 years ago
* [trevnorris](https://github.com/trevnorris) -
**Trevor Norris** &lt;trev.norris@gmail.com&gt;
* [Trott](https://github.com/Trott) -
**Rich Trott** &lt;rtrott@gmail.com&gt;
doc: add TSC members from the combined project These members were collaborators on the old joyent/node repo prior to convergence of the Node.js and io.js projects under the Node Foundation. This updates our list to represent that they are now also part of the TSC (Technical Steering Committee), which was previously known as the io.js TC. PR-URL: https://github.com/nodejs/io.js/pull/2085 Reviewed-By: Mikeal Rogers &lt;mikeal.rogers@gmail.com&gt; Reviewed-By: Rod Vagg &lt;rod@vagg.org&gt; Membership changes also previously reviewed by many more TSC &amp; former TC members in https://github.com/nodejs/io.js/pull/1710
10 years ago
### Collaborators
doc: use consistent markdown in README Improve markdown practices in README: * consistent header indicators * consistent emphasis indicators * wrap bare URLs in `&lt;` and `&gt;` * wrap at 80 chars * specifying language in fenced code PR-URL: https://github.com/nodejs/node/pull/7971 Reviewed-By: Сковорода Никита Андреевич &lt;chalkerx@gmail.com&gt; Reviewed-By: Michaël Zasso &lt;mic.besace@gmail.com&gt; Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt;
9 years ago
* [andrasq](https://github.com/andrasq) -
**Andras** &lt;andras@kinvey.com&gt;
* [AndreasMadsen](https://github.com/AndreasMadsen) -
**Andreas Madsen** &lt;amwebdk@gmail.com&gt;
* [bengl](https://github.com/bengl) -
**Bryan English** &lt;bryan@bryanenglish.com&gt;
* [benjamingr](https://github.com/benjamingr) -
**Benjamin Gruenbaum** &lt;benjamingr@gmail.com&gt;
* [bmeck](https://github.com/bmeck) -
**Bradley Farias** &lt;bradley.meck@gmail.com&gt;
* [brendanashworth](https://github.com/brendanashworth) -
**Brendan Ashworth** &lt;brendan.ashworth@me.com&gt;
* [bzoz](https://github.com/bzoz) -
**Bartosz Sosnowski** &lt;bartosz@janeasystems.com&gt;
* [calvinmetcalf](https://github.com/calvinmetcalf) -
**Calvin Metcalf** &lt;calvin.metcalf@gmail.com&gt;
* [claudiorodriguez](https://github.com/claudiorodriguez) -
**Claudio Rodriguez** &lt;cjrodr@yahoo.com&gt;
doc: adding danbev to collaborators PR-URL: https://github.com/nodejs/node/pull/8359 Reviewed-By: Rich Trott &lt;rtrott@gmail.com&gt; Reviewed-By: Santiago Gimeno &lt;santiago.gimeno@gmail.com&gt; Reviewed-By: Jeremiah Senkpiel &lt;Fishrock123@rocketmail.com&gt;
8 years ago
* [danbev](https://github.com/danbev) -
**Daniel Bevenius** &lt;daniel.bevenius@gmail.com&gt;
doc: use consistent markdown in README Improve markdown practices in README: * consistent header indicators * consistent emphasis indicators * wrap bare URLs in `&lt;` and `&gt;` * wrap at 80 chars * specifying language in fenced code PR-URL: https://github.com/nodejs/node/pull/7971 Reviewed-By: Сковорода Никита Андреевич &lt;chalkerx@gmail.com&gt; Reviewed-By: Michaël Zasso &lt;mic.besace@gmail.com&gt; Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt;
9 years ago
* [domenic](https://github.com/domenic) -
**Domenic Denicola** &lt;d@domenic.me&gt;
* [eljefedelrodeodeljefe](https://github.com/eljefedelrodeodeljefe) -
**Robert Jefe Lindstaedt** &lt;robert.lindstaedt@gmail.com&gt;
* [estliberitas](https://github.com/estliberitas) -
**Alexander Makarenko** &lt;estliberitas@gmail.com&gt;
doc: Add fhinkel to collaborators Reviewed-By: Colin Ihrig &lt;cjihrig@gmail.com&gt; Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt; Reviewed-By: Rich Trott &lt;rtrott@gmail.com&gt; PR-URL: https://github.com/nodejs/node/pull/8052
9 years ago
* [fhinkel](https://github.com/fhinkel) -
**Franziska Hinkelmann** &lt;franziska.hinkelmann@gmail.com&gt;
doc: use consistent markdown in README Improve markdown practices in README: * consistent header indicators * consistent emphasis indicators * wrap bare URLs in `&lt;` and `&gt;` * wrap at 80 chars * specifying language in fenced code PR-URL: https://github.com/nodejs/node/pull/7971 Reviewed-By: Сковорода Никита Андреевич &lt;chalkerx@gmail.com&gt; Reviewed-By: Michaël Zasso &lt;mic.besace@gmail.com&gt; Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt;
9 years ago
* [firedfox](https://github.com/firedfox) -
**Daniel Wang** &lt;wangyang0123@gmail.com&gt;
* [geek](https://github.com/geek) -
**Wyatt Preul** &lt;wpreul@gmail.com&gt;
doc: add gibfahn to collaborators PR-URL: https://github.com/nodejs/node/pull/8533 Reviewed-By: Rich Trott &lt;rtrott@gmail.com&gt; Reviewed-By: Luigi Pinca &lt;luigipinca@gmail.com&gt; Reviewed-By: Johan Bergström &lt;bugs@bergstroem.nu&gt;
8 years ago
* [gibfahn](https://github.com/gibfahn) -
**Gibson Fahnestock** &lt;gibfahn@gmail.com&gt;
doc: use consistent markdown in README Improve markdown practices in README: * consistent header indicators * consistent emphasis indicators * wrap bare URLs in `&lt;` and `&gt;` * wrap at 80 chars * specifying language in fenced code PR-URL: https://github.com/nodejs/node/pull/7971 Reviewed-By: Сковорода Никита Андреевич &lt;chalkerx@gmail.com&gt; Reviewed-By: Michaël Zasso &lt;mic.besace@gmail.com&gt; Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt;
9 years ago
* [iarna](https://github.com/iarna) -
**Rebecca Turner** &lt;me@re-becca.org&gt;
doc: add imyller to collaborators Signed-off-by: Ilkka Myller &lt;ilkka.myller@nodefield.com&gt; PR-URL: https://github.com/nodejs/node/pull/8530 Reviewed-By: Rich Trott &lt;rtrott@gmail.com&gt; Reviewed-By: Luigi Pinca &lt;luigipinca@gmail.com&gt; Reviewed-By: Sakthipriyan Vairamani &lt;thechargingvolcano@gmail.com&gt;
8 years ago
* [imyller](https://github.com/imyller) -
**Ilkka Myller** &lt;ilkka.myller@nodefield.com&gt;
doc: use consistent markdown in README Improve markdown practices in README: * consistent header indicators * consistent emphasis indicators * wrap bare URLs in `&lt;` and `&gt;` * wrap at 80 chars * specifying language in fenced code PR-URL: https://github.com/nodejs/node/pull/7971 Reviewed-By: Сковорода Никита Андреевич &lt;chalkerx@gmail.com&gt; Reviewed-By: Michaël Zasso &lt;mic.besace@gmail.com&gt; Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt;
9 years ago
* [isaacs](https://github.com/isaacs) -
**Isaac Z. Schlueter** &lt;i@izs.me&gt;
* [iWuzHere](https://github.com/iWuzHere) -
**Imran Iqbal** &lt;imran@imraniqbal.org&gt;
* [JacksonTian](https://github.com/JacksonTian) -
**Jackson Tian** &lt;shvyo1987@gmail.com&gt;
* [jbergstroem](https://github.com/jbergstroem) -
**Johan Bergström** &lt;bugs@bergstroem.nu&gt;
* [jhamhader](https://github.com/jhamhader) -
**Yuval Brik** &lt;yuval@brik.org.il&gt;
* [joaocgreis](https://github.com/joaocgreis) -
**João Reis** &lt;reis@janeasystems.com&gt;
doc: add @joshgav to collaborators Reviewed-By: Rich Trott &lt;rtrott@gmail.com&gt; Reviewed-By: Anna Henningsen &lt;anna@addaleax.net&gt; PR-URL: https://github.com/nodejs/node/pull/8146
8 years ago
* [joshgav](https://github.com/joshgav) -
**Josh Gavant** &lt;josh.gavant@outlook.com&gt;
doc: use consistent markdown in README Improve markdown practices in README: * consistent header indicators * consistent emphasis indicators * wrap bare URLs in `&lt;` and `&gt;` * wrap at 80 chars * specifying language in fenced code PR-URL: https://github.com/nodejs/node/pull/7971 Reviewed-By: Сковорода Никита Андреевич &lt;chalkerx@gmail.com&gt; Reviewed-By: Michaël Zasso &lt;mic.besace@gmail.com&gt; Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt;
9 years ago
* [julianduque](https://github.com/julianduque) -
**Julian Duque** &lt;julianduquej@gmail.com&gt;
* [JungMinu](https://github.com/JungMinu) -
**Minwoo Jung** &lt;jmwsoft@gmail.com&gt;
* [lance](https://github.com/lance) -
**Lance Ball** &lt;lball@redhat.com&gt;
doc: add lpinca to collaborators PR-URL: https://github.com/nodejs/node/pull/8331 Reviewed-By: Rich Trott &lt;rtrott@gmail.com&gt;
8 years ago
* [lpinca](https://github.com/lpinca) -
**Luigi Pinca** &lt;luigipinca@gmail.com&gt;
doc: use consistent markdown in README Improve markdown practices in README: * consistent header indicators * consistent emphasis indicators * wrap bare URLs in `&lt;` and `&gt;` * wrap at 80 chars * specifying language in fenced code PR-URL: https://github.com/nodejs/node/pull/7971 Reviewed-By: Сковорода Никита Андреевич &lt;chalkerx@gmail.com&gt; Reviewed-By: Michaël Zasso &lt;mic.besace@gmail.com&gt; Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt;
9 years ago
* [lxe](https://github.com/lxe) -
**Aleksey Smolenchuk** &lt;lxe@lxe.co&gt;
* [matthewloring](https://github.com/matthewloring) -
**Matthew Loring** &lt;mattloring@google.com&gt;
* [mcollina](https://github.com/mcollina) -
**Matteo Collina** &lt;matteo.collina@gmail.com&gt;
* [micnic](https://github.com/micnic) -
**Nicu Micleușanu** &lt;micnic90@gmail.com&gt;
* [mikeal](https://github.com/mikeal) -
**Mikeal Rogers** &lt;mikeal.rogers@gmail.com&gt;
* [monsanto](https://github.com/monsanto) -
**Christopher Monsanto** &lt;chris@monsan.to&gt;
doc: add not-an-aardvark to collaborators PR-URL: https://github.com/nodejs/node/pull/8525 Reviewed-By: Colin Ihrig &lt;cjihrig@gmail.com&gt; Reviewed-By: Anna Henningsen &lt;anna@addaleax.net&gt; Reviewed-By: Evan Lucas &lt;evanlucas@me.com&gt; Reviewed-By: Rich Trott &lt;rtrott@gmail.com&gt;
8 years ago
* [not-an-aardvark](https://github.com/not-an-aardvark) -
**Teddy Katz** &lt;teddy.katz@gmail.com&gt;
doc: use consistent markdown in README Improve markdown practices in README: * consistent header indicators * consistent emphasis indicators * wrap bare URLs in `&lt;` and `&gt;` * wrap at 80 chars * specifying language in fenced code PR-URL: https://github.com/nodejs/node/pull/7971 Reviewed-By: Сковорода Никита Андреевич &lt;chalkerx@gmail.com&gt; Reviewed-By: Michaël Zasso &lt;mic.besace@gmail.com&gt; Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt;
9 years ago
* [Olegas](https://github.com/Olegas) -
**Oleg Elifantiev** &lt;oleg@elifantiev.ru&gt;
doc: move orangemocha to collaborators list PR-URL: https://github.com/nodejs/node/pull/8062 Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt; Reviewed-By: Johan Bergström &lt;bugs@bergstroem.nu&gt; Reviewed-By: Anna Henningsen &lt;anna@addaleax.net&gt;
9 years ago
* [orangemocha](https://github.com/orangemocha) -
**Alexis Campailla** &lt;orangemocha@nodejs.org&gt;
doc: use consistent markdown in README Improve markdown practices in README: * consistent header indicators * consistent emphasis indicators * wrap bare URLs in `&lt;` and `&gt;` * wrap at 80 chars * specifying language in fenced code PR-URL: https://github.com/nodejs/node/pull/7971 Reviewed-By: Сковорода Никита Андреевич &lt;chalkerx@gmail.com&gt; Reviewed-By: Michaël Zasso &lt;mic.besace@gmail.com&gt; Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt;
9 years ago
* [othiym23](https://github.com/othiym23) -
**Forrest L Norvell** &lt;ogd@aoaioxxysz.net&gt;
* [petkaantonov](https://github.com/petkaantonov) -
**Petka Antonov** &lt;petka_antonov@hotmail.com&gt;
* [phillipj](https://github.com/phillipj) -
**Phillip Johnsen** &lt;johphi@gmail.com&gt;
* [piscisaureus](https://github.com/piscisaureus) -
**Bert Belder** &lt;bertbelder@gmail.com&gt;
* [pmq20](https://github.com/pmq20) -
**Minqi Pan** &lt;pmq2001@gmail.com&gt;
* [princejwesley](https://github.com/princejwesley) -
**Prince John Wesley** &lt;princejohnwesley@gmail.com&gt;
* [qard](https://github.com/qard) -
**Stephen Belanger** &lt;admin@stephenbelanger.com&gt;
* [rlidwka](https://github.com/rlidwka) -
**Alex Kocharin** &lt;alex@kocharin.ru&gt;
* [rmg](https://github.com/rmg) -
**Ryan Graham** &lt;r.m.graham@gmail.com&gt;
* [robertkowalski](https://github.com/robertkowalski) -
**Robert Kowalski** &lt;rok@kowalski.gd&gt;
* [romankl](https://github.com/romankl) -
**Roman Klauke** &lt;romaaan.git@gmail.com&gt;
* [ronkorving](https://github.com/ronkorving) -
**Ron Korving** &lt;ron@ronkorving.nl&gt;
* [RReverser](https://github.com/RReverser) -
**Ingvar Stepanyan** &lt;me@rreverser.com&gt;
* [saghul](https://github.com/saghul) -
**Saúl Ibarra Corretgé** &lt;saghul@gmail.com&gt;
* [sam-github](https://github.com/sam-github) -
**Sam Roberts** &lt;vieuxtech@gmail.com&gt;
* [santigimeno](https://github.com/santigimeno) -
**Santiago Gimeno** &lt;santiago.gimeno@gmail.com&gt;
* [seishun](https://github.com/seishun) -
**Nikolai Vavilov** &lt;vvnicholas@gmail.com&gt;
* [silverwind](https://github.com/silverwind) -
**Roman Reiss** &lt;me@silverwind.io&gt;
* [srl295](https://github.com/srl295) -
**Steven R Loomis** &lt;srloomis@us.ibm.com&gt;
* [stefanmb](https://github.com/stefanmb) -
**Stefan Budeanu** &lt;stefan@budeanu.com&gt;
* [targos](https://github.com/targos) -
doc: update targos email in readme per request PR-URL: https://github.com/nodejs/node/pull/8389 Reviewed-By: Anna Henningsen &lt;anna@addaleax.net&gt; Reviewed-By: Colin Ihrig &lt;cjihrig@gmail.com&gt;
8 years ago
**Michaël Zasso** &lt;targos@protonmail.com&gt;
doc: use consistent markdown in README Improve markdown practices in README: * consistent header indicators * consistent emphasis indicators * wrap bare URLs in `&lt;` and `&gt;` * wrap at 80 chars * specifying language in fenced code PR-URL: https://github.com/nodejs/node/pull/7971 Reviewed-By: Сковорода Никита Андреевич &lt;chalkerx@gmail.com&gt; Reviewed-By: Michaël Zasso &lt;mic.besace@gmail.com&gt; Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt;
9 years ago
* [tellnes](https://github.com/tellnes) -
**Christian Tellnes** &lt;christian@tellnes.no&gt;
* [thefourtheye](https://github.com/thefourtheye) -
**Sakthipriyan Vairamani** &lt;thechargingvolcano@gmail.com&gt;
* [thekemkid](https://github.com/thekemkid) -
**Glen Keane** &lt;glenkeane.94@gmail.com&gt;
* [thlorenz](https://github.com/thlorenz) -
**Thorsten Lorenz** &lt;thlorenz@gmx.de&gt;
* [tunniclm](https://github.com/tunniclm) -
**Mike Tunnicliffe** &lt;m.j.tunnicliffe@gmail.com&gt;
* [vkurchatkin](https://github.com/vkurchatkin) -
**Vladimir Kurchatkin** &lt;vladimir.kurchatkin@gmail.com&gt;
* [whitlockjc](https://github.com/whitlockjc) -
**Jeremy Whitlock** &lt;jwhitlock@apache.org&gt;
* [yorkie](https://github.com/yorkie) -
**Yorkie Liu** &lt;yorkiefixer@gmail.com&gt;
* [yosuke-furukawa](https://github.com/yosuke-furukawa) -
**Yosuke Furukawa** &lt;yosuke.furukawa@gmail.com&gt;
* [zkat](https://github.com/zkat) -
**Kat Marchán** &lt;kzm@sykosomatic.org&gt;
build, i18n: improve Intl build, add &#34;--with-intl&#34; The two main goals of this change are: - To make it easier to build the Intl option using ICU (particularly, using a newer ICU than v8/Chromium&#39;s version) - To enable a much smaller ICU build with only English support The goal here is to get node.js binaries built this way by default so that the Intl API can be used. Additional data can be added at execution time (see Readme and wiki) More details are at https://github.com/joyent/node/pull/7719 In particular, this change adds the &#34;--with-intl=&#34; configure option to provide more ways of building &#34;Intl&#34;: - &#34;full-icu&#34; picks up an ICU from deps/icu - &#34;small-icu&#34; is similar, but builds only English - &#34;system-icu&#34; uses pkg-config to find an installed ICU - &#34;none&#34; does nothing (no Intl) For Windows builds, the &#34;full-icu&#34; or &#34;small-icu&#34; options are added to vcbuild.bat. Note that the existing &#34;--with-icu-path&#34; option is not removed from configure, but may not be used alongside the new option. Wiki changes have already been made on https://github.com/joyent/node/wiki/Installation and a new page created at https://github.com/joyent/node/wiki/Intl (marked as provisional until this change lands.) Summary of changes: * README.md : doc updates * .gitignore : added &#34;deps/icu&#34; as this is the location where ICU is unpacked to. * Makefile : added the tools/icu/* files to cpplint, but excluded a problematic file. * configure : added the &#34;--with-intl&#34; option mentioned above. Calculate at config time the list of ICU source files to use and data packaging options. * node.gyp : add the new files src/node_i18n.cc/.h as well as ICU linkage. * src/node.cc : add call into node::i18n::InitializeICUDirectory(icu_data_dir) as well as new --icu-data-dir option and NODE_ICU_DATA env variable to configure ICU data loading. This loading is only relevant in the &#34;small&#34; configuration. * src/node_i18n.cc : new source file for the above Initialize.. function, to setup ICU as needed. * tools/icu : new directory with some tools needed for this build. * tools/icu/icu-generic.gyp : new .gyp file that builds ICU in some new ways, both on unix/mac and windows. * tools/icu/icu-system.gyp : new .gyp file to build node against a pkg-config detected ICU. * tools/icu/icu_small.json : new config file for the &#34;English-only&#34; small build. * tools/icu/icutrim.py : new tool for trimming down ICU data. Reads the above .json file. * tools/icu/iculslocs.cc : new tool for repairing ICU data manifests after trim operation. * tools/icu/no-op.cc : dummy file to force .gyp into using a C++ linker. * vcbuild.bat : added small-icu and full-icu options, to call into configure. * Fixed toolset dependencies, see https://github.com/joyent/node/pull/7719#issuecomment-54641687 Note that because of a bug in gyp {CC,CXX}_host must also be set. Otherwise gcc/g++ will be used by default for part of the build. Reviewed-by: Trevor Norris &lt;trev.norris@gmail.com&gt; Reviewed-by: Fedor Indutny &lt;fedor@indutny.com&gt;
10 years ago
doc: clarify collaborators &amp; ctc members relationships inspired by this conversation https://github.com/nodejs/node/pull/7183#discussion_r73786541 PR-URL: https://github.com/nodejs/node/pull/7996 Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt; Reviewed-By: Rich Trott &lt;rtrott@gmail.com&gt; Reviewed-By: Сковорода Никита Андреевич &lt;chalkerx@gmail.com&gt; Reviewed-By: Evan Lucas &lt;evanlucas@me.com&gt; Reviewed-By: Colin Ihrig &lt;cjihrig@gmail.com&gt;
9 years ago
Collaborators (which includes CTC members) follow the
[COLLABORATOR_GUIDE.md](./COLLABORATOR_GUIDE.md) in maintaining the Node.js
project.
doc: reorg release team to separate section included: * commands to run to import all active keys * list of previous Node.js releasers key details PR-URL: https://github.com/nodejs/node/pull/2455 Reviewed-By: Colin Ihrig &lt;cjihrig@gmail.com&gt;
9 years ago
### Release Team
Releases of Node.js and io.js will be signed with one of the following GPG keys:
doc: use consistent markdown in README Improve markdown practices in README: * consistent header indicators * consistent emphasis indicators * wrap bare URLs in `&lt;` and `&gt;` * wrap at 80 chars * specifying language in fenced code PR-URL: https://github.com/nodejs/node/pull/7971 Reviewed-By: Сковорода Никита Андреевич &lt;chalkerx@gmail.com&gt; Reviewed-By: Michaël Zasso &lt;mic.besace@gmail.com&gt; Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt;
9 years ago
* **Chris Dickinson** &lt;christopher.s.dickinson@gmail.com&gt;
`9554F04D7259F04124DE6B476D5A82AC7E37093B`
* **Colin Ihrig** &lt;cjihrig@gmail.com&gt;
`94AE36675C464D64BAFA68DD7434390BDBE9B9C5`
* **Evan Lucas** &lt;evanlucas@me.com&gt;
`B9AE9905FFD7803F25714661B63B535A4C206CA9`
* **James M Snell** &lt;jasnell@keybase.io&gt;
`71DCFD284A79C3B38668286BC97EC7A07EDE3FC1`
* **Jeremiah Senkpiel** &lt;fishrock@keybase.io&gt;
`FD3A5288F042B6850C66B31F09FE44734EB7990E`
* **Myles Borins** &lt;myles.borins@gmail.com&gt;
`C4F0DFFF4E8C1A8236409D08E73BC641CC11F4C8`
* **Rod Vagg** &lt;rod@vagg.org&gt;
`DD8F2338BAE7501E3DD5AC78C273792F7D83545D`
* **Sam Roberts** &lt;octetcloud@keybase.io&gt;
`0034A06D9D9B0064CE8ADF6BF1747F4AD2306D93`
doc: reorg release team to separate section included: * commands to run to import all active keys * list of previous Node.js releasers key details PR-URL: https://github.com/nodejs/node/pull/2455 Reviewed-By: Colin Ihrig &lt;cjihrig@gmail.com&gt;
9 years ago
The full set of trusted release keys can be imported by running:
doc: use consistent markdown in README Improve markdown practices in README: * consistent header indicators * consistent emphasis indicators * wrap bare URLs in `&lt;` and `&gt;` * wrap at 80 chars * specifying language in fenced code PR-URL: https://github.com/nodejs/node/pull/7971 Reviewed-By: Сковорода Никита Андреевич &lt;chalkerx@gmail.com&gt; Reviewed-By: Michaël Zasso &lt;mic.besace@gmail.com&gt; Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt;
9 years ago
```shell
doc: reorg release team to separate section included: * commands to run to import all active keys * list of previous Node.js releasers key details PR-URL: https://github.com/nodejs/node/pull/2455 Reviewed-By: Colin Ihrig &lt;cjihrig@gmail.com&gt;
9 years ago
gpg --keyserver pool.sks-keyservers.net --recv-keys 9554F04D7259F04124DE6B476D5A82AC7E37093B
gpg --keyserver pool.sks-keyservers.net --recv-keys 94AE36675C464D64BAFA68DD7434390BDBE9B9C5
doc: add @jasnell and @sam-github to release team Fixes: https://github.com/nodejs/node/issues/2416 PR-URL: https://github.com/nodejs/node/pull/2455 Reviewed-By: Colin Ihrig &lt;cjihrig@gmail.com&gt;
9 years ago
gpg --keyserver pool.sks-keyservers.net --recv-keys 0034A06D9D9B0064CE8ADF6BF1747F4AD2306D93
doc: reorg release team to separate section included: * commands to run to import all active keys * list of previous Node.js releasers key details PR-URL: https://github.com/nodejs/node/pull/2455 Reviewed-By: Colin Ihrig &lt;cjihrig@gmail.com&gt;
9 years ago
gpg --keyserver pool.sks-keyservers.net --recv-keys FD3A5288F042B6850C66B31F09FE44734EB7990E
doc: add @jasnell and @sam-github to release team Fixes: https://github.com/nodejs/node/issues/2416 PR-URL: https://github.com/nodejs/node/pull/2455 Reviewed-By: Colin Ihrig &lt;cjihrig@gmail.com&gt;
9 years ago
gpg --keyserver pool.sks-keyservers.net --recv-keys 71DCFD284A79C3B38668286BC97EC7A07EDE3FC1
doc: reorg release team to separate section included: * commands to run to import all active keys * list of previous Node.js releasers key details PR-URL: https://github.com/nodejs/node/pull/2455 Reviewed-By: Colin Ihrig &lt;cjihrig@gmail.com&gt;
9 years ago
gpg --keyserver pool.sks-keyservers.net --recv-keys DD8F2338BAE7501E3DD5AC78C273792F7D83545D
docs: update gpg key for Myles Borins Original key did not have personal information associated with it. The new key rectifies this problem PR-URL: https://github.com/nodejs/node/pull/4657 Reviewed-By: Colin Ihrig &lt;cjihrig@gmail.com&gt; Reviewed-By: Rod Vagg &lt;rod@vagg.org&gt; Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt;
9 years ago
gpg --keyserver pool.sks-keyservers.net --recv-keys C4F0DFFF4E8C1A8236409D08E73BC641CC11F4C8
doc: add Evan Lucas to Release Team Adds Evan Lucas and his public key to the README for releases PR-URL: https://github.com/nodejs/node/pull/4579 Reviewed-By: Colin Ihrig &lt;cjihrig@gmail.com&gt; Reviewed-By: Myles Borins &lt;myles.borins@gmail.com&gt;
9 years ago
gpg --keyserver pool.sks-keyservers.net --recv-keys B9AE9905FFD7803F25714661B63B535A4C206CA9
doc: reorg release team to separate section included: * commands to run to import all active keys * list of previous Node.js releasers key details PR-URL: https://github.com/nodejs/node/pull/2455 Reviewed-By: Colin Ihrig &lt;cjihrig@gmail.com&gt;
9 years ago
```
doc: use consistent markdown in README Improve markdown practices in README: * consistent header indicators * consistent emphasis indicators * wrap bare URLs in `&lt;` and `&gt;` * wrap at 80 chars * specifying language in fenced code PR-URL: https://github.com/nodejs/node/pull/7971 Reviewed-By: Сковорода Никита Андреевич &lt;chalkerx@gmail.com&gt; Reviewed-By: Michaël Zasso &lt;mic.besace@gmail.com&gt; Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt;
9 years ago
See the section above on [Verifying Binaries](#verifying-binaries) for details
on what to do with these keys to verify that a downloaded file is official.
doc: reorg release team to separate section included: * commands to run to import all active keys * list of previous Node.js releasers key details PR-URL: https://github.com/nodejs/node/pull/2455 Reviewed-By: Colin Ihrig &lt;cjihrig@gmail.com&gt;
9 years ago
Previous releases of Node.js have been signed with one of the following GPG
keys:
doc: use consistent markdown in README Improve markdown practices in README: * consistent header indicators * consistent emphasis indicators * wrap bare URLs in `&lt;` and `&gt;` * wrap at 80 chars * specifying language in fenced code PR-URL: https://github.com/nodejs/node/pull/7971 Reviewed-By: Сковорода Никита Андреевич &lt;chalkerx@gmail.com&gt; Reviewed-By: Michaël Zasso &lt;mic.besace@gmail.com&gt; Reviewed-By: James M Snell &lt;jasnell@gmail.com&gt;
9 years ago
* **Isaac Z. Schlueter** &lt;i@izs.me&gt;
`93C7E9E91B49E432C2F75674B0A78B0A6C481CF6`
* **Julien Gilli** &lt;jgilli@fastmail.fm&gt;
`114F43EE0176B71C7BC219DD50A3051F888C628D`
* **Timothy J Fontaine** &lt;tjfontaine@gmail.com&gt;
`7937DFD2AB06298B2293C3187D33FF9D0246406D`
doc: clarify that the node.js irc channel is not under tsc oversight There has been some question about whether the #node.js irc channel falls under the TSC oversight or not. See: https://github.com/nodejs/node/issues/7746 This clarifies that the #node.js irc channel is a community provided resource that is not currently directly under the oversight of the TSC/CTC. PR-URL: https://github.com/nodejs/node/pull/7810 Reviewed-By: Bryan Hughes &lt;bryan@nebri.us&gt; Reviewed-By: Julien Gilli &lt;jgilli@nodejs.org&gt; Reviewed-By: Сковорода Никита Андреевич &lt;chalkerx@gmail.com&gt; Reviewed-By: Rich Trott &lt;rtrott@gmail.com&gt;
9 years ago
[Website]: https://nodejs.org/en/
[Contributing to the project]: CONTRIBUTING.md
doc: add link to help repo in README Include link to Node.js help repo (for end user questions on how to use Node.js) in the README. PR-URL: https://github.com/nodejs/node/pull/8570 Reviewed-By: Colin Ihrig &lt;cjihrig@gmail.com&gt; Reviewed-By: Teddy Katz &lt;teddy.katz@gmail.com&gt; Reviewed-By: Luigi Pinca &lt;luigipinca@gmail.com&gt; Reviewed-By: Сковорода Никита Андреевич &lt;chalkerx@gmail.com&gt;
8 years ago
[Node.js Help]: https://github.com/nodejs/help
doc: clarify that the node.js irc channel is not under tsc oversight There has been some question about whether the #node.js irc channel falls under the TSC oversight or not. See: https://github.com/nodejs/node/issues/7746 This clarifies that the #node.js irc channel is a community provided resource that is not currently directly under the oversight of the TSC/CTC. PR-URL: https://github.com/nodejs/node/pull/7810 Reviewed-By: Bryan Hughes &lt;bryan@nebri.us&gt; Reviewed-By: Julien Gilli &lt;jgilli@nodejs.org&gt; Reviewed-By: Сковорода Никита Андреевич &lt;chalkerx@gmail.com&gt; Reviewed-By: Rich Trott &lt;rtrott@gmail.com&gt;
9 years ago
[Node.js Moderation Policy]: https://github.com/nodejs/TSC/blob/master/Moderation-Policy.md
[#node.js on chat.freenode.net]: https://webchat.freenode.net?channels=node.js&uio=d4
[#node-dev on chat.freenode.net]: https://webchat.freenode.net?channels=node-dev&uio=d4