Repository navigation
Should Node.js references be changed to io.js in Docs? #740
Description
Activity
I suppose the answer is 'yes' but I'm afraid it's going to make merges from joyent/node an absolute pain in the rear end. @iojs/collaborators Opinions?
I also think the answer is yes. I would like merging to be as painless as possible, but isn't it already becoming a huge pain?
I don't see a lot of recent documentation activity in node.js, why are we worried about merges from them?
Could we do something to flag these lingering, kept-for-mergeability references when they turn up to either allow/block an auto find-and-replace solution as part of the API docs build processes? At least then in the published docs it would be cleaned up and on the Node.js™ it would just remain the original naming (for lack of awareness of said allow/block hooks.)
So moved, see #750.
Should we also give #393 the go-ahead then?
- added 2 commits that reference this issue
on Feb 7, 2015 Closed by #750. @Fishrock123 I guess there is no point holding off if it's an improvement.
Except when specifically distinguishing between Node.js and io.js, should the Node.js and Node references in the docs be changes to io.js?
If so, I'm willing to make those changes. Just thought I'd ask first.