Need to Node – Volume 13
Over the past week, we’ve seen some interesting and atypical activity from some of the more non-technical areas of the project. These include the beginnings of some fundamental changes to how we do things in Node.js at a community level.
Here’s a quick recap of just a few of the highlights from the last two weeks in Node.js:
What’s New in the Node.js Project
- Working with the Node.js Foundation Executive Director (Mark Hinkle), the TSC Director (Michael Dawson) has submitted a PR to the Admin repo adding an initial version of an Export Control document for Node.js.
- The User Feedback initiative is looking for input from maintainers of ecosystem tooling that uses Node.js. Positive, negative, and neutral feedback is deeply appreciated.
- The N-API repository shipped firstname.lastname@example.org to reflect the changes that have been made in the core
- The Mentorship Initiative is working on a "Priority Document" to outline places to work on Node.js, should mentees be so inclined. The goal of this document is both onboarding and retention, something that the project is beginning to shift towards.
- The Community Committee began the nomination process for a new CommComm Director role to represent the Community Committee on the Node.js Foundation Board of Directors.
Awesome Articles, Links, and Resources
- JSConf Hawaii was recently announced, bringing a JSConf to the islands next year!
- The EmpireJS CFP is now open!
- Understanding How Node.js Release Lines Work is an article I published last week, aiming to disambiguate how the Node.js release process happens.
One Last Thing...