---
title: "Lang meetup 2024 agenda"
tags: ["T-lang", "meetup-2024"]
date: 2024-09-09
url: https://hackmd.io/SmUPhLlrSwORwuheeIDQDA
---

# Lang Meetup 2024 Agenda

## Schedule

(Copied from: https://docs.google.com/spreadsheets/d/1pmVGLgD5smizBfRxdvyuu5-WWmiq5i4ooJ4EW1QeLWU/edit)

### For Monday

| Time | Monday |
|-------------|-----------------------|
| 08:45-09:30 | Breakfast 13th floor |
| 09:30-09:35 | Welcome and logistics |
| 09:35-10:35 | Design goals |
| 10:35-10:45 | Break |
| 10:45-11:45 | Use cases |
| 11:45-12:30 | Lunch 13th floor |
| 12:30-14:00 | Long-standing issues |
| 14:00-14:10 | Break |
| 14:10-15:40 | Vibe checks |
| 15:40-15:50 | Break |
| 15:50-16:00 | Unconf voting |
| 16:00-17:00 | Unconference #1 |
| 17:00-17:30 | Group photo |
| 17:30-18:00 | Overflow |
| 19:30-?? | Board game? |

### For Tuesday

| Time | Tuesday |
|-------------|-----------------------|
| 08:45-09:30 | Breakfast 13th floor |
| 09:30-11:00 | Big goals |
| 11:00-11:15 | Break |
| 11:15-12:00 | Medium goals |
| 12:00-13:00 | Lunch 13th floor |
| 13:00-14:00 | Dealing with concerns |
| 14:00-14:15 | Unconf voting |
| 14:15-14:30 | Break |
| 14:30-15:30 | Unconference |
| 15:30-16:30 | Unconference |
| 16:30-17:30 | Unconference |
| 19:00-?? | Team dinner |

## Meta

Time-bound all items, do explicit time checks and make explicit decisions to continue or move on; otherwise, nerdsniping, bikeshedding, and other attractors will likely make a small number of items consume the entire time.

Aim to produce artifacts that represent a fixed point of lang team consensus, prior to feedback from outside the team.

Nominate a notes taker before each session.

## Sessions

### Design goals

Time: 60 minutes

Abstract: Rust needs a language for how to design a language. Some words and phrases have emerged over time, but they can mean different things to different people.

**Preparation: Bring notes on what you think makes Rust an effective programming language – and how it can be more effective.** We'll read through one another's notes and Tyler will share the draft he's been iterating on.

Artifact: A preliminary set of well-understood pithy phrases that capture the essence of what Rust strives to be, a great programming language. We will try these phrases out throughout the rest of the summit and revisit them at the end.

[Meetup 2024: Rust Design Goals](/3OAt4g4USDy3sl658OzoXg)

### Use cases

Time: 60 minutes

Abstract: Let's talk about the most important use cases for Rust, now and in the future, and highlight some unique needs of each.

**Preparation: Members are invited to bring examples from their own experience and projects/companies.** Tyler is preparing a high level list so we don't forget about important ones.

Artifact: A list of important, emerging, and notable use cases. Include what we know and what we don't know about the support each of the important and emerging ones needs. Examples: Web services, CLI tools, Kernels and hypervisors, Embedded.

[Meetup 2024: Rust Use Cases](/lsWQnwGCT1qP8pvBDka8gA)

### Long-standing issues

Time: 90 minutes

Abstract: Discuss some of the biggest problems that have dogged Rustaceans since the beginning of time, and what it would take to solve them. We'll hold open the possibility of multiple directions, noting our individual preferences but not hashing them out here (those can happen in unconference sessions or future design meetings).

**Preparation: Make a list of items you'd like to discuss.**

[Meetup 2024: Problems and Designs](/jD1Pmf6wQZGVWd6VOxooEw)

### Vibe checks

Time: 90 minutes

Abstract: Bring 1-2 Rust bucket list items and get reactions from the team. Come prepared with a 1-2 paragraph description that states the problem and rough solution as clearly as you can (short code samples are encouraged). Soft time limit of 6 minutes, hard time limit of 12 minutes per item (depending on how many we have to get through).

**Preparation: Make a list of items you'd like to discuss.**

Artifact: List of ideas, vote counts, and concerns. New discussion topics.

[Meetup 2024: Problems and Designs](/jD1Pmf6wQZGVWd6VOxooEw)

### Handling concerns

Time: 60 minutes

Abstract: How can we continue to make good decisions in the face of uncertainty and disagreement within the team? Quality is important, but so is speed and steady progress. Rust is not alone in the space of C/C++ successors, and many of those are able to iterate more quickly – even C++ has added async/await and coroutines.

Artifact: A list of process changes.

Notes: [Meetup 2024: Handling concerns](/M1J97zPIS1-ip8OKMDfQEw)

### Big goals (next 3-6 years)

Time: 60 minutes

Abstract: What are the big problems we hope to tackle over the next 3-6 years in Rust?

Preparation: TODO

Artifact: A list of 7 goals we think are worthy of the title "big goal".

[Meetup 2024: Strategic Goals](/qIlGycAQQEabV08R6JHeiQ)

### Medium-term goals (next 18 months)

Time: 45 minutes

Abstract: What do we think the project should be focused on in 2025?

Preparation: TODO

Artifact: A set of 3-5 likely flagship goals and 5-10 likely team goals.

[Meetup 2024: Strategic Goals](/qIlGycAQQEabV08R6JHeiQ)

### Short-term goals (24 H2)

Time: Unconf sessions for each (see below)

Abstract: What is needed to unblock our current project goals?

Preparation: TODO

Artifact: Decision trees, notes about progress made, and next steps for each.

[Meetup 2024: Unconference Topics](/UO7F1gkCT--ah8pUknQRsg)

### Unconference

Time: 60 minute slots

**Preparation: Brainstorm any topics you would like to discuss.** Additional topics will come up during the discussion.

We'll have sticky notes and vote on more topics.

[Meetup 2024: Unconference Topics](/UO7F1gkCT--ah8pUknQRsg)

Unconference topics:

- [Expanding dyn-capability](/l_EJFwlsT8KojFQIY-HoOQ)
- [Effects and associated effects](https://hackmd.io/Oc8QQ8yGRcKvkicLh7kisg)
- [Linear types](/W50y43HnRQifRNeoGcVUag)