There are three ways to propose a session:

1. A proposal for a talk/panel during the conference part : these are 30 minutes slots that will have all people's full attention as everybody will be in the one room.
2. 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) also presented to all attendees in one room.
3. Openspace session: even without a prepared presentation we welcome the discussion and interaction by having people propose a session on the fly during the openspace opening. Check the openspace format 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 tell, we want to hear everbody's voice. If you've presented a 30-minute talks at any Devopsdays in the last 2 years, we encourage you to submit an ignite talk or conduct an openspace session. In addition, please consider encourage other speakers to submit proposals!
• no vendor pitches: as much as we value vendors and sponsors, we just don't think this is the right forum. There is a demo openspace slot where you have 5 minutes to show products.

Some suggestions to get you thinking:

• Reports from the frontlines: what worked (and didn't) while implementing Devops in your organization?
• Devops at scale / in the Enterprise
• Applying Devops principles beyond the tech organization (e.g., HR, Finance, etc.)
• Devops, Lean, Agile: what's shared and what's unique?
• And of course any other topic in the realm of Devops

How to make a proposal: Send an email to [[email protected]] with the following information:

1. Proposal working title (can be changed later)
2. Type (presentation, panel discussion, moderated general discussion, debate, etc.,ignite)
3. Description or abstract

Rules:

• 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
• Nominations welcome... if you know someone who has content/experience relevant to the DevOps conversation, please point us in their direction!
• No tool talks if tools are not open-source or generally commerically available
• Multiple proposals welcome... just follow the other rules