---
# System prepended metadata

title: '\[draft\] Rust Compiler Contributor Guiding Principles'

---

# \[draft\] Rust Compiler Contributor Guiding Principles 

----

This is next iteration on previous [Guiding Principles draft](https://hackmd.io/TYGRjVIbSBmxpbcfDzll-w?view)

It incorporates the input from the April 23rd steering meeting ([zulip archive][2021-04-23 mtg]; [meeting notes](https://hackmd.io/awoymhnuQoGABt22e7JJBw)) and discussions that followed that meeting.

[2021-04-23 mtg]: https://zulip-archive.rust-lang.org/238009tcompilermeetings/95764steeringmeeting20210323GPscompilerteam424.html

Feel free to leave feedback as hackmd comments, or if you want to join the conversation, come to [the zulip topic][zulip topic].

[zulip topic]: https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/Contributor.20Guiding.20Principles.2C.20Take.202/near/235864273

---- 

These are our guiding principles; they are meant to guide people in making decisions about how to make contributions to the rustc code base, and how to interact with others on the project.

----

This list is open to change; if you have suggestions for:
1. new principles to add,
2. amendments to the existing ones,
3. an argument for why a proposed principle should not be on this list, or 
4. an unaddressed domain that should be covered here,

then please do reach out to the compiler team leadership!

----


### *(These are still in draft status)*

 * *Change Notes:*
     * *2021-04-23: created doc*

*The general format is: 1. Succinct Title, 2. expository text explaining the principle in the abstract, 3. bullets with concrete illustrative examples.*
