---
title: "Analysis of T-lang triage meeting pace YTD 2025"
author: TC
date: 2025-05-02
url: https://hackmd.io/AXiJHnLkTZOTSeB7YVRXAw
---

# Analysis of T-lang triage meeting pace YTD 2025

This is a manual collection of some statistics on recent T-lang triage meetings as derived from the minutes for each, the related issues and PRs, and my recollections. The numbers are how many nominated items we covered and what the outcome was for each.

Overall, by my count, in the first four months of the year, we developed 81 consensuses on nominated items, and we took about 17 minutes on average per consensus.

Our outlier meetings on the high end were:

- The 2025-01-08 meeting, where we developed 6 consensuses in 60 minutes.
- The 2025-04-16 meeting, where we developed 12 consensuses in 150 minutes.

In general, for each 60 minute meeting, we tended to develop 4-5 consensuses (along with 1-2 items on which we identified next steps) unless there was a notable item that ate a substantial part of the meeting. The three most notable such items were:

- One where we'd scheduled a discussion to read through a document and give general feedback on a project goal.
- One where we'd already accepted the stabilization and were on the clock to decide about a revert.
- One where we were discussing potential process improvements related to an earlier stabilization we had to revert.

The 150 minute meetings, I think, tended to drag down our average rate, as one would expect, as we knew we had more time, and so were more willing to engage to dive more deeply on a topic.

But, of course, in diving more deeply, we managed to resolve some harder longstanding items that we'd been deferring for some time.

(And this had been our plan for such meetings; we called them "deep dives".)

## 2025-04-30

This was a 150 hour triage meeting with all members present for the first 60 minutes and 4 members present for the remainder.

- 7 with consensus.
- 2 had also been discussed in the prior week but with fewer members.
- 1 consensus came apart in later async discussion.
- 1 next steps identified.
- This item had been discussed the prior week also.

## 2025-04-23

This was a 120 hour triage meeting with 3 members present.

(We took up 30 minutes of the second meeting doing a mini-design meeting on C/C++ interop since we had people show up for our canceled meeting on this.)

- 8 with consensus.
- 1 consensus came apart in later async discussion.

## 2025-04-16

This was a 150 hour triage meeting with all members present.

- 12 with consensus.
- 1 blocking concern was raised afterward.
- 1 without consensus; design meeting proposed.
- 1 next steps identified.

## 2025-04-09

This was a 150 hour triage meeting with 3 members present.

- 7 with consensus.
- 2 passed over due to ongoing async discussion or missing members.
- 1 next steps identified.

## 2025-04-02

This was a 130 hour triage meeting with 4 members present.

(We spent about 20 minutes talking about the all hands.)

- 4 with consensus.
- 1 next steps identified.

## 2025-03-26

This was a 150 hour triage meeting with 4 members present.

The plan in the second 90 minutes was to focus on moving forward stall stabilizations.

- 5 with consensus.
- One of these took an hour. We came to a consensus, but it later came apart in further discussion, and we ended up reverting to an earlier consensus.
- Another of these was a multi-year-long bikeshed that we did resolve with finality in the meeting.

## 2025-03-19

This was a 60 minute triage meeting with all members present.

- 5 with consensus.
- 1 consensus came apart in later discussion, we formed a new consensus later, and then we ended up reverting back to this one.

## 2025-03-12

This was a 60 minute triage meeting with 3 members present.

(From this, we may have burned 12 minutes or so talking about the 2025 edition, as I recall.)

- 4 with consensus.
- 2 next steps identified.

## 2025-03-05

This was a 30 minute triage meeting with 4 members present.

(About 30 minutes was taken to discuss one planned item where general feedback was sought; that was provided.)

- 1 next steps identified.
- 1 without consensus.

## 2025-02-26

This was a 60 minute triage meeting with 4 members present.

- 5 with consensus.
- 1 with next steps.

## 2025-02-19

This was a 60 minute triage meeting with all members present.

- 4 with consensus.
- 1 with next steps.

## 2025-02-12

This was a 25 minute triage meeting with all members present.

(We spent about 35 minutes discussing potential process failures related to an earlier stabilization we had ended up reverting.)

- 1 with consensus.
- 1 without consensus.

## 2025-02-05

This was a 60 minute triage meeting with 3 members present.

- 7 with consensus.

## 2025-01-29

This was a 60 minute triage meeting with 4 members present.

- 1 with consensus.
- 2 with next steps.
- One was a long discussion but we were on the clock as we had already accepted the stabilization.

## 2025-01-22

This was scheduled as a 150 minute triage meeting, but was canceled.

## 2025-01-15

This was a 60 minute triage meeting with 4 members present.

- 5 with consensus.

## 2025-01-08

This was a 60 minute triage meeting with all members present (eventually).

- 6 with consensus.