This year our theme statement is "Change is in our bones!" Like last year, the format will be smaller and more intimate than our years at the UT stadium, and focused on interaction and reflection.
Continuing from last year's format, talks will be 20 minutes on what speakers have learned going through periods of change, whether intense and unexpected or deliberate and thoughtfully planned.
If this isn't what you're looking for, we will also have Ignite talks - 5 minute 20 slide talks, where the slides automatically advance every 30 seconds. We are also accepting proposals for 90-minute workshops.
We will emphasize Open Spaces in the conference schedule, and maintain special focus on sharing each others' journeys, questions, and learning.
We have a couple of notes for our prospective speakers. Please take a moment and read the following before submitting your response: A/V and Tech Check notes.
We will have Office Hours for 2023 talks Wednesdays at 1 pm CDT (at the link that will be sent to you confirming your submission) till April 12th, 2023. If you would like to attend Office hours to polish your CFP before submitting it, please email email@example.com, and we will send you an invite with a zoom link.
The Call for Proposals is your chance to take a more active part in the DevOpsDays Austin conference and place your mark on the Austin DevOps community. We encourage a wide range of original material, focusing on new and local presenters.
What kind of proposals are we looking for?
What do the organizers what you to know before submitting a talk?
What should I include (or not include) in my proposal?
The kind of talk best received at DevOpsDays Austin is the real-world experience talk, and that's what we're looking for this year. We experienced change X; we did Y to address it, here’s how that turned out, both the good and the bad. Sometimes people feel they should dilute their experience and turn it into a more generic presentation. This almost always makes for a weaker submission. Genuine implementations and personal lessons learned are what our audience has consistently found the most compelling.
Make it personal, we care to learn about you and from you.
Write about changes you have experienced or implemented in any area we talk about in the DevOps community - culture, process, technology, tooling, sharing... How did changes affect other areas of your business? What wisdom can you share with your community, and what can you build on in this current period of uncertainty and change?
We want to thank DevOpsDays KC and DC for the inspiration for this CFP, like in the DevOps spirit we took something that worked well and iterated on it for the Austin Community!