internals
policy
About the policy category
(2)
[blog] Rust Governance: Scaling Empathy
(
2
)
(28)
PSA: Please say something in the tracking issue if you're filing a relevant PR
(1)
Thoughts on RFC/stabilization reform in 2019
(
2
3
)
(50)
Crates.io package policies
(
2
3
4
)
(61)
Indicating when unstable features intend to be removed
(1)
Tracking GitHub Issue Issues
(4)
Pre-meta-RFC: rate limiting the firehose
(
2
)
(38)
Pre-eRFC: Crate name transfer
(20)
Should Rust have an art/design team?
(
2
3
)
(42)
Content of security announcements
(11)
Fortifying the process against feature bloat
(
2
3
)
(55)
Up-votes instead of down-votes on RFCs
(
2
3
4
5
)
(80)
Idea: mandate N independent uses before stabilizing a feature
(15)
Which team owns rust-lang/rust-www?
(3)
pre-RFC: RFC "Deliberation period"
(
2
3
)
(49)
License the RFCs repo under the CC-BY 4.0 license
(18)
[Idea] Extending the RFC process: Experimental features
(16)
RFC isn't blocked - but doesn't move
(8)
Tracking issues
(5)
Priorities after 1.0
(
2
3
4
5
6
)
(105)
Mini-RFC: Introduce awareness of release trains to GitHub issues
(15)
Breaking changes by adding default method (e.g. read_exact)
(6)
RFC process for 'minor' RFCs
(11)
Pronoun Policy
(
2
)
(27)
Diversity on the governance teams
(
2
3
4
5
6
7
)
(134)
Organizing Community Organization
(
2
)
(35)
Brainstorming: community subteam
(10)
Proposed security disclosure policy
(
2
)
(26)
When should we start stabilizing libraries?
(5)
next page →
