├── CODE_OF_CONDUCT.md └── README.md /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # The Rust Code of Conduct 2 | 3 | ## Conduct 4 | 5 | **Contact**: [Secure Code WG][wg] 6 | 7 | * We are committed to providing a friendly, safe and welcoming environment for all, regardless of level of experience, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, ethnicity, age, religion, nationality, or other similar characteristic. 8 | * On IRC, please avoid using overtly sexual nicknames or other nicknames that might detract from a friendly, safe and welcoming environment for all. 9 | * Please be kind and courteous. There's no need to be mean or rude. 10 | * Respect that people have differences of opinion and that every design or implementation choice carries a trade-off and numerous costs. There is seldom a right answer. 11 | * Please keep unstructured critique to a minimum. If you have solid ideas you want to experiment with, make a fork and see how it works. 12 | * We will exclude you from interaction if you insult, demean or harass anyone. That is not welcome behavior. We interpret the term "harassment" as including the definition in the [Citizen Code of Conduct](http://citizencodeofconduct.org/); if you have any lack of clarity about what might be included in that concept, please read their definition. In particular, we don't tolerate behavior that excludes people in socially marginalized groups. 13 | * Private harassment is also unacceptable. No matter who you are, if you feel you have been or are being harassed or made uncomfortable by a community member, please contact one of the channel ops or any of the [Secure Code WG][wg] immediately. Whether you're a regular contributor or a newcomer, we care about making this community a safe place for you and we've got your back. 14 | * Likewise any spamming, trolling, flaming, baiting or other attention-stealing behavior is not welcome. 15 | 16 | ## Moderation 17 | 18 | 19 | These are the policies for upholding our community's standards of conduct. If you feel that a thread needs moderation, please contact the [Secure Code WG][wg]. 20 | 21 | 1. Remarks that violate the Rust standards of conduct, including hateful, hurtful, oppressive, or exclusionary remarks, are not allowed. (Cursing is allowed, but never targeting another user, and never in a hateful manner.) 22 | 2. Remarks that moderators find inappropriate, whether listed in the code of conduct or not, are also not allowed. 23 | 3. Moderators will first respond to such remarks with a warning. 24 | 4. If the warning is unheeded, the user will be "kicked," i.e., kicked out of the communication channel to cool off. 25 | 5. If the user comes back and continues to make trouble, they will be banned, i.e., indefinitely excluded. 26 | 6. Moderators may choose at their discretion to un-ban the user if it was a first offense and they offer the offended party a genuine apology. 27 | 7. If a moderator bans someone and you think it was unjustified, please take it up with that moderator, or with a different moderator, **in private**. Complaints about bans in-channel are not allowed. 28 | 8. Moderators are held to a higher standard than other community members. If a moderator creates an inappropriate situation, they should expect less leeway than others. 29 | 30 | In the Rust community we strive to go the extra step to look out for each other. Don't just aim to be technically unimpeachable, try to be your best self. In particular, avoid flirting with offensive or sensitive issues, particularly if they're off-topic; this all too often leads to unnecessary fights, hurt feelings, and damaged trust; worse, it can drive people away from the community entirely. 31 | 32 | And if someone takes issue with something you said or did, resist the urge to be defensive. Just stop doing what it was they complained about and apologize. Even if you feel you were misinterpreted or unfairly accused, chances are good there was something you could've communicated better — remember that it's your responsibility to make your fellow Rustaceans comfortable. Everyone wants to get along and we are all here first and foremost because we want to talk about cool technology. You will find that people will be eager to assume good intent and forgive as long as you earn their trust. 33 | 34 | The enforcement policies listed above apply to all official Secure Code WG venues; including official instant messaging channels; and GitHub repositories under rust-secure-code. 35 | 36 | *Adapted from the [Node.js Policy on Trolling](http://blog.izs.me/post/30036893703/policy-on-trolling) as well as the [Contributor Covenant v1.3.0](https://www.contributor-covenant.org/version/1/3/0/).* 37 | 38 | [wg]: https://github.com/orgs/rust-secure-code/people 39 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Rust Secure Code Working Group [![Zulip Chat](https://img.shields.io/badge/zulip-join_chat-blue.svg?logo=zulipg)][#wg-secure-code Zulip stream] 2 | 3 | ![Hermit Ferris](https://avatars2.githubusercontent.com/u/44121472?s=230) 4 | 5 | This repository is the central [issue tracker] used by the Secure Code WG to 6 | coordinate efforts towards promoting secure code development in Rust. 7 | 8 | ## Mission 9 | 10 | Our mission is to make it easy to write secure code in Rust. 11 | 12 | We have the following goals for the Rust language and ecosystem: 13 | - Most tasks shouldn't require dangerous features such as `unsafe`. This includes FFI. 14 | - Mistakes in security code should be easily caught by machines or, failing 15 | that, humans aided by machines. 16 | - It should be clear to programmers how to perform security-sensitive tasks. 17 | - Security-critical code which is relied on by Rust programmers should be bug 18 | free. 19 | 20 | ## Projects 21 | 22 | - [cargo-audit]: Audit Rust projects for vulnerable dependencies sourced from the [RustSec Advisory Database][rustsec]. 23 | - [cargo-geiger]: Gather statistics on usage of unsafe code in a Rust crate and all its dependencies. 24 | - [cargo-supply-chain]: Gather author, contributor and publisher data on crates in your dependency graph. 25 | - [safety-dance]: Auditing crates for unsafe code which can be safely replaced. 26 | - We also maintain a [list of security-related projects][projects]. 27 | 28 | ## Contact 29 | 30 | - **Zulip**: Our official chat is the [#wg-secure-code Zulip stream]. 31 | - **Twitter**: Follow us at [@rustsecurecode]. 32 | 33 | [issue tracker]: https://github.com/rust-secure-code/wg/issues 34 | [cargo-audit]: https://github.com/rustsec/cargo-audit 35 | [cargo-geiger]: https://github.com/rust-secure-code/cargo-geiger 36 | [cargo-supply-chain]: https://github.com/rust-secure-code/cargo-supply-chain 37 | [safety-dance]: https://github.com/rust-secure-code/safety-dance 38 | [rustsec]: https://rustsec.org 39 | [projects]: https://github.com/rust-secure-code/projects 40 | [#wg-secure-code Zulip stream]: https://rust-lang.zulipchat.com/#narrow/stream/146229-wg-secure-code 41 | [@rustsecurecode]: https://twitter.com/rustsecurecode 42 | --------------------------------------------------------------------------------