F23 Self Contained Change: io.js Technology Preview

[Jan Kurik]

= Proposed Self Contained Change: io.js Technology Preview =
https://fedoraproject.org/wiki/Changes/iojs

Change owner(s): T.C. Hollingsworth <tchollingsworth at gmail dot com>

io.js is an npm compatible platform originally based on Node.js™ that supports version 6
of the ECMAScript standard and additional features, developed with an open governance
model. io.js will be offered as an optional replacement for `/usr/bin/node` on Fedora
systems as a Technology Preview. node.js will remain the default implementation of
`/usr/bin/node` in Fedora 23. 

== Detailed Description ==
io.js is an npm compatible platform originally based on Node.js™ that supports version 6
of the ECMAScript standard and additional features, developed with an open governance
model. For more information about io.js and the differences between node.js, visit the
io.js website.

io.js will support the same set of binary modules currently supported by node.js on
Fedora. It is expected to be obsoleted by a future version of the `nodejs` package, as
these two projects have announced their intention to merge.

We will support both parallel-installation of the iojs interpreter alongside the existing
node.js interpreter, and permit replacement of `/usr/bin/node` with io.js in an additional
package. All existing noarch nodejs-* packages will work with both interpreters. (Though
obviously you'll have to specify iojs if you haven't installed it the
/usr/bin/node support package.) Seperate nodejs-* and iojs-* will be provided for binary
modules. 

== Scope ==
* Proposal owners:
  -- Package and build a special v8 package for io.js only.
  -- Package and build iojs
  -- Update nodejs guidelines for multiple interpreters
  -- Rebuild modules with above changes
  -- Anything that needs updates for Node.js 0.12 will need it for io.js too. 
* Other developers:
  -- Anything that needs updates for Node.js 0.12 will need it for io.js too. 
* Release engineering: N/A (not a System Wide Change) 
* Policies and guidelines:
  -- Updates to the node.js guidelines and packaging infrastructure to permit building
binary modules for multiple interpreters will be necessary. (These are also necessary to
allow for a nodejs010/nodejs012 split in EPEL, so will get done anyway.) 
* Trademark approval: N/A (not needed for this Change) 
-- 
Jan Kuřík