You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -20,24 +20,32 @@ The target audience here will be those that have a vested interest in Rust speci
20
20
21
21
Keeping up with documentation is not always the most glamorous role for any project. And folks like @ehuss and others are doing an outstanding job at trying to keep the Reference current with actual code behavior. This is a hard job just for one document like the Reference. It will be even more difficult adding another core document like the FLS. But that doesn't necessarily mean we can't keep the FLS as up to date as is needed by its users.
22
22
23
+
### Solicitation of stakeholder involvement
24
+
25
+
The FLS is an enabler document for safety qualifying versions of the Rust compiler. The safety-critical community of Rust users actively and passively benefits from the FLS.
26
+
27
+
Active users of the FLS should be consulted on changes with a "do no harm" approach taken to ensure the capability to use the FLS for safety qualification of the Rust compiler is not disrupted. Active users consulted and contributing to maintenance will ensure the ability to achieve safety qualification from an assessor.
28
+
29
+
Passive beneficiaries of the FLS include those entities that themselves do not safety qualify a compiler, but instead because the FLS exists and can be used for that purpose, grows the safety-critical set of users of Rust. Examples of passive beneficiaries include: tool vendors, library vendors, and integrators. Those passive beneficiaries becoming involved with maintenance and enrichment of the FLS supports the capability to have safety-qualified Rust compilers. Safety-qualified Rust compilers is a prerequisite for certain levels of safety-criticality in certain industries. These passive beneficiaries contributing back to the ability to ship safety-critical Rust software is a healthy model to ensure continuity of FLS maintenance.
30
+
23
31
### The next 6 months
24
32
25
-
Explore options for developing the capability to keep the FLS updated with the Rust language, in a sustainable way, at the cadence needed by its users.
33
+
Explore options for developing the capability to keep the FLS updated with the Rust language, in a sustainable way, at the cadence needed by its users and stakeholders.
26
34
27
35
The outcome of the next six months is variable. The entire six months could be investigative, with some prototyping. Or we could establish a concrete cadence and capacity for updating the FLS.
28
36
29
37
### The "shiny future" we are working towards
30
38
31
-
The shiny future we are working towards is to ensure that we have the capability in place to keep the FLS updated at the pace needed by its users.
39
+
The shiny future we are working towards is to ensure that we have the capability in place to keep the FLS updated at the pace needed by its users and stakeholders.
32
40
33
41
## Ownership and team asks
34
42
35
-
**Owner:**@JoelMarcey, in his capacity of `t-spec` team member will lead this project goal.
43
+
**Owner:**@PLeVasseurwill champion this project goal.
| Discussion and moral support |![Team][][spec], [lang]||
40
-
| Adjust tooling, as needed |@JoelMarcey|Joel to find appropriate person |
48
+
| Adjust tooling, as needed |@PLeVasseur|Pete to find appropriate person |
41
49
| Standard reviews |![Team][][lang],[opsem], [types], [bootstrap]| For any process changes, document updates and/or tooling integration |
42
50
| Continued updates for the FLS | Contributors from Ferrous Systems and others TBD ||
43
51
| Review of updates to the FLS |`t-spec` and contributors from Ferrous Systems ||
@@ -46,16 +54,18 @@ The shiny future we are working towards is to ensure that we have the capability
46
54
47
55
### Why this Project goal?
48
56
49
-
The goal is to ensure the FLS is updated sufficiently to meet the needs of its users.
57
+
The goal is to ensure the FLS is updated sufficiently to meet the needs of its users and stakeholders.
50
58
51
59
### Can this be done in six months?
52
60
53
-
Don't know. But we need to start having the conversations and see where it can lead.
61
+
Don't know. But we need to start having the conversations with stakeholders and see where it can lead.
54
62
55
63
### Getting documentation updated is hard. Who would do that work?
56
64
57
65
This may be the biggest blocker to making this goal successful. Part of this goal will be finding people who are interested in doing the work to author and review these updates or to find the budget to hire people to do this.
58
66
67
+
The safety-critical Rust community actively and passively benefits from the FLS, so it's worthwhile to solicit engagement with the Safety-Critical Rust Consortium.
68
+
59
69
### What happens if the FLS and Reference combine as one specification document?
60
70
61
71
That's actually a potential outcome of the `t-spec` work in the future. So this may not be totally theoretical. Hopefully the processes we come up with are not so document specific and they can withstand such a merger.
0 commit comments