---
# System prepended metadata

title: T-spec meeting 2024-06-13
tags: [T-spec, minutes, meeting]

---

---
title: T-spec meeting 2024-06-13
tags: ["T-spec", "meeting", "minutes"]
date: 2024-06-13
discussion: https://rust-lang.zulipchat.com/#narrow/stream/399173-t-spec/topic/Meeting.202024-06-13
url: https://hackmd.io/xNuaCGOyT82mVzL6dQi4Gw
---

## Attendees

- People: TC, ehuss, Mara, pnkfelix, Lukas Wirth, Connor Horman, carbotanium, Pietro, Pierre-Emmanuel Patry

## Meeting rules

- Minutes, driver: TC

## Go forward plan

TC: Go forward plan:

1. Adopt the Rust Reference today.
   - Keep in our back pocket adopting the FLS in parallel as e.g. the "Rust Safety-Critical Specification", but don't do that today.  If we later did that:
      - Ferrous Systems would promise to keep the Rust Safety-Critical Specification up to date.
      - The project itself would maintain its current processes; only the Reference would be updated by contributors when stabilizing new features in Rust.
2. Reformat one chapter of the Reference ourselves, using the mdbook extension Eric drafted based on Mara's proposed layout.
    - Connor: Will take the action item to reformat: <https://doc.rust-lang.org/stable/reference/inline-assembly.html>
3. Ask the Foundation to hire a technical writer to churn through the *other* 114 chapters or so and made the same transformation.
4. Expand the coverage of the Reference, in terms of the subjects on which the FLS has some coverage but the Reference doesn't, by adopting the content from the FLS into the Reference.
   - In general, narrowing the distance between the Reference and the FLS, starting from the Reference.
5. Work toward associating the tests in the Rust repository with chapters in the Reference.
   - Reuse the FLS annotations as much as possible.
   - Explore adding a separate test suite for the Reference.
6. Leave as an open question the plan for rearranging the chapter layout.
7. Leave as an open question the plan for setting out the timeline for the milestones we want to hit and the metrics for success.

Mara had to leave early, but was generally in favor of this plan and moving forward, as long as Joel is happy with it.

Eric Huss, pnkfelix, and TC are +1 on the plan as described above.

Pietro is concerned it will take us longer than we might hope to achieve the goals of the plan, in terms of having a document that meets the criteria needed for the safety-critical community, but hopes to be wrong about that.  He sees the plan to keep adopting the FLS as the Rust Safety-Critical Specification in our back pocket and to reevaluate this later as reasonable.

Connor is concerned that the chapter layout may not work for us long term and may require us to redo work later.

## Next meeting

We'll plan to discuss in the next meeting(s):

- What concrete steps we need to take to execute that plan.
- The standards of review for Reference inclusion.
- The open items above.
