Inside Rust: Write "crates.io Policy Update RFC" blog post (#1143)

Co-authored-by: Nathan Stocks <cleancut@github.com>
Co-authored-by: Adam Harvey <adam@adamharvey.name>
Co-authored-by: Carol (Nichols || Goulding) <193874+carols10cents@users.noreply.github.com>

Author: 4 people

posts/2023-09-22-crates-io-usage-policy-rfc.md

@@ -0,0 +1,22 @@
+---
+layout: post
+title: crates.io Policy Update RFC
+author: Tobias Bieniek
+team: the crates.io team <https://www.rust-lang.org/governance/teams/crates-io>
+---
+
+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 policy update addresses operational concerns of the crates.io community service that have arisen since the last significant policy update in 2017, particularly related to name squatting and spam. The RFC has caused considerable discussion, and most of the suggested improvements have since been integrated into the proposal.
+
+At the last team meeting the crates.io team decided to move the RFC forward and start the **final comment period** process.
+
+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.
+
+We invite you all to review the RFC and let us know if there are still any major concerns with these proposed policies.
+
+Here is a quick **TL;DR**:
+
+- The current policies are quite vague on a couple of topics. The new policies are more explicit.
+- Reserving names is still allowed, but only to a certain degree and if you have a good reason for it.
+- The crates.io team will try to contact crate owners before taking any actions.
+
+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!