Tracking issue: cargobomb -> crater rename

[aidanhs]

We're bringing all things 'ecosystem testing' back under the crater name, since the precise mechanism for performing the tests isn't important, just that they get done. Possibly incomplete list of things that should be done (or at least thought about):

User-facing

• Rename repo
• Update readme in this repo
• Update references on doc sites if relevant, e.g. https://forge.rust-lang.org/
• Update tag names on rust-lang repo

Code

• Update code in this repo

Infra

• Update instance hostnames
• Change s3 bucket

These are in approximate order of priority - docs, then code, then infra. This is in rough difficulty order as well, since (for example) we should make at least some effort to keep existing links alive when changing s3 bucket.

For now I'd like to get the docs section done, then see how things look after impl period.

[colinbankier]

I'd like to help out with this - I guess starting with a trivial PR to update the readme, and moving on from there.

[aidanhs]

@colinbankier that sounds great to me!

[colinbankier]

I'm not quite sure what "Update tag names on rust-lang repo" is referring to.

[aidanhs]

@colinbankier oops, I meant labels. If you take a look at https://github.com/rust-lang/rust/issues you can see that there's a filter for labels - as it happens it seems that the only relevant one has been renamed, so I've checked that item off.

With that, I think the important user-facing aspect of the rename is basically done - thanks for the help @colinbankier! The code aspect of the rename is a fair bit less pressing, but if you do feel like diving in then feel free. Alternatively, you can pop into the Crater working group chat (listed https://blog.rust-lang.org/2017/09/18/impl-future-for-rust.html#the-working-groups) if you'd like some thoughts on 'what next', or you can just take a look at an issue that interests you!

[pietroalbini]

And we have a new bucket.