Skip to content

Commit 0a41829

Browse files
committed
Inside Rust: Write "crates.io Policy Update RFC" blog post
1 parent 69c646d commit 0a41829

File tree

1 file changed

+22
-0
lines changed

1 file changed

+22
-0
lines changed
Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
---
2+
layout: post
3+
title: crates.io Policy Update RFC
4+
author: Tobias Bieniek
5+
team: the crates.io team <https://www.rust-lang.org/governance/teams/crates-io>
6+
---
7+
8+
Around the end of July the crates.io team opened an [RFC](https://github.com/rust-lang/rfcs/pull/3463) to update the current crates.io usage policies. This has caused a lot of controversial discussion and most of the suggested improvements have since been integrated into the proposal.
9+
10+
At the last team meeting the crates.io team decided to move the RFC forward and start the **final comment period** process.
11+
12+
We have been made aware by a couple of community members though that the RFC might not have been visible enough in the Rust community. We hope that this blog post changes that.
13+
14+
We invite you all to review the RFC and let us know if there are still any major concerns with these proposed policies.
15+
16+
Here is a quick **TL;DR**:
17+
18+
- The current policies are quite vague on a couple of topic, the new policies are more explicit.
19+
- Name squatting is allowed, but only to a certain degree and if you have a good reason for it.
20+
- The crates.io team will try to contact crate owners before taking any actions.
21+
22+
Finally, if you have any comments, please open threads on the [RFC diff](https://github.com/rust-lang/rfcs/pull/3463/files) to keep the discussion somewhat structured. Thank you!

0 commit comments

Comments
 (0)