--- title: T-spec meeting 2025-01-30 tags: ["T-spec", "meeting", "minutes"] date: 2025-01-30 discussion: https://rust-lang.zulipchat.com/#narrow/stream/399173-t-spec/topic/Meeting.202025-01-30 url: https://hackmd.io/-fNqhVhrRHWd35KDx5em2Q --- Attendees: - Joel Marcey - Pierre-Emmanuel Patry - Pietro - Mark - Eric Huss - TC - Niko Matsakis Regrets: - Mara Bos Agenda: - Review FLS Publish Project Goal - Spec Counterparts for Other Project Goals - Quick FLS update - Use `t-spec` Zulip channel to discuss Reference things? - T-Spec tagged GitHub Issues for Reference ## FLS Publish Project Goal https://github.com/rust-lang/rfcs/pull/3764#discussion_r1934568499 Do we have the right teams involved? Should `t-release` be an active participant and on the hook for work, particularly regarding tooling. Mark: If we are just publishing HTML pages, then release doesn't really need to be involved. Joel: What about any new tooling needing review that may be added to the project for this? Mark: If just HTML type stuff, then no. Pietro: What you do doesn't break the release process. It could be just `t-spec` and `t-bootstrap`. Niko: Would we just run script, generate HTML files and then publish those. Pietro: Two different parts - generate HTML files. Then a new x.py change is needed from `t-bootstrap` to put the files in the right directory. `t-bootstrap` would review whether the tooling is fundamentally incompatible with Project tooling. No expectation that would be the case. Pietro: The `t-spec` team is responsible for basically everything. Joel: Do we add `t-bootstrap` to the goal? Niko/Pietro: Yes, for standard reviews. But time commitment is not huge. Niko: The hope is to adopt the Ferrocene tooling with minimal changes. Is that realistic? Pietro: Yes Joel: I will make the changes. ## Spec Counterparts for Project Goals https://github.com/rust-lang/rust-project-goals/pull/238#issuecomment-2611220672 First draft: * https://rust-lang.github.io/rust-project-goals/2025h1/index.html#spec-team Joel to be point for restrictions ## Existing Reference work items nikomatsakis: GIVE ME A JOB https://github.com/rust-lang/reference/pulls https://github.com/rust-lang/reference/issues?q=label%3A%22T-spec%22+is%3Aopen * https://github.com/rust-lang/reference/pull/1693 * blocking stabilization of the related feature * changes in isolation are ok but inconsistent with surrounding text (they reference to the "asm block" but now there are "label blocks" so it introduces ambiguity) * disambiguate the 68 places where we say "block" * https://github.com/rust-lang/reference/pull/1699 * Joel can take a look at this one * See if there is anything that can be compared with the FLS too. * https://github.com/rust-lang/reference/pull/1725 * Niko will take this * https://github.com/rust-lang/reference/pull/1720 * Connor Horman looking at this one * https://rust-lang.zulipchat.com/#narrow/channel/399173-t-spec/topic/Reference.20update.20review.20process.20.2F.20target_feature.201.2E1.20PR * https://github.com/rust-lang/reference/pull/1689 * https://github.com/rust-lang/reference/pull/1622 ## Quick FLS Update Joel: Still working to establish a meeting with Ferrous to begin process for FLS integration to the Project, particularly getting the legal things out of the way. Trying to contact and coordinate calendars coordinated, but haven’t been able to match yet. Potential meet in person in mid-February. ## `t-spec` Zulip for Reference discussion? https://rust-lang.zulipchat.com/#narrow/channel/399173-t-spec/topic/Reference.20update.20review.20process.20.2F.20target_feature.201.2E1.20PR Yes, `t-spec` Zulip is a fine place for this. ## Chat https://hackmd.io/-fNqhVhrRHWd35KDx5em2Q 8:03 Mark Mark says:I'll hang around for a bit 😃 8:14 avatar Niko Matsakis Niko Matsakis says::dance: 8:14 Niko Matsakis says: https://rust-lang.github.io/rust-project-goals/2025h1/index.html#spec-team 8:15 Mark Mark says:need to drop, thanks all 8:28 Niko Matsakis Niko Matsakis says:"no prelude" 8:35 Pietro Pietro says:need to drop as well, 👋 8:48