Skip to content

Adjust branding to reflect what crates.io actually does #1787

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

Merged
merged 2 commits into from
Aug 7, 2019
Merged

Adjust branding to reflect what crates.io actually does #1787

merged 2 commits into from
Aug 7, 2019

Conversation

rye
Copy link
Contributor

@rye rye commented Jul 21, 2019

To be clear that crates.io is a Rust package registry—in fact the default crate host for Rust---this commit changes the name, short_name, and description fields in the manifest to reflect the nature of the project. crates.io isn't really "Cargo", so it seems logical to me to not mention much about it, at least in the metadata for the site.

I also more explicitly mention that crates.io is the "default" package registry to be a bit more neutral; it's the baked-in default in Cargo, but there are others out there. I got the branding "Rust Package Registry" from the tagline in the visible top bar on the landing page.

Also, update the various acceptance tests that I found floating around.

Should resolve #1777, I think.

To be clear that crates.io is a Rust package registry---in fact the
_default_ crate host for Rust---this commit changes the name,
short_name, and description fields in the manifest to reflect the nature
of the project.  crates.io isn't "Cargo", so it seems logical to me to
not mention much about it, at least in the metadata for the site.

I got the branding "Rust Package Registry" from the tagline in the
visible top bar on the landing page.

Also, update the various acceptance tests that I found floating around.

Signed-off-by: Kristofer Rye <[email protected]>
@rust-highfive
Copy link

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @sgrif (or someone else) soon.

If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.

Please see the contribution instructions for more information.

Oops!  I didn't inspect my diff very closely.

Signed-off-by: Kristofer Rye <[email protected]>
@smarnach
Copy link
Contributor

smarnach commented Aug 4, 2019

@jtgeibel This looks rather uncontroversial to me – it makes the branding in the title match the branding we already have at the top of the page. The code changes look fine to me, so maybe we can merge this?

@kzys
Copy link
Contributor

kzys commented Aug 6, 2019

Looks good to me. +1 for merging.

@sgrif
Copy link
Contributor

sgrif commented Aug 7, 2019

@bors r+

@bors
Copy link
Contributor

bors commented Aug 7, 2019

📌 Commit fcd6703 has been approved by sgrif

@bors
Copy link
Contributor

bors commented Aug 7, 2019

⌛ Testing commit fcd6703 with merge d766128...

bors added a commit that referenced this pull request Aug 7, 2019
Adjust branding to reflect what crates.io actually does

To be clear that crates.io is a Rust package registry&mdash;in fact the _default_ crate host for Rust---this commit changes the `name`, `short_name`, and `description` fields in the manifest to reflect the nature of the project.  crates.io isn't really "Cargo", so it seems logical to me to not mention much about it, at least in the metadata for the site.

I also more explicitly mention that `crates.io` is the "default" package registry to be a bit more neutral; it's the baked-in default in Cargo, but there are others out there. I got the branding "Rust Package Registry" from the tagline in the visible top bar on the landing page.

Also, update the various acceptance tests that I found floating around.

Should resolve #1777, I think.
@bors
Copy link
Contributor

bors commented Aug 7, 2019

☀️ Test successful - checks-travis
Approved by: sgrif
Pushing d766128 to master...

@bors bors merged commit fcd6703 into rust-lang:master Aug 7, 2019
@bors bors mentioned this pull request Aug 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

<head> description of crates.io confusingly refers to Cargo
6 participants