Please move to nodejs org

[mikeal]

It's ready :)

[Fishrock123]

👍

[Fishrock123]

This repo is going to be named node or node.js once it is moved, correct?

[jasnell]

@mikeal ... Ok, one challenge on this: jasnell/node.js-convergence is a fork of iojs/io.js. Attempt to transfer back over fails because of nodejs/io.js. Suggestions? ;-)

[Fishrock123]

We could request for an un-fork and then move it, or just remake the repo in nodejs.

[jasnell]

Thinking through how that would work. Unforking would destroy the history, but, so far we haven't landed changes from v0.12 so I'm not sure that's an issue. I can keep the repo as is, and we can just start fresh with a new repo, add remotes to both nodejs/io.js and joyent/node and begin fresh.

[mikeal]

you can email support@github to get them to "unfork" it

[mikeal]

it should just be called "node"

[jasnell]

Note to support@github sent. Once unforked, there will be two distinct steps. I cannot rename the repository at the same time as moving it apparently, so I'll rename immediately after moving.

[jasnell]

FYI, I'm going to be away for just a bit over the next couple of hours. Returning around 4:00pm pacific. The remaining transition on this will happen then

[jasnell]

Response from github support, repo will be de-forked. Will move this evening assuming de-fork is complete by then

[jasnell]

Moved! Renamed!

[Fishrock123]

I think github did a thing with collaborators for this repo haha, check out your news feed.

[jasnell]

Sigh.

[piscisaureus]

They just carried over the repo collabs to the new org? I think that makes some sense.

[jasnell]

I dunno, as long as everyone who is supposed to have access has access, then it works. Noisy and annoying, but it works.

[Fishrock123]

Yeah, it's fine, just noisy. iojs/collaborators should probably also have access to this repo.

[mikeal]

I added collaborators and TSC teams to this repo earlier today.