Let's
hear it!

Format for the conference

The conference is a single-track event, but there's an important difference. Delegates will be strongly encouraged to leave the room if there are sessions that they're not interested in. We're genuine when we mean that the "hallway track" is a main track.

Make use of the networking opportunities through the social spaces and the hallway track. This is a feature, not a bug. It means that the people who are watching your talk _really_ want to be there.

How to give your idea the best chance

If you are the developer of an open source project, we want to hear from you! But, please note this is a single track event and we need the material to appeal to a broad audience.

How to give your idea the best chance

Allow your enthusiasm to shine through. Please tell us why you're excited to present.

A short introduction is good. Generally, no introduction is better.

Finish the code before starting the proposal. You should talk about things that you've learned, not about software that you hope to write between now and August.

Think of your audience first. Every presentation must add to the experience.

Do not think of Rust Forge 2025 as a chance to provide an advertorial or infomercial. Instead, try to think of an opportunity to share what you've learned. You should make sure that your talk is something that you would want to listen to if you were not employed by your company, or didn't work.

Intended audience

The conference will appeal most to software developers who interested in the Rust programming language.

Rust Forge is physically located in New Zealand as part of the Asia Pacific region.

As Rust is not a predominant language in Australia and New Zealand, the conference is likely to draw a large contingent of people who are not experienced in the language. Their interests will be in ensuring that they can gain knowledge about something that is becoming more important globally.

Rust Forge is not a conference to talk about the development of the the programming language itself. That's a job for Rust Conf.

Selection criteria

The programme will be developed to create a cohesive whole. In general, we are looking to create sessions of 2-4 talks, followed by a group discussion with all of the speakers from that session.

• Completeness.The proposal is well written and demonstrates
• Thoughtfulness.The proposal demonstrates that they have the target audience in mind.
• Longevity.The topic in the proposal is likely to be relevant to Rust programmers, and people considering , for a long time.

Other questions you'll be asked

• Would you like to have comments enabled on the YouTube recording? We will default to disabling comments.

Extension possibilities

All submitters will be invited to provide

• Podcast interview. All submitters will be invited to record an interview on the Compose
• Event for students and early-career (tentative)
• Group discussion
• Session mentorship programme
• Peer-review. Will you be willing to provide some notes to speakers about their talk? Perhaps you would