---
# System prepended metadata

title: '`t-content` RustConf 2025 - Plans'
tags: [event, rustconf]

---

# `t-content` RustConf 2025 - Plans

## Goals for content produced

This is our first outing as a team. It's good to be focused and realistic with what we can accomplish. Happy to hear feedback on the below.

### Video interviews - long-form

Target: 3 or so long-form (30 minutes to an hour) that can be put on YouTube.

More are welcome of course!

#### Wednesday Interview Room (609 - Yakima) Slots

| Interviewee     | Interviewer    | Time Slot   |
|-----------------|----------------|-------------|
| Setting up      | Setting up     | 8am - 9am   |
|                 |                | 9am - 10am  |
| Tyler Mandry    | Pete LeVasseur | 10am - 11am |
|                 |                | 11am - 12pm |
| Taylor Cramer   | Pete LeVasseur | 1pm - 2pm   |
| Pete LeVasseur  | Tyler Mandry   | 2pm - 3pm   |
| Niko Matsakis & Jack Huey  | Pete Levasseur | 3pm - 4pm   |
| Yuri Astrakhan  | Xander Cesari  | 4pm - 5pm   |

#### Thursday Interviews

7th floor - coat room corner

| Interviewee        | Interviewer    | Time Slot   |
|--------------------|----------------|-------------|
| Setting up         | Setting up     | 8am - 9am   |
|                    |                | 9am - 10am  |
| Nicholas R Smith   | Tyler Mandry   | 10am - 11am |
| Christian Legnitto | Pete LeVasseur | 11am - 12pm |
| Darko Mesaros      | Pete LeVasseur | 1pm - 2pm   |
| Bart Massey        | Pete LeVasseur | 2pm - 3pm   |
| Nathaniel Simard   | Pete LeVasseur | 3pm - 4pm   |
|                    |                | 4pm - 5pm   |


#### Tyler Mandry

* Intake answers: [link](https://hackmd.io/@rust-content-team/r1FTCtXqxe/edit)
* Outline: [link](https://hackmd.io/@rust-content-team/SJzagcX9gl/edit)
* Date: 2025-09-03
* Interviewee: Pete LeVasseur
* Domain / topic: C++ / Rust interop

#### Taylor Cramer

* Intake answers: [link](https://hackmd.io/@rust-content-team/rJLH19Xqel/edit)
* Outline: [link](https://hackmd.io/@rust-content-team/BkueWcmqge/edit)
* Date: 2025-09-03
* Interviewee: Pete LeVasseur
* Domain: C++ / Rust interop

#### Yuri Astrakhan

* Intake answers: [link](https://hackmd.io/@rust-content-team/S1mWJ9Xcgx/edit)
* Outline: [link](https://hackmd.io/@rust-content-team/rkiQntQqex/edit)
* Date: 2025-09-02 or 2025-09-03
* Interviewee: Pete LeVasseur
* Domain: Automotive, scaling Rust teams, interop with existing code

#### Pete LeVasseur

* Intake answers: [link](https://hackmd.io/@rust-content-team/S1RvRKXcxl/edit)
* Outline: [link](https://hackmd.io/@rust-content-team/SkoQ-97ceg/edit)
* Date: 2025-09-03
* Interviewee: Tyler Mandry
* Domain: Automotive, safety-critical software

### "Shorts-style" run and gun video interviews

We can have some run and gun video interviews done that we extract some insightful material from.

Target: 10 or so "shorts-style" videos of 30 seconds - 1 minute that can be shared on social media and put on YouTube.

### Audio-only interviews

We'd prefer to have video interviews since we have the equipment, but some may fall in this bucket based on interviewee preference.

Therefore no explicit target.

### Text interviews

These can be nice if we have only 10-15 minutes to chat with someone or are sensing a theme we can pull together. Can be less scheduled and more impromptu.

Make use of audio recorder on phone or otherwise to make sure captured correctly while on the move.

These can be grouped together into a single article or broken out, depending on topics gathered.

Target: 5-10 shorter text interviews.

## Audio-visual equipment (Xander/pinkhatbeard)

| Gear | Source | Notes |
| -------- | -------- | -------- |
| Sony A7Cii (camera)     | Xander     | Fine primary body     |
| Lenses | Xander | I have a nice selection but a 24-50mm f2.8 should be a good fit for most shots |
| Rode Wireless Pro set | Xander | w Lav mics and handheld holder |
| Tripod and accessories | Xander | Variable ND filter etc |
| Second camera body | Rental | For a two angle interview setup |
| Hot lights + stands | Rental | For better lighting options |
| HDMI Video Recorder | Xander | For slide decks/presentations |

### Setups

#### Recorded Talk
This should be very attainable with what Xander owns, but possibly unnecessary since all official talks are being recorded. If the Unconf has anything resembling a talk we might have to use it.

#### Simple Two Person Interview
The simplest version of a two person interview would be a single camera shooting wide in 4k, cropping to each participant for back-and-forth, and exporting in 1080p. We would use ambient lighting and whatcha get is whatcha get. Xander owns all gear required to achieve this.

#### Upgraded Two Person Interview
If we wanted to boost production quality we would rent a second body, shoot two over-the-shoulder angles, and add some hot lighting.

#### Run and Gun
If we were shooting on the move around the conference we could do something similar to the simple two person interview but with the participants standing, news interview style.

## Handful of questions askable to anyone (Pete drafted, feedback welcome)

Use the questions in [this doc](https://hackmd.io/@plevasseur/rk7MSsqtle/edit) as a starting point

Answers given by interviewee are a springboard to be able to ask more nuanced questions

## A basic release form

todo(pinkhatbeard): 
- Slot in the release form.
- The release form must have a checkbox on whether the interviewee or their company must review the interview prior to publish.
- Ensure it's got a spot for contact information.
- Ensure that it's got a section on biased language (see below)
    - "Avoid using biased language including language with a racial, ethnic, group, or gender bias or language that is stereotypical."
## `t-content` Team: Interview Guidelines

Here's a [link](https://hackmd.io/@plevasseur/Hyz6MHiYxe/edit) to the document I drafted (this will stay internal to the team).

Happy for any feedback.

## Announcement to public `t-content` channel (Pete to draft)

TODO(Pete): Insert link to draft doc

## Lined up interviewees ahead of time

No pressure to do so!

But -- if you know of folks that will be at RustConf and can line them up for an interview ahead of time that'd probably be most efficient for the bulk of our first outing.

A quick example of what this may look like:

#### Interviewee Name
  * Interviewee contact info
    * email
    * phone number?
  * Availability:
    * foo
  * Interviewer (assumed self unless otherwise so-stated)
  * Primary domain / topic

### Pete

#### Availability

Tuesday:
* Limited by participation in C++/Rust interop room
* May be able to duck out here or there as needed

Wednesday:
* Available 8am - 5pm
* Attempting to be flexible / available most of the day, given we have the room for long-form interviews

Thursday:
* 10am - 11:30am
* 1pm - 2:30pm

Friday:
* unavailable, left the venue

#### Interviewees

##### Taylor Cramer

* cramertj@google.com
* Availability:
  * Wednesday: Available aside from 4pm-5pm
  * Thursday: Available aside from 3pm-4:30pm
* Interviewer: Pete/?
* Primary domain: C++/Rust Interop

##### Tyler Mandry

* tmandry@google.com
* Availability:
  * Wednesday: Available aside from marquee/keynotes, i.e.
    * Open 10am-4:15pm
  * Thursday: Available aside from 2:30pm-4:30pm
* Interviewer: Pete/?
* Primary domain: C++/Rust Interop

##### Yuri Astrakhan

* yuriastrakhan@gmail.com
* Availability:
  * Tuesday: Available approximately 2-5pm
* Interviewer: Pete/?
* Primary domain: Rust + Automotive

### Xander

* 

### pinkhatbeard

* 

### Lori

* Emailed Niko (also asked him about Jack Huey)

**Availability:**
Tuesday: 
* Anytime 

Wednesday
* 9:00 - 11:30 am
* 3:30 - 5:00 pm

Thursday
* 9:00 - 11:00 am
* 1:00 - 2:00 pm
* 3:00 - 5:00 pm
### TC



### tmandry

#### Nicholas R. Smith

* Primary domain: Rust adoption in C/C++ codebase (interop)