# policy

**URL:** https://internals.rust-lang.org/c/internals/policy/6.md

[Latest](https://internals.rust-lang.org/latest.md) · [Categories](https://internals.rust-lang.org/categories.md)

---

## [About the policy category](https://internals.rust-lang.org/t/about-the-policy-category/21)

<div class="topic-metadata">

**Author:** [@cmr](https://internals.rust-lang.org/u/cmr)\
**Replies:** 0\
**Last updated:** [July 7, 2014, 10:28pm UTC](https://internals.rust-lang.org/t/about-the-policy-category/21 "2014-07-07T22:28:10Z")

</div>

How the Rust project itself works.

---

## [pre-RFC: LTS for the Rust Toolchain](https://internals.rust-lang.org/t/pre-rfc-lts-for-the-rust-toolchain/24476)

<div class="topic-metadata">

**Author:** [@CAD97](https://internals.rust-lang.org/u/CAD97)\
**Replies:** 165\
**Last updated:** [October 1, 2026, 2:54pm UTC](https://internals.rust-lang.org/t/pre-rfc-lts-for-the-rust-toolchain/24476 "2026-10-01T14:54:16Z")

</div>

Disclaimer: I am proposing this as part of my employment at Canonical\[1\]. I am representing an interest of Canonical, but I am not representing Canonical itself. ▶ Intended Improvements I'm very aware of the volume of dis…

---

## [Rust-lang/rust LLM policy](https://internals.rust-lang.org/t/rust-lang-rust-llm-policy/24504)

<div class="topic-metadata">

**Author:** [@jyn](https://internals.rust-lang.org/u/jyn)\
**Replies:** 12\
**Last updated:** [August 9, 2026, 8:27am UTC](https://internals.rust-lang.org/t/rust-lang-rust-llm-policy/24504 "2026-08-09T08:27:21Z")

</div>

This is a discussion thread for rust-lang/rust's new LLM policy, which has been merged in rust-forge#1040. You can find more information about that policy in the blog post. Please comment here, not on the Forge or blog P…

---

## [Contributor Responsibility and Review Cost in the Age of Code Generation](https://internals.rust-lang.org/t/contributor-responsibility-and-review-cost-in-the-age-of-code-generation/24010)

<div class="topic-metadata">

**Author:** [@atix](https://internals.rust-lang.org/u/atix)\
**Replies:** 18\
**Last updated:** [March 6, 2026, 4:26am UTC](https://internals.rust-lang.org/t/contributor-responsibility-and-review-cost-in-the-age-of-code-generation/24010 "2026-03-06T04:26:12Z")

</div>

hiya! this is my first post here. I’d like to start a discussion about contributor responsibility and review cost in the context of AI-assisted code generation There have been periodic discussions about whether Rust sho…

---

## [Question about long-standing issues](https://internals.rust-lang.org/t/question-about-long-standing-issues/23220)

<div class="topic-metadata">

**Author:** [@Evian-Zhang](https://internals.rust-lang.org/u/Evian-Zhang)\
**Replies:** 10\
**Last updated:** [July 17, 2025, 4:37am UTC](https://internals.rust-lang.org/t/question-about-long-standing-issues/23220 "2025-07-17T04:37:48Z")

</div>

First of all, this post is not emotion-driven, and I am fully aware that the developers of Rust project work very hard. I'm not here to push anyone or blame anyone. There are two main types of issues in Rust project tha…

---

## [Type inference breakage in 1.80 has not been handled well](https://internals.rust-lang.org/t/type-inference-breakage-in-1-80-has-not-been-handled-well/21374)

<div class="topic-metadata">

**Author:** [@kornel](https://internals.rust-lang.org/u/kornel)\
**Replies:** 52\
**Last updated:** [December 22, 2024, 4:44pm UTC](https://internals.rust-lang.org/t/type-inference-breakage-in-1-80-has-not-been-handled-well/21374 "2024-12-22T16:44:05Z")

</div>

Rust 1.80 broke builds of almost all versions of the very popular time crate (edit: please don't shoot the messenger in that GitHub thread!!!) Rust has left only a 4-month old version working. That was not enough time f…

---

## [Any updates on the Rust Trademark?](https://internals.rust-lang.org/t/any-updates-on-the-rust-trademark/21256)

<div class="topic-metadata">

**Author:** [@programmerjake](https://internals.rust-lang.org/u/programmerjake)\
**Replies:** 1\
**Last updated:** [July 26, 2024, 1:37pm UTC](https://internals.rust-lang.org/t/any-updates-on-the-rust-trademark/21256 "2024-07-26T13:37:53Z")

</div>

It's been quite a while since there was last a public update on Rust's progress towards getting a new trademark policy, can someone provide an update on how that going, and maybe an estimated date when the new policy wil…

---

## [Improve format of Rust RFC, like Python PEP](https://internals.rust-lang.org/t/improve-format-of-rust-rfc-like-python-pep/20180)

<div class="topic-metadata">

**Author:** [@hehaoqian](https://internals.rust-lang.org/u/hehaoqian)\
**Replies:** 6\
**Last updated:** [January 16, 2024, 6:44am UTC](https://internals.rust-lang.org/t/improve-format-of-rust-rfc-like-python-pep/20180 "2024-01-16T06:44:30Z")

</div>

Compare to PEP (Python Enhance Proposal), The format of Rust RFCs is much more informal. Rust RFCs are very unlikely to be updated, while PEPs are updated whenever its status changed (Draft, accepted, Final), with ever…

---

## [Blog Post: Stability without stressing the !@#! out](https://internals.rust-lang.org/t/blog-post-stability-without-stressing-the-out/19592)

<div class="topic-metadata">

**Author:** [@matklad](https://internals.rust-lang.org/u/matklad)\
**Replies:** 13\
**Last updated:** [September 21, 2023, 4:17pm UTC](https://internals.rust-lang.org/t/blog-post-stability-without-stressing-the-out/19592 "2023-09-21T16:17:34Z")

</div>

https://smallcultfollowing.com/babysteps/blog/2023/09/18/stability-without-stressing-the-out/

---

## ["No telemetry in the Rust compiler: metrics without betraying user privacy"](https://internals.rust-lang.org/t/no-telemetry-in-the-rust-compiler-metrics-without-betraying-user-privacy/19275)

<div class="topic-metadata">

**Author:** [@ekuber](https://internals.rust-lang.org/u/ekuber)\
**Replies:** 5\
**Last updated:** [August 25, 2023, 5:23am UTC](https://internals.rust-lang.org/t/no-telemetry-in-the-rust-compiler-metrics-without-betraying-user-privacy/19275 "2023-08-25T05:23:47Z")

</div>

"No telemetry in the Rust compiler: metrics without betraying user privacy" I have some thoughts about something I believe we need: local-only stable-compiler metrics. For a while I've felt that we don't really have eno…

---

## [Crates-io metadata usage policy](https://internals.rust-lang.org/t/crates-io-metadata-usage-policy/13904)

<div class="topic-metadata">

**Author:** [@kornel](https://internals.rust-lang.org/u/kornel)\
**Replies:** 5\
**Last updated:** [July 21, 2023, 4:00am UTC](https://internals.rust-lang.org/t/crates-io-metadata-usage-policy/13904 "2023-07-21T04:00:53Z")

</div>

I don't see anything in crates-io policies about the license/usage policy of the crate metadata published to crates-io. As a package author, what usage rights do I give to crates-io? As a 3rd party crawler/consumer of …

---

## [Rust MSRV policy and Linux Distros](https://internals.rust-lang.org/t/rust-msrv-policy-and-linux-distros/17074)

<div class="topic-metadata">

**Author:** [@kornel](https://internals.rust-lang.org/u/kornel)\
**Replies:** 35\
**Last updated:** [August 18, 2022, 12:57pm UTC](https://internals.rust-lang.org/t/rust-msrv-policy-and-linux-distros/17074 "2022-08-18T12:57:52Z")

</div>

Discussion about MSRV of the libc crate raises the question of what actually is Rust's policy for support of old Rust versions. Can the Rust project have a clear minimum supported Rust version, including explicit guid…

---

## [Keeping around unstable features until their replacements hit stable](https://internals.rust-lang.org/t/keeping-around-unstable-features-until-their-replacements-hit-stable/15006)

<div class="topic-metadata">

**Author:** [@illicitonion](https://internals.rust-lang.org/u/illicitonion)\
**Replies:** 5\
**Last updated:** [July 12, 2021, 7:30am UTC](https://internals.rust-lang.org/t/keeping-around-unstable-features-until-their-replacements-hit-stable/15006 "2021-07-12T07:30:16Z")

</div>

I hit an interesting issue recently; in a crate I maintain, we have a cargo feature which enables and uses the unstable external\_doc feature so that docs.rs can load doc comments from a README.md. This works because docs…

---

## [Paying developers for pull requests](https://internals.rust-lang.org/t/paying-developers-for-pull-requests/13058)

<div class="topic-metadata">

**Author:** [@mankinskin](https://internals.rust-lang.org/u/mankinskin)\
**Replies:** 39\
**Last updated:** [September 21, 2020, 2:42pm UTC](https://internals.rust-lang.org/t/paying-developers-for-pull-requests/13058 "2020-09-21T14:42:08Z")

</div>

What do you guys think of rewarding developers for issues they resolve? This requires some more thought, and of course funding, but it is probably possible to do and it feels very much like the right direction to me.

---

## [\[blog\] Rust Governance: Scaling Empathy](https://internals.rust-lang.org/t/blog-rust-governance-scaling-empathy/9412)

<div class="topic-metadata">

**Author:** [@Manishearth](https://internals.rust-lang.org/u/Manishearth)\
**Replies:** 27\
**Last updated:** [February 13, 2019, 6:40pm UTC](https://internals.rust-lang.org/t/blog-rust-governance-scaling-empathy/9412 "2019-02-13T18:40:22Z")

</div>

Last week in prep for the Rust All Hands I wrote down a bunch of thoughts about governance in Rust, specifically focusing on how we conduct online discussions. Sharing this a bit more widely now:

---

## [PSA: Please say something in the tracking issue if you're filing a relevant PR](https://internals.rust-lang.org/t/psa-please-say-something-in-the-tracking-issue-if-youre-filing-a-relevant-pr/9432)

<div class="topic-metadata">

**Author:** [@jethrogb](https://internals.rust-lang.org/u/jethrogb)\
**Replies:** 0\
**Last updated:** [February 13, 2019, 4:59pm UTC](https://internals.rust-lang.org/t/psa-please-say-something-in-the-tracking-issue-if-youre-filing-a-relevant-pr/9432 "2019-02-13T16:59:24Z")

</div>

GitHub doesn’t send notification e-mails when an issue is referenced. If you file a PR that relates to an active tracking issue (say, implementing or stabilizing (part of) it), please also mention that you’ve done so in …

---

## [Thoughts on RFC/stabilization reform in 2019](https://internals.rust-lang.org/t/thoughts-on-rfc-stabilization-reform-in-2019/9202)

<div class="topic-metadata">

**Author:** [@mark-i-m](https://internals.rust-lang.org/u/mark-i-m)\
**Replies:** 49\
**Last updated:** [February 1, 2019, 4:45am UTC](https://internals.rust-lang.org/t/thoughts-on-rfc-stabilization-reform-in-2019/9202 "2019-02-01T04:45:14Z")

</div>

I’ve been thinking a lot about RFC and stabilization reform. This has been partly inspired by my own experience and partly by insights from reading Rust2019 posts. (EDIT: reformatted to make it less of a wall of text) (…

---

## [Crates.io package policies](https://internals.rust-lang.org/t/crates-io-package-policies/1041)

<div class="topic-metadata">

**Author:** [@steveklabnik](https://internals.rust-lang.org/u/steveklabnik)\
**Replies:** 60\
**Last updated:** [January 19, 2019, 1:40am UTC](https://internals.rust-lang.org/t/crates-io-package-policies/1041 "2019-01-19T01:40:15Z")

</div>

Packages Policy for Crates.io In a previous post to the Rust blog, we announced the preview launch of crates.io, giving the Rust community a way to easily publish packages. After a few weeks of kicking the tires, and he…

---

## [Indicating when unstable features intend to be removed](https://internals.rust-lang.org/t/indicating-when-unstable-features-intend-to-be-removed/9231)

<div class="topic-metadata">

**Author:** [@wbrian](https://internals.rust-lang.org/u/wbrian)\
**Replies:** 0\
**Last updated:** [January 18, 2019, 3:10am UTC](https://internals.rust-lang.org/t/indicating-when-unstable-features-intend-to-be-removed/9231 "2019-01-18T03:10:14Z")

</div>

This may not be a particularly common case, but I happened across the box syntax because it was a nice solution to a problem I was having. Reading through the comments in the tracking issue, it appears a foregone conclus…

---

## [Tracking GitHub Issue Issues](https://internals.rust-lang.org/t/tracking-github-issue-issues/9175)

<div class="topic-metadata">

**Author:** [@nixpulvis](https://internals.rust-lang.org/u/nixpulvis)\
**Replies:** 3\
**Last updated:** [January 10, 2019, 7:50am UTC](https://internals.rust-lang.org/t/tracking-github-issue-issues/9175 "2019-01-10T07:50:29Z")

</div>

I’m creating this thread because I feel there is a mismatch in expectations between some people following https://github.com/rust-lang/rust/issues/24111, myself included. I’m not creating this because I’m super upset or …

---

## [Pre-meta-RFC: rate limiting the firehose](https://internals.rust-lang.org/t/pre-meta-rfc-rate-limiting-the-firehose/9107)

<div class="topic-metadata">

**Author:** [@mark-i-m](https://internals.rust-lang.org/u/mark-i-m)\
**Replies:** 36\
**Last updated:** [December 28, 2018, 8:12pm UTC](https://internals.rust-lang.org/t/pre-meta-rfc-rate-limiting-the-firehose/9107 "2018-12-28T20:12:59Z")

</div>

Summary Use the rfcbot to make Github-based design discussions more manageable. This proposal is the confluence of a few different parts. I know that this proposal will likely give people a “what?! you’re kidding!” react…

---

## [Pre-eRFC: Crate name transfer](https://internals.rust-lang.org/t/pre-erfc-crate-name-transfer/9027)

<div class="topic-metadata">

**Author:** [@dtolnay](https://internals.rust-lang.org/u/dtolnay)\
**Replies:** 18\
**Last updated:** [December 18, 2018, 4:37pm UTC](https://internals.rust-lang.org/t/pre-erfc-crate-name-transfer/9027 "2018-12-18T16:37:16Z")

</div>

A real RFC has been opened as RFC 2614. A pre-RFC draft is preserved below. Summary This experimental RFC proposes a process by which a designated Rust team member or members could reassign ownership of a crate …

---

## [Should Rust have an art/design team?](https://internals.rust-lang.org/t/should-rust-have-an-art-design-team/2075)

<div class="topic-metadata">

**Author:** [@aldeka](https://internals.rust-lang.org/u/aldeka)\
**Replies:** 40\
**Last updated:** [November 8, 2018, 8:01am UTC](https://internals.rust-lang.org/t/should-rust-have-an-art-design-team/2075 "2018-11-08T08:01:53Z")

</div>

Hi! My name's Karen Rustad and I'm a designer and web developer. I made the non-official rustacean mascot, t-shirts, and stickers a few months ago. With the unveiling of the new Rust governance structure and subteams, …

---

## [Content of security announcements](https://internals.rust-lang.org/t/content-of-security-announcements/8492)

<div class="topic-metadata">

**Author:** [@fweimer](https://internals.rust-lang.org/u/fweimer)\
**Replies:** 9\
**Last updated:** [October 20, 2018, 6:28pm UTC](https://internals.rust-lang.org/t/content-of-security-announcements/8492 "2018-10-20T18:28:55Z")

</div>

May I suggest that security announcements (such as the recent (2018-09-21) Security advisory for the standard library contain at least the following: A unique, descriptive title (so no more “Security advisory for the s…

---

## [Fortifying the process against feature bloat](https://internals.rust-lang.org/t/fortifying-the-process-against-feature-bloat/7608)

<div class="topic-metadata">

**Author:** [@vorner](https://internals.rust-lang.org/u/vorner)\
**Replies:** 53\
**Last updated:** [July 24, 2018, 1:26pm UTC](https://internals.rust-lang.org/t/fortifying-the-process-against-feature-bloat/7608 "2018-07-24T13:26:21Z")

</div>

This topic originates from a sibling thread Pre-RFC: flexible \`try fn\`. If you want to catch up on that but don’t want to read it whole (it is long and sometimes a bit heated), I try to sum it up here (but I’m necessaril…

---

## [Up-votes instead of down-votes on RFCs](https://internals.rust-lang.org/t/up-votes-instead-of-down-votes-on-rfcs/6309)

<div class="topic-metadata">

**Author:** [@Centril](https://internals.rust-lang.org/u/Centril)\
**Replies:** 77\
**Last updated:** [May 17, 2018, 11:07am UTC](https://internals.rust-lang.org/t/up-votes-instead-of-down-votes-on-rfcs/6309 "2018-05-17T11:07:54Z")

</div>

Currently, some RFCs get a lot of down-votes. This can be especially frustrating and discouraging for new users to the RFC process and Rust community in general. Spending a lot of time on writing an RFC only to have it d…

---

## [Idea: mandate N independent uses before stabilizing a feature](https://internals.rust-lang.org/t/idea-mandate-n-independent-uses-before-stabilizing-a-feature/7522)

<div class="topic-metadata">

**Author:** [@vorner](https://internals.rust-lang.org/u/vorner)\
**Replies:** 13\
**Last updated:** [May 17, 2018, 8:22am UTC](https://internals.rust-lang.org/t/idea-mandate-n-independent-uses-before-stabilizing-a-feature/7522 "2018-05-17T08:22:04Z")

</div>

Hello I was pondering about an idea. Currently, the RFC is merged, then it is implemented, bakes there with a feature flag for a while and then gets stabilized (unless some problem is found on the road). While trying it…

---

## [Which team owns rust-lang/rust-www?](https://internals.rust-lang.org/t/which-team-owns-rust-lang-rust-www/6449)

<div class="topic-metadata">

**Author:** [@frewsxcv](https://internals.rust-lang.org/u/frewsxcv)\
**Replies:** 1\
**Last updated:** [January 3, 2018, 5:15am UTC](https://internals.rust-lang.org/t/which-team-owns-rust-lang-rust-www/6449 "2018-01-03T05:15:10Z")

</div>

Is there a certain team that owns https://github.com/rust-lang/rust-www/ ? I noticed there are more than a few open pull requests that have gone unreviewed for quite some time. My time is limited, but I’d be willing to h…

---

## [pre-RFC: RFC "Deliberation period"](https://internals.rust-lang.org/t/pre-rfc-rfc-deliberation-period/5710)

<div class="topic-metadata">

**Author:** [@carols10cents](https://internals.rust-lang.org/u/carols10cents)\
**Replies:** 47\
**Last updated:** [November 10, 2017, 3:08am UTC](https://internals.rust-lang.org/t/pre-rfc-rfc-deliberation-period/5710 "2017-11-10T03:08:55Z")

</div>

Summary When an RFC is posted, we start with a “deliberation period” or “quiet reading time” about the length of FCP (10 days) during which no public comments are posted on the RFC itself. Everyone gets a bit time to rea…

---

## [License the RFCs repo under the CC-BY 4.0 license](https://internals.rust-lang.org/t/license-the-rfcs-repo-under-the-cc-by-4-0-license/3870)

<div class="topic-metadata">

**Author:** [@strega-nil](https://internals.rust-lang.org/u/strega-nil)\
**Replies:** 16\
**Last updated:** [June 26, 2017, 3:29pm UTC](https://internals.rust-lang.org/t/license-the-rfcs-repo-under-the-cc-by-4-0-license/3870 "2017-06-26T15:29:31Z")

</div>

The issue being that currently, there is no license. I have already done the work, I just need to open the PR. Any concerns? It would be similar to this thread: The COPYRIGHT would read: EDITED (MIT/Apache) Short…

[Next page](https://internals.rust-lang.org/c/internals/policy/6.md?page=1)
