"Not even close. Fedor Indutny started the fork and the org, but the fork is under an open governance structure, a technical committee. That TC, which met for the first time this week, is: Indutny (listed as a Node.js code team member) Trevor Norris (also a Node.js core team member) Isaac Schlueter (cited as a Node.js core team alumni) Ben Noordhuis (also an alumni) Bert Belder (another alumni and a Node.js maintainer) Rod Vagg (Node.js supporter) also participates in the calls as he is creating and managing the build system. I just moderate and record the TC meetings and help to build the agenda."
"We've been working with Joyent since July to try and move the project to a structure where the contributors and community can step in and effectively solve the problems facing Node [including the lack of active and new contributors and the lack of releases]. My guess is that Fedor was tired of waiting and set io.js up. He didn't promote it or anything, but those of us who were close enough saw it and jumped on. Then we moved all the Node core-related Node Forward work over, which has been building for some time but can't do a release due to trademark restrictions."
io.js is a community-driven fork of Node.js created by developers frustrated with Joyent's control and slow governance changes. Fedor Indutny initiated the fork and established an open governance technical committee. The initial technical committee includes Indutny, Trevor Norris, Isaac Schlueter, Ben Noordhuis, and Bert Belder, with Rod Vagg managing the build system. Mikeal Rogers moderates and records TC meetings and helps build agendas. Contributors moved Node Forward core work to io.js but trademark restrictions prevented releasing those builds. Attempts to restructure governance with Joyent began months earlier but stalled, prompting the fork.
Read at InfoWorld
Unable to calculate read time
Collection
[
|
...
]