Weekly Update - Feb 13th, 2015

io.js support added by...

• Postmark
• node-serialport
• Microsoft Azure

io.js breaks 10,000 stars on GitHub

On Feb. 13, io.js reached the goal of 10,000 stars on GitHub. We couldn't have done it without the support of the amazing community behind JavaScript. Thank you all!

io.js 1.2.0 released

• stream: Simpler stream construction (readable-stream/issues#102)
• dns: lookup() now supports an 'all' boolean option, default to false but when turned on will cause the method to return an array of all resolved names for an address, see, (iojs/pull#744)
• assert: Remove prototype property comparison in deepEqual() (iojs/issues#636); introduce a deepStrictEqual() method to mirror deepEqual() but performs strict equality checks on primitives (iojs/issues#639).
• tracing: Add LTTng (Linux Trace Toolkit Next Generation) when compiled with the --with-lttng option. Trace points match those available for DTrace and ETW. (iojs/issues#702)
• docs: Lots of doc updates, see individual commits; new Errors page discussing JavaScript errors, V8 specifics, and io.js specific error details.
• npm upgrade to 2.5.1
• libuv upgrade to 1.4.0, see libuv ChangeLog
• Add new collaborators:
  • Aleksey Smolenchuk (@lxe)
  • Shigeki Ohtsu (@shigeki)

Opened our doors to the international community

View the original article on Medium.

• Added interested contributors to teams for their language.
• Teams registered Twitter accounts for their teams and other relevant social media accounts.
• Teams came up with their own ways of working together, and they became more of "community organizers," as opposed to just "translators"

Stats for Localizations:

• 146 people signed up to help with the localizations the first day (over 160 signed up now)
• 27 languages communities created the first day (already up to 29)

Language Communities

• iojs-bn Bengali Community
• iojs-cn Chinese Community
• iojs-cs Czech Community
• iojs-da Danish Community
• iojs-de German Community
• iojs-el Greek Community
• iojs-es Spanish Community
• iojs-fa Persian Community
• iojs-fi Finnish Community
• iojs-fr French Community
• iojs-he Hebrew Community
• iojs-hi Hindi Community
• iojs-hu Hungarian Community
• iojs-id Indonesian Community
• iojs-it Italian Community
• iojs-ja Japanese Community
• iojs-ka Georgian Community
• iojs-kr Korean Community
• iojs-mk Macedonian Community
• iojs-nl Dutch Community
• iojs-no Norwegian Community
• iojs-pl Polish Community
• iojs-pt Portuguese Community
• iojs-ro Romanian Community
• iojs-ru Russian Community
• iojs-sv Swedish Community
• iojs-tr Turkish Community
• iojs-tw Taiwan Community
• iojs-uk Ukrainian Community

io.js and Node.js

View the original article on Medium.

• Scott Hammond, CEO of Joyent, expressed his desire to bring io.js back to the Node.js.

In only a few months io.js...

• Has grown to 23 active core team members
• Has several working groups
• Has 29 language localization teams,
• Has drawn more contributors to the project than we’ve ever had in the history of Node.js, and
• Has been able to release quality software at a good pace with the support of an exceptional community.

We are eager to put this all behind us but we can’t sacrifice the progress we’ve made or the principles and open governance that got us here.

The Future

• Talks with the Node.js foundation are ongoing.

• Once the foundation has a technical governance model you will see an issue on io.js’ GitHub about whether io.js should join.

  • This will be discussed and voted on openly in a public TC meeting following the governance rules we’ve already built.

For the community, nothing has changed.

What to do right now

• Continue to send your pull requests to io.js
• Join one of the 27 language localization teams
• Contribute to io.js’ working groups (streams, website, evangelism, tracing, build, roadmap) and
• Continue to adopt io.js in your applications.