1
1
# Crate removal procedure
2
2
3
- > ** Status 2020-01-21** : this document is incomplete and unvetted. We anticipate to
4
- > be receiving guidelines from Mozilla Legal in the near future. If this notice
5
- > is still here on 2020-03-21, please comment on [ this issue] [ outdated-issue ]
6
- > asking for a status update.
3
+ If we get a DMCA takedown notice, here's what needs to happen:
7
4
8
- [ outdated-issue ] : https://github.com/rust-lang/crates-io-cargo-teams/issues/63
5
+ ## Contact Mozilla Legal
9
6
10
- If we get a DMCA takedown notice, here's what needs to happen:
7
+ Before removing the crates, [ get in touch with legal] ( ../core/legal.md ) and ask
8
+ an opinion from them on the received request and whether we have to comply with
9
+ it.
11
10
12
11
## Remove relevant version(s) and/or entire crates from crates.io
13
12
14
13
* Remove it from the database:
15
14
16
- heroku run -- cargo run --bin delete-crate [crate-name]
15
+ heroku run -a crates-io -- target/release/ delete-crate [crate-name]
17
16
18
17
or
19
18
20
- heroku run -- cargo run --bin delete-version [crate-name] [version-number]
19
+ heroku run -a crates-io -- target/release/ delete-version [crate-name] [version-number]
21
20
22
21
* Remove the crate or version from the index. To remove an entire crate, remove
23
22
the entire crate file. For a version, remove the line corresponding to the
@@ -35,9 +34,7 @@ of a crate, by running a CLI command. The people who currently have permissions
35
34
to access the server and run it are:
36
35
37
36
* docs.rs Team:
38
- * [ @QuietMisdreavus ] ( https://github.com/QuietMisdreavus )
39
37
* [ @pietroalbini ] ( https://github.com/pietroalbini )
40
- * [ @onur ] ( https://github.com/onur )
41
38
* [ @jyn514 ] ( https://github.com/jyn514 )
42
39
* Infrastructure Team:
43
40
* [ @Mark-Simulacrum ] ( https://github.com/Mark-Simulacrum )
0 commit comments