Share

The Node.js is a project that's becoming larger and more vital to the developer ecosystem. Whether you're a front-end developer using Webpack, Babel, and React as your frameworks of choice, an engineer working in DevOps at scale, or anywhere in between, you've probably already encountered Node.js.

As a project, Node.js is open source. It's maintained by a community of people who care about Node and spend their time to ensure Node is a stable, usable, and all-around awesome project. In our Node by Numbers 2016 report, the enormous amount of work put into the core project itself — in terms of both development and community — is tangible.

The community is, quite frankly, massive. There are over a dozen working groups, several committees, and hundreds (literally hundreds) of people working on Node.js.

There are millions of users of Node.js around the world, and many of them probably don't know the people who work on ensuring Node.js is a usable tool for them.

We've put together this article to introduce you to a small collection of of the developers who work on the Node.js Core Technical Committee (the CTC), contributing to the Technical Steering Committee (the TSC), CTC, and the release team. This is a first take at what I hope will be an ongoing collection of the humans who work on, build out, and collaborate on the Node.js project as a whole.

Rod Vagg - @rvagg

• Node.js TSC Chairperson, CTC Member, core contributor, and release team member
• Consistently discusses the hard problems that Node.js faces
• Works as the Cheif Node Officer at NodeSource
• Sits on the Node.js Foundation Board of Directors

The story of Express and the way it has both contributed to "idiomatic Node" and adapted to it is a key to understanding the Node ecosystem.

— Rod Vagg (@rvagg) January 10, 2017

James Snell - @jasnell

• Node.js TSC member, CTC member, core contributor, and release team member
• Actively working on HTTP/2 implementation for Node.js
• Works on Node.js at IBM
• Participates in TC-39, the standards body that defines ECMAScript

PSA: We are starting the process of assigning static error codes to every error reported by Node.js https://t.co/9G60vZ5bsn

— James M Snell (@jasnell) February 10, 2017

Trevor Norris - @trevnorris

• Node.js TSC member, CTC member, and core contributor
• Discusses some of the deeper, difficult Node.js ideas and their implementation
• Works at NodeSource as a full-time contributor to the Node.js project
• Has been working on the async-hooks (formerly known as async-wrap) functionality for Node core

node native module perf tip: instead of returning a JS array of numbers, pass in a Typed Array and write directly to its memory.

— φrevor ηorris (@trevnorris) November 12, 2016

Myles Borins - @mylesborins

• Node.js TSC member, CTC member, core contributor, and release team member
• Frequently shares updates on Node.js core - what's new and what's next
• Works as a Developer Advocate at Google
• Works on the Canary in the Gold Mine (CITGM) smoke testing tool

If all works out ya'll will get an @nodejs v7.6.0 with Async / Await available without a flag

— Myles Borins (@MylesBorins) February 1, 2017

Anna - @addaleax

• Node.js CTC member and core contributor
• Came into Node core by working on some of the less popular, more intense projects like zlib
• Extremely knowledgeable of Node.js core, from the underlying C++ to the higher-level JavaScript
• Is deeply involved in Node.js community building, including Foundation projects like Code & Learn

Are you using Node’s built-in debugger (talking about `node --debug` or `node debug some-script.js`, not `node --inspect`)?

— Anna (@addaleax) December 5, 2016

Jeremiah Senkpiel - @fishrock123

• Node.js TSC member, CTC member, core contributor, and release team member
• Consistently shares updates about Node.js and core development
• Works at NodeSource, contributing full-time to the open source Node.js project
• Contributed a large amount to the core Node.js timers implementation.

Still live and making progress on net.Socket#setTimeout()! https://t.co/DY0ozuIl6d

— units received (@Fishrock123) February 3, 2017

Evan Lucas - @evanhlucas

• Node.js CTC member, core contributor, and release team member
• Does a tremendous amount of work on cutting releases for Node.js core
• Works as a Node.js developer at Help.com
• Has written a bunch of tools to automate tedious tasks in Node Core

v7.5.0 of @nodejs is now out at https://t.co/oxNcNrSZWr. Includes openssl 1.0.2k, ability to use system CAs, @npmjs v4.1.2 and more!

— Evan Lucas (@evanhlucas) February 1, 2017

Fedor Indunty - @indutny

• Node.js TSC member, CTC member, and core contributor
• Deeply involved with the net, http, crypto, and tls core modules
• Works at PayPal as a Software Engineer
• In addition to working the TSC and CTC, Fedor contributes as part of the Crypto team to address the security of Node core

https://t.co/iboxaFXCUN got much much faster since it was initially published. Awesome job V8 team!

— Fedor Indutny (@indutny) February 7, 2017

Rich Trott - @Trott

• Node.js CTC member and core contributor
• Heavily contributes a ton to the project's tests, and helps onboard new contributors
• Works at UC San Francisco as a Director at the Center for Knowledge Management
• Heavily involved in community efforts, including Code and Learn, NodeTodo, and more

"What next?" is asked so often after people contribute to Node.js that the answer now has its own page with links: https://t.co/27EJfd9ahp

— Rich Trott (@trott) February 1, 2017

What's next?

That's a tiny sample of the huge community of people who have, do, and shall contribute to Node.js as a project. We're keen to shed light on more of the people who contribute their time, effort, and energy to the Node.js project as a whole.

In the meantime, if you'd like to get some insight to the project as a growth and community now, you can take a peek at our annual Node by Numbers report, an analysis of the Node.js project throughout the last year that demonstrates the incredible growth of the project, which continues to exceed everyone's expectations.

The More You Know

For businesses and teams that want to take risk out of their reliance on third-party Node modules, NodeSource introduced NodeSource Certified Modules which offers security, reliability, and support for the modules that they rely on to run mission-critical business applications. Everything we do at NodeSource starts with Node.js at the core. We are grateful to the Node.js CTC members for all they do to make that possible.