This repository has been archived by the owner on Mar 22, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 68
Proposal: rename the nodejs/iojs-ko WG to nodejs/nodejs-ko #148
Comments
@srl295 |
@outsideris GitHub will redirect it. Try for example your siblings that were just renamed: |
@srl295 Thank you. We know it, but we want to change it clearly, and we still have some text mentioned as iojs. |
Add check item if I miss something @nodejs/iojs-ko |
outsideris
added a commit
to outsideris/nodejs-ko
that referenced
this issue
Oct 7, 2015
outsideris
added a commit
to outsideris/nodejs-ko
that referenced
this issue
Oct 8, 2015
I just opened a ticket that addresses the related tasks. #153 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Dear members of the io.js Korean WG
iojs-ko
It is proposed to rename this repo to:
nodejs/nodejs-ko
As part of the io.js and node.js convergence, node.js releases are now based on the codebase and user base of the converged node.js and io.js communities. A number of the resources and repositories have already been renamed.
In the absence of objections or other discussion, this rename will occur on or after Oct 28, 2015
However, active language working groups should take ownership of this issue and discuss/dispose of it according to their own processes.
For more information or to discuss the overall issue, please see and comment on nodejs/node#2525
This statement was authorized by the Node.js TSC
Cc: @nodejs/iojs-ko
The text was updated successfully, but these errors were encountered: