Move repo to rust-lang organization

[brson]

Probably best to do this before 1.0. Nominating.

[brson]

P-low, 1.0

[flaper87]

Agreed about doing it prior 1.0. Probably better to do it a couple of weeks before the release.

[steveklabnik]

The sooner it happens, the more links to the correct place we can get.

[huonw]

@flaper87 why? It seems like moving earlier is better: gives us more time to avoid dead links & just generally get acquainted with the new location.

(That said, github does do its redirection thing, but linking to the true repo seems nicer.)

[flaper87]

Dead links is definitely a valid concern. My thoughts were more around the relation between introducing backwards compatibility, considering the language frozen and giving it a new home. Not a technical thought but more a community based one. Perhaps not as valid as a point against the possibility of fixing dead links and other unexpected issues. I'm not sure what's the impact of this on the buildbots, bors and other scripts.

[erickt]

I actually think this won't be that difficult. According to this Github doc, Github will automatically redirect a transferred project's git pull, git push, and git clone to the new location. We'll of course need to test it out get everyone to update their remote repos, but ideally we won't have to worry about broken links.

[steveklabnik]

I mean more from other places. I guess we tend to link to rust-lang.org the most...

[erickt]

@steveklabnik: if I interpret that doc correctly, I believe github would auto redirect people from https://github.com/mozilla/rust to https://github.com/rust-lang/rust, so those links shouldn't break either. So we could transition them over time instead of having to coordinate a big community effort to retarget the links in one big sweep.

[steveklabnik]

Right, it does do that, but it'd be even better if they just linked to the right place from the get-go :)