-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Move to the nodejs GitHub organization and combine efforts with nodejs/docker team? #28
Comments
Hi! I'm currently on vacation this week, but short answer: YES! Is there a preferred timeline for moving the repo to the nodejs org? Add yes, it would be good for me to be added to the @nodejs/docker group. @dcrudgington is the other person who helps maintain the image, so he should be added as well. |
Added, also merged the discussion @ nodejs/docker-iojs#77 so everyone's aware. Timing is up to you all to discuss, there's no great hurry but be aware that the LTS WG is suggesting we push to have a converged release by August, which is very close: https://github.com/nodejs/LTS/#proposed-lts - that'll likely be Node.js v4, coming out of https://github.com/nodejs/node. |
Transferred per nodejs/docker-iojs#77 |
Closing this out. Org change and Node.js 4.0.0 release submitted to the registry: |
Hey @chorrell, since we are in the process of combining Node.js and io.js efforts under the foundation in the new http://github.com/nodejs/ organization and have been gradually moving relevant repositories there and combining the efforts of the various working groups. Could we also plan for a move of this repository under the same organization and combine the great work you've been putting in here with the existing @nodejs/docker working group that also takes care of the official io.js Docker images @ https://github.com/nodejs/docker-iojs?
I hear great feedback about the way this project is run from people who are using it and it'd be great to be able to combine the effort and energy that are put in here and in docker-iojs under the same umbrella to set us up for when the converged work begins releasing (likely within a couple of months).
Perhaps as a start we could add yourself and anyone else who is responsible for maintaining this repository to the @nodejs/docker group and get some communication started around how you can converge your efforts as we've been doing across other groups.
The text was updated successfully, but these errors were encountered: