3 min read
A Q&A session will be held at Node+JS Interactive from 7:30 am to 8:30 am PT, October 10 at West Ballroom A to answer questions and get community input on the possible structure of a new Foundation.
Why are Node.js and JS Foundations considering merging?
What are the goals of this merger?
- To provide enhanced operational excellence
- Streamlined member engagement
Todd Moore, Node.js Board Chairperson and IBM VP Opentech, believes this merger will provide improved support to contributors:
“The possibility of a combined Foundation and the synergistic enhancements this can bring to end users is exciting. Our ecosystem can only grow stronger and the Foundations ability to support the contributors to the many great projects involved improve as a result.”
How are developers feeling about this potential move?
Not many developers are happy about this merger, which led to a discussion on Hacker News yesterday. One of the developers feels that the JS Foundation has been neglecting their responsibility towards many open source projects. They have also seen a reduction in funding and alienated many long-time contributors. According to him, this step could be “a last-ditch effort to retain some sort of relevancy.”
On the other hand, one of the developers feels positive about this merge:
“The JS Foundation is already hosting a lot of popular projects that run in back-end and build/CI environments — webpack, ESLint, Esprima, Grunt, Intern, JerryScript, Mocha, QUnit, NodeRed, webhint, WebDriverIO, etc. Adding Node.JS itself to the mix would seem to make a lot of sense.”
What we think of this move?
If you have any questions regarding the merger, you can submit them through this Google Form provided by the two foundations.