Skip to content

Move Crates.io package policies to this repo? #1030

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

Closed
behnam opened this issue Aug 31, 2017 · 1 comment · Fixed by rust-lang/cargo#4461
Closed

Move Crates.io package policies to this repo? #1030

behnam opened this issue Aug 31, 2017 · 1 comment · Fixed by rust-lang/cargo#4461
Labels
C-documentation 📜 Category: Documentation of crates.io itself

Comments

@behnam
Copy link
Contributor

behnam commented Aug 31, 2017

While we're moving cargo docs to https://doc.rust-lang.org/cargo, there's one page that's very crates.io-specific, and not build-system-specific: the Crates.io package policies.

Should we move that content to this repo, like http://crates.io/policies?

@carols10cents
Copy link
Member

sounds good!

@carols10cents carols10cents added the C-documentation 📜 Category: Documentation of crates.io itself label Aug 31, 2017
behnam added a commit to behnam/crates.io that referenced this issue Sep 1, 2017
Moving the "Crates.io Package Policies" page from
<http://doc.crates.io/policies.html>, which is hosted in `cargo` repo,
here, as this is a website-related content and not related to the
build-system.

First step for <rust-lang#1030>

Next step will be to redirect the old URL to this new page.
behnam added a commit to behnam/rust-cargo that referenced this issue Sep 2, 2017
We don't need to put `policies.md` in the book. See
<rust-lang/crates.io#1030> for more.

Renaming `introduction.md` to `index.md` prevents creating two html
files (and URL) for one source.

The rest are small styling issues.

Tracker: <rust-lang#4040>
bors added a commit to rust-lang/cargo that referenced this issue Sep 2, 2017
[doc/book] Drop reference/policies.md and small fixes

We don't need to put `policies.md` in the book. See
<rust-lang/crates.io#1030> for more.

Renaming `introduction.md` to `index.md` prevents creating two html
files (and URL) for one source.

The rest are small styling issues.

Tracker: <#4040>
bors-voyager bot added a commit that referenced this issue Sep 3, 2017
1033: Add /policies page r=carols10cents

Moving the "Crates.io Package Policies" page from
<http://doc.crates.io/policies.html>, which is hosted in `cargo` repo,
here, as this is a website-related content and not related to the
build-system.

First step for <#1030>

Next step will be to redirect the old URL to this new page.

1034: [header] Replace CARGO with crates.io r=carols10cents

As Cargo documentation is being moved to <doc.rust-lang.org>, and to
emphasis the difference between `crates.io` and `cargo`, we better not
title the website as *CARGO* anymore.

This is a quick fix for this, until we redirect `docs.crates.io`
completely and fix the menus and links here.

See <#1031>
behnam added a commit to behnam/rust-cargo that referenced this issue Sep 6, 2017
This relieves us from migrating the Package Policies document into the
new Cargo Manual mdbook.

Moved the content to `crates.io` repo in
<rust-lang/crates.io#1033>.

NOTE: We should wait until that change goes live before landing this
one. I'll notify here when it's time to land.

Closes <rust-lang/crates.io#1030>
bors added a commit to rust-lang/cargo that referenced this issue Sep 6, 2017
[doc] Redirect /policies.html to crates.io/policies

This relieves us from migrating the Package Policies document into the
new Cargo Manual mdbook.

Moved the content to `crates.io` repo in
<rust-lang/crates.io#1033>.

NOTE: We should wait until that change goes live before landing this
one. I'll notify here when it's time to land.

Closes <rust-lang/crates.io#1030>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-documentation 📜 Category: Documentation of crates.io itself
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants