SPEAKER RESOURCES

Session formats & proposals

Shape a session that fits your audience and delivers a clear outcome.

PRACTICAL SPEAKER GUIDE

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

01

Choose the right format

A conference talk is best for an argument, case study, or research finding. A workshop is best when participants should leave with a skill. A panel works when differing perspectives matter; a demonstration works when showing a tool in action is central. The programming team will confirm final formats and durations.

Practical example / takeaway

Example: β€œHow a Canadian organization migrated a service to Linux” suits a case-study talk; β€œDeploy your first container” suits a workshop.

02

Write a useful session abstract

In 100–200 words, describe the problem, who should attend, what you will demonstrate or explain, and two or three takeaways. Avoid an abstract that reads like a product advertisement. State prerequisites honestly, especially for hands-on sessions.

Practical example / takeaway

Example: β€œParticipants will learn how to identify software dependencies, evaluate migration risks, and plan a staged Linux pilot.”

03

Match the audience

Open Source Week brings together developers, system administrators, researchers, students, business leaders, public-sector teams, and newcomers. Define whether your session is introductory, intermediate, or advanced. Explain specialist terms on first use and show why the topic matters beyond your own organization.

Practical example / takeaway

For mixed audiences, begin with a short plain-language explanation, then move into technical detail.

04

Design for discussion

Reserve time for questions and audience interaction. For panels, agree on a moderator, central questions, and balanced perspectives in advance. For workshops, use checkpoints so participants who fall behind can rejoin. For demos, have a backup recording or screenshots.

Practical example / takeaway

A strong session finishes with a summary of what participants can do next.

05

What to send the programming team

Prepare a working title, concise abstract, intended audience, level, preferred format, proposed language, speaker names, and any unusual room or equipment needs. These are preparation recommendations, not an announced submission deadline.

Practical example / takeaway

Do not assume your preferred duration or equipment is confirmed until the organizing team agrees.

Continue preparing

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

Speaker Centre β†’