2016 Salt Lake City DevOps Days Speaker Proposals
Call for proposals is closed!
Call for proposals closed April 19th.
Selected proposals will be announced on May 3rd.
There are three ways to propose a session:
- A proposal for a talk/panel during the conference part : these are 30 minute slots that will have the full attention of all attendees, as everybody will be in that one room.
- An Ignite talk that will be presented during the Ignite sessions. These are 5 minutes slots with slides changing every 15 seconds (20 slides total) which are also presented to all attendees in one room
- Open Space session : even without a prepared presentation we welcome the discussion and interaction by having people propose a session on the fly during Open Space. Check the Open Space explanation for more information.
Even if you don’t propose, please consider commenting on proposals submitted by others
Our main criteria to make it to the top selection are:
- original content: content not yet presented at other conferences, or a new angle to an existing problem
- new presenters: people who are new to the space and have insightful stuff to say; we want to hear everybody’s voice
- no vendor pitches: as much as we value vendors and sponsors, we just don’t think this is the right forum. You can demo at your table or during Open Space.
How to submit a proposal: Send an email to [firstname.lastname@example.org ] with the following information
- Proposal working title (can be changed later)
- Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
- Description or abstract
- Be specific… we aren’t mind readers (a description of about 20 lines is about right)
- Detail is good… but not as important as explaining why your proposal would be interesting
- Propose your own talk; don’t have someone else do it for you.
- Nominations welcome… if you know someone who has content/experience relevant to the DevOps conversation, please point us in their direction!
- Multiple proposals welcome… just follow the other rules
- Making the Journey from Agile to Continuous Delivery Utilizing DevOps Practices – Carmen DeArdo
- Continuous Integration May Have Negative Effects – Yegor Bugayenko
- Using Git in Surprising Ways – Kristen Hunter
- DevOps Means Never Having To Say You’re Sorry – Matt Stratton
- DevOps is not a development methodology or technology; DevOps is an ideology. – Seth Vargo
- No more waterfall deployments – using feature flags to expand DevOps organization wide – Edith Harbaugh
- Watch Everything, Watch Anything: Anomaly Detection using InfluxData’s Kapacitor – Nathaniel Cook
- Tyranny of the Minimum Viable Product (MVP) – G Waldo
- Misconceptions of Automation – G Waldo
- Fear and Loathing in Systems Administration – G Waldo
- I don’t belong here – Working through impostor syndrome – Jake Champlin
- Continuous Delivery in the Application Economy – Burt Klein
- What does DevOps Mean to an AdTech Company – Mason Leung
- Stop Running with Sharp Metrics – Julia Wester
- Jumping off the hampster wheel with Kanban – Julia Wester
- Why SaaS? – Brandon Gillespie
- Security Automation in a DevOps World – Alan Robertson
- Behind Closed Doors: Managing Passwords in a Dangerous World – Noah Kantrowitz
- 2016 Speaker Proposal: Fail Proof Ways to Run Beautiful Tests Regardless Of Browser Choice – Kevin Berg
- Your own Private Heroku using Convox – Drew Bowman
- Automation and Autonomous systems, or why we orchestrate Kubernetes with SaltStack – Yaroslav Molochko
- GitHub and Docker like Peanut Butter and Jelly – Lee Faus
- Getting along with your DB Ops team – Nick Demaster
- Dealing with a different kind of scale – Nick Demaster
- The Platform Business: How Cloud Foundry Facilitates Cloud Native Transformation – David Gardner
- An ElasticSearch Cluster Named George Armstrong Custer – Will Button