Skip to content

Commit eb8b32a

Browse files
committed
fix
1 parent d736f5b commit eb8b32a

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

text/0000-rust-crate-ownership.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ We propose the following categories of published crates:
3838
- **Experiment**: This was an experiment by a team, intended to be picked up by users to better inform API design (or whatever), without a long-term commitment to maintainership. Example: [failure](https://crates.io/crates/failure)
3939
- **Deprecated**: This used to be an “intentional artifact” (or experiment/internal use) but isn’t anymore. Example: [rustc-serialize](https://crates.io/crates/rustc-serialize)
4040
- **Placeholder**: Not a functional crate, used for holding on to the name of an official tool, etc. Example: [rustup](https://crates.io/crates/rustup)
41-
- **Expatriated**: This may have been an “intentional artifact”, and still is intended to be used by external users, but is no longer intended to be official. Example: [rand](https://crates.io/crates/rand)
41+
- **Expatriated**: This may have been an “intentional artifact”, and still is intended to be used by external users, but is no longer intended to be official. In such cases the crate is no longer owned/managed by the Rust project. Example: [rand](https://crates.io/crates/rand)
4242

4343
## Policy
4444

@@ -118,7 +118,7 @@ Any transition _away_ from "Intentional Artifact" requires an RFC.
118118

119119
Any transition to "Intentional Artifact" should ideally be accompanied by an RFC, and an update to the team charter if there is one.
120120

121-
Expatriation should basically _never_ occur anymore, but it also requires an RFC and core team approval in case it is really necessary. If a team wishes to stop working on a crate, they should deprecate it and encourage the community to fork it or build their own thing.
121+
Expatriation should basically _never_ occur anymore, but it also requires an RFC and core team approval in case it is really necessary. If a team wishes to stop working on a crate, they should deprecate it and encourage the community to fork it or build their own thing. The repository may be transfered out, however the `crates.io` name is kept by the Rust project and the new group of maintainers will need to pick a new crate name.
122122

123123
If "transitively intentional" crates are being deprecated care should be taken to ensure security issues will still be handled.
124124

0 commit comments

Comments
 (0)