Wording & project description

[Fishrock123]

io.js is a compatible spork* of node

(tagline)

io.js contributions, releases, and contributorship are under an open governance model.

We intend to release, with increasing regularity, releases which are compatible with the npm ecosystem that has been built to date for node.js.

(description)

Discussion appreciated. :)

See also: nodejs/node#3 and nodejs/node#24

[reqshark]

rewording the 2nd line could read:

We intend to release, with increasing regularity, compatible builds for the npm and node.js ecosystem.

[mikeal]

"io.js is a javascript runtime compatible with modules published to npm."

Avoid the term fork, or spork for that matter.

"Initial release is planned for January 13th." and link to the Issue.

[reqshark]

yes, io.js description is much better than the release line I tried to reword.

[reqshark]

gist by @maxogden: https://gist.github.com/maxogden/d96123138522c84cdb25

Disclaimer: This is an unofficial post by a random person from the community. I am not an official representative of io.js. Want to ask a question? open an issue on the node-forward discussions repo

io.js - what you need to know

• io is a fork of node v0.12 (the next stable version of node.js, currently unreleased)
• io.js will be totally compatible with node.js
• the people who created io.js are node core contributors who have different ideas on how to run the project
• it is not a zero-sum game. many core contributors will help maintain both node.js and io.js
• io.js is not adversarial to node.js
• the io.js project uses an open governance model
• io is the 4th largest moon of jupiter. it also means 'input/output', which is what io.js is good at (asynchronous i/o)
• 'noders' is to node as 'ionians' is to io
• you will probably be able to apt-get install iojs and get a node executable
• the first stable release of io will be in January
• the io team is working on an automated build infrastructure to enable a weekly release schedule
• io core team (technical committee) meetings are on youtube
• bugs etc fixed in node will be cherry-picked as necessary into io

[Fishrock123]

"io.js is a javascript runtime compatible with modules published to npm."

Avoid the term fork, or spork for that matter.

"Initial release is planned for January 13th." and link to the Issue.

The thing is, I don't really think of io/node as a runtime. That's what V8 is.

Honestly, we do need to tell people this is the same codebase somehow, and that's what a fork is. But I'm sure we can settle for "knife", "shiv", or "culinary instrument". :D

[mikeal]

@Fishrock123 s/runtime/platform

[reqshark]

@Fishrock123 what?!

[mikeal]

@reqshark talking this much about "node.js" fuels speculation. I know that we have to address the relationship but the messaging should be more about what "io.js" is and not just about "node.js"

A good metric is, will this messaging still be relevant a year from now?

[reqshark]

@mikeal i couldn't agree with you more, keep it focused on the future

[Fishrock123]

A good metric is, will this messaging still be relevant a year from now?

At the same time, people still need to know things relative to now.

[MetaThis]

What is the precise meaning of totally compatible? Does this mean that io.js has already decided what it will never do, or is this promising something that is incompatible with the forward intent?

[mikeal]

s/totally/fully

[boopathi]

So, will the executable be node or io or iojs ?
and if it's io/iojs, will the rename happen for npm to ipm ?

[rlidwka]

and if it's io/iojs, will the rename happen for npm to ipm ?

It's "npm package manager". No rename needed. :P

[Fishrock123]

npm: no problem meatbag

[Fishrock123]

Improved, could still use work maybe. I still think we should mention it is node-compatible, for now.

@mikeal thoughts?

[javierbyte]

I also think that the site should explain how open gorvenance model works in iojs, or at least provide a link explaining what it is.

Is this wikipedia article right for this purpose?

[Fishrock123]

I'm going to link to the document once it lands in core: nodejs/node#22

[ada-lovecraft]

io.js is a compatible spork* of node

Regarding a discussion that was had in irc, I'm suggesting we change "spork" to "dinglehopper":

kenperkins: ok wtf is spork
@Fishrock123: spoon-:fork
@Fishrock123: http://en.wikipedia.org/wiki/Spork
kenperkins: Ok, I know that much, what's the significance here? :D
@Fishrock123: and spoons are less harsh, so it is a spork
@Fishrock123: oops
@Fishrock123: something like that
@Fishrock123: because we aren't supposed to call it a fork
kenperkins: #facepalm
@Fishrock123: (ok it's not a fork fork, but .. yeah)
@Fishrock123: flails arms
ljharb: it's a dinglehopper
ljharb: http://25.media.tumblr.com/tumblr_lmvk5yLzdh1qjd3rdo1_500.gif

New Tagline Would Read:

io.js is a compatible dinglehopper* of node

[therebelrobot]

@codevinsky +100000

[rlidwka]

io.js is a compatible dinglehopper* of node

lol yeah, that's the best idea to avoid "fork" term :D

[Fishrock123]

Will close with #27