Closed mikeal closed 9 years ago
:dancers:
Awesome! :+1:
:+1:
:+1::+1::+1::+1::+1::+1:
:+1:
:+1: :+1:
:+1: :+1: About time
LGTM :+1:
Congratulations all around! You guys deserve to celebrate! :smile: :+1:
πππ
(yey)
!!! Awesome
:+1:
Awesome!! +1
Very good!
Great news. Well done.
:heart:
:shipit: :+1:
And all it took was for Microsoft to fork it. Embrace, extend... profit?
:+1:
:thumbsup: Is there an ETA for first merged release?
:+1::+1::+1::+1::+1:
:thumbsup:
:tada:
Huzzah! :thumbsup:
Nice, thank you!
This is horrible :-1: ..
ok I just wanted to be contrary, woohoo ! :+1:
Great (y) !
So it is official: Node.js will rule as this big obstacle is over.
6 months before it is on the same pathetic state things were before the fork. You heard here first.
:sunglasses: :+1: fantastic
:+1:
@mrseth Not going to happen. The community has control now.
Congratulations guys!!!
What's the expected timeframe on the codebase convergence and getting to 3.0?
I see @Fishrock123's pull request. Is there a todo list of what remains after that is merged in?
Lastly, what's the deal with migrating existing open issues from node.js/io.js to the new repo?
:thumbsup:
Thanks for all your efforts!
Great job, everyone!
Oh no! This means that the logo thread will come to an end!
This is going to be awesome guys...
Started to prefer the name io.js. In my mind, we should have just continued down this forked road.
Thanks all. I'm going to limit this discussion to collaborators, but anyone is free to either email me (fishrock123@rocketmail.com) if they have a comment they'd really like to have here, or comment in irc or some other place.
Basically all issues that could be brought up have been brought up, and I'm sure you'd be able to either find them by searching, or ask a collaborator / tc member. :)
6 months before it is on the same pathetic state things were before the fork.
As said, the new master will continue as things have in io.js
Oh no! This means that the logo thread will come to an end!
Ah, sadly yes. But we can always make a new thread for community node / io.js logos. Maybe we'll be able to open the node logo up to wider community interpretation and use. :)
Started to prefer the name io.js.
Ah same (naturally, I did come up with it), but it will still live on as having a huge impact on node. :)
All the documentation for the Node Foundation is ready:
The gist of it is, the foundation's governance structure is nearly identical to io.js'. In fact, during the process of writing all this down we improved the documentation for most of these policies and made some improvements. The new "converged" node project will begin with io.js master and port changes from node.js in for its first release target.
I wrote an extensive piece on why I think we need a foundation, and why I think the structure the Linux Foundation has setup for the Node Foundation is ideal.
It's now time to make a real decision about moving io.js in to the foundation and, eventually, merging with node.js.
Once we've committed to this we would:
There's obviously going to be a lot of technical work after that continuing to release io.js until a converged release is ready, targeting the new repo for additional automation, etc, but the immediate steps would be the ones I've outlined above.
For the Working Groups, they would continue to do things as io.js (although the org is renamed) until they have access to the appropriate node.js assets and they decide as a WG to shift their focus.
PS. As a point of process, Working Groups are autonomous, so if the TSC decides to move io.js to the Node Foundation but a WG, for whatever reason, declines they would have to be moved out of the foundation org after the move. This is just a limitation of having to move the org.