SPEAKER RESOURCES

Speaker profiles & promotion

Help attendees discover your session with accurate, respectful public information.

PRACTICAL SPEAKER GUIDE

This guidance helps you prepare. Final program decisions and individual arrangements are confirmed by the Open Source Week organizing team.

01

Write a concise biography

A short biography should explain who you are, what you work on, and why your experience matters to this session. Aim for a few sentences in third person. Prioritize your current role and relevant work over a long list of past positions.

Practical example / takeaway

Example: β€œAlex Chen is an infrastructure engineer who helps public institutions operate open-source systems. Their work focuses on Linux reliability, automation, and practical training.”

02

Choose a suitable photograph

Use a recent, clear head-and-shoulders image with a simple background and permission to publish. Avoid screenshots, watermarks, and photos of groups. Supply the photographer credit if required.

Practical example / takeaway

The organizing team will provide final size and format specifications.

03

Create a session description

Write a public title and a short description that state the benefit to attendees. Avoid unsupported superlatives or vague promises. Specify the intended level and any software prerequisites.

Practical example / takeaway

A good title is specific: β€œWhat we learned migrating a municipal service to Linux.”

04

Coordinate organizational affiliation

Check the spelling of names, job titles, company or university affiliations, and project names. Only provide partner logos when you are authorized to use them. Being a speaker does not automatically mean your employer sponsors or endorses the event.

Practical example / takeaway

Ask for approval when speaking in a personal capacity versus representing an organization.

05

Share the event responsibly

Once the organizers confirm your session and provide an official listing, share that listing rather than inventing a time or room. Use approved Open Source Week graphics and preserve the supplied logos.

Practical example / takeaway

Suggested message: β€œI’m looking forward to discussing [topic] at Open Source Week 2027 in Saskatoon. Details: [official link].”

06

Respect publication and privacy

Confirm which biography, photograph, social links, and presentation materials may be published. Do not include personal phone numbers or other private contact information without consent.

Practical example / takeaway

Tell the team if your profile needs correction or if you have a preferred professional link.

Continue preparing

Explore the other speaker guides or return to the main centre.

Speaker Centre β†’