Move all crates.io instructions to crates.io ops guide

src/SUMMARY.md

@@ -30,8 +30,6 @@
         - [How to run the planning meeting](./compiler/steering-meeting/how-to-run-planning.md)
         - [How to run a design meeting](./compiler/steering-meeting/how-to-run-design.md)
 - [crates.io](./crates-io/README.md)
-    - [Crate removal](./crates-io/crate-removal.md)
-    - [Database maintenance](./crates-io/db-maintenance.md)
 - [docs.rs](./docs-rs/README.md)
   - [Adding dependencies to the build environment](./docs-rs/add-dependencies.md)
   - [Self-hosting a docs.rs instance](./docs-rs/self-hosting.md)

src/crates-io/README.md

@@ -1,3 +1,8 @@
 # crates.io
 
-This section documents the processes of the crates.io team.
+The crates.io team has [its own operations guide][ops] in [a private repo][repo]. Contact [a member
+of the crates.io team][team] if you need access to the crates.io ops guide.
+
+[ops]: https://ops-guide.crates.io/
+[repo]: https://github.com/rust-lang/crates-io-ops-guide
+[team]: https://www.rust-lang.org/governance/teams/crates-io

src/docs-rs/maintenance.md

@@ -122,9 +122,18 @@ UPDATE queue SET attempt = 0 WHERE attempt >= 5 AND build_time > 'YYYY-MM-DD HH:
 
 ## Removing a crate from the website
 
-Sometimes it might be needed to remove all the content related to a crate from
-docs.rs (for example after receiving a DMCA). To do that, log into the server
-and run:
+The docs.rs application supports deleting all the documentation ever published
+of a crate (for example after receiving a DMCA), by running a CLI command. The
+people who currently have permissions to access the server and run it are:
+
+* docs.rs Team:
+  * [@pietroalbini](https://github.com/pietroalbini)
+  * [@jyn514](https://github.com/jyn514)
+* Infrastructure Team:
+  * [@Mark-Simulacrum](https://github.com/Mark-Simulacrum)
+* People with elevated 1password access
+
+If you are one of these people, log into the server and run:
 
 ```
 cratesfyi database delete-crate CRATE_NAME