Skip to content

Commit 103d06d

Browse files
authored
Change crates.io policy to not offer crate transfer mediation (#9530)
This PR implements rust-lang/rfcs#3646. For some reason I thought this had already been implemented, but I just stumbled upon that section in the policies and was surprised that it was still in there... 😅
1 parent b1d3945 commit 103d06d

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

app/templates/policies/index.hbs

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -71,10 +71,10 @@
7171
<p>crates.io has a first-come, first-serve policy on crate names. Upon publishing a package, the publisher will be made
7272
owner of the package on crates.io.</p>
7373

74-
<p>If you want to take over a package, we require you to first try and contact the current owner directly. If the
75-
current owner agrees, they can add you as an owner of the crate, and you can then remove them, if necessary. If the
76-
current owner is not reachable or has not published any contact information the crates.io team may reach out to help
77-
mediate the process of the ownership transfer.</p>
74+
<p>If you want to take over a package, we recommend you try and contact the current owner directly. If the
75+
current owner agrees, they can add you as an owner of the crate, and you can then remove them, if necessary.
76+
For security reasons, the crates.io team will not transfer ownership of existing crates without the explicit
77+
approval of the current owner.</p>
7878

7979
<p>Crate deletion by their owners is not possible to keep the registry as immutable as possible. If you want to flag
8080
your crate as open for transferring ownership to others, you can publish a new version with a message in the README or

0 commit comments

Comments
 (0)