New for 2024: 1/2-day deep dives / hands-on labs!
PowerShell and DevOps Global Summit presentations are intense and intimate, often with plenty of audience interaction. You must expect questions and discussions. These sessions are not a “lecture to the audience” event.
We look for a compelling abstract that makes us want to see your session - so spend time writing a great abstract! We want real-world usability sessions combined with “WOW, nobody talks about THAT” awesomeness. We want to see the code. Don’t just talk about it - this is a PowerShell summit, not a PowerPoint Summit. If your session isn’t predominately demonstrations, it’s probably unsuitable for the Summit.
Based on community feedback, we’re continuing to expand the scope of our content. While OnRamp will care for those new to the PowerShell/DevOps world, we’re looking to fill the gaps with intermediate content to the master level.
If you have any doubts about the suitability of a particular session, please get in touch with us at email@example.com - we’re always happy to discuss proposed sessions.
Please note: all sessions are to be delivered in English. The presenter will provide all equipment needed for the session(s), including a laptop or computer. The presenter must be able to connect to an HDMI connection; VGA is NOT supported. The presenter must be able to select an appropriate screen resolution for video output manually.
We are open to presentations across the entire ecosystem built around PowerShell or the various DevOps tools. This includes Microsoft platforms and products with PowerShell-based management tools and third-party products. New topics will be preferred over the recycling of older topics. However, we are still open to sessions on ‘older’ topics addressing new features or clarifying confusion or uncertainty.
We have three different session lengths available this year.
Increase your chance of being accepted!
Spend time thinking about and planning out your abstract, outline, and logical order of topics presented. Consider how to make sure that your session fits in the allotted time. Total content for a 45-minute session should run 35-40 minutes and include time for Q&A without bleeding into the next session, and total content for a 90-minute session should run 70-75 mins plus Q&A.
Do not be afraid to submit multiple sessions. We LOVE to have as many candidates as possible, as it gives us a selection and allows us to select as many unique speakers as possible. Hot topics can have multiple submitted presentations - if we like two submissions on the same topic with different spins. Alternatively, if both submitters have equally good second topics, we’d select one subject from each AND get two great issues instead of one.
Unique topics and topics that appeal to a diverse audience are included. We understand that cloud computing is hot, but we prefer topics that appeal to a larger audience vs. a niche audience. That isn’t to say that your session on your cloud provider of choice isn’t going to make it, but you increase your chances with a topic that would appeal to users of all cloud providers vs. a case only focused on one cloud provider.
Internet connectivity is available in the conference center, but bandwidth is limited. If you rely on connecting to the cloud for your sessions, consider recording any demonstrations as a contingency.
Presenting a session
Presenters must commit to being in person during their session time. We will ask you to save to present shortly after selecting your presentation. No sessions will be presented virtually.
Please read: Selected Speakers will receive an honorarium at a valuation of $500 for a 45-minute session, $1,000 for a double session, and $2,000 for a workshop to assist with traveling and accommodation expenses. All US-based speakers must provide a W9 before the event.
The honorarium will be split evenly between the two speakers if you have a co-presenter.
Speakers may elect to donate their honorarium to a non-profit of their choice, including the DevOps Collective. Details will be included in speaker communications.