Skip to content

Latest commit

 

History

History
86 lines (51 loc) · 4.65 KB

File metadata and controls

86 lines (51 loc) · 4.65 KB

SAFETY CRITICAL RUST CONSORTIUM

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. See the full announcement.

The primary objective of this group is 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.

Consortium Membership

Membership to the Safety Critical Rust Consortium is free. To submit your membership application open a GitHub issue.

Note: When you file the issue for membership, the name, email address and any company you provide will be public as GitHub issues are inherently public. We do not use your information for any reason other than membership purposes.

If for some reason you are unable or unwilling to file a GitHub issue to apply for membership, 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.

Subcommittee Membership

The Safety Critical Rust Consortium has subcommittees that focuses on specific areas of work:

After you join the consortium, you can apply 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 whether to be an observer or a producer.

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.

Meeting Policies

We have agreed consortium-wide to follow some meeting policies. The intent is to allow participants to feel comfortable with being candid and foster open collaboration.

Chatham House Rule

We follow Chatham House Rule which essentially means:

Its guiding spirit is: share the information you receive, but do not reveal the identity of who said it.

No recordings, no transcriptions

Following somewhat from above in following Chatham House Rule, we prohibit taking screen or voice recordings. We also disallow any other means of taking transcriptions, such as AI bots.

Notetaker Role

Thank you for taking this role!

Please reference this doc for more details.

Contributing to This Repository

See CONTRIBUTING.md.

Licenses

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.

Privacy Policy

Read the consortium's privacy policy.

Other Policies

Read other Rust Foundation policies.