Skip to content

io.js (IO.js? iojs?) and node.js documentation fragmentation #135

@zeusdeux

Description

@zeusdeux

In a scenario where in some application, sub system A is dependent on say node 0.10.33 and another sub-system B is dependent on io.js 1.0.0-alpha1, where will the documentation reside?

Will it be fragmented (hosted by both nodejs.org and iojs.org)?
Would the devs be able to treat the io.js documentation as a superset of the documentation hosted at nodejs.org and just refer to that?
Will JNAB make a decision on this?
Does it even matter? (imho I think it does.)

I personally think it would suck for new devs coming on board if they would have to consult different docs that might be possibly conflicting.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions