In June 2024, the Rust Foundation, AdaCore, Arm, Ferrous Systems, HighTec EDV-Systeme GmbH, Lynx Software Technologies, OxidOS, TECHFUND, TrustInSoft, Veecle, and Woven by Toyota jointly announced the Safety-Critical Rust Consortium. The primary objective of this group will be to support the responsible use of the Rust programming language in safety-critical software — systems whose failure can impact human life or cause severe environmental or property harm.
See the full announcement here.
Membership to the Safety Critical Rust Consortium is free. Please file this GitHub issue to submit your membership application.
If for some reason you are unable or willing to file the application for membership via a GitHub issue, please send an email to safety-critical-rust-consortium-contact [at] rustfoundation [dot] org.
Whether you become a member or not, you can join the consortium's public Zulip channel to keep up with various happenings.
The Safety Critical Rust Consortium has subcommittees that focuses on specific areas of work.
Right now there are two subcommittees:
After you join the consortium, you can apply by filing a GitHub issue to be a member of one or more of the subcommittees as well.
Note: If you are an observer of the consortium, you will be an observer in the subcommittee. If you are a producer of the consortium, you can choose
The Rust Foundation has adopted a Code of Conduct that we expect project participants to adhere to. Please read the full text so that you can understand what actions will and will not be tolerated.
See CONTRIBUTING.md.
Rust is primarily distributed under the terms of both the MIT license and the Apache License (Version 2.0), with documentation portions covered by the Creative Commons Attribution 4.0 International license..
See LICENSE-APACHE, LICENSE-MIT, LICENSE-documentation, and COPYRIGHT for details.
You can also read more under the Foundation's intellectual property policy.
You can read about other Rust Foundation policies in the footer of the Foundation website.