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

Notice to Working Groups: renaming "iojs" org to "nodejs", joining the Node Foundation #1705

Closed
rvagg opened this Issue May 14, 2015 · 10 comments

Comments

Projects
None yet
8 participants
@rvagg
Member

rvagg commented May 14, 2015

Attention:

  • @iojs/addon-api
  • @iojs/build
  • @iojs/collaborators
  • @iojs/docker
  • @iojs/evangelism
  • @iojs/hardware
  • @iojs/streams
  • @iojs/tracing
  • @iojs/website

In case you haven't been following; as of yesterday's io.js TC meeting, io.js will be joining the Node Foundation and the GitHub org will be renamed to "nodejs", this is how the vote was worded:

The io.js TC agrees to:

  1. have the io.js project join the Node Foundation
  2. rename the entire “iojs” GitHub org to be “nodejs”
  3. invite the the current Node.js TC on to our TC to form the basis of a Node Foundation TSC under the policies of the Node Foundation
  4. moving the io.js Working Groups to be under the Node Foundation

Full meeting notes are @ #1700 and the video is @ http://www.youtube.com/watch?v=UbYiFLf7MpU

The exact timing is still being worked on by @mikeal but it could be as soon as tomorrow.

The impact on Working Groups is that they will also be moved in to the "nodejs" org and become part of the Foundation. However, since the Working Groups are autonomous they have the ability to relocate and detach from the Foundation and that is their right. If there are concerns within your Working Group(s) about this move, please discuss it and come to a decision according to the governance procedures you have set up.

In terms of the practical outworking, this is what I would expect to happen after the move:

  • The repositories in the "iojs" org will stay named as they are, including "io.js".
  • The TC will become the Node Foundation TSC and expand to include the joyent/node TC.
  • io.js will continue to release code and binaries, business as usual and we'll likely even see a v3.0.0 soon given V8 4.3's imminence.
  • There is ongoing work in https://github.com/jasnell/node.js-convergence to pull together the io.js codebase along with the changes introduced in joyent/node to form a new repo, "node", creating nodejs/node.
  • Work will continue on the converged repo towards an actual release of that code, with the version being one major version above the io.js version at that time and it will likely take over the momentum of releasing code & binaries from the io.js repository.
  • What happens to the io.js repository and brand is still up for discussion but it's clear that there's a lot of attachment to it and I'd expect it to continue in some form within the Foundation.
  • Many other issues about what will happen into the future are still up for discussion and the Foundation will be the forum for discussing and deciding and the model for how this happens will be almost identical to what io.js has been doing thus far and everyone is invited to participate in that process.

Many questions that people have about how the Foundation works can be answered in here: https://github.com/jasnell/dev-policy

I haven't been as involved in the convergence work or the dev-policy work so @mikeal, @Fishrock123, @jasnell or someone else may be able to fill in gaps or correct any inaccuracies here.

@jasnell

This comment has been minimized.

Show comment
Hide comment
@jasnell

jasnell May 14, 2015

Member

This looks good. Thank you @rvagg. There are plenty of logistics to figure out so once we've identified everything we'll make sure it gets posted. One item of note, the dev-policy and convergence repos that currently sit in my personal github account will be transferred to the nodejs org once the rename happens. Also, we still need to get the LTS WG discussions underway.

Member

jasnell commented May 14, 2015

This looks good. Thank you @rvagg. There are plenty of logistics to figure out so once we've identified everything we'll make sure it gets posted. One item of note, the dev-policy and convergence repos that currently sit in my personal github account will be transferred to the nodejs org once the rename happens. Also, we still need to get the LTS WG discussions underway.

@ChALkeR

This comment has been minimized.

Show comment
Hide comment
@ChALkeR

ChALkeR May 14, 2015

Member

What will happen to the issues and pull requests?

Member

ChALkeR commented May 14, 2015

What will happen to the issues and pull requests?

@rvagg

This comment has been minimized.

Show comment
Hide comment
@rvagg

rvagg May 14, 2015

Member

@ChALkeR since the repo will be moved they will be intact, from our repos at least, and GitHub will take care of redirects so URLs and git remotes should just still work.

Member

rvagg commented May 14, 2015

@ChALkeR since the repo will be moved they will be intact, from our repos at least, and GitHub will take care of redirects so URLs and git remotes should just still work.

@ChALkeR

This comment has been minimized.

Show comment
Hide comment
@ChALkeR

ChALkeR May 14, 2015

Member

@rvagg Nice to see, thanks! ☺

This got me confused:

  • The repositories in the "iojs" org will stay named as they are, including "io.js".
Member

ChALkeR commented May 14, 2015

@rvagg Nice to see, thanks! ☺

This got me confused:

  • The repositories in the "iojs" org will stay named as they are, including "io.js".
@jasnell

This comment has been minimized.

Show comment
Hide comment
@jasnell

jasnell May 14, 2015

Member

@ChALkeR it means that none of the existing repositories within the current io.js organization will be renamed as part of the process, only the organization itself.

Member

jasnell commented May 14, 2015

@ChALkeR it means that none of the existing repositories within the current io.js organization will be renamed as part of the process, only the organization itself.

@mikeal

This comment has been minimized.

Show comment
Hide comment
@mikeal

mikeal May 14, 2015

Member

Looks great, thanks for putting this up with a notice to the working groups :)

Member

mikeal commented May 14, 2015

Looks great, thanks for putting this up with a notice to the working groups :)

@mscdex mscdex added the meta label May 14, 2015

@rvagg

This comment has been minimized.

Show comment
Hide comment
@rvagg

rvagg May 14, 2015

Member

FYI we are about to start a Node.js / io.js Build / CI convergence meeting between the two groups maintaining those resources, details including video feed link @ nodejs/build#98

Member

rvagg commented May 14, 2015

FYI we are about to start a Node.js / io.js Build / CI convergence meeting between the two groups maintaining those resources, details including video feed link @ nodejs/build#98

@AntouanK

This comment has been minimized.

Show comment
Hide comment
@AntouanK

AntouanK May 18, 2015

Member

Should we update the roadmap to reflect those new priorities and make it easy for people to see in a glance what will happen from now on?

Member

AntouanK commented May 18, 2015

Should we update the roadmap to reflect those new priorities and make it easy for people to see in a glance what will happen from now on?

@fhemberger

This comment has been minimized.

Show comment
Hide comment
@fhemberger

fhemberger May 18, 2015

Member

If you decide to do so, don't forget http://roadmap.iojs.org (which has also been translated to various languages).

Member

fhemberger commented May 18, 2015

If you decide to do so, don't forget http://roadmap.iojs.org (which has also been translated to various languages).

@Fishrock123

This comment has been minimized.

Show comment
Hide comment
@Fishrock123

Fishrock123 Jun 1, 2015

Member

Notification served, can we close this?

Member

Fishrock123 commented Jun 1, 2015

Notification served, can we close this?

@rvagg rvagg closed this Jun 2, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment