# Types roadmap EOY 2024

Earlier this year, [we announced](https://blog.rust-lang.org/2023/01/20/types-announcement.html) the types team, our long-term expectations for the team, and a roadmap for 2023 and beyond. Last month, the team had our second in-person meetup and we'll share in this post an overview of that meeting and our plans for 2024.

## Meetup recap

## Discussions on team and Project organization

The first set of topics that we discussed in the meetup were all organizational in nature. To begin, we reviewed the roadmap proposed from the last meetup. All in all, without going into specifics, we felt that we weren't *too* far off our roadmap for 2023, but we were maybe a little *too* ambitious, which shows in our 2024 and 2027 goals. But, more on this later.

We also discussed a bit on the team itself - specifically overall team processes. Overall, we felt that team organization has been decent. However, we did discuss that our current planning meetings (which currently occur the first Monday of every month) can use some improvement. Namely, we'd like to see some better automation for tracking roadmap and initiative statuses, and for generating the planning meeting agenda. We're currently working on this. Aside from that, we noticed that the original types team RFC has "operational semantics" and const-eval under T-types purview, but this has since been split into [its own team](https://rust-lang.github.io/rfcs/3346-t-opsem.html).

Finally, we discussed the feature stabilization process, which extends beyond just the types team. We noted that the current stabilization process - particularly the *stabilization* part of the process - can sometimes let things slip through the cracks or be incomplete. To help alleviate these situations, we explored defining a "template" for stabilization, which has sections for each potential team, which checkboxes to ensure input isn't missed. We expect to open an RFC for this in the near future.