The Node.js Foundation and JS Foundation Announce an Intent to Merge (A Message from the Boards and a FAQ around the Announcement)

*The introduction of this blog comes from the Board of Directors for both the Node.js and JS Foundations.

Introduction

Today, the Node.js Foundation and JS Foundation announced an intent to merge. An intent to merge means that we the boards of both Foundations have agreed to public discussions related to a possible merger.

We have not made any formal decisions at this point regarding a new or merged Foundation and its potential organizational structure, governance policies, technical framework or leadership. This will be formalized based on feedback from the Node.js and JavaScript communities.

After having two separate Foundations for two years, we believe there needs to be a tighter integration between both Foundations to enable greater support for Node.js and a broader range of JavaScript projects. We look forward to continuing to support the healthy growth of the JavaScript ecosystem and look forward to the potential of supporting an even wider range of projects that the JavaScript ecosystem is dependent on as well as projects that focus on new areas of growth for JavaScript.

If you would like to participate in our public discussions on the topic, we encourage you to join our first public meeting, which is happening today at 1 pm PDT. Submit your questions via this form and join the livestream, which will happen on the Node.js Foundation YouTube channel.

We will also hold a Q&A session during Node+JS Interactive from 7:30am — 8:30am PT, October 10 at West Ballroom A. Anyone attending Node+JS Interactive is welcome to attend; questions can be submitted in advance anonymously via this Google Form or by email at pr@nodejs.org.

Below is a FAQ to help answer general questions you may have. If you have additional questions, please submit to the Google Form above.

We look forward to the next chapter of Node.js and the JavaScript ecosystem — we hope you do too!

FAQ

Q: What is being announced?

The Node.js Foundation and JS Foundation are announcing an intent to merge and intend to moderate a panel at Node+JS Interactive to answer questions and solicit community input on the possible structure of a new Foundation.

Q: How is intent to merge different than merging?

An intent to merge means that the boards have agreed to public discussions related to a possible merger to seek input from the community. The board of directors have not made any formal decisions at this point regarding a new or merged Foundation and its potential organizational structure, governance policies, technical framework or leadership.

Q: Why did the boards decide to pursue an intent to merge?

The boards decided to pursue an intent to merge to help:

• Enhanced operational excellence;
• Streamlined member engagement;
• Increased collaboration across the JavaScript ecosystem and affiliated standards bodies;
• An “umbrella” project structure that brings stronger collaboration across all JavaScript projects; and
• A single, clear home available for any project in the JavaScript ecosystem rather than projects having to choose between the JS and Node.js Foundation.

Q: How will this merger impact and benefit the larger JavaScript communities?

The intent here is to increase collaboration in the JavaScript ecosystem for continued and healthy growth both from a technology and standards perspective.

Q: How will this impact the technical direction of the Node.js Project and the projects that fall under the JS Foundation, like jQuery, ESLint, Appium?

This will not change the technical independence or autonomy for Node.js or key any JS Foundation projects like jQuery, ESLint or Appium.

Q: What are the next steps in the intent to merge process?

• The initial public discussion takes place today at 1pm PDT — see info on how to submit questions and join the discussion above.
• An open public discussion at Node+JS Interactive for community questions and feedback — see info on how to submit questions and join the discussion above.
• A webinar following Node+JS Interactive to gather additional community input (timing is currently being discussed).
• Begin ED search, agree on name of merged entity.
• Work with the community to develop self governance and project levels.
• Execute merger legal documents.
• Identify staffing to run merged entity.