Audience

EuroRust is a general-purpose Rust conference. We attract a heterogenous crowd:

• Professionals using Rust in their daily job
• Maintainers and contributors to Rust’s open-source ecosystem
• Developers who are curious about Rust, or just getting started

Talk formats

The conference will feature three types of talks: general-purpose, deep-dives and tutorials. You must choose one of the three formats when submitting your proposals. We will contact you if we believe your submission is better suited for another format.

Talks will be divided into two tracks: a main stage and a side stage. The conference committee will allocate talks to either stage based on the estimated size of the audience.

General-purpose talks

General-purpose talks should be appealing and comprehensible to most conference attendees. We’re open to a wide range of topics for general-purpose talks, including but not limited to:

• Rust patterns, anti-patterns and idioms
• Case studies on both industrial and hobbyist projects
• Domain-specific talks (backend, WASM, embedded, system programming, etc.), with minimal prerequisites
• A review of the state-of-the-art in a specific area
• A status report on an ongoing Rust project (or Rust ecosystem) initiative

Deep-dives

For the deep dives, you can assume that the audience is intermediately familiar with the domain or ecosystem you’re working with. For example, suppose you’re submitting an embedded talk. In that case, it’s reasonable to assume that the listener has written embedded code before (perhaps in Rust, perhaps in a different language) and they’re aware of the key Rust crates for building embedded projects (e.g. embassy).

We’re open to a wide selection of topics along the same vein as the general purpose format. Nonetheless, we’d be particularly pleased to see submissions in these areas:

• Using Rust for data processing, ML training and/or inference
• Using Rust in an industrial embedded project
• Using Rust for backend or GUI development
• Embedding Rust code in a larger codebase written in another language (or vice-versa)
• A deep dive into a certain language feature or the internals of a popular crate
• Using Rust to write kernel drivers (or of a full-blown operating system!)

Tutorials

Tutorials should teach attendees how to accomplish a specific task or use a tool/crate effectively. These talks should be practical and focused on delivering actionable knowledge. Attendees should leave your tutorial with the confidence (and the curiosity!) to apply the demonstrated skills or techniques in their work.

Some ideas for tutorial topics include (but are not limited to):

• Step-by-step guidance on using popular crates, or crates that should be popular but aren’t yet!
• Practical workflows for debugging, refactoring or profiling Rust code
• Getting started with writing Rust-based libraries, applications or tools for a specific domain (e.g., CLI tools, web APIs, desktop applications, etc.)
• Integrating Rust with another language

How we review proposals

The first round of proposal reviews is anonymous. Proposals are de-anynomized for the second round of reviews.

Don’t put any information that reveals your identity in the proposal (except for the speaker bio field, which reviewers won’t see during the first round of reviews). For example, if you need to mention your company in the final title or abstract, use [COMPANY] as a replacement.

Expense policy

EuroRust will cover up to 800€ in travel expenses. Expenses are reimbursed against receipts after the event. If you don’t need support covering travel expenses, please let us know when registering for your ticket (a link will be sent out after your talk is accepted).

We’re also happy to offer sponsorship credits for employers that cover their employee’s travel costs. In these cases, we offer a free Supporter sponsorship (minus the included passes) or a 2000€ discount towards any other sponsorship packages.