|
About the policy category
|
|
1
|
1467
|
March 25, 2019
|
|
Improve format of Rust RFC, like Python PEP
|
|
6
|
640
|
January 16, 2024
|
|
Blog Post: Stability without stressing the !@#! out
|
|
13
|
1354
|
September 21, 2023
|
|
"No telemetry in the Rust compiler: metrics without betraying user privacy"
|
|
5
|
1248
|
August 25, 2023
|
|
Crates-io metadata usage policy
|
|
5
|
1388
|
July 21, 2023
|
|
Rust MSRV policy and Linux Distros
|
|
35
|
4491
|
August 18, 2022
|
|
Keeping around unstable features until their replacements hit stable
|
|
5
|
1117
|
July 12, 2021
|
|
Paying developers for pull requests
|
|
39
|
2484
|
September 21, 2020
|
|
[blog] Rust Governance: Scaling Empathy
|
|
28
|
2464
|
May 14, 2019
|
|
PSA: Please say something in the tracking issue if you're filing a relevant PR
|
|
1
|
777
|
May 14, 2019
|
|
Thoughts on RFC/stabilization reform in 2019
|
|
50
|
5553
|
May 2, 2019
|
|
Crates.io package policies
|
|
61
|
29700
|
April 19, 2019
|
|
Indicating when unstable features intend to be removed
|
|
1
|
754
|
April 18, 2019
|
|
Tracking GitHub Issue Issues
|
|
4
|
1305
|
April 10, 2019
|
|
Pre-meta-RFC: rate limiting the firehose
|
|
37
|
2808
|
March 28, 2019
|
|
Pre-eRFC: Crate name transfer
|
|
19
|
2646
|
March 25, 2019
|
|
Should Rust have an art/design team?
|
|
41
|
8917
|
March 25, 2019
|
|
Content of security announcements
|
|
10
|
1550
|
March 25, 2019
|
|
Fortifying the process against feature bloat
|
|
54
|
8116
|
March 25, 2019
|
|
Up-votes instead of down-votes on RFCs
|
|
79
|
7335
|
May 17, 2018
|
|
Idea: mandate N independent uses before stabilizing a feature
|
|
14
|
2002
|
March 25, 2019
|
|
Which team owns rust-lang/rust-www?
|
|
2
|
1101
|
March 25, 2019
|
|
pre-RFC: RFC "Deliberation period"
|
|
48
|
3610
|
March 25, 2019
|
|
License the RFCs repo under the CC-BY 4.0 license
|
|
17
|
2944
|
March 25, 2019
|
|
[Idea] Extending the RFC process: Experimental features
|
|
15
|
3480
|
March 25, 2019
|
|
RFC isn't blocked - but doesn't move
|
|
7
|
2025
|
March 25, 2019
|
|
Tracking issues
|
|
4
|
1475
|
March 25, 2019
|
|
Priorities after 1.0
|
|
104
|
42066
|
March 25, 2019
|
|
Mini-RFC: Introduce awareness of release trains to GitHub issues
|
|
14
|
3591
|
March 25, 2019
|
|
Breaking changes by adding default method (e.g. read_exact)
|
|
5
|
2356
|
March 25, 2019
|