Skip to content
This repository has been archived by the owner on Jul 20, 2018. It is now read-only.

Joining the Node.JS Foundation #58

Closed
Starefossen opened this issue May 15, 2015 · 4 comments
Closed

Joining the Node.JS Foundation #58

Starefossen opened this issue May 15, 2015 · 4 comments

Comments

@Starefossen
Copy link
Member

io.js TC meeting 2015-05-13 voted for joining the Node.JS Foundation, meeting notes are @ nodejs/node#1700 and the video is @ http://www.youtube.com/watch?v=UbYiFLf7MpU. As per nodejs/node#1705 all repos and related working groups will be moved to the new "nodejs" org.

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.

So without further ado; should the Docker Working Group join the Node.JS Foundation or not?

@pesho
Copy link
Contributor

pesho commented May 15, 2015

Definitely +1 for joining.

We also need to decide how to handle the merging of io.js/Node.js docker images in the future (after the first converged release). Specifically:

  • How will the new image be called? node or nodejs?
  • Which GitHub repo for the sources? The current one makes the most sense probably, but it will need to be renamed, and the branches from joyent/docker-node will have to be merged (at least the ones which will be LTS-supported).
  • @chorrell has been maintaining the Node image, he should be invited into this WG

@Starefossen
Copy link
Member Author

Definitely +1 for joining from me as well.

  • How will the new image be called? node or nodejs?

The current image on Docker Hub is called node, I would suggest we stick with that.

  • Which GitHub repo for the sources? The current one makes the most sense probably, but it will need to be renamed, and the branches from joyent/docker-node will have to be merged (at least the ones which will be LTS-supported).

+1 for renaming the current one and merging in maintained joyent/docker-node versions. I see joient/docker-node has a : wheezy image tag that iojs/docker-iojs has not.

  • @chorrell has been maintaining the Node image, he should be invited into this WG

+1 from me as well.

@yosifkit
Copy link
Contributor

Just a quick +1 on keeping the name as node on the Docker hub. The Hub doesn't really have alias name support or any way to cleanly redirect one image repo to another, though you could poke [email protected] to make sure they know you want alias naming (ie, node and nodejs).

Starefossen pushed a commit to Starefossen/docker-iojs that referenced this issue May 17, 2015
PR-URL: nodejs#60
Related: nodejs#58

Signed-off-by: Hans Kristian Flaatten <[email protected]>
@Starefossen
Copy link
Member Author

Closing since the converge has been completed.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants