Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should Node.js references be changed to io.js in Docs? #740

Closed
matthewrankin opened this issue Feb 6, 2015 · 8 comments
Closed

Should Node.js references be changed to io.js in Docs? #740

matthewrankin opened this issue Feb 6, 2015 · 8 comments
Labels
doc Issues and PRs related to the documentations.

Comments

@matthewrankin
Copy link

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.

@vkurchatkin vkurchatkin added the doc Issues and PRs related to the documentations. label Feb 6, 2015
@bnoordhuis
Copy link
Member

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?

@cjihrig
Copy link
Contributor

cjihrig commented Feb 6, 2015

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?

@mikeal
Copy link
Contributor

mikeal commented Feb 6, 2015

I don't see a lot of recent documentation activity in node.js, why are we worried about merges from them?

@snostorm
Copy link

snostorm commented Feb 7, 2015

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.)

@rvagg
Copy link
Member

rvagg commented Feb 7, 2015

@mikeal's point is solid:

I don't see a lot of recent documentation activity in node.js, why are we worried about merges from them?

So I'm a +1 on just doing a full conversion.

@bnoordhuis
Copy link
Member

So moved, see #750.

@Fishrock123
Copy link
Contributor

Should we also give #393 the go-ahead then?

bnoordhuis added a commit to bnoordhuis/io.js that referenced this issue Feb 7, 2015
bnoordhuis added a commit that referenced this issue Feb 7, 2015
Fixes: #740
PR-URL: #750
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
@cjihrig
Copy link
Contributor

cjihrig commented Feb 7, 2015

Closed by #750. @Fishrock123 I guess there is no point holding off if it's an improvement.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc Issues and PRs related to the documentations.
Projects
None yet
Development

No branches or pull requests

8 participants