|
1 | 1 | # SAFETY CRITICAL RUST CONSORTIUM |
2 | 2 |
|
3 | | -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. |
| 3 | +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](https://foundation.rust-lang.org/news/announcing-the-safety-critical-rust-consortium/). |
4 | 4 |
|
5 | | -See the full announcement [here](https://foundation.rust-lang.org/news/announcing-the-safety-critical-rust-consortium/). |
| 5 | +> 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. |
6 | 6 |
|
7 | 7 | ## Consortium Membership |
8 | 8 |
|
9 | | -Membership to the Safety Critical Rust Consortium is free. Please [file this GitHub issue](https://github.com/rustfoundation/safety-critical-rust-consortium/issues/new?assignees=joelmarcey&labels=membership%2Cstatus%3A+needs+review&projects=&template=membership.yml) to submit your membership application. |
| 9 | +Membership to the Safety Critical Rust Consortium is free. To submit your membership application [open a GitHub issue](https://github.com/rustfoundation/safety-critical-rust-consortium/issues/new?assignees=joelmarcey&labels=membership%2Cstatus%3A+needs+review&projects=&template=membership.yml). |
10 | 10 |
|
11 | 11 | > 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. |
12 | 12 |
|
13 | | -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`. |
| 13 | +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`. |
14 | 14 |
|
15 | 15 | Whether you become a member or not, you can join the consortium's [public Zulip channel](https://rust-lang.zulipchat.com/#narrow/channel/445688-safety-critical-consortium) to keep up with various happenings. |
16 | 16 |
|
17 | 17 | ### Subcommittee Membership |
18 | 18 |
|
19 | | -The Safety Critical Rust Consortium has subcommittees that focuses on specific areas of work. |
| 19 | +The Safety Critical Rust Consortium has subcommittees that focuses on specific areas of work: |
20 | 20 |
|
21 | | -Here are the subcommittees: |
| 21 | +- [Coding Guidelines](https://github.com/rustfoundation/safety-critical-rust-consortium/tree/main/subcommittee/coding-guidelines) |
| 22 | +- [Tooling](https://github.com/rustfoundation/safety-critical-rust-consortium/tree/main/subcommittee/tooling) |
| 23 | +- [Liaison](https://github.com/rustfoundation/safety-critical-rust-consortium/tree/main/subcommittee/liaison) |
22 | 24 |
|
23 | | -1. [Coding Guidelines](https://github.com/rustfoundation/safety-critical-rust-consortium/tree/main/subcommittee/coding-guidelines) |
24 | | -2. [Tooling](https://github.com/rustfoundation/safety-critical-rust-consortium/tree/main/subcommittee/tooling) |
25 | | -3. [Liaison](https://github.com/rustfoundation/safety-critical-rust-consortium/tree/main/subcommittee/liaison) |
| 25 | +After you join the consortium, you can [apply to be a member of one or more of the subcommittees](https://github.com/rustfoundation/safety-critical-rust-consortium/issues/new?assignees=joelmarcey%2C+PLeVasseur%2C+alexandruradovici&labels=subcommittee+application&projects=&template=subcommittees.yml&title=Subcommittee+Join+Request+for+%5BNAME%5D) as well. |
26 | 26 |
|
27 | | -After you join the consortium, you can [apply by filing a GitHub issue](https://github.com/rustfoundation/safety-critical-rust-consortium/issues/new?assignees=joelmarcey%2C+PLeVasseur%2C+alexandruradovici&labels=subcommittee+application&projects=&template=subcommittees.yml&title=Subcommittee+Join+Request+for+%5BNAME%5D) to be a member of one or more of the subcommittees as well. |
28 | | - |
29 | | -*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* |
| 27 | +*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.* |
30 | 28 |
|
31 | 29 | ## [Code of Conduct][code-of-conduct] |
32 | 30 |
|
|
0 commit comments